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 |
|
Crowandazi
Starting Member
9 Posts |
 Posted - 2005-03-04 : 09:48:58
|
| Hello, I'm a fairly novice DTS Package designer that has been forced into maintaining something a bit over my head and need some help. I understand how to build and execute packages, but I am having a problem successfully scheduling them.Here's my set-up: My web hosting company runs SQL Server 2000 on an NT machine. I have XP Professional, and I am using Enterprise Manager to connect to their database. I have MSDE2000 on my local machine. I have no problem seeing or editing packages that I make. When I execute them manually, they work. When I schedule a job, however, it fails (I don't know how to get the error message generated from a failed job, so I can't tell why it failed). However, when the server administrators or my former programmers schedule jobs using this exact same package it works.I think the source of my problem has to do with my access to the database or setup of Enterprise Manager. When I look at the jobs queue, I can see only the jobs that I have created. I can NOT see any existing jobs that have been made by other people, when my administrator tells me that I should be able to see everything.Any thoughts? I've been trying to get this answered for five weeks now and will gladly name my child after the person who helps me solve this.Also, do you know of any resources concentrating on set-up of Enterprise Manager, or concentrating on DTS Job Properties. I have found nada on these subjects. Thanks! |
|
|
smithje
Starting Member
32 Posts |
Posted - 2005-03-04 : 10:20:25
|
| We experienced similar problems when our company forced us to consolidate to a server farm across the country. It is related to your user account and the permissions they have set on it. I can't give you specifics because I have not learned enough about the admin side of the application. You can look at who the owner of each DTS package is and figure out which owners can successfully run them by scheduling a job. Those user accounts have some rights that yours doesn't. We started out seeing only our jobs in the server agent as you describe but after the admin folks got their act together we can see everyones but can only access those related to the databases that we have rights to. Job errors are a pain to understand. I too would like to find better information when they fail. |
 |
|
|
|
|
|
|
|
Unable to Schedule or See Existing DTS Jobs