How to Enable Client Logging for FIMS to Diagnose Network Errors
- 17 Jan 2023
- Contributors
- Print
- DarkLight
- PDF
How to Enable Client Logging for FIMS to Diagnose Network Errors
- Updated on 17 Jan 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
I am having network issues with FIMS on the client machine disconnecting from the database server, how can I enable client logging to get more information on what those issue are?
Here are some examples:
- SYSTEM ERROR: I/O error 2
- The drive or network connection that the shortcut '....' refers to is unavailable.
- ERROR: msgOpen: unable to open message file: PROMSGS
- Openedge graphical client has stopped working
- SYSTEM ERROR WindowWndProc Exception code: C0000006 IN_PAGE_ERROR which is seen on the front end of FIMS and in Protrace logs as well.
- Event viewer on DC server shows ‘user terminated abnormally’
- Database log shows error ‘user terminated abnormally’
Answer:
Typically the three places that you would look for errors would be:
1. Event Viewer on the workstation and the database server
2. Protrace logs located in npo\found\fims
3. Database logs located in npo\found\dbfiles, found.lg file
If you have looked there and also reviewed the articles that we have on these topics, you can enable client logging which creates a log on the machine with the issue that can be used for diagnostic purposes.
To enable client logging:
1. Right click on the FIMS shortcut on the workstation and select properties
2. Edit the target to add these parameters. the bolded ones are what you are adding:
3. Note a log will be created in the location you specified. In this example it is C:\temp:
1. Event Viewer on the workstation and the database server
2. Protrace logs located in npo\found\fims
3. Database logs located in npo\found\dbfiles, found.lg file
If you have looked there and also reviewed the articles that we have on these topics, you can enable client logging which creates a log on the machine with the issue that can be used for diagnostic purposes.
To enable client logging:
1. Right click on the FIMS shortcut on the workstation and select properties
2. Edit the target to add these parameters. the bolded ones are what you are adding:
In this example, a logfile will be created in the C:\temp folder. You can change that to write to another folder if you wish:
N:\dlc\bin\prowin32.exe -pf n:\found\configfiles\wfound.pf -ini n:\found\configfiles\fims.ini -clientlog C:\temp\logfile.txt -logentrytypes 4GLTrace:4
Start in will remain the same:
N:\found\FIMS
N:\dlc\bin\prowin32.exe -pf n:\found\configfiles\wfound.pf -ini n:\found\configfiles\fims.ini -clientlog C:\temp\logfile.txt -logentrytypes 4GLTrace:4
Start in will remain the same:
N:\found\FIMS
3. Note a log will be created in the location you specified. In this example it is C:\temp:
Was this article helpful?
