Some notes on software development... RSS 2.0
# Friday, 02 May 2014

When using ASP.NET web services, if you see this error:

image

…it may be caused by the ISAPI & CGI Restrictions not being set correctly in IIS. From the root computer node in IIS manager select ‘ISAPI and CGI Restrictions’:

image

…and ensure that the .NET version you are using has the Restriction value set to ‘Allow’:

image

Friday, 02 May 2014 08:25:29 (GMT Standard Time, UTC+00:00)  #    -
ASP.NET | IIS
# Thursday, 22 March 2012

The below table lists the default User & Group accounts used by IIS6 & IIS7:

  Built-in User Built-in Group
IIS6 IUSR_MachineName IIS_WPG
IIS7 IUSR IIS_IUSRS

Links
Understanding Built-In User and Group Accounts in IIS 7

Thursday, 22 March 2012 10:48:50 (GMT Standard Time, UTC+00:00)  #    -
IIS
# Monday, 24 November 2008

IIS on Windows XP has a default concurrent connection limit of 10 for the root website. Any connections made after 10 connections are being used up are greeted with a HTTP 403.9 Access Forbidden: Too many users are connected error message.
The default connection limit can be changed to the absolute maximum of 40 concurrent connections using the IIS adsutil.vbs administration script:


First you need to set the default windows script host to be the console. Do this by running the following command:

cscript //h:cscript


image

Next run the adsutil.vbs script from the Inetpub\AdminScripts like so:

C:\Inetpub\AdminScripts\adsutil set w3svc/MaxConnections 40

image

Job done!

Monday, 24 November 2008 10:48:56 (GMT Standard Time, UTC+00:00)  #    -
IIS | Web Dev | Windows
Navigation

Sign In
Extras
Statistics
Total Posts: 116
This Year: 0
This Month: 0
This Week: 0
Comments: 36
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2017
Hadrian Phillips

All Content © 2017, Hadrian Phillips
DasBlog theme 'Business' created by Christoph De Baene (delarou)