March 18, 2008 at 6:51 pm
I am using SQL Server 2005 in x64 platform, when I trace back the event log, I found the following error,
Description:
Hanging application SqlWb.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Does anyone meet this before and what is the cause of the error?
March 21, 2008 at 11:55 am
Sounds like management studio simply got hung ...
Did it only happen once? If so, I wouldn't worry ...
March 22, 2008 at 8:55 pm
sqlwb is Management Studio.
As Adam mentioned, unless this happens often, I wouldn't worry.
May 27, 2008 at 7:30 am
I get this often, the 2005 management studio either at startup or when asked to open a table will hang with typically 80-90% system resources consumed by sqlwb.exe. Though this seems to be a new problem, I used MS for many months before this started. There is a discussion here https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=496262&SiteID=17 but remedies like rebuilding the OS then sql are unattractive. Video drivers are not it for me.
this problem wastes a lot of time shutting down the process and starting MgtStudio again. I recently went to Office2007 to get Access2007 and use adp to connect to a db which I have found quick and easy at least for viewing data, and better than firing up MS let alone with all this hanging problem. THen I find that I need to remove all extended properties from sql2005 tables in order for the adp to be able to read them. All very annoying.
September 19, 2008 at 2:20 pm
any luck with your question, I am getting the same thing repeatedly
September 20, 2008 at 1:11 am
yes, solved it. Bought a new PC. Sorry cant be more helpful.
September 23, 2008 at 4:42 am
Sorry any solutions same issue here, I have started a new thread as well, without seeing this one, buying a new PC will not help as it a Itanium Server with around 800 Gigs of data.
Thanks
Regards
laksUK
October 14, 2008 at 5:17 am
I ran into this problem too but I might have some advice:
When you run the query that is hanging SQL Server Management Studio (sqlwb.exe), take a look at the swirling "Executing" status at the bottom-left of the sqlwb.exe window. If that's still running--then you've got a runaway query going or one that is working hard to generate results.
Stop the query using the red icon at the top of the sqlwb.exe window and re-examine your query WHERE clause, etc. See if you can reduce the number of rows.
If you try to scroll a resultset window (especially results in a grid) while results are still being generated, CPU usage will spike to 100%.
But don't do anything like uninstall SQL Server and reinstall it. It is probably unnecessary and will take a lot of time. Also, you may mess-up add-ins or your configuration unintentionally, causing you more headaches.
I hope this helps someone out there...
October 14, 2008 at 6:54 am
I raised this issue with Microsoft and the issue was fixed by applying the hotfix, this is only for an Itanium Server running on Windows 2003 with .NET Framework 2.0. Installed.
http://support.microsoft.com/kb/945766
Thanks
Regards
laks
October 14, 2008 at 5:37 pm
This guy (previous message) has no idea what he's talking about. The hotfix he cites has nothing at all to do with a stalled sqlwb.exe process.
October 15, 2008 at 2:56 am
Jim
If this is your opinon I am fine with that. Did you go through the hotfix and what is issue is as well...
Quote from the Hotfix
SYMPTOMS
On a computer that is running an Itanium-based version of Windows Server 2003 with Service Pack 2, you may experience issues that are related to the IA-32 emulation layer.
Back to the top
Issue 1
An application may close unexpectedly. For example, Microsoft SQL Server 2005 Management Studio may close unexpectedly when you click the New Query button on the toolbar.
and by applying this hotfix it solved my problem...:)
Regards
Laks
January 6, 2009 at 3:17 am
email2laks,
did you receive this error?
Hanging application SqlWb.exe, version 2005.90.xxxx.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
January 6, 2009 at 5:13 am
Miz
Yes, by applying the patch it was solved.
Regards
Laks
July 13, 2009 at 8:53 am
I've run into this problem even post reboot and before processing any SQL queries at all. It begins as soon as SQL mgmt studio is opened. Any other thoughts? Thanks!
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply