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 |
|
Van
Constraint Violating Yak Guru
462 Posts |
 Posted - 2008-12-18 : 14:34:28
|
| I don't understand this. Using VS2008 and SQL2008. When I run the package with VS2008 manually it runs fine. When I schedule it as a job and have it run the same package it fails looking for some old connections that used to be there. I took the connections out, ran the package in VS2008 and it runs fine. Creating a new job to run it (or using the old job) results in errors because it can't find those old connections. Anybody know what it could be?Thanks,Van |
|
|
Van
Constraint Violating Yak Guru
462 Posts |
Posted - 2008-12-18 : 15:54:08
|
| When I open the package with notepad I can search and see the deleted connections that's causing it to fail. It doesn't fail when running through VS2008 though. Each line that shows one of the missing connections has "DisableEventHandlers" toward the beginning of the line. I'm not sure what to do at this point. I can't see anything in the GUI (Control Flow) part of the SSIS package to delete to get rid of the references to the old connections. Any ideas?Thanks,Van |
 |
|
|
Van
Constraint Violating Yak Guru
462 Posts |
Posted - 2008-12-18 : 17:20:34
|
| For now we have this fixed by putting the connections back in (they aren't being used though). This has got to be a bug with SQL2008 (maybe in 2005 as well). It ran fine in Visual Studio when ran manually with the unneeded connections deleted. When scheduled as a job in SQL2008 it failed looking for those connections even though they had been deleted and weren't being used. Putting the unneeded connections back in made it work as a job. Why would it run fine in VS and not as a job? Why would it look for those deleted connections as a job but not when ran in VS? I'd say I'm 100% sure it's a bug. |
|
|
|
|
|
|
SSIS failing as job