Essentially any row with the status of "5" is in a "Waiting" status Log into the Application Repository and verify under Activities that the hung Activity now shows as Aborted. Select the aborted activity and click on Remove Selected to delete.
The common log (sometimes called Common Logger) allows you to view information related to deployed applications and orchestrations. The common log data is stored in a database, as defined in the SBM Configurator. The data is only visible from the SBM Application Repository and from SBM Composer. It is best practices to prevent this log from growing too big.
Check the target servers are defined correctly for the environment. If they are using localhost then try using the server name. Also please clear the browser cache.
There are a couple things that cause this error. If there are multiple environments setup in the Repository, make sure that JBoss is running in each environment. The following kb doc S138442 will help if there are too many records in the Common Log table for the UI to display and how to clear them manually.
No Simply logging into App Repository doesn't consume a license but doing a deploy will consume a license because it needs to login to Application Engine and run web services at that point.
When you attempt to login to the Application Repository you see an error "Internal Server Error (500)" Look for the following errors in the followng two files on the SBM server. C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\server.log
One of the key elements for SSO and application repository to function correctly is the Gsoap virtual directory. It is always wise to test that this URL is accessible:
