"Multiple abends are occurring - processor halted" HELP !

[hellbeach]

Hello everyone

I have a fresh install of NW51 with SP5 and also installed ZFD 3.2 on it.
I want to make an image of a couple of workstations using Drive Image 4.0 which I have placed on the server.

When I login to the server from a workstation using a DOS client and start running Drive Image 4.0 I get this message after a while: "Multiple abends are occurring - processor halted" on the NW51 machine, and the server is dead, I have to reboot it.

Anyone have a clue ?

Sincerely
Daniel

 

[TheLad]

Check SYS:SYSTEM\ABEND.LOG and post the abend messages - don't post all of it because there may be quite a lot. Just see if it says what caused the abend.

Have you got file caching off? SET CLIENT FILE CACHING ENABLED = OFF

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Jontmke]

HAHA, thelad you might as well put that in your signature!!

Good advice, just funny.

JON

 

[hellbeach]

Strange thing is that there is no abend log, do I have to enable abend logging some where ?

About "SET CLIENT FILE CACHING ENABLED = OFF", where do I set that ? in autoexec.ncf ?

 

[hellbeach]

I set "SET CLIENT FILE CACHING ENABLED = OFF" on the console (and I guess I can add it in autoexec.ncf as well ?) and it seems to have solved my problem, thanks a lot to THELAD )

About the abend.log : Why isn´t there one when multiple abends occurred ?

 

[hellbeach]

Hmm, I was a bit hasty to say that everything seemed to work fine (
When I started to take images of 2 workstations at the same time it got about half ways and then I got the "Multiple abends are occurring - processor halted" again.

Damit, what could the problem be ?

 

[TheLad]

Jontmke - just for you, SET CLIENT FILE CACHING = ON (no please don't!!!)

Hellbeach - do you have CONLOG loaded? If so, have you got it saving the old console log? If not, add the following line to the AUTOEXEC.NCF:

LOAD CONLOG FILE=SYS:SYSTEM\CONSOLE.LOG SAVE=SYS:SYSTEM\CONSOLE.OLD ENTIRE=YES SIZE=2500

This will create a console log called CONSOLE.LOG. When the server reboots, this file will get renamed to CONSOLE.OLD so check this file for anything strange. I am beginning to think you may have a hardware issue ..... Try reseating processor and RAM as well.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------