Contents
1. KBWIN0001 - "Can't create output file: c:\tsm_images\setup\0x0404.ini"
2. KBWIN0002 - "Run-time error '70': Permission denied"
3. KBWIN0003 - "Run-time error '53': File not found"
4. KBWIN0004 - "Run-time error '5': Invalid procedure call or argument"
5. KBWIN0005 - "ANS1252W The server you are connected to does not support this function"
| Summary | This article will assist you in locating the reason that TSM is reporting error ANS1252W on your machine. |
| Symptom | Error message "ANS1252W The server you are connected to does not support this function" occurs when you attempt to start the TSM client software. |
| Cause | This message is misleading, and is only reported by early versions of TSM 6.1. It occurs when the TSM client is unable to connect to the HFS server. |
| Resolution | Please follow these troubleshooting steps:
|
| Status | Applies to older versions of TSM 6.1 only (TSM 6.1.2); either your node is locked or you do not have sufficient network connectivity to run TSM. |
| More Information | |
| Applies To | TSM, HFS, Windows |
6. KBWIN0006 - TSM Client does not load; a grey or white box appears
| Summary | This article will guide you resolving a Java client issue that prevents the TSM Client from loading. |
| Symptom | When attempting to start TSM, a grey box appears and the TSM software does not start. |
| Cause | The exact cause is unknown, but the cause is believed to be a conflict between the version of Java shipped with the TSM client and the graphics driver on the local machine. |
| Resolution | Please follow the instructions on our page concerning this Java problem to resolve the issue. |
| Status | Incompatible Java version - this is a workaround to resolve the issue. |
| More Information | This has currently been found to affect Dell Optiplex 780 machines which were shipped with Windows 7 and downgraded to Windows XP. The version of Java shipped with the TSM Client that is used within Oxford University is an IBM version of Java that was produced in approx. 2008. |
| Applies To | TSM, Java, Windows |
7. KBWIN0007 - "File Not Found" when attempting to restore data
| Summary | This article will guide you resolving a "File not found" warning message when attempting to perform a restore |
| Symptom | After selecting which files/folders to restore and clicking Restore, the task list appears
and states "Preparing".
After a period of time an warning message states "File not found". Clicking OK takes you back
to the restore screen.
|
| Cause | Possible Cause - A possible cause is that you are attempting a restoring from an old
machine to a new machine
and have left the Original location option set instead of selecting an alternative location -
this is required as when using the original location
the system uses the UNC path of the original files, e.g. \\oldnodename\c$\etc. Alternatively, perhaps
your machine has been renamed between backup and restore: in this case too, the UNC paths would not match. |
| Resolution | Please follow the instructions restoring data to a new machine.. |
| Status | You must select Following location when restoring data to a different machine, and then select a place to restore data to. |
| More Information | |
| Applies To | TSM, Windows, Restoring |
8. KBWIN0008 - Message "File Already Exists" followed by "File is Read Only - Force Overwrite" which just repeats when attempting to restore data
| Summary | This article will guide you resolving a "File Already Exists" followed by repeated (if you select the overwrite option) "File is Read Only - Force Overwrite" messages when attempting to perform a restore |
| Symptom | After selecting which files/folders to restore and clicking Restore, the task list appears and states "Transferring".
A message may appear stating a "File Already Exists", if you select Overwrite you see a message that states
"File is Read-Only - Force Overwrite", clicking the Overwrite just repeats the second message.
|
| Cause | Possible Cause - A possible cause of this issue is that you are attempting a restoring files to a location that you do not have write access to. |
| Resolution | Please follow the instructions at this link and select an Alternative Location to which you do have Write Access to. |
| Status | You must select have write access to the folder to which you are restoring data to |
| More Information | |
| Applies To | TSM, Windows, Restoring |
9. KBWIN0009 - "Failed to install client. Please contact the HFS, quoting return code: 1603"
| Summary | This article will guide you through resolving the error message "Failed to install client. Please contact the HFS, quoting return code: 1603" during TSM client installation. |
| Symptom | When trying to install TSM, the error message "Failed to install client. Please contact the HFS, quoting return code: 1603" is returned, stopping the installation from continuing. There are three possible causes. |
| Cause 1 | The most likely cause is that the user is attempting to install TSM with insufficient privileges. |
| Resolution 1 | Please check that you are logged on as a user with administrative privileges; if not, please do so, and then try again. |
| Cause 2 | Alternatively, a current TSM service may still be running, thus preventing a new installation. |
| Resolution 2 | Try stopping this service in Control Panel > Administrative Tools >
Services, and then restarting the
installation. If the error persists then it can usually be solved by rebooting the machine. |
| Cause 3 | Lastly, it may be that the version of TSM that you are trying to install is not supported on your version of Windows - e.g. the latter is Windows 2000 (not supported in TSM 5.4 or higher), or it is 64-bit but the chosen TSM installation package is for 32-bit Windows. |
| Resolution 3 | Check that you are running a supported version of Windows via our downloading page. |
| Status | |
| More Information |
If this error code is still reported a second time by the installer after
a reboot and when you are logged on as an administrator, please contact the Help Centre, stating your version of Windows and
including the TSM log files tsm-install.log and msi.log. You can see how to find these from the FAQ item 30. KBGEN0001 - ANS2622S An invalid ID or password was submitted..
|
| Applies To | TSM, Windows |
10. KBWIN0010 - "Failed to install client. Please contact the HFS, quoting return code: 1618"
11. KBWIN0011 - "Failed to install client. Please contact the HFS, quoting return code: 1619"
| Summary | This article will guide you through resolving the error message "Failed to install client. Please contact the HFS, quoting return code: 1619" during a TSM Client Installation. |
| Symptom | When trying to install TSM, the error message "Failed to install client. Please contact the HFS, quoting return code: 1619" is returned, and the installation fails. |
| Cause | This error code indicates that some files are missing during the installation. |
| Resolution | Download the installation files using the links from the Getting Started section. |
| Status | |
| More Information | |
| Applies To | TSM, Windows |
12. KBWIN0012 - "Failed to install client. Please contact the HFS, quoting return code: 1633"
| Summary | This article will guide you through resolving the error message "Failed to install client. Please contact the HFS, quoting return code: 1633" during a TSM Client Installation. |
| Symptom | When trying to install TSM, the error message "Failed to install client. Please contact the HFS, quoting return code: 1633" is returned, and the installation fails. |
| Cause | This error code 1633 indicates an incompatibility between the version of Windows and that of TSM. |
| Resolution | Windows can be 32-bit or 64-bit, and TSM needs to match it. Windows is usually 32-bit, so the normal reason for this error is an attempt to install 64-bit TSM software on 32-bit Windows. On which version to download, please see our TSM for Windows download page. |
| Status | |
| More Information | |
| Applies To | TSM, Windows |
13. KBWIN0013 - "The size of folder C:\adsm.sys grows larger with every backup"
| Summary | This article will guide you through resolving the problem that the size of the folder
C:\adsm.sys is growing larger with every backup. |
| Symptom | When TSM backs up Windows system data, it composes it beforehand in the temporary staging directory C:\adsm.sys.
Such data is backed up by default on servers, and optionally can also be backed up by desktop/laptop clients.
In some cases, older data is not removed from
C:\adsm.sys, meaning that that directory can theoretically continue to grow in size until it fills C:.
|
| Cause | In some older versions of TSM, there are bugs which cause the system data under the staging directory C:\adsm.sys
not to be deleted once it has been backed up
by TSM. The older fault, IC71847:
C:\adsm.sys directory not cleaned up during system state backup..., applies to TSM versions before
5.5.4, 6.1.5 and 6.2.3: in this case, the old files are never removed by TSM. A more recent problem, IC77458:
After system state backup completes, VSS shadows remain on the file system until the client shuts down, occurs on TSM 6.2.2 and
6.2.3 only: here, restarting the TSM scheduler will remove the unwanted data.
|
| Resolution | Upgrade to the latest version of TSM for Windows, or at least to TSM 6.2.4, which is available from our page on
downloading the TSM client for Windows. Please note that
the data accumulated due to the older fault is not removed by upgrading, so you should therefore also make sure to delete the
contents of C:\adsm.sys.
|
| Status | |
| More Information | |
| Applies To | TSM, Windows |
14. KBWIN0014 - "Unknown system error. Please check the TSM Error Log for any additional system information", followed by "ANS5179E TSM is unable to continue. Exiting program."
| Summary | This article will guide you through resolving the error message "Unknown system error. Please check the TSM Error Log for any additional system information", followed by "ANS5179E TSM is unable to continue. Exiting program", when you try to run TSM. |
| Symptom | When trying to run TSM the error message "Unknown system error. Please check the TSM Error Log for any additional system information" is returned, followed by "ANS5179E TSM is unable to continue. Exiting program." However, there is no problem with running scheduled backups, as reported in dsmsched.log and at the online facility for checking TSM scheduled backups. |
| Cause | These error messages are returned when TSM for Windows is run within an account which does not have the appropriate permissions. |
| Resolution | To run TSM on Windows for the purposes of a manual backup or a restore, it is necessary either to be logged on as a user with administrative permissions, or else to follow the instructions on our page on backing up in Windows as a non-administrative user. |
| Status | |
| More Information | TSM, Windows |
| Applies To | TSM |
15. KBMAC0001 - Backups fail to complete
| Summary | Backup of a Mac fails while sending data from a drive or partition holding a very large number of files (typically, over a million). |
| Symptom | Manual or scheduled backup of a Mac cuts out unexpectedly. |
| Cause | Possible Cause - A Mac may run out of memory while backing up a drive or partition with a high file count. Please try one or both of the following two suggested resolutions. |
| Resolution 1 | Exclude files from backup. Excluded files are not counted by TSM, and so if you have fewer files to back up then TSM is more likely to complete. You may only want to back up a small amount of the data on your machine, much less than TSM is selecting for backup by default. Please see our guide on how to exclude files and folders from backup. |
| Resolution 2 | Alter the way that TSM uses memory when it runs backups. TSM is analysing each whole drive for backup in one go, but a simple change in its settings
will make it
process just one folder at once. It will therefore use less memory and this can fix the cut-out problem. Run TSM Tools for Administrators and then
Tivoli Storage Manager. Go Edit, Client Preferences and then Performance Tuning (tab). Under
Memory Usage Algorithm to be used during backup,
change the selected button to Use memory saving method (from the default Use memory-resident method). Click Apply and then
OK.
|
| Status | |
| More Information | |
| Applies To | TSM, Mac |
16. KBMAC0002 - "ANS1971E The remote client agent (dsmagent) could not be started" or "ANS5179E TSM is unable to continue. Exiting program".
| Summary | This article will guide you through resolving the error message "ANS1971E The remote client agent (dsmagent) could not be started" or "ANS5179E TSM is unable to continue. Exiting program" when you try to run TSM. |
| Symptom | When trying to run TSM, the error message "ANS1971E The remote client agent (dsmagent) could not be started" (TSM 5.5.2) or "ANS5179E TSM is unable to continue. Exiting program" (earlier versions of TSM 5.5) is returned. |
| Cause | This message occurs because of an incompatibility between early versions of TSM 5.5 and Java Update 4 on Mac OS X 10.5.7. The TSM graphical interface is affected but both scheduled and command line backups will still function. |
| Resolution | The issue is fixed from TSM 5.5.2.3 onwards: please upgrade to the latest version of TSM for Mac OS X 10.5 from the HFS clients page. |
| Status | |
| More Information | |
| Applies To | TSM |
17. KBMAC0003 - Files expected to be available for restore by TSM for Mac are not listed.
18. KBMAC0004 - "connect_test() returned an error code 5" or "ANS5155E Valid password not available"
| Summary | This article will guide you through resolving the error message "connect_test() returned an error code 5" or "ANS5155E Valid password not available" when you try to run TSM. |
| Symptom | When trying to run TSM, the error message "connect_test() returned an error code 5" or "ANS5155E Valid password not available" is returned. |
| Cause | This error is caused by a wrongly-cached password. |
| Resolution |
|
| Status | |
| More Information | |
| Applies To | TSM, Mac |
19. KBMAC0005 - "ANS1217E Server name not found in System Options File" (Mac)
| Summary | This article will guide you through resolving the error message "ANS1217E Server name not found in System Options File" when you try to run TSM on a Mac. |
| Symptom | When trying to run TSM, the error message "ANS1217E Server name not found in System Options File" is returned, followed by "ANS5179E TSM is unable to continue. Exiting program" is returned. |
| Cause | Possible Cause - TSM is not configured, because the client did not connect to the HFS server when TSM was installed, and so no settings were saved in the TSM configuration files. For all accounts bar those using the VPN-based backup service, a direct connection to the university network, without VPN running, is required in order to install and run TSM. Accounts on the VPN-based backup service instead need VPN to be installed and running, and a connection to the internet. |
| Resolution 1 | Firstly, for a normal TSM account, check that you have a direct connection to the university network,
without VPN running. (If you
are registered with the VPN-based backup service, do start up VPN).
Then, in Finder, go to [Applications] > [Tivoli Storage Manager] and run
[TSM Tools for Administrators]; then
choose the option [Reconfigure TSM node]. You will be prompted for your TSM nodename and password. |
| Resolution 2 | If that does not work then you need to
force TSM to reconfigure by removing the faulty TSM configuration files: use Finder to browse to the folder
/Library/Preferences/Tivoli Storage Manager
(note: not /Your-username/Library/Preferences/Tivoli Storage Manager, which also exists on your machine),
and delete the files dsm.sys and dsm.opt. Then re-install TSM. |
| Status | |
| More Information | |
| Applies To | TSM, Mac |
20. KBMAC0006 - OUCS TSM client can't be installed on this disk. Installation cannot proceed, as not all requirements were met.
| Summary | This article will guide you through resolving the error message "OUCS TSM client can't be installed on this disk. Installation cannot proceed, as not all requirements were met" when you try to install TSM 6.3 or higher on a Mac running OS X 10.6 (Snow Leopard). |
| Symptom | When trying to install TSM 6.3 or higher on a Mac running OS X 10.6 (Snow Leopard), the error message "OUCS TSM client can't be installed on this disk. Installation cannot proceed, as not all requirements were met" is returned. |
| Cause | This problem occurs on older Macs which have 32-bit processors. TSM 6.3 and higher can only be installed on Macs that have 64-bit processors. Because some older Macs running Snow Leopard are 32-bit, these therefore cannot run the latest versions of TSM. |
| Resolution | To get round the problem, please instead install our package for TSM 6.2 for Mac OS X 10.5 (Leopard), which is available from our page on downloading the TSM client for the Mac. This runs on both Leopard and Snow Leopard machines. |
| Status | |
| More Information | If you wish to verify
that your Mac is 32-bit, please see Apple's page on How to tell if your Intel-based Mac has a 32-bit or 64-bit processor
and check whether your processor is Intel Core Solo or Intel Core Duo. |
| Applies To | TSM, Mac |
21. KBMAC0007 - Mac enters sleep mode while a backup or restore is running
| Summary | This article will guide you through resolving the problem that your Mac goes into sleep mode during a backup (either manual or scheduled) or a restore. |
| Symptom | Backups and restores do not complete because the Mac goes into sleep mode when it is left alone with TSM running. |
| Cause | The default sleep settings in OS X 10.7 (Lion) and 10.8 (Mountain Lion) cause the Mac to go to sleep while running a backup (either manual or scheduled) or a restore. |
| Resolution | This is fixed in recent versions of the TSM client. Download the latest package for OS X. |
| Status | |
| More Information | |
| Applies To | TSM, Mac OS X 10.8 |
22. KBNIX0001 - "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..." (command line) or "ANS1989E Initialization functions cannot open the Error Log file specified" (GUI).
| Summary | This article will guide you through resolving the command-line error message "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..." or the GUI error message "ANS1989E Initialization functions cannot open the Error Log file specified" when you try to run TSM. If you are getting this message while running rather than while installing TSM on Linux or Unix, please also see 33. KBGEN0004 - "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs...". |
| Symptom | When trying to run TSM, the error message "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..." or "ANS1989E Initialization functions cannot open the Error Log file specified" is returned. |
| Cause 1 | Possible Cause - You are attempting to run TSM as a non-root user. |
| Resolution 1 | Whether you are installing TSM or running the installation script, make sure that you are doing so as root.
In Ubuntu, precede your command to run TSM with sudo.
|
| Cause 2 | Possible Cause - Root's home directory is set to /.
|
| Resolution 2 | Check that the home directory for root is not /. If it is, use the method described in the next section to change it to a directory where you have
write permissions.
|
| Cause 3 | Possible Cause - The home directory is NFS-mounted. |
| Resolution 3 | This problem is similar to that described in the previous section - it is caused by the permissions set on an NFS-mounted home directory. If this is the source of the error, then follow the following instructions. |
| Status | |
| More Information | |
| Applies To | TSM, Linux, Unix |
23. KBNIX0002 - "ANS1501E Trusted agent execution/owner permissions are invalid".
24. KBNIX0003 - "ANS4042E Object name ... contains one or more unrecognized characters and is not valid."
| Summary | If you wish to back up files with names containing special characters such as symbols and diacritical marks, but are failing to do so, you need to ensure the backup is run with appropriate localization settings. To make sure every file is backed up we recommend the use of the "en_US" language setting. With other settings such as C, POSIX, or UTF-8, some special characters will be skipped. |
| Symptom | When backing up, you see one or more instances of the error message 'ANS4042E Object name ... contains one or more unrecognized characters and is not valid.' Scheduled backups nonetheless complete, but not all files get backed up. |
| Cause | The en_US locale is not installed on the problem machine. |
| Resolution |
|
| Status | |
| More Information | |
| Applies To | TSM, Linux |
25. KBNIX0004 - "ANS5179E TSM is unable to continue. Exiting program."
| Summary | This article will guide you through resolving the error message "ANS5179E TSM is unable to continue. Exiting program."
when you try to run the TSM GUI (dsmj) on Solaris. |
| Symptom | When trying to run the TSM GUI (dsmj) on Solaris, the error message
"ANS5179E TSM is unable to continue. Exiting program." is returned.
|
| Cause | This is a problem within IBM's distribution which occurs only on installation of the HFS package for TSM 5.5.1. |
| Resolution |
Upgrade to TSM 5.5.2 or higher, as available from our clients page.
This upgrade also has the added benefit of a security fix.
However, if you need to stay with TSM 5.5.1, you can work around this issue by creating the following symlink, as root, in /usr/lib:
cd /usr/lib ln -s ../../opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so /usr/lib/libtsm551xerces-c1_6_0.soThe link will appear similar to: lrwxrwxrwx 1 root other 55 Nov 25 17:24 /usr/lib/libtsm551xerces-c1_6_0.so -> ../../opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so |
| Status | |
| More Information | |
| Applies To | TSM, Unix |
26. KBNIX0005 - "connect_test() returned an error code 5" or "ANS5155E Valid password not available"
| Summary | This article will guide you through resolving the error message "connect_test() returned an error code 5" or "ANS5155E Valid password not available". when you try to run TSM |
| Symptom | When trying to run TSM, the error message "connect_test() returned an error code 5" or "ANS5155E Valid password not available" is returned. |
| Cause | This error is caused by a wrongly-cached password. |
| Resolution |
|
| Status | |
| More Information | |
| Applies To | TSM, Linux, Unix |
27. KBNIX0006 - "ANS1217E Server name not found in System Options File" (Linux)
| Summary | This article will guide you through resolving the error message "ANS1217E Server name not found in System Options File" when you try to run TSM on Linux. |
| Symptom | When trying to run TSM, the error message "ANS1217E Server name not found in System Options File" is returned, followed by "ANS5179E TSM is unable to continue. Exiting program" is returned. |
| Cause | Possible Cause - TSM is not configured, because the client did not connect to the HFS server when TSM was installed, and so no settings were saved in the TSM configuration files. For all accounts bar those using the VPN-based backup service, a direct connection to the university network, without VPN running, is required in order to install and run TSM. Accounts on the VPN-based backup service instead need VPN to be installed and running, and a connection to the internet. |
| Resolution | Firstly, for a normal TSM account, check that you have a direct connection to the university network,
without VPN running. (If you
are registered with the VPN-based backup service, do start up VPN).
Then you need to reconfigure TSM: on Ubuntu the command is
dpkg-reconfigure tsm-client-baseor if you have RedHat then use /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh reconfigureIn either case you must run the command with root permissions (use sudo in Ubuntu).
You will be prompted for your TSM nodename and password. |
| Status | |
| More Information | |
| Applies To | TSM, Linux |
28. KBNIX0007 - "ANS2600S Browser trying to establish connection to client; received socket exception; java.net.ConnectException: Connection refused" (GUI) and/or "/opt/tivoli/tsm/client/ba/bin/dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory" (command line)
29. KBNTW0001 - Scheduled backups fail due to failure to connect to the NDS
| Summary | This article will guide you through what to do if TSM for NetWare scheduled backups fail due to failure to connect to the NDS. |
| Symptom | TSM for NetWare scheduled backups fail due to failure to connect to the NDS. |
| Cause | Possible Cause - If a NetWare machine appears to be failing its backup due to a failure to connect to the NDS, then it is possible that the TSM and NetWare ids and passwords that are stored encrypted on disk have failed in some way. |
| Resolution | The easiest solution is to refresh and re-encrypt
them in the following manner:
|
| Status | |
| More Information | |
| Applies To | TSM |
30. KBGEN0001 - ANS2622S An invalid ID or password was submitted.
| Summary | This article will guide you through resolving the error message "ANS2622S An invalid ID or password was submitted" when you try to run TSM |
| Symptom | When trying to run TSM, the error message "ANS2622S An invalid ID or password was submitted" is returned. |
| Cause 1 | Possible Cause - TSM on your machine is configured with the wrong nodename. |
| Resolution 1 | Check your TSM nodename via the
TSM backup client information page.
Then start the TSM Backup client program and answer Yes to the
error message that displays. At the TSM main window, choose the Edit
menu and [Preferences] option. The General tab should display. Change the entry
in the Nodename field to the Nodename registered - typically of the form Username-freetext-Department/college.
Click OK and restart the TSM Backup Client program. After doing this, Windows users should proceed to follow the instructions in our page on
updating the TSM scheduler in Windows to ensure that their scheduler is correctly
configured. |
| Cause 2 | Possible Cause - TSM on your machine is configured to connect to the wrong HFS TSM server. |
| Resolution 2 | Check which server you should be contacting via
the TSM backup client information page and note
the value in the Server column for the TSM
nodename of your machine. This value will correspond to the last two characters of one of the Server Names in the table below.
To check if you are connecting to the correct OUCS TSM server, note the DNS Name and Port
from the table above, then start the TSM backup client program and answer
Yes to the error message that displays. At the TSM main window, choose the Edit
menu and [Client Preferences] option. Select the Communication tab. Ensure that the
value in the Server Address field corresponds to the DNS name and the
value in the Server Port field corresponds to the Port from the table above. If they do not,
amend them to their correct values, click OK and restart the TSM Backup Client program. After doing this, Windows users should proceed to follow the instructions in our page on
updating the TSM scheduler in Windows to ensure that their scheduler is correctly
configured.
|
| Status | |
| More Information | |
| Applies To | TSM |
31. KBGEN0002 - "ANS1357S Session rejected: Downlevel client code version"
| Summary | This article will guide you through resolving the error message "ANS1357S Session rejected: Downlevel client code version" when you try to run TSM. |
| Symptom | When trying to run TSM, the error message "ANS1357S Session rejected: Downlevel client code version" is returned. |
| Cause | Possible Cause - You have accessed the TSM server from a machine using another machine's Nodename
using a higher level of the TSM client than the current machine has loaded.
Now trying to connect to the TSM server, the session is rejected as being 'downlevel'. This is because, as of TSM 4.2,
the server records the client software level and strictly
enforces the rule of disallowing lower-level-client access.
|
| Resolution | If you have already encountered this problem, please contact
hfs@ox.ac.uk for further help. To avoid this problem, do not do cross-platform access to TSM backups.
If you need to access another node's backups, for example
to restore vital data after a disk or system crash, use the -virtualnodename option
as documented in Restoring your data to
another machine in the Command Line Interface instructions. Using this option does not
cause the client level to be updated at the TSM server with the current machine's
client level and is the supported method of cross-machine access to TSM Backups. |
| Status | |
| More Information | |
| Applies To | TSM |
32. KBGEN0003 - "ANS1361E Session rejected: The specified node name is currently locked"
| Summary | This article will guide you through resolving the error message "ANS1361E Session rejected: The specified node name is currently locked" when you try to run TSM. |
| Symptom | When trying to run TSM, the error message "ANS1361E Session rejected: The specified node name is currently locked" is returned. |
| Cause 1 | Possible Cause - You exceed the daily quota of 100GB (desktop/laptop clients), 200GB (server clients) or 300GB
(large server clients) or 20GB (VPN clients) in one day, and so your account was automatically locked.
The registered contact email address will have been
sent an automatic message to inform you of this action, asking that the reasons for such a large
data send be investigated. This email is explained further in our section on
HFS backup cancellation reports. Common reasons for such
a large data send are as follows.
|
| Resolution 1 | Except in the cases of initial backups, we ask you to review the Acceptable Use Guidelines
and contact us at hfs@ox.ac.uk detailing the cause of the
large data send. If you are unsure of the cause, please send us your
TSM log and configuration files, making sure to include dsmsched.log. |
| Cause 2 | Possible Cause - The TSM account was moved to daily backup. If you have requested to move the backups of a machine from a scheduled weekly backup to a scheduled daily backup, then the old weekly backup account will have been locked. |
| Resolution 2 | You will need to reconfigure your TSM client to connect to the correct TSM server. This is detailed in our page on changing from weekly to daily backups. |
| Cause 3 | Possible Cause - The TSM account was de-registered. If the owner of the machine has requested that the node be removed from the HFS backup service, then the account will have been locked pending deletion. If you have deregistered an account and are trying to use a new nodename on your machine, then it is likely that TSM is trying to use the old, deregistered nodename: on this see 35. KBGEN0006 - During installation, TSM does not prompt for a nodename or password; when run, it tries to use an incorrect nodename.. |
| Resolution 3 | Please contact us at hfs@ox.ac.uk if you want this machine to remain registered for the backup service. |
| Cause 4 | Possible Cause - The TSM account was manually locked by the HFS Team. In this case you should have already received an email explaining why this was done. |
| Resolution 4 | Please contact us at hfs@ox.ac.uk to determine the reason for this. |
| More Information | |
| Applies To | TSM |
33. KBGEN0004 - "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..."
| Summary | This article will guide you through resolving the error message "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..." when you try to run TSM. If instead you see this message when trying to install TSM on Linux or Unix, please see our Linux FAQ item "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs...". |
| Symptom | When trying to run TSM, the error message "ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs..." is returned. |
| Cause | Possible Cause - The problem is related to the path of the log file that is subsequently listed at the end of the error message.
Typically this
will be dsmerror.log, and the message will followed by 'errno=13, permission denied'.
As of version 5.3, TSM requires that a writable error log is available each time TSM is run.
If an error log (dsmerror.log) has been previously created/written
by an admin user with permissions that prevent a non-admin user writing to it, then TSM will
fail to start when invoked by the non-admin user.
|
| Resolution |
This is a file permissions problem and can be resolved or worked around in
standard ways such as:
|
| Status | |
| More Information | |
| Applies To | TSM |
34. KBGEN0005 - "ANS2610S TCP/IP communications failure between the client and the server machine" or "TCP/IP invalid host name. Do you wish to continue for the purposes of local backupset restore?"
| Summary | This article will guide you through resolving the error messages "TCP/IP communications failure" or "TCP/IP invalid host name", followed by "Do you wish to continue for the purposes of local backupset restore?", when you try to run TSM. Windows users are recommended to follow instead our detailed troubleshooting guide on TSM network connectivity, rather than the following brief summary. |
| Symptom | When trying to run TSM, the error message "TCP/IP invalid host name" is returned, followed by the question "Do you wish to continue for the purposes of local backupset restore?". |
| Cause 1 | Possible Cause - this message will occur if there is a problem with your internet connection. |
| Resolution 1 | Please check that you can browse web pages on the computer in question. |
| Cause 2 | Possible Cause - you are using a broadband connection rather than a direct connection to the university network. |
| Resolution 2 | The HFS cannot be accessed from outside the university network except for systems registered for VPN-based backup. This message will appear if you try to run TSM over broadband, with or without VPN running, if your computer is not registered for VPN-based backup. |
| Cause 3 | Possible Cause - VPN is running. |
| Resolution 3 | If you have a connection to the university network, this message usually means that an
attempt has been made to connect to an HFS server while VPN is
running and you are not registered for VPN-based backup.
If you are on the university network and have VPN running, close the TSM software by clicking on
No to the above question; disconnect VPN; and then try
running TSM again. |
| Cause 4 | Possible cause - a local firewall is preventing connection to the HFS. |
| Resolution 4 | Normally a firewall would not interfere with use of the HFS - see our page on connecting to the HFS through a firewall. However, a local change in your department/college could result in you being unable to connect to the HFS. Please see your local IT if you think that this may be the case. |
| Status | |
| More Information | |
| Applies To | TSM |
35. KBGEN0006 - During installation, TSM does not prompt for a nodename or password; when run, it tries to use an incorrect nodename.
| Summary | This article will guide you through what to do when TSM apparently installs gets installed without a nodename being entered. |
| Symptom | During installation, TSM does not ask for a nodename or password; when run, TSM may report that your account is locked, or that you have entered the wrong nodename or password. |
| Cause | When the TSM installer package is run, the program will normally ask you to enter both the TSM nodename
that you have registered and the password that goes with it. However, if TSM has ever previously been installed on your machine, then the TSM installer will
assume that you are upgrading an earlier version of TSM (even if the older version has long since been uninstalled). It will pick up on the
TSM nodename used previously, and will therefore not ask you to enter one. After this installation has completed, when you run TSM, one of the following will happen:
|
| Resolution |
In order to force TSM to prompt you for your new nodename, you need to remove the file(s) where the old
information is stored. For Windows, this is dsm.opt ;
for Mac and Linux, it means both dsm.sys and
dsm.opt. Locate this/these file(s) on your machine using our
TSM configuration file list. Then rename them, e.g.
to dsm-old.sys, dsm-old.opt, to keep them safe. Now run the TSM installer again: it will prompt
you for a nodename and password.
|
| Status | |
| More Information | |
| Applies To | TSM |
36. KBGEN0007 - Data restores run very slowly.
| Summary | This article will guide you through what to do when your data restores run very slowly. |
| Symptom | Data restores are running very slowly. |
| Cause 1 | If you are not using a wired university network connection, then your download speed might not be sufficiently fast for the amount of data that you wish to restore. |
| Resolution 1 | This should not be an issue on the wired university network; but, over a wireless or offsite connection, speeds will be limited. For a guide to how quickly you can restore data, use a speed test website to check your connection speed, and compare the results with the table of backup and restore speeds at our page on VPN-based backup. |
| Cause 2 | Data is being restored in many small restore sessions, rather than in a small number of large restore sessions. |
| Resolution 2 | If you are repeatedly requesting small quantities of data, then this will ultimately be slower than selecting a large amount of data to restore in a single session. The HFS robot quickly locates, mounts, and finds its place on the appropriate data tape(s); but delays will occur if the tape is then put back in its library slot, only to be brought out again for a further small restore session. Minimise the number of restore sessions by selecting for restore as much as it is practicable for you to select all at once. |
| Status | |
| More Information | |
| Applies To | TSM |
37. KBGEN0008 - "ANS1355E Session rejected: Server disabled" and/or "ANS1312E Server media mount not possible"
| Summary | This article will guide you through resolving the error messages "ANS1355E Session rejected: Server disabled" and "ANS1312E Server media mount not possible" when you try to run TSM. |
| Symptom | When trying to run TSM the error message "ANS1355E Session rejected: Server disabled" is returned.
If a backup was attempted, e.g. on a scheduled backup, then the
message "ANS1312E Server media mount not possible" is found in dsmerror.log.
|
| Cause | These messages indicate respectively that the TSM client was unable to connect to an HFS server and that it was unable run a backup, because the relevant TSM server was unavailable. |
| Resolution | Check the IT Services System Status page. There may be
information regarding an HFS system outage
in the section on HFS backup or under the Announcements heading.
If no such information is to be found, and the problem persists, please
contact hfs@ox.ac.uk. |
| Status | |
| More Information | |
| Applies To | TSM |