Hello,

Net Express 5.1 is not certified on Windows 10 and Windows Server 2012. You might want to consider upgrading to Visual COBOL, which is fully certified on those more recent versions of Windows.

Regards,

www.solvusoft.com/.../cblvios-dll

The website found on solvusoft.com is not helpful at all. Their information regarding cblvios.dll is age-old. It's only promotion for their Windows "dll-tool".

It sounds like one of the run-time files may be missing. Do you have the entire Server for COBOL 5.1 product installed and are your applications linked as dynamic?

Can you run any of the utilities from NX such as rebuild.exe or do you get the same error?

What wrappack level of NX 5.1 are you running? I would recommend that you use the latest wrappack which is 13. Even though NX 5.1 is not certified under Windows 10 the latest wrappack releases shouldn't have a problem, al least in my testing.

Running the procmon tool from SysInternals (now Microsoft) could give you more detail as to what file it cannot find.

Have a look at the last fine post from Chris Glazier.

Additional some hints for the newer Windows operating systems: Our own application (32 Bit) developed with Net Express 5.1 on Windows 7 runs on Windows Server 2012 R2 and one first test on Windows 10 seemed to be ok. Our application is deployed together with the Micro Focus Server (runtime system for Net Express).

If your application is build similar i would suggest that you check the versions of Net Express and Micro Focus Server - they always should be on the same WrapPack level. The recent WrapPack 13 is available, may be it helps. At last have a look at 32-/64-bit issues.

Regards and good luck

Net Express and Windows 10 comes with a few challenges.

Some of the things I've had to do with our developers that run Windows 10:

Set the environment varaiable MFOLECL_NO_THREAD_INIT with a value of Y - We had to do this only on a few machines (Cause unkown)

Delete the nxdebug.~ds found under C:\\Users\\The Windows Username\\Documents\\Micro Focus\\Net Express 5.1\\WORKAREA - This resolves 114 errors when you hit a Debugbreak during animation and NetExpress wants to load the source code

Delete the HKEY_CURRENT_USER\\SOFTWARE\\Micro Focus\\NetExpress\\5.1 - This key recreates itself but you'd loose your preferences. This also can resolve 114 errors when breaking into animation.

What have you got in your manifest for your executable?

Does it support Windows 10 themes?

msdn.microsoft.com/.../bb773175(v=vs.85).aspx

If you upgrade to Windows 10 from an older version of Windows it corrupts the Net Express license.

These are a few things I have come across getting Net Express working on Windows 10.

Perhaps one of the above will resolve your problem.

Neil

Hi Neil,

thank you very much for the information.

It would be very interesting what WrapPack level your are using. Please can you post it here?

At all others who are following this topic:

Keep in mind to distinguish between Net Express itself as the development product and the Micro Focus Server runtime. From the original post by "TomK" i think he was only talking about running executables on a Windows 10 end-user machine, not Net Express itself.

Regards, Torsten

Net Express - We are running wrappacks from 6 - 12. - why the huge gap? When developers upgraded to Wndows 10 and something fails....the first response from Micro Focus is "You need to be on the latest wrappack" (Which  agree with).....so those end up running on the latest wrappack.

I run windows 10 and I'm on wrappack 6. I upgraded from Windows 7 to Windows 10 and was not a new install.

Our compile server however is sitting at wrappack 6 to match the customers environment.

Probably 90% of our developers run Windows 10 (it might even be 100%), others are probably on Windows 8.

In our production code that shipped to the customer we actually  set this "MFOLECL_NO_THREAD_INIT" in code.

In terms of the Micro Focus Server that our customers run on is based on wrappack 6. - To roll out any changes to the runtime is a massive task and not undertaken lightly. There are a lot of laws, processes, testing etc that would have to be undertaken by our customers to take any "fix" or changes.

Again there are other considerations that can effect deployment especially now UAC (User Access Control) is regarded as 'ON' on everybody machine. (We only support Windows 7 SP1 and higher, Server 2008 and higher as well as Azure)

I don't deploy under "Program Files"  (Unless they are Windows services - as they run elevated)

All my executables are manifested "asInvoker"

All my executables are compiled "Shared dynamic" therefore the runtime location is derived from the registry.

The runtime is deployed under "Program Files\\CompanyName"

To roll out the Visual COBOL runtime will involve a years testing and will only happen on a product release.

To sum it up.....we have more problems or issues with Net Express, we don't have any issues with  Micro Focus Server or our application running under it.

Neil