Without a direct indicator of what may be causing an issue, it is often helpful to set up a local test folder then have one, or a few users, run RFMS from this test folder to see if the issue continues or resolves.
Note: while using the test folder the user(s) will be connected to the same live database, therefore they can continue working as they normally do.
Sections in this article:
IMPORTANT NOTES:
- No RFMS updates can be done while working with test folders as doing so could result in program files with mismatched versions and potential grief in the database.
- The use of a local test folder is for temporary DIAGNOSTIC PURPOSES ONLY. The user(s) should be redirected back to the main RFMS folder and the test folder removed once the issue is resolved.
WARNING: Continued use of multiple RFMS folders can have unexpected adverse consequences. - RFMS recommends the following processes to be done by your local qualified technician.
Create a Test Folder:
- Make a copy of the client's existing RFMS program folder and place it on the root of the C:\ drive of the user's workstation or Remote Desktop Server (for remote users).
Note: It is not necessary to copy the RFMS subfolders to the test folder. Only copy the files in the root of the RFMS folder as the subfolders are not needed for testing. - Apply permissions for the user(s) to the test folder (we recommend full control).
- Create a shortcut on the user's desktop pointing to the rfmsnav.exe file in the test folder and have them launch RFMS from it.
Note: We have found it is sometimes best to remove the existing shortcut from the user's desktop so they don't accidentally use the wrong shortcut during this testing period.
Please remember, the use of a local test folder is for DIAGNOSTIC PURPOSES ONLY. A test folder must only be used temporarily. The user(s) should be redirected back to the main RFMS folder and the test folder removed once the issue is resolved.
Purpose of a Test Folder
When running the RFMS program locally the only network communication occurring is to the SQL server via SQL calls. Therefore, the purpose of the test folder is to test network communications while also testing the RFMS folder/program files.
If the issue goes away when using the test folder, this tells us the program files are working correctly, and it points to some sort of network type communication issue. If the issue continues while using the test folder, this could still point to something with network communication, yet more likely related to a SQL communication issue, or a possible issue with the RFMS program files.
- The next step would be to redirect the user(s) back to the main RFMS folder on the server.
- If the issue returns while working on the main folder, this may indicate something wrong with the folder permissions for the user(s).
Try removing and reapplying permissions (security and sharing) for the users/user groups to the RFMS program folder. Recommended best practice for removing and reapplying permissions is to have all users completely out of RFMS. Then remove permissions and sharing for the users/user groups on the folder, restart the server, add permissions and sharing back, ensuring that the users have full control on both. We recommend users to have Full Control, so they can create, modify and remove files, such as tmp files. Note: it's important to remove and reapply permissions, not just verify they are set. One reason for this is we have found Windows updates, whether on workstation or servers, can cause grief with permissions.
Refer to this link for our recommend best practices for user rights: RFMS NTFS and Share Permissions / Best Practices
If the issue continues while using the test folder, please review the steps in the following linked article for Performance Issues. Or, if the steps in the Performance Issues article have already been completed, submit a request describing the issue and a copy of the completed Performance Issues checklist to rfms-help@cyncly.com for further assistance.
- Link to: Performance Issues Checklist
Comments
Article is closed for comments.