If you are able to open the package in designer then you have a row in
sysdtspackages.
1. Look in the error logs.
2. Reregister the DTS dlls.
3. Pump sysdtspackages to another server from which you know you can open
DTS packages
DTS is client side so try opening the packages on that server from A.N.Other
box. If the packages are good then you will be able to open things up and
prove the problem is with the server.
What errors did you get ?
If there was nothing in the package then the jobs would have worked as there
was nothing to go wrong.
Do you not have a backup of MSDB ?
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"K" <anonymous (AT) discussions (DOT) microsoft.com> wrote
Quote:
hello doug;
don't panic. query the sysdtspackages in the msdb databases to check if
the packages actually exist. if they don't, that's not good. but if they do,
|
check the drive where your msdb database resides and verify if the drive has
enough space. make some room and you should be able to see your packages. at
least this was my problem when my packages once dissappeared.