Messages
Reply
Edit
Delete03:15 pm
3QE0WOVV6
| From: | Rick Strahl |
| To: | Bob Roenigk |
| WWDOTNETBRIDGE.ZIP |
Hmmm... unable to load 32 bit dll wwipstuff.dll seems to point at a missing wwipstuff.dll file. Do other things that use wwIPStuff.dll work?
Try these two:
? GetDomainFromIp("127.0.0.1") ? GetIpFromDomain("west-wind.com")
wwipstuff.dll is not a COM object so it doesn't need registering.
There have been a few problems reported related to wwDotnetBridge loading but I think this was isolated to the Client Tools. Just in case I've attached the latest proper versions of wwDotnetBridge and wwipstuff.dll.
I just pushed those up to my Windows 2008 Server, and they work fine there although there are a lot of variables there (I got .NET 4.5 installed there).
+++ Rick ---
Rick,
In the process of moving an WW v5.65 app from my (32-bit Win7) development machine to a 64-bit Server 2008 IIS7, the loading of the wwJSONSerializer fails. I confirmed all the v5.65 dll's are in my app's folder. .NET v2 is running on this machine.
It fails within the GetwwDotNetBridge function with the error "Unable to load wwDotNetBridge: Unable to load Clr Instance."
The following commands fail with the error "Cannot load 32-bit DLL wwipstuff.dll".
CLRSETDEFAULTTO \wconnect\classesDO wwDotNetBridgeLOCAL loBridge as wwDotNetBridge loBridge = CREATEOBJECT("wwDotNetBridge")
When running stand-alone (i.e. not called through an IIS app pool), does the wwipstuff.dll need to be registered as a 32-bit app?
~bob
West Wind Technologies
Making waves on the Web
