Symantec NetBackup Device configuration status code 41 to status code 44


Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

Below are some of the NetBackup Device configuration status code 41 to status code 44 which may be received while using the Symantec NetBackup tool.

Device configuration status code 41
Message: Cannot change terminal mode
Explanation: When an attempt was made to change the mode for terminal input
between cooked and raw, a system call failed.
Recommended Action: Examine the user interface output for the system error
that is associated with the failed system call. Then troubleshoot according to
operating system vendor recommendations.

Device configuration status code 42
Message: Cannot create miscellaneous working repository
Explanation: On a device configuration request, the miscellaneous working
directory or folder is not present and cannot be created.
RecommendedAction: Find out why /usr/openv/volmgr/misc (UNIX and Linux)
or install_path\volmgr\misc (Windows) cannot be created. On Windows,
determine which accounts the NetBackup Volume Manager service and device
configuration interfaces are running under. Compare them with the security
properties of the database folder. On UNIX and Linux, determine whether users
or device configuration interface callers are running under a user and group with
permissions to create the miscellaneous directory.

Device configuration status code 44
Message: Cannot discover devices. See the Troubleshooting Guide for details.
Explanation: Device discovery cannot obtain or verify its lock file or had a problem
with the EMM server.
¦ Examine the daemon debug log and command or interface output for a more
detailed message on the system error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Retry the operation and examine the logs. One of the following may have
¦ Lock file problems: The device discovery process sets a lockfile in the
/usr/openv/volmgr/misc (UNIX and Linux) or install_path\Volmgr\misc
(Windows) directory named tpac.lock. It sets the lockfile to ensure that
only one instance of discovery runs on a particular host. It then checks the
lockfile before it updates the configuration.
¦ Cannot obtain lockfile.
The lockfile may be held by another discovery process. In this case the
following error is displayed:
another tpautoconf is already running
Use standard OS process tools (ps on UNIX and Linux or Task Manager
on Windows) to determine if another tpautoconf process is running.
If not, delete the lockfile and re-run device discovery. If another
tpautoconf process is running, wait for it to complete before retrying.
¦ Failed the lockfile check.
In the case of long device-discovery cycles, the interface may timeout
or the user may cancel the process. Part of the timeout or cancellation
is to remove the lockfile. This action tells the device discovery process
that it should not continue making modifications to the device
configuration. If action occurs, run the discovery process again.

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Device configuration status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *