<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Dear Kyle,<br>
<br>
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.<br>
<br>
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. <br>
<br>
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.<br>
<br>
Thanks again!<br>
<br>
With best regards,<br>
Aaike<br>
<br>
Kyle Braak [GBIF] wrote:
<blockquote style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space; "
cite="mid:B1E1408E-3EC0-4132-BC90-D8E16C80F000@gbif.org" type="cite">Dear
Aaike,
<div><br></div>
<div>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 <a moz-do-not-send="true"
href="https://code.google.com/p/gbif-providertoolkit/">IPT Google Code
homepage</a> or <a moz-do-not-send="true"
href="http://www.gbif.org/ipt/releases">http://www.gbif.org/ipt/releases</a>.<br><div><br></div><div>Regarding
the problem you are experiencing, Issue <a moz-do-not-send="true"
href="https://code.google.com/p/gbif-providertoolkit/issues/detail?id=840">840</a> 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. </div><div><br></div><div>Alternatively,
it could also be Issue <a moz-do-not-send="true"
href="https://code.google.com/p/gbif-providertoolkit/issues/detail?id=1038#c5">1038</a>,
so please check your homepage URL in your metadata starts with 'http'
or 'https'. </div><div><br></div><div>Kind regards,</div><div><br></div><div>Kyle</div><div><br></div><div><div><div>On
Aug 29, 2014, at 9:45 AM, Aaike De Wever wrote:</div><br
class="Apple-interchange-newline"><blockquote type="cite"><div>Dear all,<br><br>Although
I could successfully register datasets with GBIF until <br>recently, I
get a "Registration of resource failed!" message now. <br>Similarly I
tried to re-publish a number of resources after applying a <br>small
edit to the mapping and am getting a "Error publishing resource: <br>Bad
registry response" message.<br><br>As we are still on version 2.0.3, I
was wondering whether this may be <br>the reason (and we urgently need
to update) or if these error messages <br>mean something else.<br><br>Thanks
a lot for your help!<br><br>With best regards,<br>-- <br>Aaike De Wever<br>BioFresh
Science Officer<br>Operational Directorate Natural Environments<br>Royal
Belgian Institute of Natural Sciences<br>Vautierstraat 29, 1000
Brussels<br>Belgium<br>tel.: +32(0)2 627 43 90<br>mobile.: +32(0)486 28
05 93<br>email: <<a moz-do-not-send="true"
href="mailto:aaike.dewever@naturalsciences.be">aaike.dewever@naturalsciences.be</a>><br>skype:
aaikew<br>LinkedIn: <<a moz-do-not-send="true"
href="http://be.linkedin.com/in/aaikedewever">http://be.linkedin.com/in/aaikedewever</a>><br>BioFresh:
<<a moz-do-not-send="true"
href="http://www.freshwaterbiodiversity.eu/">http://www.freshwaterbiodiversity.eu/</a>>
and <br><<a moz-do-not-send="true"
href="http://data.freshwaterbiodiversity.eu/">http://data.freshwaterbiodiversity.eu/</a>><br>_______________________________________________<br>IPT
mailing list<br><a moz-do-not-send="true"
href="mailto:IPT@lists.gbif.org">IPT@lists.gbif.org</a><br><a class="moz-txt-link-freetext" href="http://lists.gbif.org/mailman/listinfo/ipt">http://lists.gbif.org/mailman/listinfo/ipt</a><br><br></div></blockquote></div><br></div></div>
</blockquote>
</body></html>