Today I got a strange error in a customer environment while logon to our Datacap applications. When you try to logon in the Navigator administration desktop you receive a HTTP 500 error.

When you take a look in the SystemOut.log of the WebSphere Server where Navigator is running you just see this error:

000000c8 SystemOut O CIWEB.DatacapWebPlugin Error: [admin @ 10.100.10.215] [REQUEST 113] com.ibm.ecm.datacap.web.repositoryType.DatacapRepositoryLogon.performAction()
Message ID : 6306
Message type : ERROR
Text : Diese Operation kann nicht verarbeitet werden.
Explanation : Bei der Verarbeitung von {0} ist ein E/A-Fehler aufgetreten.
User Response : Wiederholen Sie diese Operation oder wenden Sie sich an Ihren Systemadministrator, um Hilfe zu erhalten.
Admin Response : null
More Information: null
at com.ibm.ecm.datacap.web.repositoryType.DatacapRepositoryLogon.performAction(DatacapRepositoryLogon.java:175)

On the wTM side you see no error at all and also a successfull logon from Navigator. For some reason the JSON data the Navigator received from wTM is malformed.

In the end it turned out that a wrong URL within the Navigator EDS Plugin was the root cause for this issue.

At the customer environment somebody just entered “test:9080″ as the EDS servlet URL.

After disabling the Plugin everything works fine and you can log in again to the Datacap applications.

A small problem with a big impact :-).

41 thoughts on “IBM Datacap – Receiving HTTP500 error while logon to a Datacap application

  1. I want to to thank you for this excellent read!! I absolutely loved every bit of it. I’ve got you book-marked to check out new things you postÖ

  2. I really like what you guys tend to be up too. This type of clever work and reporting! Keep up the great works guys I’ve you guys to my own blogroll.

  3. You could certainly see your skills within the work you write. The world hopes for even more passionate writers like you who are not afraid to say how they believe. Always follow your heart.

  4. An intriguing discussion is definitely worth comment. I do think that you ought to publish more about this subject, it might not be a taboo matter but usually people don’t talk about these topics. To the next! All the best!

  5. I’m now not certain the place you are getting your info, however good topic.I needs to spend a while studying much more or figuring out more.Thanks for excellent information I was looking for this information for my mission.

  6. Generally I do not read article on blogs, but Iwish to say that this write-up very compelled me to checkout and do so! Your writing taste has been amazed me.Thank you, very nice post.

  7. Aw, this was a very good post. Taking the time and actual effort to produce a very good articleÖ but what can I sayÖ I put things off a whole lot and never seem to get anything done.

  8. Hi! I could have sworn I’ve been to this blog before but after browsing through some of the post I realized it’s new to me. Nonetheless, I’m definitely glad I found it and I’ll be bookmarking and checking back frequently!

  9. Thanks for any other great article. Where else may anyone get that type of info in such a perfect manner of writing? I ave a presentation next week, and I am at the search for such info.

  10. I will right away snatch your rss feed as I can’t to find your e-mail subscription link or e-newsletter service. Do you’ve any? Please allow me realize so that I may subscribe. Thanks.

  11. Oh my goodness! Amazing article dude! Many thanks, HoweverI am going through troubles with your RSS. I don’t know thereason why I cannot join it. Is there anybody having similar RSS issues?Anyone that knows the answer will you kindly respond?Thanx!!

  12. When someone writes an post he/she keeps the plan of a user in his/her mind that how a user can understand it.Therefore that’s why this article is amazing.Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *