Cool Solutions

GroupWise 7.02 Webaccess stops working on NW65SP2



By:

August 5, 2008 2:16 pm

Reads:5,508

Comments:0

Score:4

Problem: NetWare 6.5 sp6 server abends when apache2.nlm tries to load. OS would load fine. Abend would occur immediately after apache2.nlm would load. Server runs GW WebAccess 7.02hp only.

Abend is: Deadlock detected waiting for spinlock currently owned by CPU NLM’s at the top of the stack are nile.nlm and nwutil.nlm

  1. Upgraded to NW 6.5 sp7. This did not correct the issue.
  2. Upgraded server firmware to latest date. This did not correct the issue.
  3. Disabled hyperthreading in the bios. This did not correct the issue.
  4. Attempted to uninstall sp7 to undo changes. This did not correct the issue.
  5. Per novell – there was corruption with the install of sp7. attempted to reinstall sp7. Still had the same problem.
  6. Because of corruption – manually tried to upgrade the files. Still had problem.
  7. GroupWise WebAccess team verified wasn’t their issue. Web Services team verified it wasn’t their issue. Both said was an OS problem.
  8. Disabled ASR within the BIOS. Rem’d out “c:\acpidrv.psm” out of the startup.ncf file. Now apache2.nlm would load but would receive page fault abends with nile.nlm in the stack.
  9. Per Novell Support. Manually copy over the nile.nlm and the nwutil.nlm from sp6 to the box and restart server.
  10. Server OS came up clean. apache2.nlm came up clean and the GW WebAccess software loaded successfully.

Note: This issue was discovered on one of our servers by Christina Cline. I was assisting in the resolution of the issue. Gotta give cred where it is due!

1 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 5 (1 votes, average: 4.00 out of 5)
You need to be a registered member to rate this post.
Loading ... Loading ...

Tags:
Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS