This article addresses how to resolve the runtime error message 199.
Problem:
A runtime 199 will occur when a program is accessing a file that is located on a remote resource and somehow a network "glitch" happens that will get the runtime/file handler confused. In rare situations, it may be caused by an out-of-date installation of Net Express 4.0 which was reporting 199 errors instead of the actual runtime errors. How can this be resolved?
Resolution:
If this issue is seen on Net Express 4.0, and the version of Net Express 4.0 installed is not 4.0.38 then it should be upgraded with the all08n40.exe WrapPack available from http://supportline.microfocus.com. This should solve the issue if the 199 errors are being improperly reported by the runtime system. The actual runtime errors should now be reported.
If this is an already upgraded version of Net Express 4.0, or a later version of Net Express, some possible workarounds include:
a) Move the file being read or written to a local drive. This should eliminate the issue because the file would no longer be a remote resource.
b) Use the WRITETHRU compiler directive. This will commit to disk the changes made to a file immediately instead of having them buffered. The drawback to this would be a possible performance impact on the execution of the program.
c) Modify the program so it will close and then re-open the file on a timely basis.
Incident Number: 2090447, 2124013, 2179881, 2263975
