Native XML Driver Deployment

[Former Member]

For a while we had trouble using the native xml driver, but it has been worked out here:

In that thread there was mention of deploying the driver, and some extra work that needed to happen. I found those instructions repeated again here for another user:

https://boc.sdn.sap.com/node/1428

We have followed the instructions of coping the required files and java runtime to a new test client, but our reports do not launch.. we get this error after a good 30 seconds of hang-time,

Invalid Argument Provided

I've doubled checked the instructions and all files are copied, and edited the crconfig.xml to point to the new j2re bin folder. There doesn't appear to be many discussions with this error, what does it mean? Thanks.

Note that we are using the RDC, Native XML Driver, Crystal Reports XI R2 SP4.

[former_member183750 · Accepted solution]

Searching for the error here:

https://www.sdn.sap.com/irj/sdn/businessobjects-notes

I come up with a note regarding this being tracked and resolved in a Service Pack. As you are using CR XI release 1 (going from the orginal post), the latest RDC merge modules are here;

http://resources.businessobjects.com/support/communityCS/FilesAndUpdates/crXI_rdc_merge_modules.zip

If you did not download the msm from the above link, try that in your deployment project. If you are using the msm files from the above link, try the following;

1) Download the Modules utility from here:

https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip

and compare the dlls loading on the working and non working computers.

2) If you can, install the CR designer (just as a test) on the non working computer. See if that resolves the issue. If it does, at lease we'll know it's something due to dll differences between msm runtime and CR install, which we could again check using Modules.

Ludek

[Former Member · Accepted solution]

Ludek, yes at the start of the original thread we were on R1, but during the thread we have moved to R2 SP4 - and we are using the msm's for SP4. I will compare the DLLs and try to install the CR Developer Ed. on the test computer - thanks for the advise

[former_member183750 · Accepted solution]

OK. Sorry, I remember now that you went to CR XI r2. Just make sure you are using the MSM files from here (I'm 99% sure you are, but just in case):

https://smpdl.sap-ag.de/~sapidp/012002523100009381702008E/crxir2sp4_rdc_mm.zip

And let's see what the comparison shows us. Good thing is that it works on one box...

Ludek

[Former Member · Accepted solution]

I confirmed that the MSM package that I downloaded earlier is the same as the one you've linked above. My co-worker has left for the day so it will be a day before I reply.

[Former Member · Accepted solution]

Ignore this post - I misread something and will report my new findings

Edited by: Kurtas BB on Oct 7, 2008 4:25 PM

[Former Member · Accepted solution]

Ok I went over the process again, and am a little confused -

Install the Java (JVM) 2 Runtime Environment (this is essentially the Java Framework needed to launch the crdb_xml native driver 1.4.2 from the java sun web site at: 
http://java.sun.com/j2se/1.4.2/download.html. 
Create a java folder inside the " C:\Program Files\Business Objects\Common\3.0";. 
Copy over the Crconfig.xml(C:\Program Files\Common Files\Business Objects\3.0\java) file from the development machine to the deployed machine in at the following path "C:\Program Files\Common Files\Business Objects\3.0\java" path. Open the crconfig.xml ; this file in Notepad and search for the line <JavaDir>. If JRE is installed to C:\Program Files\Java\j2re1.4.2_12\bin then the value should be look like this <JavaDir> C:\Program Files\Java\j2re1.4.2_12\bin</JavaDir>. 
Create a folder called lib in the "C:\Program Files\Common Files\Business Objects\3.0\java". 
Copy over the entire contents of the lib folder (especially the external folder) from the development machine to the newly created lib machine on the deployed machine. The point of this is to ensure that the crconfig.xml file contains all the files here which exist at the correct path which they now should because we copied over the lib and external directories. 
Copy crdb_xml.dll, crdb_xml_res_en, and all the files with "crdb_xml_res_xx from your development machine to the deployment machine (C:\Program Files\Common Files\Business Objects\3.0\bin). 
Restart your machine and try accessing your web application. The reports will show up the data without any issue. 
The above is written for CR XI release 1. You may have to adjust the path given above as you do not specify the version of Crystal reports you are using. 

On my development machine, there is no Crconfig.xml at this location (C:\Program Files\Common Files\Business Objects\3.0\java) . In fact the java folder is not there either, I only see bin and crystalreportviewers11 folders. Can these instructions be confirmed for me as accurate? I do not even see a 3.5 folder under C:\Program Files\Common Files\Business Objects\

[former_member183750 · Accepted solution]

Well, remember that you changed to CR XI r2. The doc you quote is for CR XI release 1. The correct path for CR XI r2 is c:\program files\business objects\common\3.5\java. You will find the crconfig.xml file there.

Ludek

[Former Member · Accepted solution]

Ok, and on the client computer that I'm installing to, the files are placed in that location too c:\program files\business objects\common\3.5\

not c:\program files\common files\business objects\3.5

? That makes more sense, I don't think we did that part right yesterday.

[Former Member · Accepted solution]

I spent the better part of today setting up my box to be able to compile and deploy the entire project. After I finally got everything working on my machine, we started to kick around some ideas, and got it to work by doing this:

1. Including Everything in the Merge Modules

2. Installing the Java Runtime to some location, we used the default C:\Program Files\Java\...

3. In our install deployment, include this java folder: C:\Program Files\Busines Objects\Common\j2sdk1.4.2_08 to the client at the same location.

4. Did not adjust crconfig.xml, left it to point at the same path as step 3.

At first, Windows XP Asked me to unblock Java - this was the only time even after re-launching the application.

I then went back, and changed the crconfig.xml to the newest version of java2 1.4.2 (version 18) just as your instructions say to do, and it continued to work. So I think our error was not including something in the MSMs, or the other development box was still pulling the wrong xml db dlls.

Either way, I think we've worked this issue out. Thanks for your direction. Now its time for me to clean up the MSM and reduce the size of my install

[Former Member · Accepted solution]

A quick side question to this:

Java 1.4.2 Is at End of Life according to Sun's Website, is there a different version that we can use, or one that is recommended for this?

[former_member183750 · Accepted solution]

Let me see what I can find out...

[former_member183750 · Accepted solution]

Good news, I think...

Got this from a senior resource here:

The Java JDK that the xml driver uses is defined in CRConfig.xml - last I tested, there wasn't a issue going to JDK version 1.5

However, only JDK 1.4 is listed on the supported platforms list - it just has not been updated.

Ludek

[Former Member · Accepted solution]

This morning I went ahead and tried 1.6 Update 7 (the latest release version as of this post) - it also works when pointing the <javadir> tag to its location. Thanks for your help again!