Update GW14.2.2: After update login to the gwadmin-console is notpossible

Hi,

the update from 14.2.1 to 14.2.2 I can not login to the gwadmin-console.
In the browser the login screen comes up and after the login this
messages comes:

Failed to get data from the admin service.
Details:
Type 'com.google.gwt.user.client.rpc.XsrfToken' was not assignable to
'com.google.gwt.user.client.rpc.IsSerializable' and did not have a
custom field serializer. For security purposes, this type will not be
deserialized.

netstat shows port 9710 is listening

Logs in /var/log/novell/groupwise/gwadmin/ does not showing error messages.

Any hints what to check?

  • Am 03.05.2017 um 19:24 schrieb nntp-user:
    > Hi,
    >
    > the update from 14.2.1 to 14.2.2 I can not login to the gwadmin-console.
    > In the browser the login screen comes up and after the login this
    > messages comes:
    >
    > Failed to get data from the admin service.
    > Details:
    > Type 'com.google.gwt.user.client.rpc.XsrfToken' was not assignable to
    > 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a
    > custom field serializer. For security purposes, this type will not be
    > deserialized.
    >
    > netstat shows port 9710 is listening
    >
    > Logs in /var/log/novell/groupwise/gwadmin/ does not showing error messages.
    >
    > Any hints what to check?
    >

    The gwadminutil installcfg has to be run again after the update.

    After a few times(!) -each time when migrating (it is a cluster) a
    ressource.

    # geadmintuil installcfg -m user -u <Username> -p <Password>
    Where <Username> and <Password> are the credentials from the GWadmin.


  • On Thu, 04 May 2017 06:00:46 GMT, nntp-user <nomail@outlook.com>
    wrote:

    >Am 03.05.2017 um 19:24 schrieb nntp-user:
    >> Hi,
    >>
    >> the update from 14.2.1 to 14.2.2 I can not login to the gwadmin-console.
    >> In the browser the login screen comes up and after the login this
    >> messages comes:
    >>
    >> Failed to get data from the admin service.
    >> Details:
    >> Type 'com.google.gwt.user.client.rpc.XsrfToken' was not assignable to
    >> 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a
    >> custom field serializer. For security purposes, this type will not be
    >> deserialized.
    >>
    >> netstat shows port 9710 is listening
    >>
    >> Logs in /var/log/novell/groupwise/gwadmin/ does not showing error messages.
    >>
    >> Any hints what to check?
    >>

    >The gwadminutil installcfg has to be run again after the update.
    >
    >After a few times(!) -each time when migrating (it is a cluster) a
    >ressource.
    >
    ># geadmintuil installcfg -m user -u <Username> -p <Password>
    >Where <Username> and <Password> are the credentials from the GWadmin.
    >


    Thanks for sharing the solution!

    --
    Ken
    Knowledge Partner

    If this post was helpful and you are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

    Create and vote for enhancements!
    https://www.microfocus.com/products/enhancement-request.html
  • My supervisor gets this same error on 1 domain out of 3 that have been upgraded from 14.2.1 -125534 to 14.2.2 -126868.

    She gets it when using FireFox, but not when using IE 11.
    She's restarted her computer.
    I've asked her to clear out the cache in FF, but she hasn't had a chance to do so yet.

    She's the only person that gets the error.
    I and the 3rd admin for our system do not.

    I don't think it's germane, but the server in question hosts the primary domain.

    Most of the other search results for a not assignable to 'com.google.gwt.user.client.rpc error seem to be java-related, but those cases don't clarify whether it's a server-side java issue or not.
  • Clearing the browser's cache solved the issue for her.
  • this happened to me as well and thank you, clearing the firefox browser history (cache) made it work again.

    pretty bad!

    Max
  • this happened to me as well and thank you, clearing the firefox browser history (cache) made it work again.

    pretty bad!

    Max