Device configuration status code 44
|Article:HOWTO51431|||||Created: 2011-05-04|||||Updated: 2012-11-20|||||Article URL http://www.symantec.com/docs/HOWTO51431|
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 occurred:
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.
Article URL http://www.symantec.com/docs/HOWTO51431