Login failure during "Loading output"
search cancel

Login failure during "Loading output"


Article ID: 88712


Updated On:


CA Automic Applications Manager (AM)


Login failure during "Loading output"


Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent


Detailed Description and Symptoms

You enter your user name and password at the login screen and click OK. A progress bar is displayed, and the logon continues until it gets to the "Loading output" step. After a couple of minutes, the following error message is displayed:

ErrorMsg: E005043 Not all data was retrieved, row limit exceeded (10/7/02 2:31 PM)
Details: Output


You can clear the error message and the login will complete successfully.

The Output window row limit has been exceeded (500 entries). This is due to too many outputs tagged with the LOG status. Each time an Application Manager user connects with the Java client, it will read all outputs with LOG status. If a user has not been checking the Output window regularly, the number of entries can exceed the 500 limit.


Normally a user will check the Output window for recent output, then hide the output entries using the HIDE button. This prevents the above problem from occurring.

If outputs are normally viewed in Explorer, then the modules that have the default output set to LOG should be changed to STORE. This will prevent the Output row limit from being exceeded because modules marked STORE are not displayed in the Output window.

Changing History Records from LOG to STORE

If you want to change all LOG outputs to STORE in History, simply run the OLDPRTS module that ships with Application Manager.

Updating Module and Chain Component Definitions from LOG to STORE

To change modules with LOG output functions to STORE:

 Please contact Automic Support for SQL statements.