MissingResourceError thrown when trying to logon to BOBJ

[Former Member]

I have a simple bit of code that is first trying to create an enterprise session as follows:

es = CrystalEnterprise.getSessionMgr().logon(cmsusername, password, server, "secEnterprise");

I am receiving the following error when running recently (this used to work fine without issue):

 
java.util.MissingResourceException: Can't find bundle for base name com/crystaldecisions/celib/g/dResources, locale en_US
java.util.MissingResourceException: Can't find bundle for base name com/crystaldecisions/celib/g/dResources, locale en_US
	at java.util.ResourceBundle.throwMissingResourceException(Unknown Source)

Can anyone shed some light as to why this error is now being thrown? I am passing in the same credentials as I always have. Is this indicating that a specific JAR file is missing from my classpath?

Thanks

[former_member217070 · Accepted solution]

Hi, Jeremy,

Are you using XI R2? Please make sure you're using Fixpack 5.8 or later.

Regards,

Bryan

Internal note 1418416

[Former Member · Accepted solution]

Brian - yes this code is being run against XI R2. Specifically, FP 2.1.

What's strange is this same code was previously working, all required JARs are still present with the code, and this is failing on what should probably the most simple piece - the BOE login. I'm trying to understand exactly why the error is being thrown and if it relates to something being missing in the classpath, JAR file(s), etc....

Here is the full exception thrown:

java.util.MissingResourceException: Can't find bundle for base name com/crystaldecisions/celib/g/dResources, locale en_US
java.util.MissingResourceException: Can't find bundle for base name com/crystaldecisions/celib/g/dResources, locale en_US
	at java.util.ResourceBundle.throwMissingResourceException(Unknown Source)
	at java.util.ResourceBundle.getBundleImpl(Unknown Source)
	at java.util.ResourceBundle.getBundle(Unknown Source)
	at com.crystaldecisions.celib.exception.AbstractException.getMessage(Unknown Source)
	at com.crystaldecisions.celib.exception.AbstractException.getMessage(Unknown Source)
	at java.lang.Throwable.getLocalizedMessage(Throwable.java:267)
	at java.lang.Throwable.toString(Throwable.java:343)
	at com.crystaldecisions.celib.exception.AbstractException.toString(Unknown Source)
	at org.apache.log4j.spi.VectorWriter.println(ThrowableInformation.java:88)
	at java.lang.Throwable.printStackTrace(Throwable.java:509)
	at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:50)
	at org.apache.log4j.spi.LoggingEvent.getThrowableStrRep(LoggingEvent.java:333)
	at org.apache.log4j.xml.XMLLayout.format(Unknown Source)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
	at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:225)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
	at org.apache.log4j.Category.callAppenders(Category.java:187)
	at org.apache.log4j.Category.forcedLog(Category.java:372)
	at org.apache.log4j.Category.error(Category.java:303)
	at com.crystaldecisions.celib.trace.d.int(Unknown Source)
	at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.do(Unknown Source)
	at com.crystaldecisions.enterprise.ocaframework.aa.int(Unknown Source)
	at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.for(Unknown Source)
	at com.crystaldecisions.enterprise.ocaframework.p.a(Unknown Source)
	at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.getManagedService(Unknown Source)
	at com.crystaldecisions.sdk.occa.security.internal.t.a(Unknown Source)
	at com.crystaldecisions.sdk.occa.security.internal.t.a(Unknown Source)
	at com.crystaldecisions.sdk.occa.security.internal.t.userLogon(Unknown Source)
	at com.crystaldecisions.sdk.occa.security.internal.l.userLogon(Unknown Source)
	at com.crystaldecisions.sdk.framework.internal.d.logon(Unknown Source)

[former_member217070 · Accepted solution]

Hi, Jeremy,

I found internal documentation stating that this was a known problem and that it would be fixed by fix pack 5.8 (ADAPT01323647). It is unrelated to having all of the jars, so it's not that. We're up to at least fix pack 6.4, so please update your R2 and see if that fixes your problem.

Regards,

Bryan

[Former Member · Accepted solution]

Thanks for the follow-up Bryan. I understand what you're saying, but I'm struggling with why anything server side should need to be patched if this identical code was previously working against the same XI R2 deployment and no fix pack / service packs have been introduced. Is there a specific SDK JAR file that this error relates to or any other components I could look into?

Thanks

[former_member217070 · Accepted solution]

Hi, Jeremy,

Our jars are distributed as sets and you wouldn't want to change out just one of them. It's also best to match them with the Enterprise you're attaching to. So, if your Enterprise is XI R2 6.1, it's best if your app is also using the R2 6.1 jars. And as it is a client / server relationship, when a problem is found, it's not necessarily in the client jars - sometimes it's on the server.

Here's the fix note: "Don't release lock when object hasn't been locked" - and that's all I know. It doesn't say if it's on the server or client side. I think that, if only for testing purposes, it would be good to know if updating to a fixpack after 5.8 will fix it. If it does, you've bought yourself some time for figuring out the cause later. If not, then you'll be able to look for other causes. Besides, if you want to open an actual case for this issue, the first thing we'll ask you to do is to update to the latest fix pack, because that's all that's supported.

Please note that XI R2 is now out of patch support. This means that, although you can still get technical support for this product, that no more patches or fix packs will be released for it. XI R3.1 still has patch support available and we'll soon be releasing XI R4. Since your installation was working correctly before "something" happened, there's a chance you could get fix pack 2.1 working again, but there's no guarantee that whatever it was (odd bit being cached, weird sequence of events, etc.) wouldn't happen again.

Good luck and please let me know if updating to the latest fix pack fixes it.

Bryan

[Former Member · Accepted solution]

Thanks again for your help Bryan. Strangely enough, we restarted all BOE services and the error no longer is thrown.

[former_member217070 · Accepted solution]

Sweet! Yeah, guess I should have started with "Have you rebooted the server?"