May 10, 2010 at 12:47 pm
I created a credential based on a windows user that has sysadmin role, then created a proxy to map this credential. I setup a sql job and try to run it manually but I get this error msg. Any ideas how to work this around. I'm not sure why this is not running as the windows user has already sysadmin role privilege and it's mapped to a credential and proxy. Thanks.
Message Executed as user: domain\sqluser. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:39:00 AM Could not load package "\ssispackage" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80040E4D (Login failed for user 'domain\sqluser'.). The SQL statement that was issued has failed.
May 10, 2010 at 3:21 pm
Is your domain really called 'domain'?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
May 10, 2010 at 11:40 pm
No
May 12, 2010 at 7:14 am
This is an obscure bit of information that I always seem to forget with proxys. The SQL Agent account that runs the job will have a Temp folder. The proxy needs Read/Write to that folder.
http://support.microsoft.com/kb/933835
Third paragraph in the More Information section.
Hope this helps
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
May 12, 2010 at 9:27 am
That is such a good tidbit I have saved it for later use...
CEWII
May 12, 2010 at 10:03 am
Glad I could I help. It drove me nuts when I ran into it.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
February 3, 2011 at 7:04 am
Hi,
I put the Read & Write permissions to the Temp directory of SQL Server Agent Service Startup account. But I am still getting the same error.
Could anyone please help me with this issue?
August 2, 2011 at 2:06 pm
I ran into this issue...
'the loadfromsqlserver method has encountered ole db error code 0x80040e4d (login failed for user'
because my generic proxy could not 'read' the SSIS package. I added the proxy to the db_ssisoperator role and initial tests show that this may have worked (more issues to resolve). It wasn't a read issue with the source database but a read issue with the package itself.
I don't know if this follows best practices, just working my way through this but hope this may help someone.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply