After Upgrade, New clietn cannot Login

Hi,
I have upgraded to the latest 18.1 upgrade of groupwise, and while the previous client would log into the upgraded version of the groupwise server, I foolishly forced the client upgrade around the network, !!!! I now get the message that the new client from the upgrade cannot log into the server!!! If I downgrade the client to the previous version, it can then log in. My main problem is that I have set the server to force an upgrade after 2 logins of the old client. HELP.

Anyone got any ideas.

I am using vms, I have tried this a couple of times with the same result.

Any help would be mist welcome.

Regards

ChasR.
  • chas wrote:

    > Anyone got any ideas.


    18.1 is considered a major upgrade.

    Did you complete the configuration after installing?

    Check the version of the post office database. Did it get upgraded?

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
  • Hi,
    I have run the upgrade a couple of time with no errors: - but in addition to the previous problems, the groupwise mobility server now loses the users login to its service. If I revert to the previous vm with no changes, the andoid phone will connect with no problems, but when I update the groupwise server to the new version, the phone cannot verify the account.

    I must say that this is the worst update that I have encountered up to now with things not working. Normally the updates work with no problems, but this is a nightmare. My phones will not synchronize, and the client within the install cannot connect to the server. If go back to the previous client, and get over the "force update client" which I set up on the server, the older client connects with no problems.

    Please get this sorted.!!

    Regards

    ChasR
  • On 17.11.2018 02:36, chas wrote:
    >
    > Database version 1800
    >
    >

    Again. You did not run the absolutely necessary configuration and
    database upgrade step, you just ran the install.

    Because this is such a common problem this time round, I checked the
    docs again. They are absolutely clear on this, I fail to understand why
    nobody seems to read them.

    https://www.novell.com/documentation/groupwise18/gw18_guide_install/data/inst_upgrade_install_linux.html

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • Thanks Massimo:- this does the trick. I am getting complacent in my old age, and did not bother to check the documentation. The new clients are now connecting properly.

    After the upgrade to 18.1, my groupwise mobility server cannot find any users in the groupwise database:- it connects OK to the server, and there are no errors coming up, but users cannot be found. Is this to do with the updated database? I have checked for new versions of the mobility server but as yet have found nothing to help. I may have to post this problem in another section, but you may have an idea where the problem lies and how to get things working again.

    Thanks again for your help

    ChasR
  • mrosen;2491032 wrote:
    On 17.11.2018 02:36, chas wrote:
    >
    > Database version 1800
    >
    >

    Again. You did not run the absolutely necessary configuration and
    database upgrade step, you just ran the install.

    Because this is such a common problem this time round, I checked the
    docs again. They are absolutely clear on this, I fail to understand why
    nobody seems to read them.

    https://www.novell.com/documentation/groupwise18/gw18_guide_install/data/inst_upgrade_install_linux.html

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


    I just went over the documentation and will disagree with you as to being absolutely clear. If it said to upgrade to 18.1 then I would agree, but when I read it I (and I guess I and a lot of others) assume as upgrading to 18 software from an earlier version such as 14

    When doing the upgrade to 18.02 there were instructions with the file download as to how to upgrade the "Groupwise 18 Support Pack 2" At the bottom of these instructions it says "There is no need to reconfigure any aspect if it has been installed or configured previously.

    I have learned a good lesson. I will wait a while before I upgrade again.
  • In article <ptKHD.1668$C62.1143@novprvlin0914.provo.novell.com>,
    Massimo Rosen wrote:
    > I fail to understand why
    > nobody seems to read them.


    RTFM? Lots of us skip them on what is easily perceived as a 'just' a
    service patch, after all it is what SP stands for.
    Reading every version of them is almost like reading every instance of
    the EULA so many of us just skip through to get to the install. Just
    too much to read. <sigh>


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://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!

  • Andy,

    On 19.11.2018 23:18, Andy Konecny wrote:
    > In article <ptKHD.1668$C62.1143@novprvlin0914.provo.novell.com>,
    > Massimo Rosen wrote:
    >> I fail to understand why
    >> nobody seems to read them.

    >
    > RTFM? Lots of us skip them on what is easily perceived as a 'just' a
    > service patch, after all it is what SP stands for.


    Well, I already said elsewhere that the versioning is more than just a
    bit confusing currently. At least it's the whole industry that has
    adopted that whole nonsense. Why? I have *NO* idea, but we have to live
    with it. Last time it was "R2" (shamelessly following every nonsense
    Microsoft starts), now it's that .1 is a new version and the service
    pack is .01. MAybe next time we could try the good old "EP" again (only
    very very old folks will get that).

    > Reading every version of them is almost like reading every instance of
    > the EULA so many of us just skip through to get to the install. Just
    > too much to read. <sigh>

    Of course, *BUT*, at least when I run into problems I start to read them.

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • In article <1jTID.1710$C62.549@novprvlin0914.provo.novell.com>, Massimo Rosen wrote:
    > MAybe next time we could try the good old "EP" again (only
    > very very old folks will get that).

    Ah Y2K 'fun' where version numbers couldn't get incremented to 5.6 ;)

    > Of course, *BUT*, at least when I run into problems I start to read them.

    Which is why we get to answer the questions for those who just can't be bothered to read. <sigh>


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://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!