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 |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-11-14 : 07:25:50
|
Keefe writes "(Question applies to SQL Server 2000, SP3/ Windows Server 2000 SP4)One of our production DTS packages runs as a scheduled job every 15 minutes. It processes Web data, collected in SQL Server, and forwards it to a legacy DOS application. The package is not complicated, even though it has many steps, and it has run for years. Its last step is to run a bat file that opens the legacy app., runs a routine, closes itself and closes the cmd window.The job stopped working. Microsoft Technical Support (Windows and SQL Groups) traced a recent server change to a file called ntvdm.exe as a culprit. The upgrade disabled the ability of the server to open the DOS app. When we reverted to the prior copy of ntvdm.exe, the app could be opened and used, but the DTS package continued failing on the execution of the bat file. A step-by-step execution of the bat file contents, in a separate cmd window on the server, is always successful, but the package itself does not complete from Enterprise Manager on the same server, though it will complete from other machines.Is there a twin for ntvdm.exe that provides the files/libraries used while running a DTS package, and that would be required to execute a DOS bat file, that might have been affected by an update the way ntvdm.exe was? The reasoning is that there must be such a twin in the SQL environment, the recent change to which is preventing the successful completion of the package.Any help would be greatly appreciated. If I find out first, I'll let you folks know (the question has not been answered out in the Wide Google World, though often asked).Sincerely, KOG" |
|
juvethski
Starting Member
46 Posts |
Posted - 2005-11-19 : 03:54:36
|
this is a weird behavior that i experienced also, although our cases is different. here's what i sugesst:--- select the package (in ent mgr)--- if there are multiple versions of the package, make sure you delete the old versions (you can see the versions by right clicking the package and selecting versions)--- click on design package--- check the properties of each object, the package might be referencing the old path to the old exe, so just set the right path to the right exe. i think the object that you should focus on is the 'connection'hope this helps.~~~~~~~~~~~~~~~~how's your data? |
 |
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-11-19 : 06:21:07
|
Try using "xp_cmdshell". But there are also few risk fastors involved.Check BOL for more details.RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
 |
|
|
|
|
|
|