Hi Ken,

The VXSVC is a DELL Array Manager module.

We've found that DELL couldn't care less about what NLM versions are already
installed on your server. The best bet here is to reapply all NetWare
patches.

Be extra careful when applying DELL utilities and patches. Compare ALL
versions to
ensure it doesn't downgrade your existing versions.

The way I do it is to run a utility such as Beyond Compare (or something
similar) after I've
extracted the DELL utilities to a temporary location. I then update all the
files with the newest
version before running the installation program. This way, any updated files
will be of the same (or newer)
version. This has worked well.

Just don't trust DELL to be current.

Frank

"Ken Martin" wrote in message
news:3f9ed587@ROSASTDMZ05....
>
> I am using the demo version of BE 9.1. I am running on nw 6 sp3 with
groupwise
> 6.5 sp1. For the last week when I load bestart the server abends with the
> following:
>
> Server MAIL1 halted Tuesday, October 28, 2003 2:29:18.739 pm
> Abend 1 on P00: Server-5.60.03: Page Fault Processor Exception (Error code
> 00000000)
>
> Registers:
> CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
> EAX = 00000001 EBX = C1C02200 ECX = ACC4BC4C EDX = C0EE4CD0
> ESI = C401D3C0 EDI = C3FF0C56 EBP = C0EE4CB4 ESP = C0EE4C94
> EIP = D0D34C1B FLAGS = 00010202
> D0D34C1B 3300 XOR EAX,[EAX]=?
> EIP in UNKNOWN memory area
> Access Location: 0x00000001
>
> The violation occurred while processing the following instruction:
> D0D34C1B 3300 XOR EAX,[EAX]
> D0D34C1D 2922 SUB [EDX],ESP
> D0D34C1F 0300 ADD EAX,[EAX]
> D0D34C21 7F02 JG D0D34C25
> D0D34C23 48 DEC EAX
> D0D34C24 3400 XOR AL,00
> D0D34C26 B324 MOV BL,24
> D0D34C28 0300 ADD EAX,[EAX]
> D0D34C2A 9E SAHF
> D0D34C2B 004835 ADD [EAX+35],CL
>
>
>
> Running process: VXSVC__P 8 Process
> Thread Owned by NLM: VXSVC.NLM
> Stack pointer: C0EE502C
> OS Stack limit: C0ED52C0
> Scheduling priority: 67371008
> Wait state: 5050100 Delayed
> Stack: C3FF43BD (ASPIPRO.NLM|ASPIPerformSCSICommand+B0)
> --C0EE4CD0 ?
> --C0EE4C02 ?
> --C0ED5202 ?
> --00010000 ?
> ACC4371E (THREADS.NLM|__Must_Have_Three_One_Or_Greater+A)
> --00000006 ?
> --0000000E ?
> --C0EE4D4C ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FF68D8 (ASPIPRO.NLM|MarbleGetDevState+A9)
> --00000002 ?
> --C0EE4CD0 ?
> --01020002 ?
> --00000000 ?
> --00000005 ?
> --000E0000 ?
> --00000000 ?
> --06000000 ?
> --42E20000 ?
> --0000C3FF ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --479446C0 ?
> --00000001 ?
> --C0ED52C0 ?
> --00010000 ?
> ACC437FF (THREADS.NLM|_InternalSuspendOrStop+1F)
> --00000002 ?
> --C401D302 ?
> --C0EE4D80 ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FDDDF5 (ASPIPRO.NLM|GetCdromState+57)
> --00000000 ?
> --00000000 ?
> --00000005 ?
> --C0EE4D7C ?
> --00010000 ?
> ACC4371E (THREADS.NLM|__Must_Have_Three_One_Or_Greater+A)
> --00000034 ?
> --C401D3C0 ?
> --C0EE4E5C ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FDC79A (ASPIPRO.NLM|AllCdromRescan+24C)
> --00000000 ?
> --00000000 ?
> --00000005 ?
> --C0EE4E34 ?
> --C0EE4E24 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --C1C02200 ?
> --00000000 ?
> --00000463 ?
> --C2DE3100 ?
> --C1D7E1C4 ?
> --00000463 ?
> --C0EE4E18 ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C1D5D2EC (VXSVC.NLM|_VxSVCIsServiceON@0+11D6)
> --C2DE3128 ?
> -C1D6EC0B (VXSVC.NLM|(Data Start)+9C0B)
> --000000A6 ?
> -C1D78130 ?
> --00000000 ?
> --C2DE3128 ?
> --00000FFF ?
> --00000000 ?
> --00000FFF ?
> --00000000 ?
> --00000001 ?
> --00000000 ?
> --00000000 ?
> --01000000 ?
> --00000000 ?
> --00000FFF ?
> --00000000 ?
>
> Additional Information:
> The CPU encountered a problem executing code in SERVER.NLM. The
problem
> may be in that module or in data passed to that module by a process owned
> by VXSVC.NLM.
>
> Loaded Modules:
> BECLIENT.NLM Backup Exec - Administration Console
> Version 9.10
> Code Address: 4CD1B000h Length: 000D53B9h
> Data Address: 4CDF1000h Length: 00047470h
> BESRVR.NLM Backup Exec - Job Server
> Version 9.10
> Code Address: 4C74B000h Length: 00119B83h
> Data Address: 4C865000h Length: 0004AC00h
> BEPSVR.NLM Backup Exec - NCPE Server
> Version 9.10
> Code Address: 4C49D000h Length: 000D7664h
> Data Address: 4C575000h Length: 00033F50h
> Thanks

Ken Martin wrote:

>
> I am using the demo version of BE 9.1. I am running on nw 6 sp3 with
> groupwise 6.5 sp1. For the last week when I load bestart the server
> abends with the following:
>
> Server MAIL1 halted Tuesday, October 28, 2003 2:29:18.739 pm
> Abend 1 on P00: Server-5.60.03: Page Fault Processor Exception (Error
> code 00000000)
>
> Registers:
> CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
> EAX = 00000001 EBX = C1C02200 ECX = ACC4BC4C EDX = C0EE4CD0
> ESI = C401D3C0 EDI = C3FF0C56 EBP = C0EE4CB4 ESP = C0EE4C94
> EIP = D0D34C1B FLAGS = 00010202
> D0D34C1B 3300 XOR EAX,[EAX]=?
> EIP in UNKNOWN memory area
> Access Location: 0x00000001
>
> The violation occurred while processing the following instruction:
> D0D34C1B 3300 XOR EAX,[EAX]
> D0D34C1D 2922 SUB [EDX],ESP
> D0D34C1F 0300 ADD EAX,[EAX]
> D0D34C21 7F02 JG D0D34C25
> D0D34C23 48 DEC EAX
> D0D34C24 3400 XOR AL,00
> D0D34C26 B324 MOV BL,24
> D0D34C28 0300 ADD EAX,[EAX]
> D0D34C2A 9E SAHF
> D0D34C2B 004835 ADD [EAX+35],CL
>
>
>
> Running process: VXSVC__P 8 Process
> Thread Owned by NLM: VXSVC.NLM
> Stack pointer: C0EE502C
> OS Stack limit: C0ED52C0
> Scheduling priority: 67371008
> Wait state: 5050100 Delayed
> Stack: C3FF43BD (ASPIPRO.NLM|ASPIPerformSCSICommand+B0)
> --C0EE4CD0 ?
> --C0EE4C02 ?
> --C0ED5202 ?
> --00010000 ?
> ACC4371E (THREADS.NLM|__Must_Have_Three_One_Or_Greater+A)
> --00000006 ?
> --0000000E ?
> --C0EE4D4C ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FF68D8 (ASPIPRO.NLM|MarbleGetDevState+A9)
> --00000002 ?
> --C0EE4CD0 ?
> --01020002 ?
> --00000000 ?
> --00000005 ?
> --000E0000 ?
> --00000000 ?
> --06000000 ?
> --42E20000 ?
> --0000C3FF ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --479446C0 ?
> --00000001 ?
> --C0ED52C0 ?
> --00010000 ?
> ACC437FF (THREADS.NLM|_InternalSuspendOrStop+1F)
> --00000002 ?
> --C401D302 ?
> --C0EE4D80 ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FDDDF5 (ASPIPRO.NLM|GetCdromState+57)
> --00000000 ?
> --00000000 ?
> --00000005 ?
> --C0EE4D7C ?
> --00010000 ?
> ACC4371E (THREADS.NLM|__Must_Have_Three_One_Or_Greater+A)
> --00000034 ?
> --C401D3C0 ?
> --C0EE4E5C ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C3FDC79A (ASPIPRO.NLM|AllCdromRescan+24C)
> --00000000 ?
> --00000000 ?
> --00000005 ?
> --C0EE4E34 ?
> --C0EE4E24 ?
> --00000000 ?
> --00000000 ?
> --00000000 ?
> --C1C02200 ?
> --00000000 ?
> --00000463 ?
> --C2DE3100 ?
> --C1D7E1C4 ?
> --00000463 ?
> --C0EE4E18 ?
> C3FF0C56 (ASPIPRO.NLM|PollStatus+0)
> --C401D3C0 ?
> --C1C02200 ?
> C1D5D2EC (VXSVC.NLM|_VxSVCIsServiceON@0+11D6)
> --C2DE3128 ?
> -C1D6EC0B (VXSVC.NLM|(Data Start)+9C0B)
> --000000A6 ?
> -C1D78130 ?
> --00000000 ?
> --C2DE3128 ?
> --00000FFF ?
> --00000000 ?
> --00000FFF ?
> --00000000 ?
> --00000001 ?
> --00000000 ?
> --00000000 ?
> --01000000 ?
> --00000000 ?
> --00000FFF ?
> --00000000 ?
>
> Additional Information:
> The CPU encountered a problem executing code in SERVER.NLM. The
> problem may be in that module or in data passed to that module by a
> process owned by VXSVC.NLM.
>
> Loaded Modules:
> BECLIENT.NLM Backup Exec - Administration Console
> Version 9.10
> Code Address: 4CD1B000h Length: 000D53B9h
> Data Address: 4CDF1000h Length: 00047470h
> BESRVR.NLM Backup Exec - Job Server
> Version 9.10
> Code Address: 4C74B000h Length: 00119B83h
> Data Address: 4C865000h Length: 0004AC00h
> BEPSVR.NLM Backup Exec - NCPE Server
> Version 9.10
> Code Address: 4C49D000h Length: 000D7664h
> Data Address: 4C575000h Length: 00033F50h
> Thanks

I would uninstall Dell Array Manager and use the Fast Utility. It was
nothing but problematic for me on my PE4400. Fast is command line, but
doesn't abend my server like Array Manager was doing. I'm responsible
for 4 Del Netware servers in 3 locations and I have to have something
depnable. Array manager is obviously a Windows toy, are you listening
Dell Tech Support?

"Peter Jam" wrote:
>Ken Martin wrote:
>
>>
>> I am using the demo version of BE 9.1. I am running on nw 6 sp3 with
>> groupwise 6.5 sp1. For the last week when I load bestart the server
>> abends with the following:

>
>I would uninstall Dell Array Manager and use the Fast Utility. It was
>nothing but problematic for me on my PE4400. Fast is command line, but
>doesn't abend my server like Array Manager was doing. I'm responsible
>for 4 Del Netware servers in 3 locations and I have to have something
>depnable. Array manager is obviously a Windows toy, are you listening
>Dell Tech Support?

Thanks for identifying the problem. This is a 4400 also and the raid firmware
needed to be updated. This was installed with it. The fast cli thing worked
well so I will see to getting rid of the array manager. Thanks

Ken

Ken Martin wrote:

>
> "Peter Jam" wrote:
> >Ken Martin wrote:
> >
> >>
> >> I am using the demo version of BE 9.1. I am running on nw 6 sp3
> with >> groupwise 6.5 sp1. For the last week when I load bestart the
> server >> abends with the following:
>
> >
> >I would uninstall Dell Array Manager and use the Fast Utility. It
> was >nothing but problematic for me on my PE4400. Fast is command
> line, but >doesn't abend my server like Array Manager was doing. I'm
> responsible >for 4 Del Netware servers in 3 locations and I have to
> have something >depnable. Array manager is obviously a Windows toy,
> are you listening >Dell Tech Support?
>
> Thanks for identifying the problem. This is a 4400 also and the raid
> firmware needed to be updated. This was installed with it. The fast
> cli thing worked well so I will see to getting rid of the array
> manager. Thanks
>
> Ken

You are very welcome, we learn from our mistakes :>