| Author |
Topic |
|
Stella
Starting Member
4 Posts |
 Posted - 2007-04-17 : 07:35:52
|
| I have scheduled a job in Management Studio, but it doesn't work. However, when I run it maually in Visual Studio it works. I have connected an outside server by mapping it to mine. Maybe this is the problem?I have also tried to configure a linked server, but I cannot find out how to connect my SSIS package to the linked server.Can anybody help me?Thank's! |
|
|
prpball
Starting Member
19 Posts |
Posted - 2007-04-17 : 11:14:33
|
| How are you connecting to your server? Through a UNC name or a mapped drive? |
 |
|
|
Stella
Starting Member
4 Posts |
Posted - 2007-04-17 : 11:34:35
|
quote:
Originally posted by prpball
How are you connecting to your server? Through a UNC name or a mapped drive?
I'm not quite sure what you mean... I connect to my own server by remote. My server, on the other hand, is linked to another server through a mapped drive. On the other server there is an Access database from which I want to get data. This works properly when I do it manually in Visual Studio from my server. The scheduled work does not work right however. I can not figure out if it depends on the mapped drive or something else...Thank's again. |
|
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2007-04-17 : 12:21:10
|
| Each Maintenance Plan creates a job.I have noticed several times in the past, that when I change the job or the plan, the schedule becomes disabled. or the "Enable Schedule" check box in the job steps automatically gets unchecked. It is a good place to look into. Further, if you change the selection of the database the location of the output also automatically defaults to the "Default Vaules".Example: I have a new server on which we are systematically migrating SQL 7 apps to.Everytime one more app/database is added to this new 2005 server, I have to change the maintenance plans and the backup plans. The moment I select another database, the location of the output goes back to the default value like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup (sounds weird, but it is true)RegardsParesh MotiwalaBoston, USA |
|
|
|
Stella
Starting Member
4 Posts |
Posted - 2007-04-17 : 12:47:12
|
| Thank's for your answer, but it doesn't seem to help. I have checked the check boxes and the job is enabled. Also, there are no maintenance plans, only scheduled jobs.Should I try to redeploy the SSIS package? Maybe it helps?/S |
|
|
|
prpball
Starting Member
19 Posts |
Posted - 2007-04-19 : 08:04:31
|
| Stella,In the SSIS how are you connecting to the linked server where your access database resides? I have ran into a similar issue and I found out that when you use a mapped drive, the schedule can not find the mapped drive. For instance, Are you connecting to your Access database like this: d:\servername\folder\folder\db.mdb or are you connecting like this: \\servername\folder\folder\db.mdb? The later is called UNC name, the first is called a map drive path.If you are connecting through a mapped drive change it to the UNC name and try running the job again. |
|
|
|
Stella
Starting Member
4 Posts |
Posted - 2007-04-20 : 09:52:17
|
| I think your answer could help me, I'll try this. Right now I'm not using UNC. |
|
|
|
TejasLambu
Starting Member
1 Post |
Posted - 2007-04-25 : 09:21:30
|
| Stella,I am going thr' the same problem and found out that the if you run the schedule under local login then you may not be able to access network resources. I am trying to create a file on other server. Job runs fine but nothing happens as my activex ignores the errors. If I run the DTS manually it works fine. Try to run the job under domain\username who has access to the other server. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-25 : 10:18:49
|
| If need access remote data source, have to start sql agent service with domain account that has proper permission. |
|
|
|
|
Scheduled job doesn't work, but works manually