Sage 100

When installing FRX to 64 BIT OS - the MSXML.DLL does not appear to register. This seems to drive the drill down viewer. Has anyone figured out a way to get FRX to work on an FRX 64 bit OS. No matter how many times I tell customers that using a 64 bit os will break FRX they continue to upgrade. I guess it's time to break the bad news to them that they need to pick a new reporting tool.

http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=516330

We have FRx working on 64-bit OS (Applianz environment). Chuck will have the details to the secret.

Jerry, I think you are about the second person I have heard that is successful in this environment. I just had a client go 64 on me and I told them that the vitual XP PC is the only way FRx is going to work for them now. Hopefully, Chuck will be in touch with the secret sauce soon.

I would be interested in this secret sauce too

Currently, here are their options using FRx on a 64 bit machine. http://www.microsoft.com/windows/virtual-pc/download.aspx http://www.microsoft.com/windows/virtual-pc/

I've attached a screen shot of the FRx client showing the specifics of the system. As you can see, it is a 64 bit environment. As Jerry indicated, this is an Applianz workstation and the file server is a Windows Storage Server 2008 R2 Essentials. The server and workstations are running in 64 bit mode. I installed the original FRx disk that they received (and got the same error about MSXML.DLL) but then, at Jerry's suggestion, I uninstalled that, downloaded the most recent version from Microsoft. This didn't work because it DID NOT have the MAS 90 hooks but it did register the file. So to get the MAS 90 ODBC and reporting to work, I downloaded the FRx from 90 Minds and installed it on top of the MS version. We have no problem with FRx running nor do we have any problem with MSXML.DLL registering. For grins and giggles I just looked at the registry of this workstation and it was there. I then ran ""regsvr32 msxml.dll"" from the SYSWOW64 directory and it registered cleanly. It either has something to do with the Applianz environment or the DLL from the Microsoft install has ""fixed"" the problem.

So if I read this correctly, you downloaded the latest MSXML.DLL from the MSFT website and that fixed the problem? If not, what do you mean by the ""latest MSFT version""?

Sounds like he registered the latest version of msxml.dll then replaced it with the version needed for FRX?

No, it was more lame that that. We obliviously downloaded the latest FRx that is on microsoft.com. (We didn't realize that there were Sage-specific additions to the OEM version.) That wouldn't work right. Then we installed the Sage FRx version that is in this socialcast area. Everything magically came to life. So, the latest FRx on msft apparently has the needed 64-bit file in it, and installing the whole app fixed that problem. Then installing the Sage-specific version on top of it added the pieces to make it work with Sage 100.

Do you have the link to the MSFT FRx? Is it even available on their system now?

I think these work for the links for FRx 6.7 and 64-bit Support: http://support.microsoft.com/kb/2014857 the SP 11 download: http://www.microsoft.com/en-us/download/details.aspx?id=7864 the MSX Group message board: http://boards.msxgroup.com/post/Does-FRx-work-on-a-64bit-Operating-System-5081894

Jerry, I did download and try to install the ""web portal"" which is your second link but this is the link to the MSFT version that I downloaded and installed in that last round of installs: http://www.microsoft.com/en-us/download/details.aspx?id=388

Thanks guys...I've been having problems and have done just about everything else...I will try the all the links and hopefully stop pulling my hair out!

Copy the MSXML.DLL file to the C:\Windows\SysWOW64 directory and then manually register it. Be sure you are logged in as a local administrator when you manually register.

I believe that John is right, the key is getting the MSXML.DLL file into the SysWOW64 directory then manually register it. For some reason, the FDM version that I downloaded did that automatically. I also noticed that the version of MSXML.DLL was ""created"" on December 7, 2011 and modified on July 21, 2000. The version of the file is 8.0.5226.0.

Can someone post that 64 bit msxml.dll ? I can test on an FRX install that I'm working today.

Here is the file.

That looks like the same one I'm using.

Thanks this worked though the customer had linkedin XLSX versions of an Excel spreadsheet and claimed that was working before using the MSXML version. I'm not sure if a newer MSXML would allow him to continue linking to that specific Excel file.

Note: XLSX issue might be service pack related

Note the 64 bit msxml seems like the same one I installed from FRX 6.7 SP 11. Is the only difference that you manually copy it to syswow64 and run regsrv32? It seemed to work ok and got the customer running FRX on 64 bit OS

Wow, this is in incredible. I have it working on my 64 OS system. Been so long that I had to work at remembering how to format a row......... This is a great day. Thanks to Wayne for reposting the question and hats off to Jerry and Chuck for providing the answer. My client is going to be VERY happy today.

I am not positive but using SP11 may also help update the msxml -- though you likely still need to register it manually - remember on 64 bit that you need to drop the msxml.dll into sysWOW64 and register with regsrv32. Here's the URL for FRX SP11 for Sage 100 ERP: http://www.microsoft.com/en-us/download/details.aspx?id=3354

This service pack has been out for over two years. Could it be that all it took was placing and registering the dll in the correct folder?

I have had FRx install and working on 64-bit Windows 7 for a while now. I've found that installing OUTSIDE the Program Files directory is also key.

Dawn, I can't count the number of times this topic has been posted over the past several years. This is the FIRST time that a solution has been posted.................. I can't even begin to count the number of lost hours trying to solve this issue! And here all along, you've known the answer!!!!!!!!! .Who'd have thought?

I didn't know that everyone didn't know that.

I did not realize it either!

Chuck had installed it on 64-bit maybe 8 months ago. We often install on common drive, missing PF(32). So he basically lucked into, and we didn't think much about it. A couple months ago, I had reason to look whether 64-bit was compatible with FRX, and Google search turned up MS posting of the update that was almost 2 yrs old, so I figured that this was ""a previously solved problem"" and didn't want to ask stupid questions. That's when I discovered that the MS release is doesn't fully work with Sage. Again, we basically lucked into the solution because we this last install was on the AppEazy Data drive, and therefore not in pf(32). So by not much more than serendipity, we never thought much about the problem .... that was driving lots of folks nuts! There's a lesson in there somewhere.

This has been a popular topic since WIN 7 64 came out. I started dealing with it when 12/09 when I bought a new laptop with Win 7 64. And as Wayne noted, everytime a client replaces their equipment, we have to recommend the 32 OS in order for FRx to run. Sometimes they listen, sometimes they don't even ask. For the OASIS people, the older posts are behind the 90Minds door so you wouldn't even have a chance to search for them. The important thing is we now have a solution that we all build upon. In fact, I have a session starting in 10 minutes to install FRx on a 64 bit machine instead of a Virtual PC running XP.

The one other thing we have had success with on recent new machines is to run it in compatability mode for Windows 2000. Not sure why, but this has worked when nothing else has.

Reinstalled FRx on client's new 64 OS workstation. Installed from CD. Installed all patches sequentially (this seems to alleviate issues on WIN 7 encountered during a WIn 7 32 install last year), installed and registered the dll in the syswow64 folder. Client is very happy that we didn't have to go the virtural PC XP install route. I think I will stop recommending 32 OS for FRx now.

@JeffSchwenk, I did what you did. Installed to C:\FRx folder. When my install from the CD completed, I got a message that this version of FRx needs Micorosft .NET Framework 1.1 SP1 or later. I did NOT install it. Did you? When I downloaded it from MS site, and launched, got message that it has known compatibility issues with this platform. Haven't continued yet. Attached my diary of installation notes with error messages. Any reason I should be afraid to download the SP?

I did install whatever .net files it wanted to. I did get some errors on the install but not as many as you did. Did you remember to ""run as administrator"" when launching? Each SU gave me the same error message. When all were installed, The worst that can happen is that at the end of it all, it doesn't work and you start over. Be CAREFUL when installing the SU's as I have had trouble in the past with the dafault folder that it wants to install to. It is the wrong one. The only way I noticed is the that Help about reported the wrong version.

Ok, I'm starting over. I think I forgot to ""Run as Administrator"". And Help and About reports the wrong version. Stay tuned . . . Thanks!

I probably have a bunch of the files in DropBox is you need them

Thanks Wayne, I have them. And it worked! I installed.NET Framework 1.1 SP1, then installed ""as administrator"" the program and all 3 SPs. Woohoo!