Summary - "Print Queue ID cannot be read."

  • 10014975
  • 4.0.32137218.2288588
  • 24-Aug-1999
  • 13-Jul-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

Formerly KB 2942030,  2923985,  292868,  2939789

Novell NetWare 4.11

NetWare Administrator 32 (NWADMN32.EXE)

The users tried Pconsole, 16-bit NWAdmin, and NWAdminNT and in each case could view the details fine.

If the queue is created on the new 4.11 server, the error does not appear.

Symptom

Creating print queue returns the error "Print Queue ID cannot be read."

Error: "The Print Queue ID cannot be read. Verify the queue volume is mounted, then try again."

Error: 3038

Error occurs when viewing detail of a Print Queue Object, through NWAdmin.

The error occurred for print queues that resided on the SYS: volume.

Error occurred for print queues that are on any volume.

Change

After upgrading from NW4.10 to NW4.11 the error occurs.  

Fix

There are multiple issues that can cause this error.   Following is a list of different fixes that have resolved the error.  They are in no particular order.

Cause

Accessing a NW4.11 server in one NDS tree, and then accessing a NW4.10 server in a different tree, in that order, has caused this problem.  The issue is the different schema's that exist on the two trees.

Fix

You can either upgrade to a pure 4.11 environment, or as a workaround you could access the queues on the 4.10 server first, or by not authenticating to the 4.10 tree.

Cause

Corrupt Novell Client install.

Fix

Re-installing the Novell Client32 for Windows 95 at the workstation. Also see the Solution: "How to do a clean uninstall / reinstall of the NetWare client."

Rename your volume and reinstall NetWare to a new drive. This will make it so there is not a queue directory on the new sys volume. There are several ways of handling this, but in each case the queue object in DS needs to be pointing to the correct location where the queue directory really is.

1. You could copy the old .QDR directories to the new sys volume.
2. You could also go to each queue object using NWAdmin and modify each print queue object in NWADMIN to point to the new queues         volume.
3. You could also delete and recreate the print queues.

Cause

Corrupt NDS schema.

Fix

Repair schema:
1.  Load DSREPAIR.NLM | Advanced options | repair local DS database | Select "rebuild operational schema = YES."  All others can be set to NO.

Cause

Corrupt DS volume object.

Fix

Remove and recreate the volume object.
1. Go to NWAdmin | choose the volume object | Delete it.
2. Run DSREPAIR.NLM | Advanced options menu | Check volume objects and trustees. (This step will recreate the volume object.)
2A.  Another way to recreate the volume objects is to go to load INSTALL.NLM | directory services options | upgrade mounted volumes into the directory.

Cause

Various issues with NWAdmin32.

Fix

Downloading the latest version of NWAdmin32.  Currently (14 Mar 2000) the file is ADMN519F.EXE from the Support Connection Web Site / File Finder page.

Cause

Possible communication delay problem.

Fix

Place a copy of the replica where the print queue objects reside on the server where print queue volumes are located.

Cause

Trustee Assignments were lost during the upgrade.  

Fix

Verify or Re-establish Admin as a trustee of the server object and grant explicit Supervisor rights (object and property).  

Cause

Inconsistencies in the replica ring where the print queue resides.

Fix

Verify that print queue is on each server in the replica ring.  Use DSBROWSE (5.x) or DSVIEW (4.X) on each Read Write and Master replica to see if the print queue is each server in the replica ring.  Errors in synchronization in the replica ring were the print queue resides can cause this error.