How do I fix a corrupt Print Queue

[Learningaccess]

The following is what I see in the vol$log.err file<br><br>Thank You in advance.<br><br>Volume SYS mounted on Tuesday, May 2, 2000&nbsp;&nbsp;&nbsp;1:53:23 pm.<br>Volume mount had the following errors that were fixed:<br>Problem with file Q_02D5.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file _T-00004.TMP, length extended.<br>Problem with file _T-00004.TMP,&nbsp;&nbsp;old length = 0, new length = 65536<br>Problem with file ACCESS, length extended.<br>Problem with file ACCESS,&nbsp;&nbsp;old length = 131072, new length = 196608<br>Problem with file _SWAP_.MEM, length extended.<br>Problem with file _SWAP_.MEM,&nbsp;&nbsp;old length = 0, new length = 2228224<br>Problem with file TP11006, length extended.<br>Problem with file TP11006,&nbsp;&nbsp;old length = 128, new length = 131072<br>Problem with file Q_0269.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0268.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0266.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0265.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0264.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0262.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0260.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_025F.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file CONSOLE.LOG, length extended.<br>Problem with file CONSOLE.LOG,&nbsp;&nbsp;old length = 0, new length = 65536<br><br>Volume SYS mounted on Tuesday, May 2, 2000&nbsp;&nbsp;&nbsp;5:15:54 pm.<br>Volume mount had the following errors that were fixed:<br>Problem with file Q_02D5.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file _T-00004.TMP, length extended.<br>Problem with file _T-00004.TMP,&nbsp;&nbsp;old length = 0, new length = 65536<br>Problem with file _SWAP_.MEM, length extended.<br>Problem with file _SWAP_.MEM,&nbsp;&nbsp;old length = 0, new length = 2228224<br>Problem with file TP11039, length extended.<br>Problem with file TP11039,&nbsp;&nbsp;old length = 128, new length = 131072<br>Problem with file Q_0269.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0268.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0266.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0265.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0264.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0262.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_0260.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file Q_025F.SRV, (TTS file...was not changed)<br>&nbsp;&nbsp;length kept = 0, had allocated = 65536<br>Problem with file CONSOLE.LOG, length extended.<br>Problem with file CONSOLE.LOG,&nbsp;&nbsp;old length = 0, new length = 65536

 

[Brianc2k]

It has been my experience to delete the queue and then set up another one.&nbsp;&nbsp;Often it is quicker to just rebuild a queue's printing service then to troubleshoot beyond initial user postings.&nbsp;&nbsp;

 

[met]

You didn't say what version of netware but if it's using queue based printing I assume it less than five. My suggestion would be to delete and re-create the queue. It's not that difficult and I've found in novell that sometimes deleting and re-creating objects is much quicker than trying to repair them.<br>MET

 

[dfg]

Well as can be seen by the swap file on sys, the dude is running NW5+.<br>Anyway dismount sys try vrepair, otherwise blow the mother and recreate as suggested above.

 

[ss702sh]

I agree with the delete and recreate method. This will work without error or lost sleep. Dont worry about recreating this type of object. While deleting and recreating a container would be cumbersome and complex, this type of object should always be deleted if corruption is suspected. I have worked with Novell for a couple of years and I have done this several times. Keep inmind to make the name of the object the same or you may have other items that will need changing that you may not be aware of, e.g.Login Scripts or similar.

 

[Guest_imported]

These problems caused by improper shutdown, not a queue problem. Hitting the power switch instead of down/exit will leave open files that get repaired on next boot

 

[TheLad]

nw411 - I agree. There is no need to take any action as the problems were repaired when the volume mounted. -----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------