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
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
Rich
I worked with Microsoft last night and we had to update the System.cfg file in the SysData folder.
It had a move to command that was sending us back to the old server.
Success!
Chuck
Please do update this thread when you find a resolution. I have spent many a time beating my head against the wall with an FRx issue in the past and I know how much it helps to have another person just listening and asking a few questions.
Based on what you have said, I cannot think of why it would want to resort back to the old server. If you did an install, this server installation of FRx should have no reference back to the old server which tells me that we are missing some other file that needs an edit. Again, I am assuming you drug the old FRx folder or parts thereof, from the old server so as to get the catalogs and such. Did you drag after the fresh install or prior to the fresh install? Just curious. When doing something like this, I have only pulled over the f32 file from the systdata folder. If you happened to pull over the entire sysdata folder, did you look at the system.cfg file in there? It has a link to the rates table which could also have a reference to the old server name.
Rick
I really appreciate your troubleshooting. No need to set up a remote session as I opened up a ticket with Microsoft due to the time crunch on this issue.
To answer your questions above:
I get the same error message when opening FRX32.exe in the FRx folder.
I installed FRx on the new server and yes, I get the error upon launching FRx.
I will update this post when I get a resolution from Microsoft.
Thanks again for all your help.
Chuck
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).
Rick
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.
Thanks,
Chuck
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 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.
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?
Rick
Thanks for the response.
I am invoking FRx from a server and drive D should be mapped properly.
Thanks,
Chuck
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.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,532 Super User 2024 Season 2
Martin Dráb 228,501 Most Valuable Professional
nmaenpaa 101,148