June 12, 2009 at 7:30 pm
Hi,
I have a execute SQL task in my OnError event which log an error record in my log table when error occurs. However, I am getting this vague message and just couldn't figure out the problem. I checked carefully my parameters and connection, they all looked correct. There should be no ResultSet returning.
By the way, I have a local development SQL server db on the same machine that I am running the SSIS.
[Execute SQL Task] Error: Executing the query "INSERT INTO dbo.LogTable
(..." failed with the following error: "The statement has been terminated.".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."
How can I further debug this problem?
Thanks a lot for any help provided!
June 12, 2009 at 9:47 pm
Hello again,
This could relate to your “Connection Error” post i.e. the SSIS Package is the cause of the maximum number of concurrent connections being exceeded. (Please see my post on the other thread).
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
June 12, 2009 at 10:15 pm
How did concurrent processes happen? Does it mean the previous process didn't work? How do I clean it up then?
Thanks a lot!
June 12, 2009 at 10:41 pm
Actually this should not be related to the concurrent problem. Because I restarted the SQL server, and even reboot the machine and it still got the same "The statement has been terminated" error.
June 13, 2009 at 3:32 pm
Hello,
If this is not related to your connection issue then it is worth looking in the Event Log and SQL Server Error Log for any relevant (and hopefully more detailed) messages from the time your SSIS package has the issue.
You can also run a Profile against the SQL Server to see what SQL Statement is actually being sent by the SSIS Package. It will also confirm if the process is getting that far i.e. if the SQL statement is being executed, it will eliminate a connection issue.
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
June 13, 2009 at 5:23 pm
Hi John,
Profile is such a good idea. I should have thought about it. I've finally figured out the problem was because of the data type issue and the error shows clearly when the sql statement was copied over to SSMS!
Thanks a lot for the great help! I'd like to ask you further about the use of Event Log and SQL Server Error Log. I am not seeing anything useful under SQL Server Agent-> Error Logs, is that what you mean above? And how do I look at the Event Log in SSMS?
Thanks again for all the useful tips!
June 13, 2009 at 5:33 pm
Hello,
You can get to the SQL Server Logs via SSMS again under the Management Node. (In SQL 2005 anyhow).
By Event Log I mean the Windows Logs such as Application, Security, System. These can be accessed via Computer Management or Administrative Tools, and then Event Viewer
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply