After 18.1 upgrade, cannot find users

[chas1]

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.

[chas1]

Version 18.0.1 Build 280

[mathiasbraun]

Please elaborate "cannot find any users". Also, while likely unrelated, the GMS build which came with 18.1.0 is 410.

[chas1]

Hi,
Thanks for the response. I must have pasted the wrong iso when I did the upgrade. Put this right and now running 410. Problem is still there though, but I have worked around it. When I originally set up the system, I had the user source as groupwise, and could find the users when I made an interrogation. This no longer happens, and nothing can be found. I have changed the source to LDAP, and interrogated the LDAP server, and can add users successfully from here, and they all work successfully. I have rebooted the server, and tried again with interrogating groupwise, but still no good. Looks like I am stuck with LDAP.

Hope you have some ideas what has changed or what needs changing.

Cheers

ChasR

[mathiasbraun]

Just a guess: SSL settings changed somewhere, e.g. SSL for SOAP on the POA set to "required" where it's been disabled before. Validation enabled in the GMS config, ...

[chas1]

No Luck
Tried this out but didn't work. Still using LDAP.

Thanks for the suggestion,,
ChasR.

[mathiasbraun]

Did you already run a "general health check" from within dsapp?
With log level set to "debug", upon trying to browse users in the "add" (with groupwise selected as a source) dialog, which errors do you see in /var/log/datasync/configengine/configengine.log ?
Have you tried changing the GAL user?

[KonecnyA]

In article <chas.8qvr3c@no-mx.forums.microfocus.com>, Chas wrote:
> I upgraded our groupwise server to 18.1,

did you run the Configuration after the install of the upgrade.
It is actually needed on this particular service patch just like any of
the major upgrade.



Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
GMS troubleshooting tips at
https://www.konecnyad.ca/andyk/gwmobility.htm

[chas1]

Yes, if you do not run the configuration which updates the databases, the new client cannot access groupwise (you get a warning messagewhen you run the client):- the configuration fixes this.

[laurabuckley]

Hi Andy,

Just need to point out "particular service patch" - 18.1 is not a service a patch as you refer to it as. It's a major release and therefore a database upgrade is mandatory.

Cheers,

[KonecnyA]

In article <laurabuckley.8r72i0@no-mx.forums.microfocus.com>,
Laurabuckley wrote:
> Just need to point out "particular service patch" - 18.1 is not a
> service a patch as you refer to it as. It's a major release and
> therefore a database upgrade is mandatory.

Hi Laura
It is a perception thing. We were expecting a service patch and got
this thing that on the surface appeared to match the expected service
patch, so therefor many have simply treated it as a service patch.
That it was not a service patch is not clear for so many who weren't
expecting a version level change and are so used to version/patch
number definitions constantly changing. Sometime a service patch is .1
or sometimes it is a .0.1 we just aren't a consistant industry and
this is the result.
Yes I know, it is point were we just 'sigh'


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
GMS troubleshooting tips at
https://www.konecnyad.ca/andyk/gwmobility.htm

[chas1]

Have run dsapp and done health check, rebuild database etc, but still cannot see groupwise users. OK with LDAP, but the problem is bugging me. Will try with the debug level set this weekend to see if it throws any light on this problem.

[laurabuckley]

Hi,

Using dsapp rebuild the GAL.

Cheers,

[chas1]

Thanks, will try this weekend.

ChasR

[chas1]

Tried this:- made no difference. This only happened after the new major upgrade to groupwise. It worked fine before then.

ChasR