I have hesitated to install SP6 just becuase what they had going with SP5 was so stable, why screw with it. Probably try it out sometime in the near future.
We are running 4.91 sp2 client. I do not support the desktops, so I don't know all the issues that may have come up, but nothing major has come my way that would require us to revert to a prior client. Personally, I have had no problems with the client on my workstations.
We have not upgraded to SP6, either.
After the upgrade you will also want to check for any new fixes that have been released since the service pack you apply. I know we have applied several after our install of SP5.
I successfully installed NW6.5 SP6 the other day to our production GroupWise server. No major problems. Minor problem was that it overwrote my custom apache configurations (for WebAccess), and it didn't backup the files it replaced with backups. So I had to salvage the original configurations and put them back in place.
It's been solid. Haven't had a single running problem.
Like I mentioned previously, when I first installed it, it blew up my custom Apache configuration and didn't save backups (even though I selected the 'backup all files" option).. I was able to pull them out of Salvage and was back in business in about 5 minutes. But other than that, it's been great.
I have only installed it on my servers running GroupWise, Messenger, iFolder, NetStorage. I have not applied it to any server running iPrint, eguide, Virtual Office, or ZEN services.
The violation occurred while processing the following instruction:
863E2BDC 0FB60E MOVZX ECX, byte ptr [ESI]
863E2BDF 83EB01 SUB EBX, 00000001
863E2BE2 880F MOV [EDI], CL
863E2BE4 75F0 JNZ 863E2BD6
863E2BE6 5F POP EDI
863E2BE7 5E POP ESI
863E2BE8 5B POP EBX
863E2BE9 C3 RET
863E2BEA 90 NOP
863E2BEB 90 NOP
You're looking at the wrong abend. That shows Abend #8. You need to trace the abend.log file back to abend #1 - that is the only reliable abend, and your starting point for troubleshooting. Each abend 'should' be logged in sequence of when it happened.
Note that if this is an NDPS problem, Novell does have a Post SP6 NDPS patch - I believe there was an abend problem identified immediately after SP6 was released.
The violation occurred while processing the following instruction:
863E2BDC 0FB60E MOVZX ECX, byte ptr [ESI]
863E2BDF 83EB01 SUB EBX, 00000001
863E2BE2 880F MOV [EDI], CL
863E2BE4 75F0 JNZ 863E2BD6
863E2BE6 5F POP EDI
863E2BE7 5E POP ESI
863E2BE8 5B POP EBX
863E2BE9 C3 RET
863E2BEA 90 NOP
863E2BEB 90 NOP
Running process: GW_TaskThrd_0 Process
Thread Owned by NLM: NDPSGW.NLM
Stack pointer: 982F08D8
OS Stack limit: 982ED800
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Yes that looks like the abend they mention in the 'issues resolved' section for NDPSGW in that patch. Did that resolve your issues and is your server stable again?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.