ANS1999E Incremental processing of '/usr' stopped

benmartins

ADSM.ORG Member
Joined
May 1, 2007
Messages
19
Reaction score
0
Points
0
I am getting this error:
ANS1999E Incremental processing of '/usr' stopped

With this error,tsm is failing while trying to backup this client.Any ideas?Thanks.
 
Hi,

ANS1999E type of the operation processing of ’filespace-name’ stopped.

Explanation: The client has encountered a condition where it can not continue processing the specified file space. The TSM client error log or schedule log should contain additional messages related to this error.
System action: Processing stops.
User response: Check the TSM client error log and schedule log for any additional messages related to this error. Take any corrective action that might be suggested by the related messages, then try the operation again. If the problem persists, contact your TSM administrator for further assistance.


So, what do the log files say?

Harry
 
0/02/07 10:55:53 PrivIncrFileSpace: Received rc=131 from fioGetDirEntries: /usr /
lpp/bos/bos.rte.filesystem/5.3.0.52/inst_root/sbin/helpers/jfs2
10/02/07 10:55:53 ANS1999E Incremental processing of '/usr' stopped.
10/02/07 10:55:53 ANS1028S An internal program error occurred.
10/02/07 17:20:31 ANS9505E dsmc: cannot initialize the DMAPI interface. Reason: Oper
ation not permitted.
.
The administrator for your system must run TSM and enter the password to store it loca
lly.
10/02/07 17:20:31 ANS1520E Failure writing to the Tivoli Storage Manager error log:
errno = 13, The file access permissions do not allow the specified action.
10/02/07 17:21:03 TransErrno: Larger than errno in opendir, errno = 127
10/02/07 17:21:03 PrivIncrFileSpace: Received rc=131 from fioGetDirEntries: /usr /
lpp/bos/bos.rte.filesystem/5.3.0.52/inst_root/sbin/helpers/jfs2
10/02/07 17:21:03 ANS1999E Incremental processing of '/usr' stopped.
10/02/07 17:21:03 ANS1028S An internal program error occurred.
 
benmartins-

Is this a new client or previously installed client that started to failing it backup?
It seem like, client was no install with Root or admin level of authority.
Try re-install with Root or server Admin authority and reset client password node
on the server.

"The administrator for your system must run TSM and enter the password to store it loca
lly"
 
Back
Top