We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Why am I not able to run Syncfusion ASP.Net sample in the sample browser? Also error occurs when I try to open samples from its installed location, though my virtual directory settings are correct.

 

Error: Unable to open Web project 'ProjectName'. The file path 'FilePath' does not correspond to the URL 'ProjectURL'. The two need to map to the same server location. Error:404 object not found.

This error in an Asp.Net project might occur in various scenarios.

Here as the virtual directories and other settings are correct, it could be because your system might not allow the usages of period ('.') symbol in virtualdirectoryname. Also you might either be using IIS 6.0, IIS 5.0 or later with UrlScan and IISLockdown.

See here for more details on UrlScan and IISLockdown.

Solution

To rectify this, set 'AllowDotInPath=1 which allow dots that are not file extensions' option in URLScan, that allows '.' operator to be used in virtual directory name.

Visit the following link to know more on virtual directory settings:

http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3FrontBack/05153ee0-9b66-4176-aa40-e7867d46ec9c.mspx?mfr=true

About Urlscan

Many attacks launched against web servers involve a maliciously crafted URL. The URL may be unusually long, may be encoded by an alternate character set or may include character sequences which are not common to a legitimate request. Such URLs, if processed by the IIS server, may cause severe damage to the server and/or the web site hosted by it. In order to prevent this, Microsoft has developed a tool known as Urlscan.

As the name suggests, Urlscan scans all incoming URL requests. Based on a set of pre-established rules, Urlscan filters out the request and sends only valid data to the server process. It provides an option to store the filtered requests in a log file.

It is important to note that Urlscan is practically obsolete with IIS 6.0. Most of the features provided by Urlscan have either been implemented by default in IIS or can be enabled by simply modifying registry keys.

Article ID: Published Date: Last Revised Date: Platform: Control:
994 04/30/2011 07/10/2014 ASP.NET Web Forms (Classic) General
Tags:
Did you find this information helpful?
Add Comment
You must log in to leave a comment

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.