web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

FRx on W2012 R2 server or W10 workstation cannot set default

(0) ShareShare
ReportReport
Posted on by 75,850 Moderator
I have another client that refuses to give up FRx. Their IT staff forced a W10 upgrade across the board and, of course, FRx does not work.
I can install FRx but after creating the new company in FRx it fails with the ever popular
"Runtime error -2147319779 (8002801d) automation error library not registered."This error occurs when trying to set a company as default.
I have loaded the old GPConn.dll in the common files Dexterity folder. I registered the file msadox.dll located in the C:\Program Files\Common Files\System\ado folder.
Is there some old MDAC component I am forgetting? Or perhaps some other clue?

*This post is locked for comments

I have the same question (0)
  • JoshP Profile Picture
    on at

    Hello Richard,

    Thanks for the details. That type of error is generally associated with a DLL file that is either not registered or not recognized. You can try and run the files FRxReg67.cmd and FRxReg.exe as an Administrator to see if it completes successfully. If it is a 64-bit OS, there are ones that will likely fail. Please keep in mind FRx has only very limited support on a 64-bit OS (technically written as not supported per support.microsoft.com/.../2014857) so I recommend seeing if they can get it working successfully on a 32-bit terminal server and give users remote access.

    A couple of other things: I would make sure that they have FRx on SP11 if not SP12, and SP9 at an absolute minimum. All workstations that share a SysData folder need to be at the same version. Also, do not install FRx to "Program Files" or "Program Files (x86)" but install it outside of those folders, such as at "C:\FRx".

    If you still have the problem, try using Process Monitor (docs.microsoft.com/.../procmon) to see if you can identify which file it is looking for and failing.

    Lastly, FRx is only supported up to GP 2010 so I would check which GP version they are using. Any version after GP 2010 is not supported by FRx (support.microsoft.com/.../848107).

    Thanks!

  • Richard Wheeler Profile Picture
    75,850 Moderator on at

    Josh, they have been a GP client for decades so the FRx tables inside SQL are sitting there so even though they are on GP 2015 FRx will continue to work. They were fine until IT forced the W10 upgrade. I just got a call one day to install FRx on the W10 computer and I had warned them after the fact that I doubted I would be successful.  I have a call with their IT group later today and I am going to plead that they find an old W7 computer someplace and I will put FRx on that one. We already have replacement financial reporting tools in place which I thought they were using. So right now we will commence emergency training so we can turn off FRx. FRXREG67 was run but that did not correct the issue. At this point in time the W7 idea is the least costly so that is how we will proceed. Thanks for your thoughts.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans