Cheers
Jamie
Abend 1 on P00: Server-5.60c: Page Fault Processor Exception (Error
code 00000000)
Registers:
CS = 0008 DS = 005B ES = 005B FS = 005B GS = 005B SS = 0010
EAX = CBE52654 EBX = 20202020 ECX = D7121C40 EDX = CBE52654
ESI = 00000002 EDI = 00000000 EBP = CBE52640 ESP = CBE5263C
EIP = D6CCB98D FLAGS = 00010202
D6CCB98D 8B432C MOV EAX,[EBX+2C]=?
EIP in DS.NLM at code start +001AF98Dh
Access Location: 0x2020204C
Running process: NtfySrvr 4 Process
Thread Owned by NLM: NTFYSRVR.NLM
Stack pointer: CBE530DC
OS Stack limit: CBE4F3A0
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Additional Information:
The CPU encountered a problem executing code in DS.NLM. The
problem may be in that module or in data passed to that module by a
process owned by NTFYSRVR.NLM.
"Jamie" <Jamie...@jcu.edu.au> wrote in message
news:2d9d4717.04062...@posting.google.com...
The original problem was clashes between our NT print que and our
novell print que going to the same printer. So due to jobs not
getting completed we put a banner page on them to let people know
who's is who's. We then separated the ques, so people on NT couldn't
see the same ques as novell. Hence the server continue to crash. But
on monday I managed to find this link:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10074417.htm
Which told me that this problem was caused by the banner page. The
surprising thing was that the error messages was the same as a printer
clash between NT and Novell.
Cheers
Jamie
Jamie...@jcu.edu.au (Jamie) wrote in message news:<2d9d4717.04062...@posting.google.com>...