Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hismightiness
Posting Yak Master
164 Posts |
Posted - 2004-09-16 : 09:31:33
|
quote: SQL Server Scheduled Job 'SpecialOrdersExport' (0xE992FEB7886FAC49AD20C2CAF0FAC388) - Status: Failed - Invoked on: 2004-09-16 09:23:33 - Message: The job failed. Unable to determine if the owner (DOMAIN\USER) of job SpecialOrdersExport has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\USER'. [SQLSTATE 42000] (Error 8198)).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am trying to get a table to export to an Access DB on another server in our network. When I just perform the export manually, it works fine. However, if I choose to schedule it to occur at regular intervals on its own, it doesn't. I am fairly certain this is because it is exporting it on my behalf since I am logged on to windows. How can I have the SQL Server perform this job successfully on its own?- - - -- Will -- - - -http://www.servicerank.com/ |
|
|
syedrehman
Starting Member
7 Posts |
Posted - 2004-09-16 : 14:22:47
|
| Add a login/user to SQL Server that is either a domain admin on your network or has those privileges. Then pull up the properties on the scheduled task in question. About halfway down the main tab is an "owner" drop down list. Change the owner to the login/user you added. Test the job by right-clicking and selecting "Start Job". This way you will know if your changes are working. |
 |
|
|
hismightiness
Posting Yak Master
164 Posts |
Posted - 2004-09-16 : 16:44:21
|
| I have admin rights to the two servers in question, and the job owner is using my domain account. Is that not enough?- - - -- Will -- - - -http://www.servicerank.com/ |
 |
|
|
hismightiness
Posting Yak Master
164 Posts |
Posted - 2004-09-17 : 09:43:52
|
| Well, just to amuse myself, I created a folder locally on the SQL Server itself and performed the same task. I still get the same result. If I perform the data export through the wizard, it works, but if I try and execute the job it creates, it still fails with the same message. What gives? :(- - - -- Will -- - - -http://www.servicerank.com/ |
 |
|
|
hismightiness
Posting Yak Master
164 Posts |
Posted - 2004-09-21 : 08:51:09
|
| syedrehman, I have tried several accounts now which all have sufficient access to the SQL Server and the remote server/directories in question. Do you have any other advice?- - - -- Will -- - - -http://www.servicerank.com/ |
 |
|
|
|
|
|