Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Logon failure: unknown user name or bad password


Logon failure: unknown user name or bad password

Author
Message
andy-463940
andy-463940
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 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.
Jason Wisdom-380639
Jason Wisdom-380639
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 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.
CapnHector
CapnHector
SSC Eights!
SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)SSC Eights! (917 reputation)

Group: General Forum Members
Points: 917 Visits: 1789
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
Chandrachurh Ghosh
Chandrachurh Ghosh
SSC Veteran
SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)

Group: General Forum Members
Points: 203 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.
Chandrachurh Ghosh
Chandrachurh Ghosh
SSC Veteran
SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)

Group: General Forum Members
Points: 203 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.
SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
Say Hey Kid
Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)Say Hey Kid (665 reputation)

Group: General Forum Members
Points: 665 Visits: 513
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.
Chandrachurh Ghosh
Chandrachurh Ghosh
SSC Veteran
SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)SSC Veteran (203 reputation)

Group: General Forum Members
Points: 203 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.
T Childers
T Childers
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 151
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.
sboehler
sboehler
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 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
Brian Christie
Brian Christie
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search