Re: SBS 2003 Internet Connection Wizard failure

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi:

There are no references that I can find linking VSD and SBS with or without
CEICW.

Maybe going down the wrong path here, but the Visual Studio Debugger may be
causing you to not see the real messages. Here is an article explaining how
to stop it from picking up such errors:

http://support.microsoft.com/default.aspx/kb/923827

in that article it describes 'data execution prevention" as one of the
things that can happen to cause VSD to start.

Here is an article about data execution prevention.

MS response to a IIS/DEP Data Protection Error:
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/2dec93e3dd37d1cf/d1169338a0af55be
So I am thinking along these lines: If you disable the VSD long enough to
get the error trapped by Dr.Watson, perhaps you can get more information?

Larry


"Jay" <j@xxxxx> wrote in message
news:OxPtJBj7HHA.2476@xxxxxxxxxxxxxxxxxxxxxxx
Hi Larry

The first window titled 'Configure E-mail and Internet Configuration
Wizard' appears, then I get the exception when I press <Next>. Task
Manager tells me that icw.exe is one of the active processes, and it
disappears when I <OK> the error message. Since the problem first
occurred, I've restarted the machine..

Jacques

"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
news:eRjJfjh7HHA.980@xxxxxxxxxxxxxxxxxxxxxxx
Hi Jay:

The CEICW fails at different points for different reasons. While the
reasons are often mysterious, at best, it might help to know if you
really mean that it fails right at the start... that is, no progress is
made at all?

Larry

"Jay" <j@xxxxx> wrote in message
news:u1RbYug7HHA.536@xxxxxxxxxxxxxxxxxxxxxxx
When I start the Internet Connection Wizard on my SBS 2003, I get
'Visual Studio Just-In-Time Debugger - An unhandled win32 exception
occurred in icw.exe [164]. Just-In-Time debugging this exception failed
with the following error: No installed debugger has Just-In-Time
debugging enabled.'

Has anybody else encountered this and fixed this? The last time I ran
icm was some months ago: it's not the sort of app you use regularly.
Perhaps some window updates, which I regularly apply, have introduced
this error. I haven't applied Windows Server 2003 Service Pack 2 yet,
because it's not clear to me whether it's a good idea to apply it to SBS
2003.

Thansk for any input.

Jay







.