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.
↧