Web Development

Ask something
Discussion Locked

ASP pages (includes) broken after move

0 helpful
6 replies

by joshua1 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Myself and 1 other person configured an ASP site called 'labels' on a server named 'testing': http://testging/labels/default.asp
I programmed the processing/logic and he did the creative stuff (images/layout).

The site was approved, so now I need to change it to just 'labels' on a production server: http://labels/default.asp
Problem is that I haven't worked w/ ASP much and the guy that built all the includes was released.

I've set up a new site (IIS 5.0), configured 'labels' as the hostheader, added an alias in DNS. I can connect to .htm pages on the site, so that stuff seems to all be in order.

When I attempt to connect to the asp page, I receive "The specified module could not be found."
I feel like I've tried 50 adjustments on the includes & .inc files, and I can't get it to go.

I currently have:
>
The body of the page

header.inc contains a banner, navigation bar, table definitions, etc.

Do you know why I got this error and how to correct it?
Thanks.

6 replies

by joshua1

There's no ISAPI DLL's installed on either server. If there is some DLL difference, I can't find it. The IIS settings appear to be the same. Also, we didn't use any Visual C++, just text-based envrinoments: WebEdit & Jext, mainly. A little bit of FrontPage.

by joshua1

There is something different between the 2 servers. On the original server, I altered the site from http://testing/labels to http://labels and made the appropriate adjustments in the code. The site works fine. I don't see any apparent differencesin the servers. Same service pack, same IIS basic configs, no ISAPI's, nothing in the Event Viewer.

by madestroitsolutions

My friend, this MUST be a problem with an ISAPI, since it is an ISAPI (asp.dll) that processes ASP Pages.
Compare your configuration in Internet Information Services between both servers by right clicking on the website in the following 2 places:
- ISAPI Filters Tab (obviously)
- Home Directory Tab : Click on the [Configuration] button and check the Mappings Tab. You will find a list of ISAPI's in the Test server that need to be installed in the new server.

I hope that helps, and if it does help you solve the problem, consider sending a note to the guy on answer one, cause he was right, he he.

Good Luck!

by joshua1

That was it! Thanks! My first ASP application is running! Your post showed me how to fix the problem, which is what I needed. I checked every setting in IIS (almost). The ISAPI tab was about the extent of my DLL knowledge. Thanks for the instructions on the mappings.
I appreciate every repsonse and everyone's time (Thanks AlterEgo2). I'm really new to ASP/VB, so there's a lot I don't understand yet. I'll be better in a few months, though! :)
I had read the article, it basically says somewhere on the server you might have a damaged/missing DLL and provides info on Vis C++ and FoxPro (I don't know either one). While something was different on the server, I didn't how to fix it. Your post showed me.
Thanks again.

This discussion is closed to new replies.