Web Connection
500 Internal Server Error when trying access static connect
Gravatar is a globally recognized avatar based on your email address. 500 Internal Server Error when trying access static connect
  Simon White
  All
  Jul 8, 2017 @ 06:55pm

Hi I have a number of virtual directories setup under my website. All of them work except one. They were all configured at the same time in the same way but on the "wconnect" virtual directory I always get a "500 - Internal server error." The security settings are the same for all the folders to which the virtual directories point. Does anyone have any suggestions for the solution to this problem. This a brand new Windows 2016 server I am setting up. My web-connection applications all work fine. I just cannot access anything in the "wconnect" virtual directory.

Thanks, Simon

Gravatar is a globally recognized avatar based on your email address. re: 500 Internal Server Error when trying access static connect
  Rick Strahl
  Simon White
  Jul 9, 2017 @ 10:43am

If you plan to run Web Connection in one of those folders make sure you mark the folder as an Application not a Virtual. Virtuals are just folder mappings while virtual applications get their own application environment and AppDomain. Web Connection requires an Application to run properly.

Regardless though, static pages should just work, but most likely you have a configuration issue in your web.config. You can try renaming web.config to something else and see if you can then access the static pages. If that's not it then permissions are the next likely culprit.

The best thing you can do to troubleshoot is access the page locally from the server (if possible) and look at the error information that the server returns then - IIS error info is only displayed on local access.

+++ Rick ---

Gravatar is a globally recognized avatar based on your email address. re: 500 Internal Server Error when trying access static connect
  Simon White
  Simon White
  Jul 10, 2017 @ 06:15am

Thanks Rick for your suggestion about accessing the page locally to get more error details. This showed me that there was a web.config error in the dCipherComputing website. It was trying to add a handler at the wrong level. Once I removed this everything worked fine.

Simon

© 1996-2017