• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 399
  • Last Modified:

Netware 3.11

Hello, I work in company that has some old stuff.  We have a problem in one of the printer queues, where every time you select it or try and delete it from pconsole it crashes the server. Also the server crashes if we try and run the Pserver.

The abend error message is:

System halted Friday March 4
Abend General Protection Processor Execption (Error code 00000000)
OS Version: Novell Netware v3.11

We believe that if we can delete the queue we can clear the problem, however this is not possible through pconsole due to it causing the abend each time we even try to select the queue. Any backdoor ways to do this?

Thanks
0
Alpine
Asked:
Alpine
  • 3
  • 2
  • 2
  • +2
1 Solution
 
geoffrynCommented:
try deleting the print queue directory on the sys vol first, then use pconsole to delete the queue.
0
 
AlpineAuthor Commented:
We have tried that but when we select the folder it crashes again.  

This message seems to popup, when we even connect to the server.  

The abend error message is:

System halted Friday March 4
Abend General Protection Processor Execption (Error code 00000000)
OS Version: Novell Netware v3.11

All I want to do is try and get it stable for long enough to download some data off the hard drives.  Any Suggesions?
0
 
geoffrynCommented:
Have you done a vrepair on the volume?  The crsh asscessin the folder indicates corruption.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
klchamberlinCommented:
If you just want it up long enough to copy data from, edit the autoexec.ncf (in the system directory) and comment out the line that loads pserver.
Hope that helps
0
 
jgarrCommented:
Run bindfix on the server. It will clean up the bindery database. Then run bindfix AGAIN.
After that is complete, give it a try.

0
 
mmerhoffCommented:
I agree with jgar. Bindfix a couple of times. Also, make sure there aren't any print jobs which may be corrupt in the queue before you try to delete the queue itself.
0
 
AlpineAuthor Commented:
Accept
0
 
jgarrCommented:
I  guess it was corrupt jobs and not bindfix?
0
 
AlpineAuthor Commented:
There were corrupt jobs.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now