July 16, 2024 at 12:13 am
Hi,
We are migrating from SQL 2000 to SQL 2017.
As a first step, we are migrating to sql 2008r2.
We have dts packages running on the 2000 box. I copied the dts packages to sql 2008r2 server by copying the msdb table.
The dts packages are executing using the sql jobs. The jobs are failing showing as below
Executed as user servername\system. DTS Run: Loading: Provider Error:18456 (4818). Error string: Login failed for the user domain name \computernsme. Error source: Microsoft OLEDB provider for sql server
I tried creating the new login with that computer name & provided sysadmin permission but the issue didn’t resolve. SQL & agent are ruining as local system. NT Authority \system has sys admin permission.
Any suggestions/help will be appreciated
Thanks,
July 16, 2024 at 3:58 pm
The job runs as a particular login. Change the login under which the job runs.
July 16, 2024 at 7:12 pm
The login that running the job is sysadmin on sql server. It is showing login failed as domain\machine$. This domain \machine also already sysadmin in SQL server.
Tried creating the proxy but still same issue
July 19, 2024 at 5:36 pm
I noticed the job is executing the below command in CmdExec subsystem.
DTSRn / ~ Z z0xfx….
Seems /~Z means it is encrypted. How can we identify the dts package name in the job is executing, if the job doesn’t have description. I tried using/!X /!C as suggested in some other post. This didn’t help me
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply