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 |
|
zeeshan13
Constraint Violating Yak Guru
347 Posts |
 Posted - 2011-01-31 : 10:10:39
|
| Hi All,A client DB server has SQL Server 2008. I have a SSIS package that runs every friday evening and pickup a .dat file from a location (folder name is "Import") on application server, process it in the database, create the output XML file on application server (folder name is "Import"), and then moved the .dat file to another location on application server (folder name is "Move"). This SSIS package in DB server is run through a batch file which is scedhule through windows task schedular. The whole process take few minutes to run and its been running sucessfully for more than a year now. It looks that this last Friday it did not run sucessfully since the .dat file on application server is still in "Import" folder and the XML does not exist either. Is there a way to findout/read the SSIS logs to troubleshoot what happened? Please suggest.Thanks,Zee |
|
|
zeeshan13
Constraint Violating Yak Guru
347 Posts |
Posted - 2011-01-31 : 11:46:23
|
| Can someone help please. Thanks a lot ! |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2011-01-31 : 12:09:29
|
Don't know what you are doing in your batch file...But if you are using DTEXEC in your batch file then you can add this (for example) to get a logfile:DTEXEC ... /REPORTING EWCDI >> error.log For me it was helping a lot in the past...
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
SSIS did not generate the output file?