JCo 'user' missing Error in Mii 12.1.4

[Former Member]

We have a BLS that is performing a remote function call via JCo. The BLS works normally 75% of the time but intermittently the JCo Action Block throws an exception with only the text: 'user' missing. This is obviously some sort of authentication problem with JCo but I cannot find any information on potential fixes.

This is what the NetWeaver Log shows me:

"Unable to decrypt credentials for alias MII_MES_JCO"

MII_MES_JCO is referring to the entry in the Credential Editor used by the JCo Action Block.

It is very strange because immediately after receiving this message I can execute the BLS and it is successful.

Has anyone else experienced this problem? I would sincerely appreciate your help.

Thanks

Edited by: mubgt38 on Jun 1, 2011 6:09 PM

[jcgood25]

I haven't heard of this particular issue before, but something to try. Create a new credential alias and apply this within your JCO action block and see if the random lookup errors go away.

I assume you may also be using the problem alias in other transactions too - is it just the one that causes the problem or does it look as though it is randomly happening for all TRX's that use this alias?

[Former Member]

Hello Jeremy,

RIght now we are only using this particular set of credentials in one TRX. I will create a new alias as you suggested to see if that solves our problem.

Thanks

[Former Member]

I have been able to identify the scenario that results in this error. We only encounter this error when the TRX is executed repeatedly within a very short period of time or by multiple users at the same time. Is there some setting that we need to change to allow this?

[jcgood25]

Any chance you are running Oracle underneath your NetWeaver instance? It almost sounds like the database query to lookup the credential alias information (assuming that is how things work) is hitting a record lock or some sort of query error.

Have you looked at the log entries surrounding the error message you mentioned?

If you have a newer 12.1.x system (sandbox or test) I wonder if you can reproduce it on the latest build.

Logging a customer support message might also be the best path forward, along with steps to reproduce the situation.

[Former Member]

Hi Jeremy,

We are running SAPDB not Oracle. Yes, I included the NW Log error that we are receiving in my original post.

Thanks

[salvatore_castro]

According to development there was a multi-threading access issue to the credential aliases in releases prior to SP7, so please update your instance to fix this issue.

Thanks,

Sam