April 4, 2006 at 5:03 am
SQL Server 2000 SP3. When the database was running on Windows 2000 Server, I set up a job to run a DTS package which called a number of other DTS packages, as well as running an number of Execute SQL tasks. With an eye to the future I set up all the connections using the DNS name of the server, so that if we ever moved servers I'd only have to change the DNS once. We moved to another Windows 2000 machine without problems. However now the database has been moved again to a Windows 2003 SP1 machine and the domain has been migrated to Windows 2003, the job fails with messages that Login failed for user '(null)'. After a lot of banging my head against a brick wall I've found that I can get the job to run by going through all the connections and changing the server from the DNS name back to the server name. Although I'm happy that I can now schedule the job overnight, this seems like a retrograde step and I have a nagging feeling that I've done something wrong. Can anyone give me any pointers?
--
Scott
April 4, 2006 at 8:59 am
Login failed is a different message than the name resolution. It means the context of the package execution is running under a local or non-network account.
I suspect that you resetting the connection has somehow fixed the account issue. Check and be sure that your accounts setup in the connections are valid. I might try changing them back and seeing if that works.
April 4, 2006 at 9:23 am
All the connections are (and always have been) set to Windows authentication and the server is set to mixed mode. All I did was paste the server name over the DNS name. Changing the name back to the DNS entry sounds like a good idea, but I must admit that I'm loath to touch any of it now that it's working and I don't have to log in every night just before going to bed to kick off the package. I think I will treat myself to a night off and have another look at it tomorrow.
--
Scott
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply