Tag Archives: Windows

mqjbnd.dll – Can’t load IA 32-bit .dll on a AMD 64-bit platform

For me this happened when I was trying to run a program that uses JMS to connect to a Websphere MQ queue. The solution was pretty simple.

My PATH variable looked like this:

PATH="C:Program Files (x86)\IBM\WebSphere MQ\Java\lib;C:Program Files (x86)\IBMWebSphere MQ\Java\lib64;..."

The problem here was simply that the first MQ lib pointed to ‘lib‘ and not ‘lib64‘. So after I swapped the order of the paths

PATH="C:Program Files (x86)\IBM\WebSphere MQ\Java\lib64;C:Program Files (x86)\IBM\WebSphere MQ\Java\lib;..."

Everything worked again. Pretty simple solution but it took me quite a while to find it.
The Path variables were set by the installation program. I guess that if I had set them myself I would have seen it sooner but you never know. Sometimes you just can see the forest for all the trees 😉

Happened on Websphere MQ Server 7.0

Stop and start synchronization site by site in the DataExchange Manager

Say you have installed PSQL and DX and everything is up and running. Now you temporary want to stop the synchronization of one or more sites in the project.
The safest way to do this is to temporarily remove the site from the synchronization list on the first site. This will not affect the Hook Module on the partner site, it will only stop the first site sending the replication request to the partner site.

On the First site:
1. Open Pervasive control Center
2. In the menu go to “DataExchange” -> “Manager”
4. Password: “password”
5. Click on the site you want to stop/start the replication
6. Go to the tab “Schedule”
7. Select the option “Do not replicate”
8. Click “Apply” and close the window

Done! – It is easy when you know how 😉

Tested in Pervasive DataExchange v2.8 and v4

Getting Pervasive DataExchange to work when working thru RDP

When setting up a Pervasive DataExchange synchronization over remote desktop there is one importent step to take to get the permissions right. The step is to set the ‘Restricted Access On WTS client’ to false (0).

Here is a short description of how to set the WTS key correctly:
1. Click “Start” -> “Run”
2. Enter “Regedt32” and click “OK”
3. Find the following Registry key: “HKEY_LOCAL_MACHINESoftwarePervasive SoftwareUtilities InterfaceSettingsRestricted Access On WTS client”
4. Double click REG_DWORD for the key
5. In the Value Data field, change the value from 1 to 0 (zero)
6. Click “Ok”
7. The REG_DWORD value should read 0x00000000 (0)
8. Exit registry editor

If the key does not exist – create it

Tested with PSQL v9, PQSL v11, DataExchange v2.8 and v4 on XP, Vista and Win7