Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
None of our users are able to access FRx Row formats, Column Layouts or Reporting trees directly, they get the error above. They are able to access the Catalog of Reports. From what research I've done so far it looks like we have a column in a table with either missing or corrupt data but I'm not sure where to have my DBA start searching. I located this list of tables used by FRx support.microsoft.com/.../867365 and one user indicated he was missing column information that contained GL Account information so I'm targeting GL00100, 10110, 30000, 30001, 10111, SY00302 and 00300. Just wanted any other advice if I'm headed in the right direction or should be approaching this differently. Thanks!
Make sure you sysdata is pointed correctly, that is usually a shared file and it looks like yours has gone missing. You can check by opening System>>Administration and looking at where your sysdata file is. It is usually located in a shared location. Take a look and see where it is supposed to be. The Sysdata contains all your rows, columns and trees.
We are on FRx release 188.8.131.528 and I do not see the menu path System > Administration.
I can see the SysData folder on our server but not file named that either. ?
Doesn't matter where it is getting the files. If it can't see the Sysdata files you won't see anything. Here is a TK to go by. Basically check within the local install of FRx look at the FRX32.cfg and see where your Sysdata and your I/O Data are pointed to and see if the file actually exists.
The FRX32.cfg file is pointing to the correct location. We also checked to make sure our users have the correct permissions to all folders that Microsoft FRx must access and also that they have Full Control permissions to the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\FRx Software. As well we verified the shared SysData folder is set to shared.
The only other thing I could find was out on the following website:
www.techspot.com/.../frx-run-time-error-2147220502.106237 but their's was a language issue:
Are you able to log in as 'sa' and if so have you tried compacting the db. Make sure all other users are out of the db.
Try compressing the system database and spec set.
Sue and Nathan are dispensing some solid advice here. I have found the two major causes of problems with FRx are installation (one user is typically affected) and data corruption (all users are affected). In this instance it sounds like the latter. One of the most ubiquitous fixes is to delete the *.g32 files in the sysdata folder.
If you were to run an Internet Search, you would find numerous cases resolved by this approach. In case you miss my warning in my signature below, always have a backup.