Rick, You have a reference to a problem with the wwDotNetBridge from back in 2013. Looks like the issue has resurfaced. We are getting the same error all of a sudden (0x80131515). Comes from the return of a -1 in the line

lnDispHandle = ClrCreateInstanceFrom(FULLPATH("wwDotNetBridge.dll"),; "Westwind.WebConnection.wwDotNetBridge",@lcError,@lnSize)

I have used "Streams" to unblock the dll but still nor working. Works fine on Windows 10 machines.

Thought? Paul Mannes

There could be any number of issues there. Check here:

• Cannot load CLR Instance Error

+++ Rick ---

Thanks for the note and link, but it just started on April 14, 2017, several weeks ago. No other changes other than two updated from MS and Security Essensials. Everything has been working great for a long time (years). As I say it works on Windows 10, but these two new updates may have created and issue. And they cannot be removed!

I have unblocked the files (actually done with Streams to the entire folder). So all in all, not sure what is going on.

Paul

There is more than unblocking in the topic. Did you check the other issues?

One difference in the newer versions of wwDotnetBridge is that it now defaults to .NET 4 where it used to default to .NET 2. So you might want to explicitly set the .NET version you are targeting on application startup with:

*** In MyServer::OnLoad()
loBridge = GetwwDotnetBridge("V2") && or V4

This forces an initial load of the .NET runtime and pins it to that version. Any subsequent access to wwDotnetBridge will then use that version of .NET regardless what parameter you specify for the version.

+++ Rick ---