Discussion Locked

Novell GroupWise 5.5 server

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Tried to add or delete users on GW server and received "lock file error" while in NWADMIN. I worried GW server is out of space on HD. Downed server and ran VREPAIR to make sure all deleted files were purged. Still could not delete or add users. I need to add 4 new employees to the GW server ASAP. Any ideas. Server is small 2 4GB drives mirrored. would it be much of a job to add a 40GB drive. Server was never configured to be backed up via tape drive. Worried about lossing data. Admin at other office had to leave so I am taking responsibility of other network (75 miles away) including email server (separate Novell network). Runs via TCP/IP for client access. 35 users.

Any help would be appreciated....

Rob

5 replies

by tbradley

1st, vrepair will not purge deleted files, you have to do this through nwadmin, tools, salvage.... or via the filer command in the public directory.

Not sure from your description wether you are trying to add or delete users from a local server,or the remote server.

I've come across this problem before, and it has to do with your connection type. Check your connection, and if you are only "authenticated" you do not have file system rights. You must have a logged in connection to affectGroupwise objects in the wphost.db file. Log in as admin directly to the GW server, and run NWadmin from it's public\win32 directory.

by epait

Hey,

Thanks.... ended up logging into server via network neighborhood and then logging in as ADMIN through NWADMIN.... which opened up the tree for the GW server. I then had rights to delete and add users. Also ran a purge via the Filer.exe program via windows explorer. Found I still have 3GB of free space left... should be okay for a while.

thanks for your help!
Rob

by dle

Was it an 8201 error? Your WPHOST.DB file is locked by another client somewhere on the network.

Since it is a small network, you can try having everyone quit GroupWise, use Monitor.nlm to check open files by each user. There will probably a connection out there that still hangs on the the GroupWise DB. Shut down that station to terminate the connection and clear the connection from the console if you need to.

If the above steps do not work, you may need to bring down and restart the GroupWise POA, or even bring down the NW server.

Also, what is the version of the client32 that you are using? There were some serious problems with the early 3.2 release. The one we are using is 3.21 with SP5 and it seems to be working fine so far.

This discussion is closed to new replies.