Sage 100

FRx upgrade from 6.0.81 to 6.7x. Does anyone have a dummies version of how to successfully upgrade FRx? In this case it's 6.081 to 6.7x, 2 workstations both with FRx installed locally, with the Sysdata on the server.

I have had better experience exporting everything out of the old FRx, then installing 6.7.x fresh and importing everything.

Now that you mentioned it, I've heard that also. What specifically would need to be exported? Spec Sets I assume. Anything else? Can't recall exactly what's stored in the Spec Sets.

I did locate this for upgrading FRx. http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isResolutionConceptID=442064

Have to agree with the above...

Can't get into the SSO kb. Anyone? ""Error 429 - You do not have an appropriate license to use this functionality."" when launching FRx

Very slow - same symptoms as usuall - can navigate to the home KB page but the articles/KB links take forever to load or do not load.

http://support.microsoft.com/kb/964430

Workaround Should it be necessary to run another version of FRx, the DLL files for that version need to be re-registered. To do this, explore to the folder where FRx is installed (search for the FRx32.exe file).Within this folder is a file named FRxReg.exe. Double-click on this file to execute the program that registers the necessary DLL files.A DOS window will appear briefly while the program executes. When the program is complete, the window will clear and you will be able to run the problematic version of FRx.

Thanks. I did do a Google search but didn't see that write-up initially. I'll take a look. I did call Sage (did not provide Acct #) and they located the sso write-up and e-mailed to me. And the rep I spoke with had no idea there were any current issue with the sso kb, and therefore did not have any kind of eta. ""Error 429 - You do not have an appropriate license to use this functionality."" when launching FRx Entry Type: Informational Product: FRx Application: FRx Desktop Version Reported: 6.5 Subject: ""Error 429 - You do not have an appropriate license to use this functionality."" occurs when launching FRx. Possible Resolution: Multiple versions of FRx exist on the affected workstation, and the DLL files for the version being launched are not registered correctly. To resolve this issue, register the FRx DLL files on the affected workstation. 1. From the affected workstation, open Windows Explorer, and browse to the ..\FRx\ program directory. 2. Double-click the FRxReg.exe file. This utility registers the necessary files for the specific version of FRx. Note: When running the other version of FRx on this workstation, perform the above steps from the other version's program directory.

microsoft and sage write-ups appear to suggest the same thing. however, that did not resolve the issue.

I think you need to run the FRxReg67.cmd program.

+1 Gene --

Thanks. I actually did that also which appears to do a lot more than frxreg.exe. But still that didn't resolve the error.

From what I remember FRX REG and The REG67 may apply to different versions? I know in the past I've done them both and I *think* only the FRXREG67 worked for current levels (probably 6.7)

I found another article on error 429 which suggests - wait for it - user permissions on the local machine. Make sure you have local machine admin rights.

Here's at least one part of the puzzle. It does seem like it is user rights related. The problem that we perpetually run into is that clients make someone an administrator equivalent -- however that does not seem to automatically make them full fledged administrators in every instance (I'm not sure but guessing that group policy or specific changes might over-ride some portion). What started to work here (ignore that it says VISTA because this was happening on XP and the instructions seem to work): Execute the regsvr32.exe command as an administrator of the Windows Vista computer. Click Start, point to All Programs, click Accessories and then right-click Command Prompt. Click Run as administrator. If you are prompted with a logon, enter the Administrator credentials. Otherwise, click Continue to authorize the action. Within the Command Prompt, type regsvr32.exe and then type enter the path of the .dll file to be registered. For example: regsvr32.exe C:\Program Files\FRx Software\FRx 6.7\filename.dll

Wasted five hours on FRx issue last month which turned out to be a rights issues. This was after the IT dude kept insisting that we had local admin rights on a WIN 7 machine. Turned out we didn't..............................

Oh yeah we had the speech today ""I've been in IT for 20 years - I know that your problem isn't user rights"" .... I wish I were kidding. I mean I'm not sure how else they explain that we keep getting ""could not register"" errors on multiple DLL files. And for extra fun the IT guy refused to login as administrator because we didn't need to. You can't make this stuff up....

Client was running 6.081 - and the 6.081 Sysdata folder is still in tact. Haven't yet upgraded FRx on any workstations yet. I want to get a new workstation on 6.7. Is it recommended to just install 6.7 locally to that workstation (both program folder and sysdata), then copy the 6.081 Sysdata to a new Sysdata folder on the server, and then re-point the new workstation's FRx to the new Sysdata folder? And is it expected that this should bring in all Report formats (rows, columns, etc.), Spec Sets and Companies? Can/should the other workstations be done in the same manner?

I have never had an issue installing the client locally and the sysdata on the shared network drive. In troubleshooting FRx last month, they recomended installing sysdata locally and then move it to the shared drive via the administrator move. Also, when installing the service packs, make sure you install SP 10 prior to SP 11. Another issue I had last month on the WIN 7 install (beside Admin rights) was traced to skipping SP 10. I always thought (as Dawn) that to upgrade to 6.7, you should export all spec sets and then import to the new version leaving sysdata for 6.081 behind.

I ran into a couple of challenges today when installing the FRx client on a new Windows 7 workstation. Had to add the user to the local maching admins, run the FRxReg67.cmd program, manually register the DAO360.dll and MSRD3x40.dll files, download the .net framework 1.1 service pack 1 AND change the path for the SysData folder from the mapped drive to the UNC path. Other than that everything went smoothly.

that's all?

Sorry, it was an easy one.