Link to home
Start Free TrialLog in
Avatar of Wayne Barron
Wayne BarronFlag for United States of America

asked on

Include file not found (include virtual no longer works under Win10)

Hello, All;

Error
Active Server Pages error 'ASP 0126'
Include file not found
/cs/Header.asp, line 3
The include file '../Imported_Data/ACN.asp' was not found.

Code Line
<!--#include virtual="../Imported_Data/ACN.asp"-->

Open in new window


OK. I have been using this for years, and it still works on my Win2016 Server.
However, running it on my development system, of which is a Win10 Pro.
No longer works.
Enable Parent Paths
Is Enabled in IIS, for the Default Web Site, and all sub sites.

WHAT in the heck did Microsoft do, in the last update to break this?

The actual path of the files is stores in
wwwroot/Imported_Data/

I reference this location with all my sites.
And have NEVER had an issue, until the most recent Windows 10 update, and now it is broken.
At least on my Win10 system.
As stated, it all still works under my Win2016 servers.

Any idea on what can be done in order to get this back working again?
I would really hate to re-code all sites, just because of this one stupid issue.

Carrzkiss
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

then there is a difference between the IIS installation on these 2 machines as they use the same base code
Avatar of Wayne Barron

ASKER

Hey, David.
Everything is darn near identical.
The only thing that is different is, one is a Win10, and the other is a 2016 Server.

Now, lets go back a little here.
I was working on the sites, getting them ready to move over to a RAID setup.
This was about a month ago. And I was working on the sites on my laptop (Win10)
And everything was perfect.
I spent a few days with my granddaughter and away from the computers and when I came back, my Win10 had rebooted after the latest update.
I had to do one more thing to one of the sites, before moving them over to the RAID. and that is when I experienced this issue.
So, it came AFTER the latest Windows 10 Update.
do you also have ServerSide Includes enabled in IIS setup in add windows component?
How about a handler mapping User generated image
I put the imported_data under the folder that contains sample.asp

<!DOCTYPE html>
<html>
<body>
<h3>Words of Wisdom:</h3>
<p><!--#include file="imported_data/wisdom.inc"--></p>
<h3>The time is:</h3>
<p><!--#include file="imported_data/time.inc"--></p>
</body>
</html>

Open in new window

wisdom.inc
"One should never increase, beyond what is necessary,
the number of entities required to explain anything."

Open in new window

time.inc
<%
Response.Write(Time)
%>

Open in new window

it worked
Include files (work)
It is only the Include Virtual that no longer works.

I also did a clean install of my Laptop, in hopes that it would resolve the issue, but nope.
Issue still exist.

I did install the SSI, and that did not do anything either.
I have never had to use Handler Mapping before, so that would not be an issue either.

This is just something that just happened.
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
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
I have trace setup in IIS.
However, what status code should I add in, in order to trace the error?
Or, how do you have it set up to trace the error?
OK, what had happened was the following.

In Windows 10, IIS, I had to set the Default Web Site, to the location of which the sites are kept. (G:\Inetpub\wwwroot)
This is something that I always do, however, in this case. I had forgotten it, since messing with Windows 2016 Server IIS
I delete the default website and add in all the sites, and well, I just forgot.

So, with David mentioning the trace routing, I was able to run a 500 trace on the site and found out it was not finding the site under the ../
So, I had to remove the .. from the beginning of the path.
And it works now.

Thanks, David.
Learned how to do trace routing and remembered to change the Default web site to the path it needs to be for all the Virtual Directories to work properly.

Wayne