After disabling TLS 1.0 AND TLS 1.1 AND ENABLING TLS 1.2. Our application which sends email fails with

Method: WWDOTNETBRIDGE.INIT Line : 150 Error: 1098 Unable to load wwDotNetBridge: Unable to load Clr Instance. 0x8013101b: Unknown error 0x8013101B getwwdotnetbridge Line:46 Code: __DOTNETBRIDGE = CREATEOBJECT("wwDotNetBridge",lcVersion) `"

When I run :

IF !FILE("wwdotnetbridge.dll") OR !FILE("wwipstuff.dll")
  ? "ERROR: wwdotnetbridge.dll or wwipstuff.dll not found."
  RETURN
ENDIF

DO wwDotnetBridge
loBridge = GetwwDotnetBridge()
WAIT WINDOW loBridge.GetDotnetVersion()

I get the following result:

Then when I check the registry I find:

The "Release" value is for version 4.7.02556

When I checked the mscorlib.dll in C:\Windows\Microsoft.NET\Framework\v4.0.30319 This is what is reported:

Does anyone have any ideas what may be causing the error we are gettin?

Thanks

Not sure I understand.

You say it fails to load, yet you see the actual result of wwDotnetBridge loading?

+++ Rick ---

I may be getting close.

As I said when sending an email from a simple test program run in the development environment I have no problem. But when running from the full compiled application the mail fails. with Error 0x8013101b.

If I run the main program of the application from the development system it also produces the same error. However if I run the test program from a "fresh" development environment and then follow that with the Main program from the application it does not produce the Error 0x8013101b. It seems there is another program running in the application which is loading a older Net runtime prior to sending the email.

However Now when running the email from the application loSMTP.ErrorMessage returns "Failure sending mail."

Ok, the version issue is resolved with placing InitializeDotnetVersion("v4") in our application environment setup.

Now we only need to figure out what the "Failure sending mail" message is all about.

Yes - you need to make sure you don't load another version of the .NET runtime first. Most likely you have another old component that explicitly is loading .NET V2 and that's probably goofing things up.

A few guidelines for any application using wwDotnetBridge:

• Call InitializeDotnet("V4") in your app's startup code
• Use GetwwDotnetBridge() without a version number to get instances
• Never specify a version number anywhere except in InitializeDotnet()

All West Wind Components do this so they always the version you specify on startup.

The other issue is more likely to be related to email configuration.

Good luck,

+++ Rick ---

Thanks Rick,

Working well. As always top notch software and support.

Glenn