Messages


Chapter 9. Enterprise Management (2500-2999)



ANS2600SBrowser trying to establish connection to client; received socket exception: exception-name

Explanation: The browser received the exception exception-name trying to connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Determine what might be causing this kind of an exception. Validate that the LAN is up and that you are trying to connect to the correct port number.



ANS2601SBrowser trying to establish connection to client; received unknown host exception: exception-name

Explanation: The browser received the exception exception-name trying to connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Retry the operation. If it persists, determine what might be causing this kind of a problem. Determine if your LAN went down. Determine if you are trying to connect to the correct TSM client machine.



ANS2602SBrowser trying to establish connection to client; received IO exception: exception-name

Explanation: The browser received the exception exception-name trying to connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Determine what might be causing this kind of an exception. Retry the problem, and check if the LAN is down.



ANS2603SBrowser trying to establish connection to client; received exception: exception-name

Explanation: The browser received the exception exception-name trying to connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Determine what might be causing this kind of an exception. Determine if the LAN may be down, or if the TSM Client Acceptor Daemon on the TSM machine is up and running.



ANS2604SThe Web client agent was unable to authenticate with the server.

Explanation: The TSM Web client agent was unable to authenticate with the TSM server.
System Action: The TSM operation ends.
User Response: One possible solution is to run the command line client so that the client password can be re-entered. Another approach is to check the error log on the TSM Web client agent for any relevant messages.



ANS2605SBrowser could not re-establish connection to client; received protocol error.

Explanation: The browser received a protocol error trying to re-connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Determine what might be causing this kind of an error. Determine if the TSM browser and the TSM client code might be out of sync.



ANS2606SAn invalid password was sent to the server.

Explanation: The TSM password that was sent to the TSM server was invalid.
System Action: The TSM operation ends.
User Response: Make sure that you have the correct password. Also make sure that it is valid, for example it is not too short.



ANS2607SBrowser could not establish connection to client.

Explanation: The TSM browser could not connect to the TSM client machine.
System Action: The TSM operation ends.
User Response: Determine what might be causing this kind of a problem. Determine if the LAN is down, or if the TSM Client Acceptor Daemon on the TSM machine is up and running.



ANS2608SNothing was selected so no operation was performed.

Explanation: No object was selected in the GUI for the operation to be performed upon.
System Action: The TSM operation ends.
User Response: Make sure you select one or more objects (volume, directory or file) in the GUI before clicking on the operation to be performed.



ANS2609STCP/IP communications failure between the browser and the client machine.

Explanation: This error can occur due to any of the following:
System Action: The TSM operation ends.
User Response: Retry the operation and make sure the LAN is up. Also check that the port number is correct, and that the Client Acceptor Daemon is started and running on the TSM client machine, and that it is listening on the correct port number.



ANS2610STCP/IP communications failure between the client and the server machine.

Explanation: This error can occur if the LAN connection between the TSM client machine and the server machine went down.
System Action: The TSM client ends.
User Response: Retry the operation and make sure the LAN is up. Make sure that both the TSM server and the TSM client are up and running.



ANS2611SAn unknown error occurred in the browser.

Explanation: An unknown error occurred in the applet running in the browser.
System Action: The TSM operation ends.
User Response: Retry the operation. If the problem persists, turn on tracing and see if the trace to the browser console gives the reason for the error.



ANS2612SAn unknown error occurred in the client Please check the TSM Error Log for any additional information

Explanation: An unknown error occurred in the TSM client.
System Action: The TSM client ends.
User Response: Retry the operation. If the problem persists, check the TSM Error Log for any additional information.



ANS2613SA protocol error occurred in communications between the browser and the client.

Explanation: A protocol error happened between the applet running in the browser and the TSM client.
System Action: The TSM operation ends.
User Response: Retry the operation. If the problem persists, turn on tracing and see if the trace to the browser console gives the reason for the error.



ANS2614SA protocol error occurred in communications between the client and the server.

Explanation: A protocol error happened between the TSM client and the TSM server.
System Action: The TSM client ends.
User Response: Retry the operation. If the problem persists, check the TSM Error Log for any additional information. Verify that you are running the correct applet with the appropriate level of the client.



ANS2615SThe user ID entered does not match the nodename configured on the client machine.

Explanation: The user ID that was entered is not the same as the nodename on this TSM client.
System Action: The TSM operation ends.
User Response: Verify that the nodename entered is configured correctly on the TSM client.



ANS2617SThe destination directory specified is invalid.

Explanation: The user specified a destination target directory for restore or retrieve which is invalid.
System Action: The TSM operation ends.
User Response: Retry the operation specifying a valid directory name.



ANS2618SBrowser trying to retrieve resources; received resource exception: exception-name

Explanation: The browser received the exception exception-name trying to retrieve resources from the TSM client machine.
System Action: The TSM operation ends.
User Response: Verify that the resources are installed correctly on the TSM client machine.



ANS2619SThe Client Acceptor Daemon was unable to start the Remote Client Agent.

Explanation: The TSM Client Acceptor Daemon could not start the TSM Remote Client Agent.
System Action: The TSM operation ends.
User Response: Check the error log on the TSM Web client agent for any relevant messages. Then correct the problem and retry.



ANS2620WThe expand entire branch operation may take a long time, and cannot be canceled once it has started. Are you willing to wait for the operation to complete?

Explanation: The expand entire branch operation could take a long time and cannot be canceled once it is started.
System Action: Processing stopped; waiting for user intervention.
User Response: Answer 'Yes' to start the expand entire branch operation. If you answer 'No', the current operation will be canceled.



ANS2621WThis function is not available on the client platform

Explanation: The browser received a request that is not available on the TSM client machine. For example, registry backup and restore are available only on the Windows platform.
System Action: The TSM operation ends.
User Response: Request only those functions that are valid for the platform of the TSM client machine.



ANS2622SInvalid ID or password submitted.

Explanation: An invalid ID or an invalid password was submitted.
System Action: The TSM operation ends.
User Response: Verify that the ID and the password that you entered are correct. If going to a different server (for example by hyperlinking) then make sure that the different server has the same ID defined with the same password.



ANS2623SWeb Client applet level is out of sync with Web Client agent.

Explanation: The Web Client applet and Web Client agents are at incompatible levels.
System Action: The TSM operation ends.
User Response: Verify that you have the correct level of the applet installed with the client, and that an incorrect level of the applet was not placed in the install directory.



ANS2624EThis operation requires client owner authority.

Explanation: Your user ID has insufficient authority to perform this operation.
System Action: Processing continues, but the user is not allowed to do this operation.
User Response: Do not perform this operation, or get a higher authority level for your user ID in order to perform this operation.



ANS2625ENode does not support this image operation.

Explanation: Node does not support or is not configured to perform this image operation.
System Action: Processing continues, but the user is not allowed to do this operation.
User Response: Verify whether this image related operation is supported or configured on the target platform.



ANS2641ERegistry Backup failed

Explanation: TSM An error occurred while backing up the registry.
System Action: Registry backup function fails.
User Response: See your system administrator.



ANS2642EAn Error occurred creating the registry directory structure

Explanation: An error occurred while creating the directory structure to save/replace registry key.
System Action: Registry function fails.
User Response: See your system administrator.



ANS2643EAn error occurred saving the registry key

Explanation: The active registry key cannot be saved.
System Action: Registry backup operation terminates.
User Response: See your system administrator.



ANS2650EAn error occurred replacing the registry key

Explanation: The backed up registry key(s) were restored from the server but cannot be made active into the registry.
System Action: Current Registry key remains active.
User Response: See your system administrator.



ANS2660ERegistry activation failed

Explanation: An error occurred while restoring the registry key from the server.
System Action: Registry restore function fails.
User Response: See your system administrator.



ANS2662EEvent Log Backup failed

Explanation: TSM An error occurred while backing up the event logs.
System Action: Event log backup function fails.
User Response: See your system administrator.



ANS2663EEvent Log Restore failed

Explanation: An error occurred while restoring the event logs from the server.
System Action: Event Log restore function fails.
User Response: See your system administrator.



ANS2664EAn Error occurred creating the event log directory structure

Explanation: An error occurred while creating the directory structure to save the event logs.
System Action: Event Log function fails.
User Response: See your system administrator.


[ Top of Page | Previous Page | Next Page | Table of Contents ]