February 22, 2016 at 10:08 am
scotdg (2/22/2016)
So I wasn't able to change the account until this morning. I changed the account to use my credentials as I did on the QA machine while testing. As expected I got the same result.So I have tried the following (the package runs in every circumstance on the QA machine):
I created proxy using my account
I changed the SQL Server Agent Service account login (for trying to run as a job)
I changed the SQL Server Service (for trying to run as a SP)
I checked all of the SQL login permissions for my account and the local system account
I ran a trace on the jobs and did not see any code being executed related to the package being run
I checked the XML of the package and there is no reference to any other server
I tried using a configuration file
I tried changing the connections string provider from SQLNCLI.1 to SQLOLEDB.1 and back again
The package is on the same machine as the database
OK. And what were the results? Or is this now resolved?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
February 22, 2016 at 11:19 am
Same result.
February 26, 2016 at 11:42 am
Problem is resolved. I had changed the server name to the server\instance name at some point and it didn't work. After trying the BCP utility and receiving similar errors I added the -S option with the server\instance name and it worked. I then went back into my job and changed my connection string again to the same and it worked. I found out that when setting up another job that the server on the general tab also needs to be set to the server\instance. I must have not had them both set that way at the same time.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply