Sage 100

We have a client running Sage100 version 4.5 SU 3. They have been running FRx on an XP workstation for some time (FRx version 6.7.8) They recently put in a new workstation with Windows 7 64-bit. We installed FRx and added FRx SP11 (6.7.11) but they cannot connect to Sage. When they try to set the default company in FRx they get an error message ""The login failed for the XXX company. Make sure the login ID and password are correct and verify the settings on the System Specific Information in Company Information"". (see attached screen shot) So far, we have tried: . Uninstalling and reinstalling FRx on the workstation. Installing SP7 for Sage MAS90 version 4.5 Installing SP11 for FRx Creating a new ODBC connection for FRx to use. Installing Microsoft Visual C++ 2008 Redistributable Setting up a user in Sage 100 with no password Verified that Allow External Access was selected in MAS 90 We have a local install with the same version of windows, Sage 4.5, and FRx that works fine the only difference we can ""see"" in the two installations is that the client has Microsoft Office 2013 installed and our test system has Office 2007 I'm not sure why that would make a difference but at this point I'm looking for anything. Any help would be welcomed at this point.

when you look at FRx (help, about) do you see that the version is SP11? It woudl need to be 11 or 12 and sometimes it acts like it installs but if UAC is on it doesn't.

Hi David, First try moving them up to product update 12. It's at the very least Windows 7 32 bit compatible. When you do the install do not install to Program Files. Try installing to c:\FRx Software\FRx 6.7\ . It looks like you have everything else correct, and regardless of Office version it should at least let you login. Hope that helps! ~Chris

Has the MAS workstation been installed? Can you connect to MAS90 from the SOTAMAS90 DSN?

Double click on pvxcom.exe in program files/common files/sage/common components.

If it's a 64 bit machine, you should use this version of the msxml.dll file.

1. install FRX - right click and run as admin 2. Install latest patch- right click and run as admin 3. Verify 4. Run the REG67.BAT in the local FRX directory- right click and run as admin

Thanks for the quick responses. We did check the help>About and confirmed SP 11. Does anyone have a link to download Service Pack 12? We did have the PVXCOM.exe issue earlier but we resolved that one and still having this login issue; however, I believe FRx might be installed in the programs folder. I'll have them try reinstalling outside that folder. and we'll work on all of the suggestions and get back - thanks again! (I'm not our resident FRx Guru so I'm passing all this along to him. )

I would start with the PVXcom (as mentioned by Jon). It will appear to do nothing. It is the easiest and the most common issue (without having what pops up when you click ""Details"".

David; where is sysdata from previous installation? if out on the server, you need to change the sysdata to point to it (since you installed locally, it would have defaulted to local machine).

The local install of FRx does reference the sysdata folder on the server installation.

David, installing on a 64 bit Windows 7 is interesting. I have doe it and failed equally. What I did is Install FRx to the Program Files (x86) folder and I had the sysdata folder both on the server and workstation. That said run as Administrator. Then install SP 9, then SP9 Hot Fix then SP 11. Run all of these as Administrator and use what everyone else has said regarding PVXCOM,msxml.dll etc. The only other thing I used is the soatamas90.dsn versus setting up one for FRx, plus use the DNS located in WOW64 folder.

In MAS Company Maintenance, does the default company have ""Allow External Access"" checked?

On the System Specific Tab, is the DNS the SOTAMAS90? I used to always setup a separate DNS (FRX_MAS) according to the training guide. It can cause problems as it no longer exists on the new workstation.

we did check company maintenance and tried a new ODBC DNS and the standard SOTAMAS90 and neither of those worked.

This will be the dumb question, but is the company code correct on the System Specific Tab? Did you have to setup the companies or were they there are pointing sysdata correctly?

The companies were already there and I appear to have the correct code and there is no such thing as a dumb question.

I realize you said you installed SP11, but does help/about show SP11? I often have to install twice. Can you set the demo company as default? Can you compare to old install? Is the spec set correct and in the correct location? I've had many where spec set is in a totally different location. Are you sure old install pointed to server sysdata?

Here is the latest update from the tech trying to get FRx working on a 64 bit machine. I uninstalled FRx and SP 11. I installed as the administrator to C:\FRx Software\FRX 6.7. I also selected this same directory for the SysData folder. I did this so I could take the old SysData directory out of the equation. I received the error message noted below, but clicked on OK to continue. I installed SP 11 as the administrator. I ran FRxReg67. I created a new DSN and tried it. We are still receiving the same error message when trying to set the default company. @MaryJoKrueger we are not sure where the msxml.dll should be located on the workstation so we have not yet copied it over I attached the login error message with the details this time along with the self-registration error screen shot.

It should be in the syswow folder. Rename the existing one and paste the new one in. Are you installing SP 9 and 10 as well as 11? I always do that as I don't believe SP 11 includes fixes from 9 and 10.

If you're installing to c:\frx software, why is the error pointing to the program files (x86) folder? When you uninstalled, did you make sure all existing folders were deleted?

I guess I misunderstood that this was a new message. He just told me that is an old screenshot from a previous installation, but he got the same message this time. I'm leaning toward either that message or the msxml.dll being the issue. Apparently the client needed to leave so we are done for this evening and I will need to pick it up with him tomorrow. I'm going to take it over from this point. Thanks again for every one's input.

We are back at this and still failing so far this morning. - does anyone know where is best to download SP12 for FRx?

This post was the first reference I've seen to SP12. I've always gotten it to work with SP11.

http://www.microsoft.com/en-us/download/details.aspx?id=12339

1. install FRX - right click and run as admin 2. Install latest patch- right click and run as admin 3. Verify versions 4. Run the REG67.BAT in the local FRX directory- right click and run as admin I have not yet seen MSXML be the issue UNTIL you go to print or preview a report.

Thanks Wayne, I will go through the steps again. with SP 12 I've got 2 consultants that work with FRx regularly and myself - we have never seen this not work either with SP11 I'm running out of options short of making the client upgrade (they are on sage version 4.5.7) but I'm not very confident that an upgrade is the answer. hopefully sp12 will work along with a complete re-install will work.

Well thank you to everyone. it is now working with service pack 12 but I'm not 100% sure which step actually fixed the issue. we walked through the steps Wayne outlined plus one other step - I copied the pvxcom.exe file out to the MAS90\home folder (it did not exist there) and I ran it from there (right-click and run as admin) and now FRx is connecting again.

I know that we have other installs where the pvxcom.exe is not in the MAS90\home Directory and FRx is working fine but I found an obscure Microsoft tech note that says it is a know issue and you need to copy it there which is what prompted me to do that. then I ran it from there as admin. I'm not sure if having it there or running it as admin from there worked because I did not test in between those two steps