IOException on Login



I have been implementing the API @ 11.2 into one of our internal apps for looking up images. All was going fine until my login call started failing with the error IOException marshaling EJB parameters

I can still login to the Portfolio Web Client with no issues so I am assuming that I don’t have an account lock? I can also retrieve the encryption key so I know the service is running.

I have run the request through both my own code and SoapUI to make sure it is not my code. I have used the C# password encryption example from your online documentation.

Please see the attached image from SoapUI containing the request and response.

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"> <faultcode>S:Server</faultcode> <faultstring>IOException marshaling EJB parameters</faultstring> <detail> <ns2:AssetFault xmlns:ns2="http://portfolio.extensis/service/asset"> <faultCode>UnexpectedError</faultCode> <message>IOException marshaling EJB parameters</message> </ns2:AssetFault> </detail> </S:Fault> </S:Body> </S:Envelope>

Can someone advise me on what might be the problem and how to resolve?



Hi Andrew,

One thing to be aware of is that the public key changes when Portfolio Server restarts. So if you are storing the key, you will want to refresh it on restart, or just fetch the key each time you go to log in, which is what our client apps do.

If that’s not the issue, let us know and we can get on a call, and/or look at your code and reproduce the problem here.

Please do let us know how it goes, and we’ll get you all sorted out.



Thanks Loren.

I found what the issue was… my AD password got reset and I did not update it in the app.config… Schoolboy error! Sadly, the error message misdirected me down the wrong path.

Anyway this could be addressed - perhaps a “User credentials invalid”? Anything more helpful than “IOException marshaling EJB parameters”!!



Hi Andrew,

I’m glad to hear you figured it out.

I have filed a bug on the bad error message you received. Indeed you are correct that we intend to return a more clear “authentication failed” error in that case.

Thanks so much for reporting this issue, it will help us improve the product for all our API users!