Skip to main content

Hi,

We have the application running on live environment for more than 5 years without any issue. But from last month we have encountered following error in event viewer (XYZ is a native COBOL module):

Load error : file 'XYZ' 

Error Code: 173, PC = 0, Call= 1, Seg = 0

173 called program file not found in drive/ directory.

Also, the event source was  Micro focus RTS for Visual COBOL.

Can anyone please help as it impacts the business.

Regards

Hi,

We have the application running on live environment for more than 5 years without any issue. But from last month we have encountered following error in event viewer (XYZ is a native COBOL module):

Load error : file 'XYZ' 

Error Code: 173, PC = 0, Call= 1, Seg = 0

173 called program file not found in drive/ directory.

Also, the event source was  Micro focus RTS for Visual COBOL.

Can anyone please help as it impacts the business.

Regards

wich version of visual studio/visual cobol?
This is a runtime error, the call program 'XYZ' was not found?

Did you load your program in a lbr or dll?

Can you debug your application to see more?

Hi,

We have the application running on live environment for more than 5 years without any issue. But from last month we have encountered following error in event viewer (XYZ is a native COBOL module):

Load error : file 'XYZ' 

Error Code: 173, PC = 0, Call= 1, Seg = 0

173 called program file not found in drive/ directory.

Also, the event source was  Micro focus RTS for Visual COBOL.

Can anyone please help as it impacts the business.

Regards

A 173 error means that the program XYZ cannot be found. If this program is not in the current directory when it is called, then it has to be located within one of the directories specified within the PATH or COBPATH environment variables.

Perhaps the settings of one of these environment variables has changed recently and is the cause of the program not being found? If the program is located on a network then perhaps the connection to the network drive is no longer in effect?

What is this program, a .dll, .int, .gnt or is it an entry point within a .dll with a different name which needs to be loaded first?

A 173 error means that the program XYZ cannot be found. If this program is not in the current directory when it is called, then it has to be located within one of the directories specified within the PATH or COBPATH environment variables.

Perhaps the settings of one of these environment variables has changed recently and is the cause of the program not being found? If the program is located on a network then perhaps the connection to the network drive is no longer in effect?

What is this program, a .dll, .int, .gnt or is it an entry point within a .dll with a different name which needs to be loaded first?

It is part of a server-client architecture. and the dll resides on the server side.

It is part of a.DLL which is being invoked from an .exe using procedure pointer and entry point is set for the dll.

wich version of visual studio/visual cobol?
This is a runtime error, the call program 'XYZ' was not found?

Did you load your program in a lbr or dll?

Can you debug your application to see more?

Visual studio 2012 and visual cobol 3.0

It is part of a .DLL.

The application  has been working fine for more than 5 years. this has been encountered only twice in last month.

It is part of a server-client architecture. and the dll resides on the server side.

It is part of a.DLL which is being invoked from an .exe using procedure pointer and entry point is set for the dll.

Are there other entry points within that same .DLL that are being called successfully? It sounds to me like the .DLL is not being loaded properly. If you debug the application after the set procedure-pointer statement the proc-pointer should have a value. If it is null then the load is failing most likely because it cannot find the .DLL.

When you say server-client architecture, are there really two separate processes running where one is running on the server machine and one is running on the client and they are communicating with each other or is the application running solely on the client and it is simply loading the .DLLs from the server machine?

Terms & ConditionsAccessibility statement