Troubleshooting in WebSafetica
Modified on: Fri, Jan 27, 2017 at 3:38 PM
|Troubleshooting in WebSafetica|
When opening WebSafetica in a domain that is not certified, or using an address without a domain, a security exception must be approved in the relevant Web browser window. As the addition of an exception differs in each browser, the following procedure is only general:
- Open Advanced settings option in the window with the warning
- Then click on continue / add exception
- Confirm the addition of exception
Connection string wrong or missing
- The Index is outside the field limits.
- Login failed for user 'user'.
- Cannot open database "My_database_main" requested by the login. The login failed. Login failed for user 'user'.
Reason: Default Connection string in Internet Information Services Manager, hereinafter IIS Manager, is wrong or empty. The reason may be an update or missed change in the password.
- Open Internet Information Services Manager.
- In the left panel Connections open My_PC > Sites > Default Web Site> WebConsole.
- In the panel open Application settings and select DefaulConnection. Its value must match this format: server address;database_prefix;login_to_SQLServer;password_for_SQLServer (e.g. 192.168.15.115;My_database;user;trustno1)
Unable to load WebSafetica or localhost
- The provided anti-forgery token was meant for a different claims-based user than the current user.
- WebSafetica or address https://localhost cannot be loaded.
Reason: WebSafetica is already open in a web browser, try to close previous tab with WebSafetica or use F5 to reload page. If the problem persists, follow a guide and check the IIS Manager whether its working. The reason may be a failure in starting it, or an application occupying port 80 or 443.
- Start IIS Manager and make sure it is running (the Run button in the right bar Event is grey)
- Restart IIS Manager by pressing Restart button in the right bar.
- If IIS is still not started, an application is probably blocking port 80 or 443. Most often it is Skype or VMware
- Open the command line and enter netstat -aon | findstr : 80
- Sort the processes in the Task manager by PID and view the processes listed in the command line. If they are third-party applications, they should be stopped gradually until the port is free.
- If IIS Manager still does not start, repeat steps 4 and 5 for port 443 ( netstat -aon | findstr :443 )
- If the problem persists, restart the device.
Did you find it helpful?
Sorry we couldn't be helpful. Help us improve this article with your feedback.