|
Group: Moderators
Posts: 136,
Visits: 639
|
Hi Julian
The most common cause of this error is a migration from a 32-bit machine to a 64-bit system. When you migrate this way, but install a 32-bit package on the new server and import settings using the legacy method of a .pcfg file, the settings will not match correctly.
If this is the issue, you have two options.
Option A
1. Uninstall the 32-bit package and install a 64-bit package
2. Manually copy the settings over. You might be able to import the .pcfg file, but you could continue to have issues. The .pcfg file is a registry export, so it might import to the 32-bit hive and not the 64-bit hive.
Option B
1. Check that your installation directory is C:\Program Files (x86)\Pragma
2. Go to the registry hive, using regedit.exe, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PragmaSystems
3. Change all references of Pragma Files to Program Files (x86)
I recommend option A because it will get you running the correct platform for your new server.
The most common cause of this error is a migration from a 32-bit machine to a 64-bit system. When you migrate this way, but install a 32-bit package on the new server and import settings using the legacy method of a .pcfg file, the settings will not match correctly.
If this is the issue, you have two options.
Option A
1. Uninstall the 32-bit package and install a 64-bit package
2. Manually copy the settings over. You might be able to import the .pcfg file, but you could continue to have issues. The .pcfg file is a registry export, so it might import to the 32-bit hive and not the 64-bit hive.
Option B
1. Check that your installation directory is C:\Program Files (x86)\Pragma
2. Go to the registry hive, using regedit.exe, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PragmaSystems
3. Change all references of Pragma Files to Program Files (x86)
I recommend option A because it will get you running the correct platform for your new server.
Pragma Systems Technical Support
13809 Research Blvd, #675
Austin, TX 78750
http://www.pragmasys.com
|