Highlighted
Absent Member.
Absent Member.
3832 views

After 18.1 upgrade, cannot find users

I upgraded our groupwise server to 18.1, and after a few issues, updated the databases to the latest version. The only problem is that the mobility server connects OK to the updated groupwise with no errors, but cannot find any users in the database. I have checked all the settings, created a new trusted key, etc, but the mobility server still cannot find any users. This is hosted on a separate computer (Linux), and no changes were initially made before it stopped processing emails (after the 18.1 upgrade)

Anyone got any ideas what has happened, and how to get things going again?

Cheers

ChasR.
Labels (1)
0 Likes
36 Replies
Highlighted
Absent Member.
Absent Member.

This is now working, and I can telnet in from the mobility server. Now still not working, as I have checked whether the GAL is populated, and the SELECT * FROM gal returns nothing. I have run dsapp to recreate the GAL but nothing is coming through.

Thanks fro getting back to me so promptly,

Chasr
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

On 05.12.2018 00:44, chas wrote:
>
> This is now working, and I can telnet in from the mobility server. Now
> still not working, as I have checked whether the GAL is populated, and
> the SELECT * FROM gal returns nothing. I have run dsapp to recreate the
> GAL but nothing is coming through.
>
> Thanks fro getting back to me so promptly,
>
> Chasr
>
>

Do you still see the same errors in the log?
Question: Do you have a http proxy configured in Yast?

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi,

Look in the groupwise-agent.log file just after the GMS service is started for where [GALMonitor_Thread] starts and does it's thing. Pay attention to the lines that look like this:

{http://schemas.novell.com/2005/01/GroupWise/types}firstSequence = <there's a number here> [IntElement]
{http://schemas.novell.com/2005/01/GroupWise/types}lastSequence = <there's a number here> [IntElement]

Where the numbers are the "lastSequence" should be greater than the "firstSequence".

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Things which come into my mind
- invalid address book user
- problems with the trusted app
- invalid characters in address book entries
- visibility problems

Check Laura's post
https://forums.novell.com/showthread.php/510354-After-18-1-upgrade-cannot-find-users?p=2491941#post2491941
maybe a concurrent SOAP trace might help.
If you like it: like it.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi Laura,
Just tested out the log files and the forst and last sequence are the same: see below

{http://schemas.novell.com/2005/01/GroupWise/types}firstSequence = 37 [IntElement]
{http://schemas.novell.com/2005/01/GroupWise/types}lastSequence = 37 [IntElement]

Where do we go from here?

ChasR
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi ChasR

Your address book deltas appear to be out. Try this:

1. Login to the GroupWise Admin Console
2. Go to the Post Office that contains the GMS Address Book User
3. Go to the Settings tab
4. Ensure that Create Deltas is enabled under the Address Book Update Settings section

You might need to restart the POA and GMS to kick this into place.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi Laura,
This was already set, but I increased the number of days by 1 and saved the new setting. Restarted the groupwise server and the other mobility server, but the problem still exists. Have to continue with the LDAP option.

Thanks for trying,

ChasR.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

While not 100% sure i think the corresponding theads runs at midnight, so maybe you wouldn't see a possible effect immediately. I'd still be interested in a SOAP trace. Apart from that: did you validate the corresponding DBs? Did you try to rebuild the listing indexes?
If you like it: like it.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,
This did not work either. I rebuilt all the databases, and no luck after this was carried out. This weekend I intend to run up the groupwise vm which I saved before the upgrade and see if the new mobility server connects correctly. I Also have a saved vm for the mobility server, I can try both, though I did not initially install the new mobility server after the Groupwise update, and noticed the problem here which then prompted me to upgrade the mobility server.

Will post the results next week.

ChasR
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Just to make these sure, as it's never been mentioned:
Is your current 18.1.0 mobility box at SLES12SP3?
Which GW build were you on before upgrading to 18.1.0?

Also, just in case, be aware of this one
https://support.microfocus.com/kb/doc.php?id=7023577
If you like it: like it.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,
I have given up with this problem, and will rebuild the mobility server, then the groupwise server over Christmas to get over the problem, even though I can use LDAP and everything works fine. As an aside, I did not upgrade to the SLES12SP3 when I encountered the problem. However, just to make sue, the last thing I have done is upgrade to the SP3 making sure that I have newest python-pyOpenSSL (note they have updated the 7023577 to reflect a newer version of this program), and it made no difference to my initial problem. However, after this update, I find that the dashboard of the mobility server is no longer working, although everything else is!! I might wait an see before I do a rebuild is this is a function of the SLES12SP3 before I make any more changes.

Thanks everyone for their assistance,

ChasR.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

AFAIK SP3 is a prerequisite for GMS18.1
https://support.microfocus.com/kb/doc.php?id=7023545

As for the dashboard: this one might help...
https://download.novell.com/Download?buildid=rII7z_6ASIk~#
If you like it: like it.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.