11-10-2009 01:08 PM
Has anyone successfully installed FRx 6.7 under Windows 7 and MAS 200 4.3? Although the installation process completes fine, I receive the error 'FRx is unable to process this output request for the following reason: C:\Windows\system32\msxml.dll could not be found' when I try to print to FRx DrillDown Viewer. I tried to install MSXML 4.0 SP1 as suggested in the error message, but I continue to get the error.
Solved! Go to Solution.
05-24-2010 10:32 AM
12-08-2010 02:51 PM
When I copy the msxml.dll file to the System 32 directory and try to register it, the registration fails. This in on a Windows 7 64-bit OS. Has anyone been able to get to work in this environment?
12-17-2010 12:23 PM
02-02-2011 11:39 AM
Hi All. if I read this correct, you can install FRX on a windows 2007 64 bit OS, and put this file in place and register it manually, and FRX will run on a 64 bit operating system. Have people successfully been able to run FRX on a 64 bit OS? Has anyone run into any other issues with running FRX in a 64 bit Windows 2007.
Thanks for the help
05-25-2011 08:14 AM
I have successfully installed it on 2 machines with Windows 7 SP1 64 Bit.
The steps I had to follow where
1.) Backup your existing FRX SYSDATA FOLDER
2.) Install MS XML 4 SP 2
3.) Install from the disk using the client install option
4.) The installer will look like it is 100% done and then toss an error. Wait for this error
5.) Press CTRL+SHIFT+ESC to open the processes tab
6.) Kill the 3 setup processes. 2 demoshields and an updateinstall process. If you don't kill the processes the installer will roll back the install so this is the hack to prevent the rollback from happening.
7.) Copy msxml.dll from another machine into the c:\windows\syswow64 folder
8.) Restore the sysdata folder from the back up in step 1. This installation will leave you will no registration so you need to restore the original sysdata. If you don't restore this all other FRX's on other machine using this SYSDATA folder will not work until they are licensed or registered.
This was a trial, error and discovery process that worked in our environment.