Calling asp from a asp.net web application

Posted on 2007-11-21
Medium Priority
Last Modified: 2013-11-26
I have recently converted a VS2003 Web Application to VS2005 Web Application.

I moved the application to the local machine running XP and IIS V5.1 in order to convert the code.

Under VS2003 I could do a Response.Redirect("AspPage.asp"), however under VS2005 this flags up the following error:

Server Error in '/'Application

This type of page is not served.

Description: The type of page you have requested is not served because it has been explicitly forbidden.  The extension '.sap' may be incorrect. Please review the URL below and make sure that it is spelled correctly.

Requested URL: /NewClientMenu.asp

The Response. Redirect works if I am calling another .aspx page, however if I am trying to go to a parent directory as in Response.Redirect("../Anotheraspxpage.aspx") I get the following error:

Cannot use a leading .. to exit the above directory.

Again this worked in VS2003 siiting under IIS V5.1.

Is there a way around these two problems in VS2005?  
Is it anything to do with IIS V5.1 or that I am running it locally and it is using VS2005 Virtual Server.

I would appreciate any help in this matter.

Question by:burness-dev
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
LVL 21

Expert Comment

ID: 20328321
try using absolute path instead of a relative path
instead of Response.Redirect("AspPage.asp") try Response.Redirect("www.aspsite.com/AspPage.asp")

Author Comment

ID: 20338260
The problem is it is not a Web Site I am dealing with - it is a web application.

I take it that I would then change to do the following:

Response.Redirect("http://ServerName/Virtual Directory of App in IIS//subdirectory/requiredaspfile.asp")

This may not get around the problem of the asp page not being allowed to execute

I will try this and see if it works.  I will also set the project up on a Web Server running 2003 and IIS 6.0 and then point Visual Studio over to this to see if I get better results.
LVL 21

Expert Comment

ID: 20346156
Sure it should work. If the URL works when you manually type it in the browser, it should work when used through redirect also
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.


Author Comment

ID: 20350180
The problem with the asp pages not running seem to stem from Visual Studio Development Server not being able to run asp pages.

Thinking that the problem was IIS I migrated the code over to a Test Webserver.

When setting up the project application settings under the Web tab for debugging I set the 'Use IIS Server' and set the vitual path of where the application sits.  E.g. http://Webserver/Website/Application Driectory.

I also set the Start Page as the Start page for the Application.

The web.config file has the setting <compilation defaultLanguage="vb" debug="true" />

The problem I am getting now is that although remote debugger is launching it will not show anything in the browser and throws the following error:

No symbols have been loaded for this document.

I would be appreciative if someone could shed some light on this.
LVL 21

Expert Comment

ID: 20359637
You are trying to debug a ASP application from Visual Studio?

You might want to check this out too

Author Comment

ID: 20364374
The Web Application was originally written in VS2003 and then converted over to VS2005,  therefore it is a .Net Application.

It sometimes calls an asp page.

The problem however is that we cannot get remote debugging to work.
LVL 21

Expert Comment

ID: 20374292
I was going through ur initial post. I saw this error "The extension '.sap' may be incorrect. " 

Author Comment

ID: 20380740
Had a look and it was a typo on my part - The error mentions .asp not .sap.

LVL 21

Expert Comment

ID: 20381404
>>The problem however is that we cannot get remote debugging to work.
What process do you use to remotely debug?
Are you trying to debug the ASP .net pages or the Classic ASP pages

Author Comment

ID: 20381540
Thanks for your patience.

We are attaching to the Msvsmon.exe process.

This is running on the web server as a service.

We are trying to debug VB.NET code

Hope this helps.  Thanks

LVL 21

Accepted Solution

surajguptha earned 2000 total points
ID: 20381827
ohhh cool. I am not sure if you have followed all the steps to use the remote debug mon.
can you quickly skim through this article which contains a step by step process to start remote debugging to see if you have followed all the steps?

Expert Comment

ID: 20591198
Forced accept.

EE Admin

Featured Post

Introducing Priority Question

Increase expert visibility of your issues by participating in Priority Question, our latest feature for Premium and Team Account holders. Adjust the priority of your question to get emergent issues in front of subject-matter experts for help when you need it most.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us here at EE write code. Many of us write exceptional code; just as many of us write exception-prone code. As we all should know, exceptions are a mechanism for handling errors which are typically out of our control. From database errors, t…
Today I had a very interesting conundrum that had to get solved quickly. Needless to say, it wasn't resolved quickly because when we needed it we were very rushed, but as soon as the conference call was over and I took a step back I saw the correct …
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question