FAQs: Troubleshooting the Hyperion DMA

Typically, this means that the Hyperion server processes are not running on the Hyperion server. To correct the problem, start the Hyperion server processes. Verify that the workstation can connect to the server via TCP/IP and check your workstation’s network configuration and connections.

Why can’t the image viewer display the stored image?

Occasionally, these messages display.

(Archview Error Dialog)
Image file is bad, error in format. (-4453)

One of the following reasons could cause the messages to appear.

•

The file that is attempting to be displayed is not viewable with the included Hyperion viewer. Hyperion can store and retrieve any type of file, including files that the Hyperion viewer cannot view. For example, Acrobat PDF files cannot be viewed by the Hyperion image viewer, although Hyperion will launch the Acrobat Reader if the reader is properly configured with the workstation’s Windows operating system. It is possible that Hyperion could not correctly determine the type of the file when it was originally added to the system. For instance, if a PDF file with the name techrpt.001 was imported into Hyperion, the file will come out of Hyperion with a 001 extension. It is unlikely that your Windows is set up to launch the Acrobat Reader for files of type 001. When Hyperion encounters a file type that is not configured in Windows, Hyperion will attempt to view the file itself. In this case, the Hyperion viewer will be unable to display the PDF document and will generate this error.

•

You may have a corrupted image file.

On your workstation, load the viewer applications for each of the different file types managed within the metadata. When Hyperion retrieves the file, Hyperion will be able to find and launch the correct viewer for that file. Be sure all files that are imported into Hyperion have an extension that indicates the type of file being imported. Avoid importing files that have numeric extensions or extensions different from the correct file type.

Why can’t I see images that other people can see?

If you cannot display images that other users can, your access level is below that of the other users.

If you need access to those unseen items, review your access control policies and consider changing your user access level to a higher level. Also consider lowering the access level of the unseen documents, keeping in mind the overall access control policies and procedures.

Why can’t I access images from the e-Library?

Periodically this message displays.

The Archive is currently unavailable {503}

The Hyperion server processes are not running on the Hyperion server. You may also have network problems, or no TCP/IP network connection between the e-Library server and the Hyperion server.

Start the Hyperion server processes.

What if I get a message such as “Image ID not Found”?

This message can occur when you are trying to access an image on the file server. Verify that you are using the correct image ID and the correct server path. Check your workstation’s network configuration.

What if I get a message such as “Required Datacode Missing”?

This message can occur when you are trying to access an item or image on the server. Hyperion is unable to find the database containing the item information. Verify that you are using the correct image ID and the correct server path. Verify that the image file server is functioning correctly.

What if I get a message such as “File not Found”?

This message can occur when you are trying to access an image on the file server. Verify that you are using the correct image ID, the correct file name, and the correct server path.

What if I get a message such as “By Reference (only fname) Not Allowed”?

What if I get a message such as “Failed DB Call”?

What if I get a message such as “Error Getting Image Size”?

This message can occur when you are trying to access an image on the file server and indicates problems with the file server. It could also indicate a corrupted image file. Verify that you are using the correct image ID and the correct server path.

What if I get a message such as “Duplicate Resource ID Not Allowed”?

This message occurs when you are trying to add an image to the file server or modify an item on the file server. Hyperion requires that Resource IDs be unique. Verify that you are using the correct item information and the correct server path. Change the Resource ID to a unique value.

What if I get a message such as “Could not Find Free Directory”?

This message occurs when you are trying to add an image to the file server or modify an item on the file server. Use Hyperion’s Image Directory policy and add a directory on the server or modify an existing directory to increase the file size and number of bytes allowed.

What if I get a message such as “Error Getting File Size”?

This message can occur when you are trying to access an image on the server. It could also indicate a corrupted image file.

Verify that you are using the correct image ID and the correct server path. Modify your Image Directory policy by using the Maximum Images and Maximum Bytes gadgets to allow for larger files.

What if I get a message such as “Problem with Directory — Name Too Long”?

This message can occur when you are importing images on the server. Image directory names cannot exceed 80 characters. Verify that you are using the correct image ID and the correct server path. Modify the Image Directory policy.

What if I get a message such as “Insufficient Space on PC”?

This message means that there is not enough space left on the device or the number is set too low in the Hyperion Configuration policies. This message can occur when you are trying to access an image on the server.

Modify the Configuration policy for Hyperion to be a larger number of bytes and files or obtain more space on the image file server. This can be also be done in the WorkFlows client with the Image Directory wizard.

What if I get a message such as “Error in Send”?

An error message can occur if you have the ARFSERVER on a different server than your ARCHIVE SERVER.

If you add additional directories to the Textarchmgr utility (UNIX platforms using the telnet character client) and do not halt and run the archiveadmin servers, this error can appear if you try to use the Import/Scan function in the Hyperion staff client. You can access this same policy with the WorkFlows client. It is found in the Image Directory wizard on the Configuration toolbar.

Modify the /Unicorn/Textarchive/tarchpols file to point to the correct directory where the images are to reside. You can use the Textarchmgr utility if you are on a UNIX platform and using the telnet character client. You can also access this policy with the WorkFlows client. Select the Hyperion Configuration policy and the Image Directory policy on the Configuration toolbar. After making the change, halt and run the Archiveadmin servers on the UNIX platform. On Windows servers, stop and start the archive and archive file servers via the services program.

What if I get a message such as “Error Writing Images — No Space on Image server”?

The following message means that there is not enough space left on the device, or, the number in the Textarchive policy is too low.

ERROR WRITING IMAGES
NO SPACE ON IMAGE SERVER

Modify the Textarchive policy to be a larger number of bytes and files or obtain more space on the image file server. This can be also be done in the WorkFlows client with the Image Directory wizard on the Configuration toolbar.

What if I get a message such as “Error Receiving Files”?

An error message can occur when you are using the Import/Scan function and are importing from the server.

Check the permission on the SirsiDynix Symphony files and directories. The files need to be owned by Sirsi.