Environment
Novell GroupWise 2014
Novell GroupWise 2012
Situation
When you change a user password from C1 (for GW201) or from webadmin console (GW2014), you can see admin message being passed to the user owning POA but new password was not set.
What you will see is similar to an example bellow:
11:37:28 FB42 MTP: Received file: /721101/po/wpcsout/ofs/2/a3cf9e78.003, Size: 754 11:37:28 FBB3 Processing a3cf9e78.003 Message ID(:0:0) 11:37:28 FBB3 Processing Admin Message (a3cf9e78.003) 11:37:28 FBB3 Processed OK 11:37:28 FBAB ADM: Completed: Update object in post office - Misc AEDOM.AEPOST (Administrator: admin.GWAE, Domain: AEDOM) 11:37:28 FBAB ADM: Completed: Update object in post office - Misc AEDOM.AEPOST (Administrator: admin.GWAE, Domain: AEDOM) 11:37:31 FB19 MTP: AEDOM: Connection established: 147.2.77.46 11:37:31 FB2A MTP: AEDOM: Connection established: 147.2.77.46 11:37:31 FB19 MTP: File sent: A3cf9e78.003 Queue: 2 Size: 426 11:37:31 FB2A MTP: File sent: A3cf9e78.001 Queue: 2 Size: 426
whilst it shall end up like:
11:48:18 2FDF MTP: Received file: /721101/po/wpcsout/ofs/2/a3cfa102.001, Size: 494 11:48:18 2FDF MTP: Received file: /721101/po/wpcsout/ofs/2/a3cfa102.003, Size: 494 11:48:18 3028 Processing a3cfa102.001 Message ID(:0:0) 11:48:18 3028 Processing Admin Message (a3cfa102.001) 11:48:18 3028 Processing admin task: Update Settings 11:48:18 3028 Successful merge of settings for novell1 11:48:18 3028 Processed OK 11:48:18 3028 Processing a3cfa102.003 Message ID(:0:0) 11:48:18 3028 Processing Admin Message (a3cfa102.003) 11:48:18 3028 Processing admin task: Update Settings 11:48:18 3028 Successful merge of settings for novell1 11:48:18 3028 Processed OK
where "successful merge of settings for <user>" is a assign that the user password was successfully changed.
Resolution
A reason for this problem is usually long name (more than 8 chars) of the POA object of post office. A fix is to delete such long name POA object and give it a regular name like POA ... or if really needed then POA1 or POA2. After you recreate new POA object, check all IP and port numbers and then also Post Office Links to make sure it is set to TCP using new POA object with all correct IP / port information.
Here are steps for GW2014:
1. Use webadmin console and click on Post Offices link.
2. Find a post office that you have problems with and in Object tab find Post Office Agents link. This is a place to delete old POA object and create and configure new POA object.
3. Once you create new POA object, a link between this PO and owning domain is set (still at the moment) to UNC which would not work for Linux server. Therefore click on Domains link and find the domain that owns your PO.
4. In Objects tab find a Post Office Links item - click on it. You will get a list of POs that belong to this domain.
5. Find the PO in a list and click on it. Here you can change the link from UNC -> TCP/IP protocol using newly created POA object. Confirm the change.
6. Return back to the PO object and click on Maintenance | Post Office Database.
7. From options select Rebuild Database which required POA to be downed.
8. Once a rebuild of the PO is finished you can start POA agent and test how changing a password for any user from this PO works.