Skip to main content

I have a COM object that was written originally in NetExpress and was recently imported into Visual CoBOL for VS 2017.  When I install the COM object on my local development machine, I am able to activate it with no issues.  When I install it on the Server, I get a Dynamic bind error, using the same programs that appears to reference a version issue.  I have included screenshots of the error, and version of run-time installed and of the version installed on my local development machine. 

In the past we had to install a complete development license on the servers in order to have this work, is this still required under visual CoBOL or is there something else we can do?

I have a COM object that was written originally in NetExpress and was recently imported into Visual CoBOL for VS 2017.  When I install the COM object on my local development machine, I am able to activate it with no issues.  When I install it on the Server, I get a Dynamic bind error, using the same programs that appears to reference a version issue.  I have included screenshots of the error, and version of run-time installed and of the version installed on my local development machine. 

In the past we had to install a complete development license on the servers in order to have this work, is this still required under visual CoBOL or is there something else we can do?

Whenever a dynamic binding error occurs on a run-time entry point and it also states about the dynamic binding requires at least a certain version of CBLRTSM.DLL, this indicates a mismatch of the version of the patch update of the COBOL runtime library.

In your case, it is likely that the patch update level on Visual COBOL is higher than the one on COBOL Server. The latter should always have the same or higher patch update, not older.

Please note the patch update level is not shown in the version you see in 'Programs and Features'. You need to click 'View installed updates' to see the patch update level.

Terms & ConditionsAccessibility statement