>
 



Remote desktop connections remain active until the logged in user selects "Log Off" from the Start Menu. If a user closes the remote desktop window without logging off, the user will still remain logged on.

Only up to two simultaneous Remote Desktop connections are allowed by default and active and disconnected sessions are calculated in this connection limit.

If a third simultaneous attempt is made to login to the server "The terminal server has exceeded the maximum number of allowed connections" error will be shown to the user, and they will be unable to complete the login process.

More...

Currently rated 4.8 by 5 people

  • Currently 4.8/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5



After taking a web application online, you need to track exceptions and errors effectively in order to debug problems. ELMAH (Error Logging Modules and Handlers) is an application wide error logging facility which is completely pluggable therefore it can be added to a running ASP.NET web application without any need for compilation or deployment.

HTTP modules and handlers can be used in ASP.NET to provide a high degree of componentization for code that is orthogonal to a web application, enabling entire sets of functionalities to be developed, packaged and deployed as a single unit and independent of an application. ELMAH (Error Logging Modules and Handlers) illustrates this approach by demonstration of an application-wide error logging that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.

Elmah Project Site

Elmah logs nearly all unhandled exceptions. It offers web pages to remotely view the exception log and its details. Even if customErrors mode in web.config file is turned off, you can view the yellow error screen. It offers notifications via e-mail and an RSS feed of the error log. 

Elmah offers a web page to remotely view the exception log.
Elmah offers a web page to remotely view the exception log.


Elmah offers a web page to remotely view the exception log detail.
Elmah offers a web page to remotely view the exception log detail.


To learn more about ELMAH, see the MSDN article Using HTTP Modules and Handlers to Create Pluggable ASP.NET Components by Scott Mitchell and Atif Aziz.

Currently rated 5.0 by 2 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5



After Migrating the application to work with the Integrated .NET mode, you might come across a problem: Server Error in Application "WebSiteName" - HTTP Error 401.3 – Unauthorized 

HTTP Error 401.3 – Unauthorized
HTTP Error 401.3 – Unauthorized


Resolving HTTP Error 401.3 – Unauthorized Error
Resolving HTTP Error 401.3 – Unauthorized Error


Click on Authentication and click edit after choosing Anonymous Authentication. In the opening window select Application Pool identity and click OK.

Resolving HTTP Error 401.3 – Unauthorized Error - Application Pool Identity
Resolving HTTP Error 401.3 – Unauthorized Error - Application Pool Identity

 

Currently rated 4.9 by 10 people

  • Currently 4.9/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5



You might have come across to the following “HTTP Error 500.0 - Internal Server Error” while working on Windows Vista. 

HTTP Error 500.0 - Internal Server Error
HTTP Error 500.0 - Internal Server Error


Follow the directions shown on the error message to resolve the problem:

You can migrate the application configuration, including the contents of the configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "bloggingdeveloper/"

1) Migrate the application to work with the Integrated .NET mode (PREFERRED).

You can migrate the application configuration, including the contents of the configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "bloggingdeveloper/"

After you migrate your application, it will run in both Classic and Integrated .NET modes, as well as on downlevel platforms.

2) Move this application to an application pool using the Classic .NET mode.

You can move the application to the default application pool using the Classic .NET mode by running the following from an command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE set app "bloggingdeveloper/" /applicationPool:"Classic .NET AppPool"

Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.

Currently rated 5.0 by 3 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5



You might have come across to the following “HTTP Error 500.19 - Internal Server Error” while trying to create IIS 7.0 web site on Windows Vista. Actually Microsoft has tightened the security on Windows Vista and most of the time it is annoying when it asks your permission. 

HTTP Error 500.19 - Internal Server Error
HTTP Error 500.19 - Internal Server Error


To resolve this problem:

Compile the project and place the deployable files under C:\Inetpub\wwwroot\. Make sure that the physical path of the respective Application (e.g. BloggingDeveloper in above error case) under IIS now points to new path.

OR

Browse your application root folder and add group IIS_IUSRs.

Resolving HTTP Error 500.19 - Internal Server Error
Resolving HTTP Error 500.19 - Internal Server Error

 

Currently rated 5.0 by 4 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories : IIS 7.0 | Errors | All
Share & Support : del.icio.us | DZone it! | Kick it! | digg it! | Furl | Technorati