Notifications
Announcements
No record found.
Does anyone know how to accomplish this issue?
We cannot get past "The FRx Sysdata location is not valid" error and cannot update the FRxConfig.xml file.
Thanks,
Chuck
*This post is locked for comments
Hi Chuck,
it's been a while since I've done this...but of course make sure you have a good back up. Secondly, FRX32.CFG in the FRX program directory file contains information that you can edit.
Renee
Thanks for the quick response.
I try to edit the file and it says "Cannot create the D:\Program Files\FRx Software\FRx6.7\FRx32.cfg file".
Make sure that the path and file are correct.
It keeps defaulting to the old SL/FRx server's name.
Chuck,
As Renee said, the frx32.cfg file that is located in the FRx folder on the server will contain a line defining the directory of where the sysdata folder exists. Depending on the original installation, this could include a mapped drive or a UNC path. If it is a UNC path then the first part is the server name. If it is specifying a mapped drive then this will be the drive mapping to that server where the share was created.
There is also an xml file in the user folder (appdata\local\frx software) that contains the location of the sysdata folder as well.
You have not indicated if this error is coming from a workstation trying to invoke FRx or if you are trying to invoke FRx from the server. Your latest response indicates that you have used a mapped drive (drive D). Have you made sure that drive D is appropriately mapped with a proper share? Given that this is drive D, I am thinking you are attempting to launch FRx from the server since server mapped drives specified on a workstation are typically much higher drive letters.
So, lets step back a bit and tell us where you are invoking FRx from (server or workstation) and if drive D is mapped properly.
By the way, I have moved SL and FRx to new servers many times at it works fine as long as you get all the parts pointing to the correct location.
I vaguely remember having that issue too. I can't recall what I did to fix that. Do you still have the original install? Have you tried in FRx Admin (from original install) to move the data folders? I've never done that but might be worth a shot. And then try from new install to open.
Rick
Thanks for the response.
I am invoking FRx from a server and drive D should be mapped properly.
OK, what is the content of the frx32.cfg file in the frx67 folder? Also, look at the xml file in the user folder on the server and let me know what it contains.
Can you use Windows Explorer to browse to drive D and see FRx32.cfg? If so, try renaming it to see if you have full rights to that folder and then rename if back.]
What service pack level do you have FRx at (the build number will tell us that)? And, what version of Windows Server is installed on the new server?
I was able to change the name of the file and edit the sysdata path.
We are on SP12 and Windows Server Standard 2007 in installed on the new server.
So far so good. did you look at the xml file under the users folder that I indicated and edit the path there as well?
A couple of other ideas. Sometimes using a UNC path seems to work better than a mapped drive. However, that typically applies when invoking from a workstation and not directly on the server.
Have you tried running the FRxreg67.cmd command located in the FRx folder? That rebuilds the registry entries needed for FRx. Note: you must be a local admin to successfully run this cmd. I typically enter CMD in the programs field but do not hit enter. I then right click that and select run as administrator.
I am using the unc path to update the xml file, but every time I try to open FRx it changes the sysdata path back to the old server.
I ran the CMD file as admin as well, but still have the same issues.
Got to love how FRx is picky (but not as picky as Management Reporter). Obviously, it is picking up the older server name from somewhere. Now we just need to figure out where.
I have not asked how you are invoking FRx but let's start by simply double-clicking FRx32.exe directly from the FRx folder where you have FRx installed on the new server and where you edited the FRx32.cfg file.
By the way, did you install FRx on this new server or did you just drag the folder over from the old server? Also, I am assuming you get this error upon launching FRx even before you can connect to a company or even get past the user name prompt. Is that correct?
Would you be interested in setting up a remote session with me so I can see what is going on and look at some things? I have a tool that would let us connect (GotoAssist from Citrix).
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
