October 31, 2003 at 10:35 am
For quite some time I have been creating DTS packages and scheduled them and all of them work fine. We add a new server and after installing SQL Server 2000 SP 3a, I creaate a few databases and DTS packages to import some dta on daily basis. Exactly as we have been doing for the past couple of years.
Created the SQL Server Account, set the permissions as a member of the admin group in that domain, and run the packages individually to make sure they were working fine. They did work fine.
Then, I proceed to schedule them up to run at night. Here is the weird thing. Some days the schedule works as a charm and some other they do not! Any suggestions? I checked permissions all over the user and the domain as well as the server itself. All the permissions are exactly as the other servers. The only difference is that the new server has windows SP4. Any help is greatly appreciated.
Cordially,
cafemar1
October 31, 2003 at 12:14 pm
Any error message when DTS jobs failed?
November 3, 2003 at 1:58 am
take good care NOT having a windows-account as jobowner. (make it a SQLuser which has enough permissions to run the dts-packages)
If you are using a windows-account as jobowner, you'll find errormessages in the jobs joblob.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 3, 2003 at 8:11 am
Thank you. jobs are run with a Windows user in all other servers and they run fine. the users have admin permissions as well as SQL Server admin rights. What remains weird is that, the jobs run fine one day and not the next, or run fine two days in a row and then fail the enxt two or three. Thank you. Still the same, even though I uninstall SQL Server and run a fresh install. I will recreate the pakcages from scratch now to see if that does the trick. I remember in 6.6 some queries return errors even though the query was run manually and everything worked fine, but when the same query was added to any processes, it failed. The trick back then was, delete the query and recreated from scratch. Let's see if this is the case. Thank you anyway.
November 3, 2003 at 8:17 am
When the package's job goes wrong, what's it saying in the jobs jobhistory ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply