Devices do not fully support serialization

If a robot or drive does not fully support device serialization, the wizard may be unable to configure the device automatically. The more drives and robots that do not support serialization, the greater the chance of configuration problems.

Table: Limited serialization support scenarios

Scenario

Description

Robot or drive does not return a serial number

For example, you have a robot that can contain two drives, but you initially install only one drive. Although the drive does not return a serial number, the wizard discovers and configures the robot and the drive.

Later, you install a second drive in the robot and run the wizard again. The wizard now discovers two drives in your configuration. Because these drives do not return serial numbers, the wizard cannot configure the devices correctly.

The wizard is unable to determine which of the following is true:

  • You added a new drive and kept the drive you originally configured.

  • You added two new drives and removed the drive you originally configured.

Robot does not return serial numbers for each of its drives

In most of these cases, the wizard cannot determine which robot drive number should be assigned to the drives in the robot. This means that the wizard is unable to determine the order of the drives (their location) within the robot.

Also, if a request for drive serial numbers fails, the wizard cannot determine whether the drive is in a robot or is a standalone drive.

For example, suppose you have a robot that contains one drive and you have one standalone drive of the same drive type. If the robot does not support serialization, the wizard cannot determine which drive is in the robot and which drive is the standalone drive.

Robot returns only the number of drives in the robot

If the robot returns one as the number of drives in the robot but does not return a serial number for the drive, the wizard configures the devices. Because of the simplicity of this configuration, the serial number for the drive is not needed.

If no appears in the Serialized column for the device, the device does not support serialization.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.