Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Logon failure: unknown user name or bad password Expand / Collapse
Author
Message
Posted Wednesday, September 22, 2010 1:22 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 1, 2012 11:46 AM
Points: 4, Visits: 17
My issue was trying to have a DTS package connect to two remote databases and transfer data between the two of them (not on the server running the package). Before setting up a proxy, I would get errors when the job tried to run under the local server system account, which of course, has no privileges on any other server.

I followed all the steps to create a proxy account for a domain user with a password that does not expire. I still got the error: I would get the logon failure message.

After reading the last poster's message, I realized (thank you) that I had failed to go into the credential to change the password to the domain user account.

Resetting the password indeed works.

The SQL for creating a credential is as follows (got this from "How to Schedule and run a SSIS package (DTS) Job in SQL Server 2005." on CodeProject.com by hong wei li):

USE master
GO

CREATE CREDENTIAL [SSISExecCredential] WITH IDENTITY = domain\username', SECRET = 'WindowLoginPassword'
USE msdb
GO

sp_add_proxy @proxy_name = 'SSISExecProxy', @credential_name = 'SSISExecCredential'
GO
sp_grant_login_to_proxy @login_name = 'ssisexec', @proxy_name = 'SSISExecProxy'
GO
sp_grant_proxy_to_subsystem @proxy_name = 'SSISExecProxy', @subsystem_name = 'SSIS'
GO

Note that you can use any proxy name, credential name and user name you want. The choices above were just easy for me to implement and track.
Post #991512
Posted Wednesday, December 21, 2011 3:56 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, December 21, 2011 3:55 PM
Points: 73, Visits: 145
This happened to me as well, and it happened because the AD password changed.
By going into Enterprise Manager > Server > Security > Credentials, and opening up the proxy account name and updating the password, these Jobs worked again.
Post #1225478
Posted Thursday, December 6, 2012 10:57 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, July 20, 2014 7:16 AM
Points: 945, Visits: 1,769
I know this is an old post but needed to update. i just experienced this same error (only on 2008) and changing to the local system account for the agent service resolved the issue.


For faster help in answering any problems Please read How to post data/code on a forum to get the best help - Jeff Moden for the best way to ask your question.

For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw

Need to Split some strings? Jeff Moden's DelimitedSplit8K
Jeff Moden's Cross tab and Pivots Part 1
Jeff Moden's Cross tab and Pivots Part 2

Jeremy Oursler
Post #1393653
Posted Wednesday, July 10, 2013 1:36 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 3:44 AM
Points: 179, Visits: 331
I have the same problem -

Unable to start execution of step 1 (reason: Error authenticating proxy Domain\WindowsID, system error: Logon failure: unknown user name or bad password.). The step failed.

> Have tried changing the password, but did not resolve the error
> The indivual package is runing fine using multiple user IDs outside the SQL job
> I am using a proxy with credential of the ID having access and who is able to execute the package outside the Agent Job
> Have provided sa priviledge to the agent service account

Please help.


Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
Post #1471986
Posted Wednesday, July 10, 2013 3:12 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 3:44 AM
Points: 179, Visits: 331
Additionally, changing to local system account is out of scope for me.

Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
Post #1472016
Posted Wednesday, July 10, 2013 8:21 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, August 13, 2013 9:44 AM
Points: 627, Visits: 509
Not sure what the SSIS is doing inside, But many times people forget that if there are other OLEDB conenctions and and you are accessing other server and databasese then your SQL agent need to have access to that server and DB.
Also, it can be a fire wall issues like in our work environment we have a something called NetSeg, two server cannot communicate if one is outside of NetSeg and other is inside.

Alos, Check if your are usning any password in SSIS and if the SSIS is password protected. This usually creates an issue while running in job.
Error message would be helpful.
Post #1472179
Posted Sunday, July 14, 2013 10:08 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 3:44 AM
Points: 179, Visits: 331
Just to re-cap....the issue is as follows -
> I have a SSIS package which connects to multiple servers
> It executes properly when directly executed from the dtsx file (double click -> execute)
> I have created a credential and a proxy on an instance (enterprise edition)
> I have created a job to execute the SSIS package using the proxy
> The job has a output log file
> I have tried both scheduling and directly executing the job, but it fails before starting with the following error - "Unable to start execution of step 1 (reason: Error authenticating proxy <Domain>\<WindowsID>, system error: Logon failure: unknown user name or bad password.). The step failed."

> Have tried changing the password, but did not resolve the error
> The indivual package is runing fine using multiple user IDs outside the SQL job
> I am using a proxy with credential of the ID having access and who is able to execute the package outside the Agent Job
> Have provided sa priviledge to the agent service account
> Additionally, changing to local system account is out of scope for me.


Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
Post #1473366
Posted Thursday, August 8, 2013 2:36 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 8, 2013 2:27 PM
Points: 7, Visits: 146
Just in case others have gotten here for the same reason. Make sure that the account your proxy/credential is using is a user in its default database in SQL Security.

We went through all the other suggestions and until we did this, for some reason that was causing it to pass a Null SID when it was trying to authenticate to AD.
Post #1482578
Posted Tuesday, March 4, 2014 7:43 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 30, 2014 12:04 AM
Points: 1, Visits: 1
Hello

We have a SQL 2012 which runs on a Windows 2012 Server in domain 1

The Problem is:

We like to use the SQL Agent, to backup over a script, all our Print Server which are in domain 2

The Script looks as follows.

c:\windows\System32\Spool\Tools\Printbrm.exe -s \\Servername.domain.XY -b -f c:\temp\Printer_Servername.printerExport

The Script itself works perfectly, when I run the script over cmlet "cmd" with a user in domain 2
- run as ----

Our SQL Server is not in the same Domain as the Printer server but we have a one way trust between them.

Anyway... every time when we run the job, we get a failure like:

Message
Unable to start execution of step 1 (reason: Error authenticating proxy domain2\admin, system error: The user name or password is incorrect.). The step failed.

We added the same user on SQL Credentials which we used when we run the script as a run as account in cmlet.

Then we added a Proxy with that account and set all the subsystem on that User without success.

Any Ideas why we get an error "The user name or password is incorrect"

Thanks for help
sb

Post #1547338
Posted Friday, April 4, 2014 3:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, April 4, 2014 3:55 AM
Points: 1, Visits: 7
Hi,

I can concur regarding this being caused by the SQLAgent service account being configured with a domain account. Impersonation may well solve this but to work around the issue for now I have set the SQLAgent to run as Local System and my package is now executing on schedule.

Brian
Post #1558417
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse