Stop/Start IIS from DOS Prompt

iisreset.exe /restart
To see more information about iisreset.exe,
type on the MSDOS command line
iisreset /?

Other commands

net start iisadmin
net stop iisadmin

Parse Error Message: Could not load 'WebApplication1. global while accessing ASP.Net Web Site

Parse Error Message: Could not load 'WebApplication1. global while accessing ASP.Net Web Site

You may receive the following error when browsing an asp.net application.
Parser Error Message: Could not load type 'WebApplication1.Global'

The solution I found for this was to Check the ASP.NET properties in IIS. It was displaying incorrect .net version, I then changed the setting to the correct version and again clicked apply than OK to exit. I was than able to display the web page without the error message
Hope it helps U!

Error-‘unable to find script library '/aspnet_client/system_web/1_1_4322/WebUIValidation.js’

Error-‘unable to find script library '/aspnet_client/system_web/1_1_4322/WebUIValidation.js’
We were getting following error in of our Asp.net(.net framework 1.5) website

‘unable to find script library '/aspnet_client/system_web/1_1_4322/WebUIValidation.js’

This error mostly occur if you are using validation controls in your website

The aspnet_client folder contains the WebUIValidation.js which is required to handle the asp.net validation controls.

After googling on web I did find following which you may also find useful:


If the aspnet_client folder is missing in the IIS virtual directory listing you may encounter the above error. to resolve this, you may need to run the following from command prompt

%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -c

This will install the aspnet_client folder to the default virtual directory website.

Further, if you are using a sub-virtual directory you need to have this aspnet_client folder in your root directory as well.



if you are still having this issue try following:

a) IIS Manager-->Web Sites-->Default Website-->aspnet_client

Properties-->Directory Security-->

Edit IP Address and Domain Name Restrictions

Make sure, by default, all computers will be granted permission.

b) Another potential cause of this error is that your default website is set to .NET Framework 2.0, and you're trying to debug a .NET Framework 1.1 application. In this case, you can change the setting on the ASP.NET tab of the Default Web Site's properties

c)Check if the script files directory(/aspnet_client/system_web/1_1_4322/) in IIS manager to see whether it has been granted read access.

The name 'Session' does not exist in the current context

This error normally occurs when you are trying to access the value of a session variable such as Session["StickID"] and you're not doing that from a webform, usercontrol or a class that inherits from System.Web.UI.

In this situation you can still access the session variable, but using a different path.
For example to access a session variable named StockID you would normally use Session["StockID"]

however, if the error The name 'Session' does not exist in the current context is returned, use the following path for retrieving the value of the session variable:

HttpContext.Current.Session["StockID"]

We may get a Page cannot be found message when we browse aspx pages in a Windows Server 2003 environment.

We may get a Page cannot be found message when we browse aspx pages in a Windows Server 2003 environment.

That is because in Windows 2003, all the webservice extensions are "Prohibited" by default to ensure security.

To resolve this, do the following steps:-

1. Go to IIS Manager or From your Run command, type inetmgr and press enter.
2. Expand the appropriate nodes in the IIS to locate the "Webservice Extensions" Node
3. Click on the same.
4. You will find a list of "prohibited" extensions in the right.
5. Click on ASP.NET and "allow" it

That should resolve this issue.

This article applies for Windows Server 2003, IIS 6.0 environment.