Do I require a different xml license key from 6.1a?
I got 6.5.1 running on a dev box. Infoview works fine, but when I try to open up WebI, I get a “Cannot perform this operation: no valid license found.”
ive gotten past that problem, but now im getting a
"The WebIntelligence Java Report Panel cannot connect to the server. Close the report panel and tr ot connect again or see your BusinessObjects administrator. (Error: WIJ 200002)
We are on Windows 2000SP3
Oracle 8.1.7
Tomcat, Apache
I ran into the same error last week…on a totally different setup. I believe it was related to rights…but I was running it with W2K3 and IIS 6.0.
I don’t remember exactly which setting it was. Do a search on Tech Support with WIJ20002…It didn’t show up for that version but it was the same thing to fix it in the new version.
i did do a search for WIJ20002 and found as you stated it was a permission thing, but it only shows the resolution for IIS ( IE: whether to grant execute or scripting privaledges on the folders. ) Im trying to figure out what the equivalent would be for Apache/Tomcat.
I was using an expired xml key, that was my first problem.
Then my second problem was resolved by using a temporary XML license key even though tech suppot told me my 6.1a license key should have worked.
It didn’t for me.
Everyone worked except WebI itself using my 6.1a key.
I am currently using a temporary key for my 6.51 development deployment without any problems.
BO techsupport found this wierd as well. Then they looked at my current xml key and found it wierd I had no upper and lower time limits in my xml key file.
java.lang.IllegalStateException: Cannot load DS; no ID set at
com.bo.wp.om.OMDataProvider.getDataSource(OMDataProvider.java:192) at
com.bo.wp.tc.TCMain.newDocument(TCMain.java:807) at
com.bo.wp.tc.TCMain.initDocument(TCMain.java:649) at
com.bo.wp.tc.TCMain.initClient(TCMain.java:1253) at
com.bo.wp.tc.thread.InitAppletRunner.run(InitAppletRunner.java:82) at
java.lang.Thread.run(Unknown Source)
This started happening about the same time as when we updated from the transition key to the new permanent XML key.
After trying all the IIS rights and permissions suggestions from BO KB and other posts here with no success, I deleted the new XML key file from all relevant folders on the server (I do have a backup, of course) and replaced it with the transition key we had been using. Rebooted the server, and now I am able to open Universes and create documents from Webi again. this could be something particular to our case i.e. what got ordered. but hope this helps…
We also got this error and reason was that one of our secondary server date was wrong causing license not to work. After correcting date all work’s fine