May 4, 2009 at 11:35 pm
Dear Experts,
Please find the below issue. The SQL job executes SSIS package, which flows data from one - one server. It was working well and good last 10days. But suddenly we noticed the data isnot being imported to the server and checked the history of job. I noticed below error:
Please help me ASAP to fix this issue......
Unable to start execution of step 1 (reason: Error authenticating proxy kwcpwc\datasystm, system error: Logon failure: unknown user name or bad password.). The step failed.
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 5, 2009 at 1:05 am
Hello,
As your Job was previously working Okay I was just wondering if the password has just been changed for kwcpwc\datasystm? If not, it may also be worth checking that the account has not been locked-out.
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
May 5, 2009 at 1:09 am
Thanks for the post Marsh,
But with that accout other JOBs are working fine and well. Am totally confused why is this not working ?
Done lots of troubleshooting and still, its not yet resolved.
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 5, 2009 at 1:41 am
Hello again,
In that case I would guess it is a permission on a specific resource that the kwcpwc\datasystm account is missing. As you mentioned that the job was working well previously, what has changed in the meantime? For example has a Windows Administrator tightened security on one of the servers involved, or does the job now read or write to a different file or folder (e.g. because of the recent change in month), have any security patches just been applied?
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
May 5, 2009 at 1:49 am
Hello Marsh,
Yes i believe the same too.. About the security updates, but the only update done is towards Windows level and its not that much related to SQL server.
Will that WIN2k3 update effect the SQL accounts and so and so issues also ?
Cheers,
- Win
"Dont Judge a Book by its Cover"
May 5, 2009 at 2:25 am
Hello,
Naturally I don’t know what your SSIS package is doing, but if it needs access to any Windows Resources then an OS security update may well affect it.
Assuming that your SSIS package contains multiple steps, then you might try adding logging to it and then you could identify exactly where the error occurs.
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply