If your Venio web site is not functioning properly, here are some basic things to check:
- Make sure the application pool is set to use .NET Framework v4.0.30319 or later. This can be configured in IIS Manager under the Advanced Settings for the application pool.
- Check that the identity of the application pool is utilizing the same credentials to to access files and folders as the Venio Export Service.
- Verify that the application pool is not recycling too frequently. Frequent recycling can cause intermittent errors. Configure recycling settings under Advanced Settings.
- Check for maximum worker process crashes under Advanced Settings. Too many crashes may indicate a problem with your application code or dependencies.
A 502.3 Bad Gateway error usually indicates a communication problem between IIS and the application pool. Try these troubleshooting steps:
- Restart the application pool in IIS Manager.
- Recycle the AppDomain in IIS Manager using the Recycle button.
- Verify the application pool identity has access to the app's folders and files.
- Check for maximum worker process crashes. Too many crashes can cause communication issues.
- Make sure your web.config has a httpRuntime targetFramework set for .NET 4.5.
If your app returns 403 errors, check the following:
- Verify NTFS permissions on the app's folders allow access by the application pool identity.
- Check that authentication settings in IIS allow anonymous access if required.
- Confirm your web.config has proper authorization rules for folders and files.
- Disable Windows authentication in IIS if not needed. Enable anonymous authentication.
¶ Additional articles and Resources:
When encountering the HTTP Error 500.19 while trying to access the login.aspx page, you will see the following error message:
HTTP Error 500.19 - Internal Server Error
Follow the steps in the following Wiki page for detailed troubleshooting: HTTP Error 500.19