| Author |
Topic |
|
cjserrato
Starting Member
4 Posts |
 Posted - 2004-03-03 : 14:27:52
|
| I got problem when I schedule a DTS package as a Job, the package simply doesn't works and error message appears "Unknown Error"What do you recommend me? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-03 : 14:31:30
|
| Does the package work if you execute it outside of a job? Have you tried logging into the database server with the account that the MSSQLSERVER service uses and then executing the job outside of a job? The reason why I ask is that when you schedule a job, it uses the MSSQLSERVER service account. So you need to test the package with that account before setting it up in a job. You also need to test it on the database server so that you know all drive letters work and anything else that would be specific to the machine.Tara |
 |
|
|
ChrisFretwell
Starting Member
43 Posts |
Posted - 2004-03-03 : 14:41:58
|
| Also, log the job output. It may give more than you see when you look at the history.Chris |
|
|
|
sphadke
Yak Posting Veteran
55 Posts |
Posted - 2004-03-03 : 15:19:45
|
| Also SQL Server Error Log.. that is a good place to find out whats going on.Sachin |
|
|
|
cjserrato
Starting Member
4 Posts |
Posted - 2004-03-03 : 16:10:12
|
quote:
Originally posted by tduggan
Does the package work if you execute it outside of a job? Have you tried logging into the database server with the account that the MSSQLSERVER service uses and then executing the job outside of a job? The reason why I ask is that when you schedule a job, it uses the MSSQLSERVER service account. So you need to test the package with that account before setting it up in a job. You also need to test it on the database server so that you know all drive letters work and anything else that would be specific to the machine.Tara
My package works good when I execute it out a job, the problems comes when I put it inside a job.Also I put a log file for the package but like the package is not executed the log file doesn't have changes |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-03 : 16:15:06
|
| But did you execute it while logged into the database server (not your client machine unless SQL Server is on your machine and that is where the DTS package resides) using the MSSQLSERVER service account? This is very important to check. Or is the service using the local system account? If so, that's probably your problem. It is recommended that the service accounts use a domain account that has local admin privileges.Tara |
|
|
|
cjserrato
Starting Member
4 Posts |
Posted - 2004-03-03 : 16:58:43
|
quote:
Originally posted by tduggan
But did you execute it while logged into the database server (not your client machine unless SQL Server is on your machine and that is where the DTS package resides) using the MSSQLSERVER service account? This is very important to check. Or is the service using the local system account? If so, that's probably your problem. It is recommended that the service accounts use a domain account that has local admin privileges.Tara
I'm executing it from the server directly and even if I execute it from my client it doesn't works either. Can you tell me how can I use the MSSQLSERVER service account or where can I look it at? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-03 : 18:00:00
|
| You need to open up control panel, then go to adminnistrative tools, then to services. Then double click on MSSQLSERVER and go to logon tab. Does it say to use the Local System Account? If so, that's most likely your problem.Tara |
|
|
|
ChrisFretwell
Starting Member
43 Posts |
Posted - 2004-03-03 : 18:22:42
|
| I was refering to the job log. On the advanced tab of the job step, you can log the job. This may give you the details of the error. |
|
|
|
|
DTS Jobs problems