Need Help With IIS / Visual InterDev Connection
Hello,
I am having a problem connecting to IIS using Visual InterDev (the VB6 ASP Classic code authoring system). When I open a project in Visual InterDev, and double click a file, I get the error popup attached. Normally, Visual InterDev simply opens the file for editing.
I recently ran a PC Cleaner (PC Cleaner Pro), and it may have deleted a needed service or file.
I am running Win XP SP4 w/ 2.66GHz P4 CPU.
Thank you very much for any help you can provide.
Best regards, Stu Engelman
vs6error.jpg
I am having a problem connecting to IIS using Visual InterDev (the VB6 ASP Classic code authoring system). When I open a project in Visual InterDev, and double click a file, I get the error popup attached. Normally, Visual InterDev simply opens the file for editing.
I recently ran a PC Cleaner (PC Cleaner Pro), and it may have deleted a needed service or file.
I am running Win XP SP4 w/ 2.66GHz P4 CPU.
Thank you very much for any help you can provide.
Best regards, Stu Engelman
vs6error.jpg
Dave Baldwin
What do you get when you enter 'http://locahost/' in your browser? Maybe IIS is turned off for some reason. Also, on my machine (XP SP3) I have limited IIS to the machine IP address so it does not answer at localhost. It was causing me some problems. If you choose "All unassigned", it should answer on 'localhost'.
ASKER
Hi Dave,
On invocation of http://locahost/ in a browser, I get "Server Application Error. The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance."
My IIS Default Web Site, which is the container for all other web virtual directories in IIS, already has "All Unassigned" as its IP address.
Stu
On invocation of http://locahost/ in a browser, I get "Server Application Error. The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance."
My IIS Default Web Site, which is the container for all other web virtual directories in IIS, already has "All Unassigned" as its IP address.
Stu
It appears you need to fix that error before you can do anything else.
ASKER
Hi Dave,
You may be right, but the error message is so generic it provides no clue as to how to proceed.
At this point my question is what do I do? I don't even know what's causing the problem, let alone how to fix it.
Stu
You may be right, but the error message is so generic it provides no clue as to how to proceed.
At this point my question is what do I do? I don't even know what's causing the problem, let alone how to fix it.
Stu
I assuming you are running Windows XP SP3 since there is no SP4. First look in C:\Inetpub\wwwroot for one of the 'default' index files like 'default.asp' or 'default.aspx'. Rename that to something like 'default0.asp' and then put a simple index file in there like 'default.htm' or 'index.htm'. Then 'localhost' should come up without that error because an 'htm' file is not going to be an 'application'. Then you can look at whatever file is causing the error.
In your IIS setup under "Home Directory" in the Properties for your web site, click on Configuration and look at the Debugging tab and make sure that "Send detailed ASP error messages..." is selected.
In your IIS setup under "Home Directory" in the Properties for your web site, click on Configuration and look at the Debugging tab and make sure that "Send detailed ASP error messages..." is selected.
ASKER
Hi Dave,
You are correct that I am running Win XP SP3 (sorry for the mistake in my initial post).
C:\Inetpub\wwwroot does not have any default or index page.
"Send Detailed Error Messages" is already selected both for my Default IIS Web Site, as well as the web site I am trying to work with (the latter is a child object of the former within IIS).
I added index.htm to C:\Inetpub\wwwroot with the following code:
<HTML>
<HEAD>
</HEAD>
<BODY>
This is a test.
</BODY>
</HTML>
I then made sure that index.htm was a default document for the Default IIS web site.
http://localhost/ now displays "This is a test." So it looks like I'm making some progress.
Let me check Visual Interdev and see if the problem is fixed in respect of the actual site I want to work with,
Stu
You are correct that I am running Win XP SP3 (sorry for the mistake in my initial post).
C:\Inetpub\wwwroot does not have any default or index page.
"Send Detailed Error Messages" is already selected both for my Default IIS Web Site, as well as the web site I am trying to work with (the latter is a child object of the former within IIS).
I added index.htm to C:\Inetpub\wwwroot with the following code:
<HTML>
<HEAD>
</HEAD>
<BODY>
This is a test.
</BODY>
</HTML>
I then made sure that index.htm was a default document for the Default IIS web site.
http://localhost/ now displays "This is a test." So it looks like I'm making some progress.
Let me check Visual Interdev and see if the problem is fixed in respect of the actual site I want to work with,
Stu
ASKER
Hi Dave,
When I try to open up a page from the web site I want to work with in Visual Interdev, I get the error popup attached below. Also, the World Wide Web Publishing Service turns off, and the Default web site in IIS turns off. The latter will of course turn off all other IIS web virtual directories, as the Default web site in IIS is the parent object of all other web virtual directories in IIS.
Stu
vid-error.jpg
When I try to open up a page from the web site I want to work with in Visual Interdev, I get the error popup attached below. Also, the World Wide Web Publishing Service turns off, and the Default web site in IIS turns off. The latter will of course turn off all other IIS web virtual directories, as the Default web site in IIS is the parent object of all other web virtual directories in IIS.
Stu
vid-error.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Dave,
Thanks very much for the link.
Will test it out.
Stu
Thanks very much for the link.
Will test it out.
Stu
ASKER
Hi Dave,
Your link was very helpful. I uninstalled/reinstalled IIS and this seemed to fix my registry problems. I still have the issue of getting VID to communicate with IIS, but the WWW Publishing Service and IIS shutdowns are now resolved.
I'll start a new request to deal with the remaining issue.
Thanks very much for your help.
Stu
Your link was very helpful. I uninstalled/reinstalled IIS and this seemed to fix my registry problems. I still have the issue of getting VID to communicate with IIS, but the WWW Publishing Service and IIS shutdowns are now resolved.
I'll start a new request to deal with the remaining issue.
Thanks very much for your help.
Stu
ASKER
Very helpful advice, that solved two of my three problems.
You're welcome, glad to help.