SQL Clone
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
ljackson-498535
ljackson-498535
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 38
Hi, I'm completely lost here... I have a SQL Server Agent job that execute a SSIS package. The same job works perfectly at on SQL server but errored out at the other with the "system error: Logon failure: unknown user name or bad password". As far as I can tell, both are setup the same. Here is my setup:

1. Create a credential AccountName to use the credential of a domain account (domain\AccountName).
2. Create a proxy AccountName that utilize the credential created from step 1.
3. In the "Run As" of the SQL Server Agent job step, use the proxy created from step 2.

When I executed the SQL Server Agent job, it prompted failed at one server with this unknown user name or bad password message. I know for sure that the user exists and the password is correct. It failed "before" executing the package. It acts like the SQL Server Agent Service account is unable to use the security context of the proxy account. As I said, the same job works fine at another server. The problem is I cannot find why. The account is sysadmin at both SQL Servers.

Could someone shed some light? Thank.s
SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1496 Visits: 565
Hey can you post the exact error that you receive while executing the job.

I used to have the same kind of issue .......it used to say ...teh file cannot be found and XML node an dpassword something.........

One thing make sure that on the server that fails, sql agent ( under which the jobs run) have all the rights that it needs to perform in SSIS.
ALos, make sure all the objects that SSIS is using u have on the server, and also enough permissions to do the work for sql agent.

My case was. one of the objcet was missing, and before runnning the job, it was trying to validate things, and thrwoing errors before executing the ssis.
Other time, sqlagebt had no enough permission to delete and archive files........

this was one of my error and if u look at the error it talks all about something............

Executed as user: ADHCSCINT\sqlagt. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:03:20 PM Error: 2008-10-16 16:03:20.68 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTSTongueassword" with error 0x80070002 "The system cannot find the file specified.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-10-16 16:03:28.10 Code: 0xC002F304 Source: Rename and Archive flat file File System Task Description: An error occurred with the following error message: "Access to the path is denied.". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:03:20 PM Finished: 4:03:28 PM Elapsed: 7.547 seconds. The package execution failed. The step failed.


but the actual solution was to give enough rights to sqlagent to move, rename and delete files.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)

Group: General Forum Members
Points: 50964 Visits: 17653
if running under a sql agent job as sql agent (i.e. a user other than the user who created the project) this is well known. How does the sql agent run the job sucessfully on the other server?
are you using xml config file, server roles\etc, registry or environment variables?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
ljackson-498535
ljackson-498535
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 38
There was not much message to the error. Here it is:

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

If I should look at some other places for messages, please let me know...

This proxy account (SDRGE\svcBOKPosPay) is sysadmin on SQL Server database level. It also belongs to administrators group on the server level. So I don't know what else it might need...

The process is setup basically the same. Same SSIS package, same procedure to create all the steps, etc. The proxy account actually has less privilege on the other server that succeeds as it is not a admistrator group member on the server.

I am completely lost... Only thing I can say is that the setup somwhere along the way is different between the two servers, but I cannot figure out where and what...
SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1496 Visits: 565
Looks like the issue is Proxcy Account.
I had the same issue for sql agent. My DBA was able to figure out the problem. Though they belong to adminstrator group, there might be some explicit kind of some deny permission. One step you can do if possible is Give all th ehighest level of permission, and slowley test each time by removing few permiisons. Or make both the environment exactly the same...........
ljackson-498535
ljackson-498535
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 38
Um. I am not sure what "Give all th ehighest level of permission".. What else can I give? Thanks.
anvie
anvie
Old Hand
Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)Old Hand (386 reputation)

Group: General Forum Members
Points: 386 Visits: 110
I am having the same problem.

This syntax runs fine with my other SQL server except for my newly installed SQL server. I check all the permission and they all the same.

EXEC master..xp_cmdshell 'MKDIR Servername\test'

Error:

Logon failure: unknown user name or bad password.

Please help...
patr
patr
SSC Veteran
SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)SSC Veteran (252 reputation)

Group: General Forum Members
Points: 252 Visits: 149
I am also facing the same issue...but my scenario is little bit funny .....the sql server job is running some few days back perfectly but the same job with the same priveleges without changing any information.........it is not working now ......


am completely lost .......please help me out this problem....


the error am getting is .....



Error authenticating proxy.system error: invalid logon bad username or password
crackpundare
crackpundare
Grasshopper
Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)

Group: General Forum Members
Points: 21 Visits: 50
On the machine where it does not work, you are probably running the SQL Agent as a user which is not the default "Local System Account", and on the machine where it DOES work, you are running Agent as local system, right?

I just fixed this by going back to local system for Agent and running steps with proxies when needed. It seems like the domain service account we used for running Agent is not allowed to impersonate the proxy, but the local system account is.

Probably also solvable by allowing the domain service account to delegate.
SUBRAHMANYA HEDGE
SUBRAHMANYA HEDGE
SSC-Addicted
SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)SSC-Addicted (461 reputation)

Group: General Forum Members
Points: 461 Visits: 406
Hi Friends,

I got same problem today for one of our job after resetting password of a windows account. This job to run SSIS package was running fine till we changed the password. After resetting the password we got following error:

Unable to start execution of step 2 (reason: Error authenticating proxy REDMOND\***ADMIN, system error: Logon failure: unknown user name or bad password.).

I never used Proxy before. After some googling & trial & error, we tried changing the password of respective 'credential' [Security -> Credential] of this proxy. :-) It worked for us.

Hope my experience helps someone else !!!
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