Exception ex.Message I am getting in debug mode calling AcquireConnection is much shorter than the logged message in run time because all the errors come to output window in debug. Is there any way to get all these errors description from exception object in debug time to be able to parse it
Thanks.
ex.Message in debug mode is much shorter
kuponutcom
What you are saying does not make sense. The exception details will always bee the same debug or otherwise. The exception will only have one message, but you suggest there should be more. You could check the InnerException property of the caught exception, that may give something. I really do not understand how you are describing the two modes, with all errors or otherwise.
Is this perhaps to do with a UI If so try the IErrorCollectionService interface. This allows you to get details of the fire error, warning methods called from the IDTSComponentMetaData90.
shmulik_segal
Will try to explain what actually I am actually looking for.
Try
connection = connMgr.AcquireConnection(Nothing)
Catch ex As Exception
'Dts.Events.FireError(1, ex.TargetSite.ToString, ex.Message, "", 0)
MsgBox(ex.Message)
Dts.TaskResult = Dts.Results.Failure
End Try
In the msgbox reading the message "Exception from HRESULT: 0xC0202009".
Error: 0xC0202009 at EnvConfig, Connection manager "DB_SOURCE": An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'DTSUSE'.".
katgreen
Ok, now I see. This is not a SSIS issue, rather a .Net programming issue, in so much as it is actually bad practice to just catch the general Exception type. It is also very common, we all do it! Really you should catch targeted exceptions as they are richer classes that have more information relevant to the exception thrown.
If you catch the SqlException type you can get access to the Errors collection, that is a property on the SqlException class. That will give you that extra level of detail, both for the messages and things like the source.