NPO\found\fims\customer\fm\11111SRC\v-fmgran.w was not found (293) when Committing Fieldmaker
- 18 Jan 2023
- Contributors
- Print
- DarkLight
- PDF
NPO\found\fims\customer\fm\11111SRC\v-fmgran.w was not found (293) when Committing Fieldmaker
- Updated on 18 Jan 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
When committing Fieldmaker in either the live or demo database, the following error occurs. The number in the error will be the number of the database as outlined in the fm.ini file located in npo\found\fims\custom\fm folder.
The v-fmgran.w is one example of a file that will be listed as missing.
\\servername\npo\found\fims\custom\fm\11111SRC/v-fmgran.w was not found. (293)
\\servername\npo\found\fims\custom\fm\11111SRC/v-fmappl.w was not found. (293)
After that, when the database is being compiled, several errors stating Error, this version of Progress compiles only encrypted programs (1086) also occurs.
Answer:
This issue occurs because the files are not being created during the Fieldmaker commit process which can be caused by several things:
1. Be sure to right click and run FIMS as admin
2. Be sure that all user are logged off of FIMS except for person running the commit process.
3. Make sure that the Window user has permissions to write to N drive locations.
4. Using UNC paths in the FIMS shortcut. May want to use N paths.
5. If the issues still occur, do the following:
1. Be sure to right click and run FIMS as admin
2. Be sure that all user are logged off of FIMS except for person running the commit process.
3. Make sure that the Window user has permissions to write to N drive locations.
4. Using UNC paths in the FIMS shortcut. May want to use N paths.
5. If the issues still occur, do the following:
- Go to npo\found\fims\custom\fm
- You will see 4 folders, two for each database. One will just be a number, the other will be a number with follwed by SRC.
- Each database has its own number, look in the fm.ini file located in npo\found\fims\custom\fm folder for the number that corresponds to each database.
- In this example you can see that the FIMS live database has the number 76538 with two folders and Demo has the number 1927 with two folders. The name of your databases may be something different than FIMS or Demo.
- As a precaution, copy the specific SRC and the non-SRC folder for the database in which the errors occurred and move the copies out of npo\found\fims\custom\fm, say to the desktop of the computer
- Go back to npo\found\fims\custom\fm and delete the specific SRC and non-SRC folders for the database in which the errors occured.
- So, for example, if you were committing Fieldmaker in Demo and received the error referencing the number for the Demo database, then you would look for the folder numbers that match that database and then copy and delete those folders. It depends on what database you were logged into and committing Fieldmaker and in which the errors occurred.
- Re-commit Fieldmaker in the database that had the error before.
Was this article helpful?
