SQLWB - SQL Server has encountered a user-defined Breakpoint

Question

Post reply

SQLWB - SQL Server has encountered a user-defined Breakpoint

andrewkane17

SSCertifiable

Points: 7529
More actions
August 1, 2006 at 12:38 pm

#113913

I have done an install of SQL 2005, both Server and client tools and the installation went fine. The issue I am having is that after I have opened up the local Management Studio and try and connect to a SQL instance I get the error:
SQLWB - SQL Server has encountered a user-defined Breakpoint
After clicking either debug or close Management Studio exits, all SQL services look fine and I can connect to the instance from another machine using Management Studio. Does anyone have any clues?

Thanks in advance
Andrew
August 4, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Balmukund SSCertifiable Points: 6648 More actions · Answer 1

Do you have Visual Studio 2005 installed on same box?

andrewkane17 SSCertifiable Points: 7529 More actions · Answer 2

Balmukund,

doesn't visual studio get installed when you install SQL 2005, if there was a previous installation would that cause issues?

Yuri55 SSCrazy Eights Points: 8449 More actions · Answer 3

Sorry for renewing this 2 month old post but I've just got same issue after installing SP1 on Sql Server 2K5. I mean after installation was completed and I rebooted machine I can not connect to Database Engine (DE) locally (but I can connect to all services locally or to DE remotely, i.e. Sql Server is OK with SP1 installed). Error is the same as was pointed in initial message- "Sql Server Management Studio has encountered ...”. Andrew: Did you somehow solve this problem?

Thanks in advance, Yuri

andrewkane17 SSCertifiable Points: 7529 More actions · Answer 4

Yuri,

It was an install on a developers machine, I noticed that he had installed a version of Visual Studio 2005 installed that he had downloaded from msdn. I uninstalled that, and uninstalled SQL 2005 and did a fresh install and all was fine. I believe the install of Visual Studio 2005 that SQL does is a cut down version but I don't think the developer was realy using the full blown version anyway (he is an oracle developer venturing into SQL)

Yuri55 SSCrazy Eights Points: 8449 More actions · Answer 5

Unfortunately I do not have this luxury to uninstall Sql Server as this is production server. Funny thing is that I run SP1 installation in 2 production servers in parallel- one is fine,second one- bad (I mean SSMS issue). Probably it’s a bit too late to look for a reason but instead I need to find a way how to fix this problem. Thanks

icarabana Newbie Points: 7 More actions · Answer 6

hi, i have the same problem. i'm upgrade to SP1 this morning and ia found the same problem. please i need help, we have this server in production.

Mitch Bonham SSC Enthusiast Points: 123 More actions · Answer 7

I don't whether this will help but have you tried this sql cumulative fix:

http://support.microsoft.com/kb/933097

I have the same issue, I did a Disaster Recovery of a Client server and now have the same issue, cannot open the management studio because of the sqlwb has encountered an error. Now I have to export the 46GB database somewhere else so we can get the information we require before formatting the whole DR box for another DR operation.

cnoceda Newbie Points: 9 More actions · Answer 8

Hi, Same problem after installing the SP1. Anyone try to install the SP2 to fix it?

Regards

Mitch Bonham SSC Enthusiast Points: 123 More actions · Answer 9

Tried re-installing Windows Server SP 2 yesterday after the restore and re-booted the server, still had the same problem, I suppose the extreme would be to stop the server, cut and paste the databases so another volume and use windows cleanup utility to get rid of SQL 2005 & VStudio, then do a fresh re-install, but that might be my only solution after the fix from microsoft, or was that miserysoft?