Media and device management messages
| Article:HOWTO35736 | | | Created: 2010-10-29 | | | Updated: 2010-10-29 | | | Article URL http://www.symantec.com/docs/HOWTO35736 |
This topic can be used as a cross reference to the status code descriptions and recommended actions listed previously. Use the information in this topic if you know the error message itself, but don't have access to the status code number.
Table: Media and device management messages and status codes lists the NetBackup error messages alphabetically in the left column and the corresponding status code number in the right column.
Table: Media and device management messages and status codes
Error message | Status code number |
|---|---|
< NONE > | Device Configuration status code 36 |
A memory allocation attempt failed in the robotic daemon | Robotic status code 240 |
a scratch pool is already defined | Media Manager status code 171 |
A SCSI inquiry sent to the device has failed | Device Configuration status code 16 |
ADAMM GUID does not exist in database | Media Manager status code 168 |
ADAMM GUID is not unique in the database | Media Manager status code 167 |
Add Drive Name Rule request failed | Device Configuration status code 82 |
Adding this device would exceed the maximum allowed | Device Configuration status code 40 |
Adding this drive would exceed the maximum allowed | Device Configuration status code 39 |
another daemon already exists | Media Manager status code 89 |
Another device configuration is already in progress | Device Configuration status code 90 |
barcode does not exist in database | Media Manager status code 78 |
barcode label is unreadable | Robotic status code 235 |
barcode not unique in database | Media Manager status code 36 |
barcode tag is not unique in rule database | Media Manager status code 122 |
cannot allocate requested memory | Media Manager status code 18 |
Cannot assign a robotically controlled device | Device management status code 64 |
Cannot assign due to media ID mismatch | Device management status code 57 |
cannot auto-eject this robot type | Media Manager status code 51 |
cannot auto-inject this robot type | Media Manager status code 52 |
Cannot change terminal mode | Device Configuration status code 41 |
cannot connect to robotic software daemon | Media Manager status code 42 |
cannot connect to vmd [on host host name] | Media Manager status code 70 |
Cannot create miscellaneous working repository | Device Configuration status code 42 |
cannot delete assigned volume | Media Manager status code 92 |
cannot delete one of the default volume pools | Media Manager status code 118 |
Cannot discover devices. See the Troubleshooting Guide for details. | Device Configuration status code 44 |
Cannot execute command, permission denied | Device Configuration status code 1 |
cannot get host name | Media Manager status code 76 |
Cannot move from media access port to slot | Robotic status code 218 |
Cannot move from slot to media access port | Robotic status code 219 |
cannot obtain daemon lockfile | Media Manager status code 21 |
Cannot open/create the media access port status file | Robotic status code 243 |
cannot perform operation on this host | Media Manager status code 60 |
Can not retrieve Job ID from Job Manager | Device management status code 79 |
Cannot stop device daemon with tapes assigned | Device management status code 20 |
cannot update database due to existing errors | Media Manager status code 80 |
child process killed by signal | Media Manager status code 63 |
Cleaning/unknown media in drive | Robotic status code 258 |
Configuration has changed, robot daemons and ltid need restarting | Robotic status code 262 |
Control daemon connect or protocol error | Robotic status code 224 |
CORBA communication error | Media Manager status code 195 |
Could not get hostname | Device Configuration status code 3 |
Credentials already exist | Device configuration status code 99 |
Current version does not support remote device host | Device Configuration status code 38 |
current version does not support this configuration | Media Manager status code 149 |
daemon cannot obtain socket | Media Manager status code 58 |
daemon failed accepting connection | Media Manager status code 59 |
daemon resources are busy | Media Manager status code 5 |
daemon terminated | Media Manager status code 7 |
database open operation failed | Media Manager status code 26 |
database read operation read too few bytes | Media Manager status code 28 |
database read record operation failed | Media Manager status code 27 |
database server is down | Media Manager status code 23 and Device Configuration status code 93 |
database write record operation failed | Media Manager status code 32 |
Delete Drive Name Rule request failed | Device Configuration status code 84 |
device entry is not unique in global device database | Media Manager status code 153 |
device management error | Media Manager status code 83 |
Device path is already in use | Device Configuration status code 22 |
device test state file does not exist | Media Manager status code 182 |
Devices located in multiple domains | Robot Error status code 16 |
Disk Optimization feature is not licensed | Device Configuration status code 94 |
Door is open on cabinet | Robotic status code 216 |
Drive being assigned is either not NDMP or on the wrong NDMP client | Device management status code 37 |
Drive does not exist in robot | Robotic status code 213 |
Drive does not support pending request density | Device management status code 17 |
Drive index is in use by another drive | Device Configuration status code 29 |
Drive is currently assigned | Device management status code 2 |
Drive name does not exist | Device Configuration status code 35 |
Drive name is already in use by another drive | Device Configuration status code 34 |
Drive name rule has exceeded its maximum length of 48 characters | Device Configuration status code 89 |
Drive not available in library for mount request | Device management status code 62 |
EMM database error | Media Manager status code 196 |
EMM DB record not found | Media Manager status code 194 |
EMM error | Robotic status code 261 and Robot Error status code 13 |
EMM library call failed | Device management status code 72 |
error auto-generating volume group | Media Manager status code 57 |
Error in attaching the shared memory | Robot Error status code 4 |
Error in getting process Id | Robot Error status code 5 |
Error in getting semaphore | Device management status code 32 |
Error in getting shared memory | Robot Error status code 3 |
Error in IPC SHMAT call | Device management status code 14 |
Error in IPC SHMGET call | Device management status code 13 |
Error in MsgGet | Device management status code 28 |
Error in Receiving Daemon Message | Device management status code 6 |
Error in Receiving Operator Message | Device management status code 4 |
Error in Receiving User Message | Device management status code 8 |
Error in SEMAPHORE operation | Device management status code 33 |
Error in SEMAPHORE operation | Robotic Error status code 9 |
Error in Sending Daemon Message | Device management status code 5 |
Error in Sending Operator Message | Device management status code 3 |
Error in Sending User Message | Device management status code 7 |
Evaluation period expired. Go to www.symantec.com to order this product. | Media Manager status code 165 |
failed appending to pool database | Media Manager status code 104 |
failed appending to rule database | status code 121 Media Manager See Media Manager status code: 121. |
failed changing terminal characteristics | Media Manager status code 45 |
failed initiating child process | Media Manager status code 88 |
failed making the database directory | Media Manager status code 25 |
failed opening tmp output file | Media Manager status code 86 |
Failed reading drive or robot config file | Device Configuration status code 13 |
failed receiving from robotic software daemon | Media Manager status code 44 |
failed receiving from vmd | Media Manager status code 72 |
failed redirecting input to pipe | Media Manager status code 62 |
failed redirecting tmp output file | Media Manager status code 87 |
failed sending request to vmd | Media Manager status code 69 |
failed sending to robotic software daemon | Media Manager status code 43 |
failed sending to vmd | Media Manager status code 71 |
Failed to find an available slot to inject to | Robotic status code 246 |
failed to initialize a connection to the Enterprise Media Manager | Media Manager status code 189 |
File name already exists | Device management status code 40 |
File name does not exist | Device management status code 25 |
Fork failure occurred | Robot Error status code 10 |
generic EMM SQL error | Media Manager status code 193 |
global device database append operation failed | Media Manager status code 155 |
global device database host name is invalid | Device Configuration status code 49 |
global device database record not found | Media Manager status code 152 |
Host is not the scan host for this shared drive | Device management status code 48 |
incompatible database version | Media Manager status code 146 |
Incomplete robot information | Device Configuration status code 24 |
Incorrect tpreq access mode | Device management status code 42 |
internal database access failure | Media Manager status code 169 |
Internal NDMP error | Device Configuration status code 57 |
invalid barcode | Media Manager status code 10 |
invalid change type | Media Manager status code 75 |
invalid change-entry request | Media Manager status code 50 |
Invalid command code | Robotic status code 207 |
invalid command usage. | Media Manager status code 4 |
invalid container id. | Media Manager status code 186 |
invalid database host. | Media Manager status code 19 |
invalid database version header | Media Manager status code 56 |
invalid description | Media Manager status code 11 |
Invalid device path name | Device Configuration status code 19 |
Invalid drive index | Device Configuration status code 14 |
invalid drive name | Media Manager status code 129 |
Invalid Drive Name Rule | Device Configuration status code 86 |
Invalid Drive Number | Device management status code 23 |
Invalid drive type for the robot | Device Configuration status code 27 |
Invalid Drive Type/Density | Device management status code 1 |
invalid EMM argument | Media Manager status code 191 |
invalid expiration date | Media Manager status code 113 |
Invalid host | Device Configuration status code 88 |
invalid host name | Media Manager status code 136 |
invalid maximum mounts | Media Manager status code 114 |
invalid media generation rule | Media Manager status code 140 |
invalid media ID for naming mode | Media Manager status code 41 |
invalid media ID | Media Manager status code 8 |
invalid media type | Media Manager status code 9 |
Invalid NDMP device | Device Configuration status code 64 |
Invalid NDMP hostname | Device Configuration status code 55 |
Invalid NDMP password | Device Configuration status code 60 |
invalid number of cleanings | Media Manager status code 74 |
invalid number of mounts | Media Manager status code 141 |
invalid offsite location | Media Manager status code 142 |
invalid offsite return date | Media Manager status code 144 |
invalid offsite sent date | Media Manager status code 143 |
invalid offsite session id | Media Manager status code 148 |
invalid offsite slot | Media Manager status code 147 |
Invalid Operator | Device management status code 12 |
invalid pool database entry | Media Manager status code 102 |
invalid protocol request | Media Manager status code 6 |
invalid query type | Media Manager status code 73 |
invalid robot coord1 | Media Manager status code 16 |
Invalid robot drive number for the robot type | Device Configuration status code 28 |
invalid robot host | Media Manager status code 14 |
Invalid robot number | Device Configuration status code 15 |
invalid robot number | Media Manager status code 13 |
Invalid robot type | Device Configuration status code 18 |
invalid robot type | Media Manager status code 12 |
invalid rule database entry | Media Manager status code 119 |
invalid scratch pool name | Media Manager status code 173 |
Invalid SCSI bus number for the robot | Device Configuration status code 8 |
Invalid SCSI logical unit number for the robot | Device Configuration status code 10 |
Invalid SCSI port number for the robot | Device Configuration status code 7 |
Invalid SCSI target for the robot | Device Configuration status code 9 |
Invalid Usage | Device Configuration status code 11 |
invalid volgroup | Media Manager status code 15 |
invalid volume move mode | Media Manager status code 53 |
Invalid volume pool specified | Device management status code 65 |
invalid volume pool | Media Manager status code 90 |
IPC Error: Daemon may not be running | Device management status code 22 |
IPC sequence error | Device management status code 10 |
Job Manager returned error: see activity monitor | Device management status code 80 |
List Drive Name Rule request failed | Device Configuration status code 85 |
LTI Daemon may not be running | Robot Error status code 2 |
LTI system error | Device management status code 75 |
Media access port already contains media | Robotic status code 221 |
Media access port does not contain media | Robotic status code 220 |
Media access port is available | Robotic status code 250 |
Media access port is in eject mode | Robotic status code 253 |
Media access port is in inject mode | Robotic status code 252 |
Media access port is unavailable | Robotic status code 251 |
media access port not available | Media Manager status code 166 |
Media does not exist in database | Device management status code 83 |
media generation rule already exists | Media Manager status code 138 |
media generation rule does not exist | Media Manager status code 139 |
media ID is not the specified media type | Media Manager status code 95 |
media ID not unique in database | Media Manager status code 34 |
media type and volume group mismatch | Media Manager status code 101 |
Mount canceled, device daemon is terminating | Device management status code 56 |
NDMP authorization error, verify username/password | Device Configuration status code 74 |
NDMP config_get_connection_type failed | Device Configuration status code 76 |
NDMP config_get_mover_type failed | Device Configuration status code 75 |
NDMP failed to verify host | Device Configuration status code 58 |
NDMP get_host_info failed | Device Configuration status code 71 |
NDMP get_server_info failed | Device Configuration status code 72 |
NDMP host does not exist | Device Configuration status code 62 |
NDMP host exists, use change option | Device Configuration status code 61 |
NDMP host not connected | Device Configuration status code 69 |
NDMP is not installed on platform | Device Configuration status code 59 |
NDMP request failed | Device Configuration status code 63 |
NDMP robot does not exist | Device Configuration status code 66 |
NDMP robot exists, use change option | Device Configuration status code 65 |
NetApp Disk Storage Unit feature is not licensed | Device configuration status code 94 |
NetBackup Snapshot client not licensed | Device configuration status code 100 |
network protocol error | Media Manager status code 39 |
No action pending for given mount index | Device management status code 50 |
no child process to wait for | Media Manager status code 64 |
No cleaning tape is defined in the device's robot or 0 cleanings remaining | Device management status code 59 |
No compatible device is registered at these SCSI coordinates | Device Configuration status code 51 |
No devices are configured on the robot | Robot Error status code 6 |
No drive available | Device management status code 82 |
no entries changed | Media Manager status code 47 |
no entries deleted | Media Manager status code 48 |
no entries inserted | Media Manager status code 49 |
No Error on operation, sideband data only | Device management status code 84 |
No media found in device or robot slot, please verify | Device management status code 61 |
No memory available | Robot Error status code 8 |
No mount pending for given mount index | Device management status code 16 |
no pools in the pool list | Media Manager status code 112 |
Robot daemon and/or robotic hardware is not available | Device management status code 60 |
No robot is defined of this type | Device management status code 52 |
No robots are configured | Robot Error status code 7 |
No valid license key for Disk Array configuration | Device Configuration status code 97 |
<NONE> | Device Configuration status code 36 |
Not authorized by VxSS | Robotic status code 259 |
not authorized to connect to vmd | Media Manager status code 126 |
Only the administrative user can perform the requested operation | Device management status code 19 |
Open Storage feature is not licensed | Device configuration status code 98 |
operation not allowed on cleaning cartridge | Media Manager status code 117 |
Operator denied mount request | Device management status code 55 |
oprd request is not supported on the remote host | Media Manager status code 137 |
oprd returned abnormal status | Media Manager status code 96 |
Parameter is invalid | Device management status code 39 |
Physical drive is not available | Robotic status code 245 |
pool does not exist in pool database | Media Manager status code 109 |
poolname is not unique in pool database | Media Manager status code 105 |
pool not defined as a catalog backup pool | Media Management status code 198 |
pool not defined as a scratch pool | Media Manager status code 172 |
pool type change is not allowed for <CatalogBackup> pool | Media Manager status code 22 |
Process killed by parent | Robotic status code 212 |
Process killed by signal | Robotic status code 211 |
protocol error | Media Manager status code 20 |
registering this host would exceed the maximum allowed | Media Manager status code 150 |
request can only be performed on the Media and Device management Domain Server | Media Manager status code 177 |
request completed | Media Manager status code 1 |
Request has been queued (Cancel to clear message | Device management status code 53 |
Request terminated because host not validated for volume pool | Device management status code 26 |
Request terminated because media id is expired | Device management status code 27 |
Request terminated because media id will exceed maximum mount count | Device management status code 30 |
Request terminated because media is a cleaning tape | Device management status code: 71 |
Request terminated because media is unavailable (in DOWN drive, misplaced, write protected or unmountable | Device management status code 35 |
Request terminated because media is unmountable | Device management status code 69 |
Request terminated because media is write protected | Device management status code 70 |
Request terminated because mount requests are disabled | Device management status code 63 |
Request terminated because of volume pool mismatch | Device management status code 66 |
Request terminated by tpunmount call from another process | Device management status code 36 |
Requested drive could not be reserved | Device management status code 24 |
requested drive is already reserved by host | Media Manager status code 145 |
requested drive is already reserved | Media Manager status code 130 |
Requested drive is in an offline domain | Robotic status code 238 |
requested drive is not currently registered | Media Manager status code 132 |
requested drive is not currently reserved | Media Manager status code 134 |
requested drive is not registered for host | Media Manager status code 131 |
requested drive is not reserved by host | Media Manager status code 133 |
requested host is not currently registered | Media Manager status code 135 |
Requested operation is not supported by the robot | Robotic status code 229 |
Requested slot already has cartridge | Robotic status code 217 |
Requested slot contains the wrong tape | Robotic status code 226 |
Requested slot does not exist in robot | Robotic status code 228 |
Requested slot is empty | Robotic status code 208 |
Requested tape in other or non-configured drive | Robotic status code 215 |
Requested volume is in an offline domain | Robotic status code 239 |
Residence is not licensed for multihosted drive support | Device Configuration status code 37 |
Retry later | Device management status code 81 |
Robot busy, cannot perform operation | Robotic status code 223 |
Robot busy, inject operation in progress | Robotic status code 255 |
Robot busy, inventory operation in progress | Robotic status code 254 |
Robot busy, multiple eject operation in progress | Robotic status code 256 |
Robot busy, multiple inject operation in progress | Robotic status code 257 |
Robot busy, robot diagnostics in progress | Robotic status code 260 |
Robot denied access to the resource | Robotic status code 234 |
Robot drive number in use for this robot | Device Configuration status code 25 |
Robot hardware or communication error | Robotic status code 225 |
Robot has misplaced the media | Robotic status code 236 |
robot host and volume group mismatch | Media Manager status code 82 |
Robot/LTI protocol error | Device management status code 76 |
Robot media access port does not exist | Robotic status code 242 |
robot number and robot host mismatch | Media Manager status code 61 |
robot number and robot type mismatch | Media Manager status code 54 |
robot number and volume group mismatch | Media Manager status code 55 |
Robot number does not exist | Device Configuration status code 31 |
Robot number does not exist. | Robotic status code 214 |
Robot number is already in use | Device Configuration status code 21 |
Robot number is in use by another robot | Device Configuration status code 30 |
Robot operation failed | Device management status code 74 |
robot type and volume group mismatch | Media Manager status code 81 |
Robot type must be controlled locally | Device Configuration status code 33 |
Robotic arm has no addressable holder | Robotic status code 222 |
Robotic daemon not licensed | Robot Error status code 17 |
Robotic dismount failure | Robotic status code 206 |
Robotic mount failure | Robotic status code 205 |
robotic volume position is already in use | Media Manager status code 37 |
RSM is not supported | Device Configuration status code 48 |
rule does not exist in rule database | Media Manager status code 97 |
Shared Storage Option (SSO) is not licensed | Device Configuration status code 53 |
specified robot is unknown to vmd | Media Manager status code 79 |
STATUS_SUCCESS | Robotic status code 200 |
Stopping device daemon with tapes assigned | Device management status code 73 |
Success | Device Configuration status code 0 |
System Error | Device Configuration status code 87 and Media Manager status code 2 |
System error occurred | Robot Error status code 11 |
System error occurred during robot operation | Robotic status code 230 |
Tape file path exceeds 255 character maximum | Device management status code 49 |
Tape needs to be write enabled | Device management status code 46 |
The device is not robotic, cannot perform cleaning | Device management status code 58 |
The device_mappings file has invalid license info | Device Configuration status code 2 |
The device name is not valid, no device responded | Device Configuration status code 52 |
The drive is DOWN | Device management status code 15 |
The drive is not ready or inoperable | Device management status code 21 |
The drive serial number already exists in the device database | Device Configuration status code 91 |
The eject command was aborted by the user | Robotic status code 244 |
The EMM server failed to process the request | Device Configuration status code 78 |
the global device database device name is invalid | Media Manager status code 162 |
the global device database device type is invalid | Media Manager status code 160 |
the media is allocated for use | Media Management status code 199 |
the operation requested has failed | Media Manager status code 163 |
The requested operation is not valid for the specified Disk Type | Device Configuration status code 95 |
the request sent to the Device Allocator has failed | Media Manager status code 190 |
the robotic daemon returned an invalid volume GUID | Media Manager status code 164 |
the robotic library is full and may still have media in its map | Media Manager status code 185 |
The specified Disk Array Host is not configured in NetBackup | Device Configuration status code 96 |
the specified pool is not empty | Media Manager status code 111 |
This is a drive path operation, use the -drpath option | Device Configuration status code 81 |
this machine is not the database host | Media Manager status code 84 |
This robot type does not support multiple media types | Device Configuration status code 17 |
Timeout waiting for robotic command | Robotic status code 203 |
too many volumes in volume group | Media Manager status code 68 |
Unable to allocate memory for this process | Device configuration status code 79 |
Unable to connect to NDMP host verify hostname | Device configuration status code 67 |
Unable to connect to the EMM server | Device configuration status code 77 and Device management status code 78 |
Unable to create NDMP session | Device configuration status code 70 |
unable to find any records in the device test database | Media Manager status code 176 |
unable to generate a unique media id | Media Manager status code 127 |
Unable to initialize robot | Robotic status code 204 |
Unable to open drive | Robotic status code 209 |
Unable to open robotic path | Robotic status code 201 |
unable to open the device test state file | Media Manager status code 175 |
Unable to process NDMP message | Device configuration status code 68 |
Unable to SCSI unload drive | Robotic status code 210 |
unable to send exit status | Media Manager status code 67 |
Unable to sense robotic device | Robotic status code 202 |
unexpected data from robotic software daemon | Media Manager status code 46 |
unexpected data received | Media Manager status code 40 |
Unknown drive name | Device management status code 41 |
unknown EMM error code | Media Manager status code 192 |
Unsupported NDMP version | Device configuration status code 73 |
Update Drive Name Rule request failed | Device configuration status code 83 |
Usage error in creating child process | Robot Error status code 12 |
user id was not superuser | Media Manager status code 3 |
volume daemon fork failed | Media Manager status code 85 |
volume does not exist in database | Media Manager status code 35 |
volume group does not exist | Media Manager status code 65 |
volume has exceeded maximum mounts | Media Manager status code 116 |
volume has passed expiration date | Media Manager status code 115 |
volume is already assigned | Media Manager status code 93 |
Volume is in home slot | Robotic status code 249 |
Volume is in library, but not in drive domain | Robotic status code 233 |
Volume is in use | Robotic status code 237 |
volume is not in specified pool | Media Manager status code 94 |
Volume not found in library | Robotic status code 232 |
VxSS Access Denied | Media Manager status code 188, Device management status code 77, and Device configuration status code 92 See Media Manager status code: 188. |
VxSS authentication failed. | Media Manager status code 187 |
You do not have permission to create the file | Device management status code 44 |
You must be administrator to execute | Robot Error status code 14 |
You must be ROOT to start daemon | Robot Error status code 1 |
|
|
Legacy ID
v15107009_v47163124
Article URL http://www.symantec.com/docs/HOWTO35736
Terms of use for this information are found in Legal Notices









Thank you.