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 |
|
RyanAustin
Yak Posting Veteran
50 Posts |
 Posted - 2009-07-22 : 16:16:36
|
| I am in the process of moving a user controlled process over to be a server controlled process and have hit a small snag. The process itself is usually submitted via Scheduled Jobs on the desktop level. I want to move this into a SSIS package so that SQL Server Agent submits the SSIS package and it handles the actual processing. Where I am running into an issue is that when I run the SSIS package in debug mode within BIDS, it runs fine and catchs the error that is occuring and sends out the correct notifications. But when I install that package into the database and run the job through SQL Server Agent, it never catches the error that would normally pop on the users desktop. So basically it sits and spins away not doing anything. Is there a way to have SSIS catch this error and either supress it or have SSIS hit the enter key or escape the screen that would appear?Thanks. Ryan |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-07-22 : 16:18:25
|
| whats the error? how is the SSIS handling it, or isn't it at all? by the way, SQL Agent will catch the error if SSIS doesn't |
 |
|
|
RyanAustin
Yak Posting Veteran
50 Posts |
Posted - 2009-07-22 : 16:55:22
|
| The error is actually a syntax error converting an Oracle timestamp that is invalid. So what the program will do is pop up the syntax error message. Error converting data type DBTYPE_DBTIMESTAMP to datetime.Now I'm not saying this is always the error, I'm just saying in this case I know that the error is not being collected by SQL Server Agent.I have a precedence constraint on the Execute Process Task so that when it doesn't return a result of 0 it fails. |
|
|
|
|
|
|
SSIS Package