[IPT] Unable to register and update resource in IPT 2.0.3

[Aaike De Wever]

Dear Kyle,

Thanks a lot for your advise and sorry for not replying earlier. 
Nevertheless I wanted to report back on how things went for us in case 
this is useful for other IPT-users.

As you suggested, we updated our IPT to the most recent version. [I also 
checked the other suggestions, but was in doubt this was the case here.] 
In the process, we realised that we had somehow remained in test mode 
(but didn't realised it due to the customisation we performed, hence not 
showing "test mode" pic, which could also have been among the reasons we 
saw the described problems.

This forced us to do a reinstall of the IPT and recreate the resources 
starting from the DwC-A-files that we recuperated before doing the 
re-install. This process went relatively smooth (albeit time-consuming). 
So, now we are back up and running.

Thanks again!

With best regards,
Aaike

Kyle Braak [GBIF] wrote:
> Dear Aaike,
>
> You should upgrade to version 2.1.1 because it fixes security 
> vulnerabilities in the Apache Struts 2 web framework, which the IPT 
> uses. For more information about these security vulnerabilities and 
> the IPT version history, you can check the IPT Google Code homepage 
> <https://code.google.com/p/gbif-providertoolkit/> or 
> http://www.gbif.org/ipt/releases.
>
> Regarding the problem you are experiencing, Issue 840 
> <https://code.google.com/p/gbif-providertoolkit/issues/detail?id=840> affected 
> version 2.0.3 and may be the cause. If you are unable to perform an 
> "update registration" (under Administration/GBIF Registration 
> options), please write to me directly with your IPT's password or 
> registration.xml file located inside the IPT data directory's config 
> folder.
>
> Alternatively, it could also be Issue 1038 
> <https://code.google.com/p/gbif-providertoolkit/issues/detail?id=1038#c5>, 
> so please check your homepage URL in your metadata starts with 'http' 
> or 'https'.
>
> Kind regards,
>
> Kyle
>
> On Aug 29, 2014, at 9:45 AM, Aaike De Wever wrote:
>
>> Dear all,
>>
>> Although I could successfully register datasets with GBIF until
>> recently, I get a "Registration of resource failed!" message now.
>> Similarly I tried to re-publish a number of resources after applying a
>> small edit to the mapping and am getting a "Error publishing resource:
>> Bad registry response" message.
>>
>> As we are still on version 2.0.3, I was wondering whether this may be
>> the reason (and we urgently need to update) or if these error messages
>> mean something else.
>>
>> Thanks a lot for your help!
>>
>> With best regards,
>> -- 
>> Aaike De Wever
>> BioFresh Science Officer
>> Operational Directorate Natural Environments
>> Royal Belgian Institute of Natural Sciences
>> Vautierstraat 29, 1000 Brussels
>> Belgium
>> tel.: +32(0)2 627 43 90
>> mobile.: +32(0)486 28 05 93
>> email: <aaike.dewever at naturalsciences.be 
>> <mailto:aaike.dewever at naturalsciences.be>>
>> skype: aaikew
>> LinkedIn: <http://be.linkedin.com/in/aaikedewever>
>> BioFresh: <http://www.freshwaterbiodiversity.eu/> and
>> <http://data.freshwaterbiodiversity.eu/>
>> _______________________________________________
>> IPT mailing list
>> IPT at lists.gbif.org <mailto:IPT at lists.gbif.org>
>> http://lists.gbif.org/mailman/listinfo/ipt
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gbif.org/pipermail/ipt/attachments/20140925/32f68354/attachment.html