February 12, 2004 at 10:38 am
February 13, 2004 at 9:35 am
February 14, 2004 at 6:45 pm
I had some theories as to what might have happened. What did you do to fix it?
Russel Loski, MCSD
Russel Loski, MCSE Business Intelligence, Data Platform
February 15, 2004 at 5:51 pm
Discovered that scheduled JOBs are run by Windows SQLSERVERAGENT service.
This service can be set to to act like a domain-user with its own (startup) userID and password.
We have now applied for SQLSERVERAGENT (user ID) to be given access permission on the domain\server where our source data is held - password not to expire.
We believe this should solve the problem.
Regards,
Ian.
February 15, 2004 at 6:37 pm
PS.......
Before discovering SQLSERVERAGENT there was confusion supreme as the JOB failed because I don't have CmdExec permission and when the Administrator set up the JOB, it failed with "connection error" and we thought it was because the Administrator doesn't have access to the other domain\server.
Further to this I suddenly realised that my remote logon is not the same as my logon for the other domain\server.
TechTeam.com pointed me in the right direction.
Ian.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply