Dear Dinesh,
Are you 100% sure that you reused the existing IPT data directory during your upgrade?
If you didn't, please redo the upgrade specifying your existing IPT data directory.
If you did, please inspect the IPT data directory/config/users.xml file and make sure is lists all existing users. Then please compare this users.xml file with the one in your backed up IPT data directory (the one you backed up before performing the upgrade). The contents should be identical. If they are, please just try restarting Tomcat. If they aren’t, please write me back directly without copying the list and we can continue to debug this problem together.
Best regards,
Kyle
On 17 Sep 2015, at 06:30, Dinesh Singh Pundir dspundir@wii.gov.in wrote:
Dear Kyle,
I have upgraded the IPT v2.3.1 released but there is one issue. I am not able to see the users which where there in the earlier version. Secondly a new user cannot be created in this version.
Kindly look into it.
Regards
Dinesh Pundir WII, INDIA Node
On 9/16/2015 3:30 PM, ipt-request@lists.gbif.org wrote:
Send IPT mailing list submissions to ipt@lists.gbif.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.gbif.org/mailman/listinfo/ipt or, via email, send a message with subject or body 'help' to ipt-request@lists.gbif.org
You can reach the person managing the list at ipt-owner@lists.gbif.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of IPT digest..."
Today's Topics:
- IPT v2.3.1 released (Kyle Braak)
Message: 1 Date: Tue, 15 Sep 2015 17:14:36 +0200 From: Kyle Braak kbraak@gbif.org To: ipt@lists.gbif.org Subject: [IPT] IPT v2.3.1 released Message-ID: 6D664F2A-BEC1-4CD5-9FAA-7F5E209F3587@gbif.org Content-Type: text/plain; charset="windows-1252"
Dear IPT users,
A new minor release of the IPT (v2.3.1) has been released and is available for download here [1].
This minor release fixes a bug [2] limited to IPT version 2.3, and affects resources whose metadata: contains non-English characters was edited after upgrading to version 2.3 To fix the problem, please upgrade to 2.3.1 and fix badly encoded characters in your metadata.
Instructions on how to upgrade your IPT can be found in the IPT?s Release Notes [3].
Sorry for the inconvenience this bug may have caused you,
Kyle
[1] http://repository.gbif.org/content/groups/gbif/org/gbif/ipt/2.3.1/ipt-2.3.1.... [2] https://github.com/gbif/ipt/issues/1197 [3] https://github.com/gbif/ipt/wiki/IPTReleaseNotes23.wiki