Troubleshooting License Server Issues

If users are not able to open XML files because Web Author cannot obtain a valid license, there are several things that could cause this issue.

Web Author Connection Details for the License Server are not Configured Correctly

You can go to the Administration Page and select License to check the License Server connection.

This problem is linked to the deployment setup that you chose. There are several possible causes:

On Windows, there is an anti-virus software or firewall that blocks the connection between Web Author and the License Server. You may need to add exceptions for this connection.
Due to the server configuration, Web Author uses IPv6 to connect to the License Server. You can force IPv4 by setting the following System Properties:
```
-Djava.net.preferIPv4Stack=true
-Djava.net.preferIPv4Addresses=true
```
You can also set the address that the server listens for by editing the [WEB_AUTHOR_INSTALL_DIR]/tomcat/conf/server.xml file and adding the address="0.0.0.0" attribute to the <Connector> element.
The connection passes through an HTTP proxy server that blocks this connection. You can add an exception in Web Author for the License Server using the Proxy Configuration Page.
The License Server uses a self-signed HTTPS certificate (or another certificate that is not trusted by default in Java). In this case, you can go to the Administration Page and select Connection to configure Web Author to accept any HTTP certificate.

To gather more information about the problem:

Enable verbose HTTP logging in Web Author.
Check the application server access logs to check whether requests made by Web Author are received by the License Server.
Check the License Server Management and Statistics pages.

This might include:

Most of these problems can be checked by going to the License Server's administration page.