October 30, 2006 at 2:04 pm
Help! We changed our service accounts (SQL and agent) to a new domain account without any issues. There are some jobs that call DTS packages, however, that are still showing as being executed as the old service account. I can not find any place where the old service account is still referenced, but since the old account doesn't even have a login, the job fails with a 'login failed for domain\old_account'.
Jobs that do not call DTS packages are not having this problem. They execute as the new service account.
Any ideas?
TIA for any help.
October 30, 2006 at 2:25 pm
Hello,
In order to bring all the DTS related jobs under the new service account, you need to log into the box with the specified new service account, then open the existing DTS package and then save as, so that it changes the ownership of the DTS packages. You can delete the old DTS after verifying them.
Hope this helps.
Thanks
Lucky
October 30, 2006 at 4:41 pm
No help there, Lucky, but thanks anyway.
It turned out to be the Proxy account. It was still set to the old domain account. The reason I didn't look there was that even when I changed the job owner to be SA, it would run under the old account. That is strange, since BOL states that the proxy account will only be used by NON-SA accounts using cmdexec. Hmmm.
October 31, 2006 at 2:57 pm
DTS packages wraps account with themselves. After an account is changed, the packages may not change accordingly. As a result, it is not recommended to use DTS in my company unless necessary. Even so, we require owners keep their copies. Wierd!
I am very interested if anyone has a solution for your problem.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply