Troubleshooting Problems on AWI Clients

If you experience display or handling issues when using AWI, or you are not able to log in the way you normally do, check whether this comes from one of the known issues.

If you experience any of these problems, see the solution suggestions here.

This page includes the following:

Port already in use Error when Configuring AWI

As a system administrator, I am configuring the network settings (http.port). I get a Port already in use error when trying to overwrite the default value.

Solution: Check Instances, Browsers, Port

  • To make sure that no other instance is running, check the console tab in Eclipse
  • Close your browsers. Some lingering WebSocket connections might be blocking the port
  • Change the port if you have multiple repositories and multiple Eclipse instances running

Error: java.net.BindException: Address already in use: bind

As a system administrator, I am installing and configuring AWI.

For Installations with the Jetty Launcher

There are several causes for this error:

  • The Jetty launcher has been started twice by accident.

    Solution: Close all instances of the launcher and try again

  • A stale WebSocket connection might be preventing the OS from freeing the port

    Solution: Close all browser windows on your local machine, or reboot.

  • The launcher has been configured to use a port already in use. For example, it has been configured to use 8080 but another application server (for example Tomcat) is still running.

    Solution: Enter a different port in the configuration.properties file or stop the process of the foreign service that is using the port.

I can't log in because the session expired

On the AWI login page, I cannot log in and I get a warning that the "Session expired" although I haven't even logged in yet.

Solution: Allow cookies on your browser.

AWI can only work with cookies enabled.

The AWI screen is blank

I just logged in and I see the menu bar, but other than that the screen is blank.

Solution: Empty your browser's cache

If your AWI instance has been upgraded, then you need to empty your browser's cache and log out and back in. Even if you don't do this, if you select a perspective from the menu bar, the perspective opens. It's still a good idea to empty your cache before using a new version.

Kerberos login is not available

On the AWI login page, I see the warning message "Kerberos login is not available" and I can't sign on with my Windows name and password.

Note: This error message indicates that AWI expects that you are setup to be able to log into AWI with the same name and password which you log into your computer with. This capability is known as "single sign-on" (SSO). The system uses the Kerberos authentication protocol to manage SSO.

Solution: Use default login

If you have been able to login with your Windows name and password, but you are now trying to log in from a different computer or different domain, it could be that Kerberos is not installed on that resource. In this case, you need to login with your username and login information.

More information:

Solution: In Firefox allow the AWI help pop-up

If you are trying to log into AWI on a Firefox browser, then you need to enable single sign-on in your browser with the following steps:

  1. In the address bar of your Firefox browser window, type "about:config" and press Enter.
  2. Confirm that you accept the risks of changing configurations by clicking I promise, I'll be careful!
  3. Search for "network.negotiate-auth.allow-non-fqdn".
  4. Double-click the Value to change it to "true".
  5. Close the window and try logging into AWI again.

You can test whether the problem is in Firefox by trying to log into AWI on Google Chrome or Internet Explorer. If there is no problem there, then use the previous steps to configure Firefox.

If this does not help, then contact your system administrator. There might be a problem in the configuration of your environment.

I can't unpin the AWI Message window

I would like to AWI messages appear in a separate window, but I can't unpin the Messages panel from the main pane when monitoring process executions.

Solution: Disable pop-up blockers

Disable pop-up blockers in your Internet browser.

Screen text is cut off and other things look strange

After an AWI upgrade, you notice display problems, like text on buttons, labels and links being cut off.

Solution: Empty cache to retrieve latest stylesheet

Your browser is still using an old version of the AWI stylesheet, which it has stored in its cache.

Empty the cache of the browser and login to AWI again. With the new login, you browser will retrieve the latest AWI stylesheet. For instructions about emptying the cache, see the user help for your internet browser. For example, for Microsoft Internet Explorer, you can do this by pressing Ctrl + F5.

I can't open the online help

I can't open the AWI online help from the menu.

Solution: Allow the AWI help pop-up

Allow pop-ups for blockers of the AWI help URL (http://docs.automic.com/) in your Internet browser.

If your company security policy prohibits employees having Internet access, then you cannot access the default location of the online help. In this case, contact your administrator and request that the AWI online help is placed on a secured intranet. For more information, see configuration.properties - Configuring Your Local Setup.

I can't find my object in search

I just added an object and I can't find it when I search.

Solution: Wait a bit

Wait a minute and try again.

To make global search work quickly without compromising other system processes, AWI does not read directly from the database. Instead, AWI loads the searchable fields of all objects into a separate indexed search file, which it updates in short intervals. This means there can be a short lag before newly added or edited objects show up in the search results.

Bad Performace due to Poor Connection

For Installations with Tomcat

To improve performance on browsers with poor connections, adapt your Tomcat configuration so that Tomcat uses the NIO2 connector and the upload timeout attribute is enabled.

To do this, open the <Tomcat>/conf/server.xml file and edit it as follows:

Before:

<Connector port="8080" protocol="HTTP/1.1"

     connectionTimeout="20000"

     redirectPort="8443" />

After:

<Connector port="8080" protocol="org.apache.coyote.http11.Http11NioProtocol"

     connectionTimeout="20000"

     redirectPort="8443"

     disableUploadTimeout="false"

     connectionUploadTimeout="10000"/>

For complete information about the Tomcat connector configuration attributes, see https://tomcat.apache.org.