After installing Visual Studio 2005 I now receive the following error every time I boot the laptop: “SQLDUMPER library failed initialization.Your installation is either corrupt or has been tampered with.Please uninstall then re-run setup to correct to correct this problem.” in a modal dialog with the title “SQL Writer”.
Any advice (other than uninstalling SQL Server – unless you think it’s truly my only option) would be appreciated.Also, if there is a more relevant forum or thread that I should be posting to (like a SQL forum instead) I’m willing to give it a try.
I ran into the same exact issue. Do you have a resolution on the same?
1) Had Visual Studio 2005 Trial installed
2) Uninstalled the trial and installed Visual Studio Professional 2005
3) Installed .net framework 3.0 september2006
4) Uninstalled all prerelease versions of .NET framework 3.0 using "vs_uninst_winfx.exe".
5) Installed the released version of .net framework 3.0 November 2006
6) Installed Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP
7) Installed Blend (Microsoft interactive expression designer November 2006)
On the logon screen I get the message box “SQLDUMPER library failed initialization.Your installation is either corrupt or has been tampered with.
Please uninstall then re-run setup to correct to correct this problem.”
I am running windows XP 2002 professional SP2. I would appreciate any inputs on resolving the above issue.
Nope, I've learned to live with it as it doesn't seem to affect performance and it's on a box that I only occasionally use. I'd still love to have it gone though. There is one difference between our scenarios...I did not install .NET 3.0 just all of the
2.0 CTPs, Betas, and RTM.
Thanks. When i run my application (which is a C#.Net windows application), it throws up the following exception :
"The CLR has been unable to transition from COM context 0x1a3df0 to COM context 0x1a3f60 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without
pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA)
threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations. "
I am not sure if this is a consequence of the above issue. : (
sjd0103
Member
418 Points
86 Posts
SQL Writer - SQLDUMPER failed initialization
Jun 10, 2006 08:05 AM|LINK
After installing Visual Studio 2005 I now receive the following error every time I boot the laptop: “SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct to correct this problem.” in a modal dialog with the title “SQL Writer”.
I have SQL Server 2000 installed and later installed SQL Express. Prior to this VS2K5 Pro installation I had the VS2k5 Trial installed (with both SQL versions installed before either). I used the uninstall tool vs_uninst.exe located at http://download.microsoft.com/download/0/a/a/0aacd9c1-a0c5-43ab-a428-0ee440d4472c/vs_uninst.exe.
Any advice (other than uninstalling SQL Server – unless you think it’s truly my only option) would be appreciated. Also, if there is a more relevant forum or thread that I should be posting to (like a SQL forum instead) I’m willing to give it a try.
Thanks!
Muks
0 Points
2 Posts
Re: SQL Writer - SQLDUMPER failed initialization
Dec 13, 2006 09:16 AM|LINK
Hello:
I ran into the same exact issue. Do you have a resolution on the same?
1) Had Visual Studio 2005 Trial installed
2) Uninstalled the trial and installed Visual Studio Professional 2005
3) Installed .net framework 3.0 september2006
4) Uninstalled all prerelease versions of .NET framework 3.0 using "vs_uninst_winfx.exe".
5) Installed the released version of .net framework 3.0 November 2006
6) Installed Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP
7) Installed Blend (Microsoft interactive expression designer November 2006)
On the logon screen I get the message box “SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct to correct this problem.”
I am running windows XP 2002 professional SP2. I would appreciate any inputs on resolving the above issue.
Thanks & Regards
sjd0103
Member
418 Points
86 Posts
Re: SQL Writer - SQLDUMPER failed initialization
Dec 13, 2006 12:25 PM|LINK
Nope, I've learned to live with it as it doesn't seem to affect performance and it's on a box that I only occasionally use. I'd still love to have it gone though. There is one difference between our scenarios...I did not install .NET 3.0 just all of the 2.0 CTPs, Betas, and RTM.
Good luck!
Muks
0 Points
2 Posts
Re: SQL Writer - SQLDUMPER failed initialization
Dec 13, 2006 02:46 PM|LINK
Thanks. When i run my application (which is a C#.Net windows application), it throws up the following exception :
"The CLR has been unable to transition from COM context 0x1a3df0 to COM context 0x1a3f60 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations. "
I am not sure if this is a consequence of the above issue. : (
axbhat
Member
2 Points
1 Post
Re: SQL Writer - SQLDUMPER failed initialization
Feb 22, 2007 08:11 AM|LINK