Skip to main content

Online license problems

Cannot log in​

You tried to log in with your Asprova ID to authenticate Asprova My Schedule with an online license, but the login failed with a "could not log in" message.

Simple causes​

First, check for the possibility of simple causes.

Check the Asprova ID username and password​

Confirm that you can log in through a channel other than Asprova My Schedule, for example the Asprova ID My Page.

If you cannot log in through other channels either, it is likely that the username or password is wrong. Please try resetting your password.

Check the internet connection of the server where My Schedule is installed​

On the server where My Schedule is installed, try accessing something like the Asprova ID My Page using a browser such as Microsoft Edge. If you cannot access it, check the server's internet connection.

Resolution​

If the server has an internet connection and the Asprova ID information is correct but you still cannot log in, the following causes are possible.

The My Schedule server application's communication to the internet is blocked by a firewall or similar​

In Windows Firewall, outbound communication by applications is permitted by default, but if you operate it on a whitelist basis, you need to add the server application (AsprovaWS.exe) to the whitelist. Also, if EDR software is installed in your environment, check the EDR tool's settings as well.

An HTTP proxy must be used for the server to connect to the internet​

The My Schedule server application does not automatically read the proxy settings from Windows, so if Windows is configured to use a proxy, communication works in Microsoft Edge and the like but fails in My Schedule. In this case, you need to make the proxy server location explicit to the server application. For how to do this, see /docs/server/proxy.

A transparent proxy is present​

If a transparent proxy that performs TLS inspection is present, the server application does not trust the certificate that proxy presents, so communication fails. Because the server application does not have a feature to recognize user-added certificates, you need to add the following entry to the transparent proxy's inspection exclusion list.

  • Protocol: HTTPS (port 443)
  • Destination: www.asprova.com (our server)
  • Source: specify the server where My Schedule is installed