Skip to main content

I'm currently updating our current v2.3 Micro Focus COBOL instance with Visual Studio 2015 to v8 with Visual Studio 2019 and have had issues with installing FileShare.

I've been able to run FileShare from a command prompt and have it running on server startup.

The only issue I have now is that when I open a solution, I get the message "Error COBCH0942 Could not load assembly 'MicroFocus.COBOL.FHRedir.dll".

Running the program and writing to a file is no issue, the data is written, and the file is closed.  I'm just wondering why this error is showing.

I'm currently updating our current v2.3 Micro Focus COBOL instance with Visual Studio 2015 to v8 with Visual Studio 2019 and have had issues with installing FileShare.

I've been able to run FileShare from a command prompt and have it running on server startup.

The only issue I have now is that when I open a solution, I get the message "Error COBCH0942 Could not load assembly 'MicroFocus.COBOL.FHRedir.dll".

Running the program and writing to a file is no issue, the data is written, and the file is closed.  I'm just wondering why this error is showing.

You must be compiling for managed .NET code and using the CALLFH"FHREDIR" directive? We recently discovered this same problem.
Yoiu need to add a reference to this assembly which is installed in the GAC in the following folder:

C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\MicroFocus.COBOL.FHRedir\\v4.0_4.0.0.0__0412c5e0b2aaa8f0

Right click on the references folder and select Add and then browse to this location and add the reference to the assembly.

The error should then go away...


You must be compiling for managed .NET code and using the CALLFH"FHREDIR" directive? We recently discovered this same problem.
Yoiu need to add a reference to this assembly which is installed in the GAC in the following folder:

C:\\Windows\\Microsoft.NET\\assembly\\GAC_MSIL\\MicroFocus.COBOL.FHRedir\\v4.0_4.0.0.0__0412c5e0b2aaa8f0

Right click on the references folder and select Add and then browse to this location and add the reference to the assembly.

The error should then go away...

Thanks Chris.  Yep, that worked.