-
1
- #1
After a few months, i ws not able to debug any VBNET applications.
When the debugging starts, the IDE Freezes , the
application is shelled and only visible in the task manager but does not use any CPU times.
No Gui is displayed and the IDE is completely blocked.
This is due to IIS which is running on my Win200O.
The internet information service is not able to start
( Verify with the events viewer )
The solution consist of recreating the IIS.MSC file by a new one.
From the start button , Run "MMC".
In the console menu , click "add" and select "Internet Information service".
Save the file in \\Winnt\system32\inetsrv\ as iisNew.msc
Reboot in safe mode and rename iis.msc as iis Old.msc and
iisnew.msc as iis.msc
Reboot the machine
if you have still problem , at the command prompt,
lauch "IISRESET".
IIS is stopped and restarted
Now you should be able to debug again.
I hope it can help you to avoid to loose a lot of time.
When the debugging starts, the IDE Freezes , the
application is shelled and only visible in the task manager but does not use any CPU times.
No Gui is displayed and the IDE is completely blocked.
This is due to IIS which is running on my Win200O.
The internet information service is not able to start
( Verify with the events viewer )
The solution consist of recreating the IIS.MSC file by a new one.
From the start button , Run "MMC".
In the console menu , click "add" and select "Internet Information service".
Save the file in \\Winnt\system32\inetsrv\ as iisNew.msc
Reboot in safe mode and rename iis.msc as iis Old.msc and
iisnew.msc as iis.msc
Reboot the machine
if you have still problem , at the command prompt,
lauch "IISRESET".
IIS is stopped and restarted
Now you should be able to debug again.
I hope it can help you to avoid to loose a lot of time.