Link to home
Start Free TrialLog in
Avatar of pepps11976
pepps11976

asked on

Visual Studio Error Message

Hi All we have a SBS 2003 Server and on occasion we get the following error message

User generated image
We Have Symantec installed on the Server and the Problem is nobody can remote Login to the Server whilst that message is Displaying, I Believe SMC.exe is Symantec but have no idea how to Rectify the issue

John
Avatar of Joe Howard
Joe Howard
Flag of United States of America image

It has been reported that the DEP settings are changed with the  installation of SQL 2005 or
Visual Studio and that will cause a series of trouble without any information to the user.

The reported solution is:

a. Right click My PC / Properties.
b. Click Advanced Tab
c. Under Performance, click Settings
d. Click Data Excecution Prevention tab
e. Select Turn on DEP for essential Windows programs and services only
f. Restart Windows

http://social.msdn.microsoft.com/Forums/en-US/24b356ad-59ef-446f-aa8b-df6b55fa78bb/an-unhandled-win32-exception-occurred?forum=Vsexpressinstall
ASKER CERTIFIED SOLUTION
Avatar of Jacques Bourgeois (James Burger)
Jacques Bourgeois (James Burger)
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of HooKooDooKu
HooKooDooKu

Try uninstalling Visual Studio.

As I understand it, SMC.exe has crashed (caused an exception).  It has done something like attempted to access memory beyond the bounds of the program, and the program didn't have an active exception handler.

But because you have Visual Studio installed, Visual Studio has jumped in as the exception handler and is offering you the option of debugging your way through this exception.

So if you want to avoid the this dialog, try uninstalling Visual Studio.
Avatar of pepps11976

ASKER

Ok but I am not sure if uninstalling Visual Studio will stop anything else working
You are right, uninstalling Visual Studio won't prevent the users from logging. It will just prevent the message from displaying, which is event worst because you might not be aware that the problem is happening.

It's not Visual Studio that prevents the logging, it's the fact that the firewall is having problems.

Contacting Symantec is your best bet.