Good afternoon -
Info:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
I am trying to debug a script task within a SSIS package by setting a breakpoint within the design window of teh script taks and I get the following error:
EventType : clr20r3 P1 : dtattach.exe P2 : 9.0.242.0 P3 : 434f5e26
P4 : microsoft.sqlserver.scripttask P5 : 9.0.242.0 P6 : 434f5e02
P7 : 4f P8 : 0 P9 : pszqoadhx1u5zahbhohghldgiy4qixhx
Other packages within the solution have script tasks and I can debug these with no problem. This particular script task has constanly given me this error.
Please let me know if there is additional information that I need to provide to facilitate a solution.
Respectfully,
James
I kind of figured nobody would tackle this...|||Looks like a nasty error, and one that should not occur. You could try breaking down the task to try and isolate the cause, as obviously not all scripts do it, so what part of this one does cause the issue. Even if you find it, unless you can change what you are doing it will not fix it, but you may then be able to log a support case with MS giving them more information. You could just log a call now, it does seem like something is very wrong, since the normal task/VSA error handling is not catching this.|||Thanks for the reply. I will log an incident with MS to resolve this. It's odd because the script task functions properly, I just can't debug this particular task. When the debugger begins, the text displayed is from a totally different script task and a box pops up saying that, "Microsoft Visual Studio has lost the link to your application and will attempt to recover when you logoff."
Respectfully,
James
|||Hi
I had a similar issue, the details of which can be found below. I believe my issue was around a line of code that assigned a string containing a string of xml directly to a dts string variable:
Dts.Variables("CaseDetail").Value = myNode.OuterXml.ToString()
I removed the above line, copied the script, deleted the script task, added a new script task and then pasted back in the code without the above line. The code then debugged fine but I still needed to save the OuterXml so I assigned it to a string variable first:
Dim outerXML As String
outerXML = myNode.OuterXml.ToString()
Dts.Variables("CaseDetail").Value = outerXML
This seems to work ok and debugs too. I'm not sure why I couldn't assign directly to the dts variable, but I'm more of a c# man these days, so maybe my VB skills are to blame.
My Error:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 28/06/2006
Time: 14:01:16
User: N/A
Computer: ****
Description:
EventType clr20r3, P1 dtattach.exe, P2 9.0.242.0, P3 434f5e26, P4 microsoft.sqlserver.scripttask, P5 9.0.242.0, P6 434f5e02, P7 4f, P8 0, P9 pszqoadhx1u5zahbhohghldgiy4qixhx, P10 NIL.
Data:
Was facing the same issue even after trying all of the above.
Have found workaround for this annoying problem
Everytime you get this error, right click on the problematic project in solution explorer and select 'clean' and then select 'rebuild'
Debugging should then work ok.
ta
arun
|||Thanks Arun,
I tried ur stuff and it worked. I had been having hard time debugging my scripts and used to get this error evrytime.
Thanks again,
Mohit
|||MohitGupta wrote:
Thanks Arun,
I tried ur stuff and it worked. I had been having hard time debugging my scripts and used to get this error evrytime.
Thanks again,
Mohit
If someone replies with an answer please could you mark it as such. This helps when other people are searchig the forums for answers to their own questions.
Thanks
|||Hello,
I've got the same problem here. Previous week i had no probleme, now i'm not able to put a breakpoint in any of my scripts. This cause a crash... it is very annoying
Version of server 9.0.3153 32 bit
Version of client 9.0.3142 32 bit (last sp2 + hotfixes) - dotnet framework 2.0 + sp2
What change since then : update in windows defender...
I suspect a problem with the antivirus, or windows defender preventing the script from debugging...
No comments:
Post a Comment