Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
-Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
West Wind Technologies
Making waves on the Web
from Maui
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
West Wind Technologies
Making waves on the Web
from Hood River
I updated my app with the latest wwDotNetBridge.prg file. That didn't fix the problem. The error was then "Error #1099 in line 208 of wwDotNetBridge.prg" That line contains this code: DECLARE Integer SetClrVersion IN WWC_CLR_HOSTDLL string
I then updated the .Net run time on her system to 4.5.2 and updated wwDotNetBridge.dll and wwipstuff.dll to the latest versions and now get this error: "Error #1753 in Setclrversion line 208 - Cannot load 32-bit DLL clrhost.dll" I checked the properties of wwDotNetBridge.dll and there was no "unblock" button.
What should I try next?
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
-Phil
Are you running the Open Source version or the West Wind Client tools version? They use different DLLs. Open source version uses CrlHost.dll (as defined by #WWC_CLR_HOSTDLL) the client tools version uses wwIpstuff.dll.
So either you're mixing versions or you're getting configuration/header files mixed up.
Easiest way to check is dump out the DLL name in the constant in a print statement.
+++ Rick ---
I updated my app with the latest wwDotNetBridge.prg file. That didn't fix the problem. The error was then "Error #1099 in line 208 of wwDotNetBridge.prg" That line contains this code: DECLARE Integer SetClrVersion IN WWC_CLR_HOSTDLL string
I then updated the .Net run time on her system to 4.5.2 and updated wwDotNetBridge.dll and wwipstuff.dll to the latest versions and now get this error: "Error #1753 in Setclrversion line 208 - Cannot load 32-bit DLL clrhost.dll" I checked the properties of wwDotNetBridge.dll and there was no "unblock" button.
What should I try next?
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
West Wind Technologies
Making waves on the Web
from Maui
That's it. I downloaded the latest wwDotNetBridge from your website which was from the open source. I'll change the flag in wwDotNetBridge.prg so that it's not looking for clrhost.dll and let you know how it works once I can test it at the client site.
Thanks!
-Phil
Are you running the Open Source version or the West Wind Client tools version? They use different DLLs. Open source version uses CrlHost.dll (as defined by #WWC_CLR_HOSTDLL) the client tools version uses wwIpstuff.dll.
So either you're mixing versions or you're getting configuration/header files mixed up.
Easiest way to check is dump out the DLL name in the constant in a print statement.
+++ Rick ---
I updated my app with the latest wwDotNetBridge.prg file. That didn't fix the problem. The error was then "Error #1099 in line 208 of wwDotNetBridge.prg" That line contains this code: DECLARE Integer SetClrVersion IN WWC_CLR_HOSTDLL string
I then updated the .Net run time on her system to 4.5.2 and updated wwDotNetBridge.dll and wwipstuff.dll to the latest versions and now get this error: "Error #1753 in Setclrversion line 208 - Cannot load 32-bit DLL clrhost.dll" I checked the properties of wwDotNetBridge.dll and there was no "unblock" button.
What should I try next?
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
-Phil
Switching the flag to West-Wind .T. fixed the problem. Updating to the latest wwDotnetBridge.prg I think was the ticket to get it working.
Thanks!
That's it. I downloaded the latest wwDotNetBridge from your website which was from the open source. I'll change the flag in wwDotNetBridge.prg so that it's not looking for clrhost.dll and let you know how it works once I can test it at the client site.
Thanks!
-Phil
Are you running the Open Source version or the West Wind Client tools version? They use different DLLs. Open source version uses CrlHost.dll (as defined by #WWC_CLR_HOSTDLL) the client tools version uses wwIpstuff.dll.
So either you're mixing versions or you're getting configuration/header files mixed up.
Easiest way to check is dump out the DLL name in the constant in a print statement.
+++ Rick ---
I updated my app with the latest wwDotNetBridge.prg file. That didn't fix the problem. The error was then "Error #1099 in line 208 of wwDotNetBridge.prg" That line contains this code: DECLARE Integer SetClrVersion IN WWC_CLR_HOSTDLL string
I then updated the .Net run time on her system to 4.5.2 and updated wwDotNetBridge.dll and wwipstuff.dll to the latest versions and now get this error: "Error #1753 in Setclrversion line 208 - Cannot load 32-bit DLL clrhost.dll" I checked the properties of wwDotNetBridge.dll and there was no "unblock" button.
What should I try next?
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
-Phil
It's not ideal, but I don't want to ship additional DLLs with our tools. There are a lot of things rolled into wwipstuff.dll if all of it was broken out there'd be dozens of DLLs.
+++ Rick ---
Switching the flag to West-Wind .T. fixed the problem. Updating to the latest wwDotnetBridge.prg I think was the ticket to get it working.
Thanks!
That's it. I downloaded the latest wwDotNetBridge from your website which was from the open source. I'll change the flag in wwDotNetBridge.prg so that it's not looking for clrhost.dll and let you know how it works once I can test it at the client site.
Thanks!
-Phil
Are you running the Open Source version or the West Wind Client tools version? They use different DLLs. Open source version uses CrlHost.dll (as defined by #WWC_CLR_HOSTDLL) the client tools version uses wwIpstuff.dll.
So either you're mixing versions or you're getting configuration/header files mixed up.
Easiest way to check is dump out the DLL name in the constant in a print statement.
+++ Rick ---
I updated my app with the latest wwDotNetBridge.prg file. That didn't fix the problem. The error was then "Error #1099 in line 208 of wwDotNetBridge.prg" That line contains this code: DECLARE Integer SetClrVersion IN WWC_CLR_HOSTDLL string
I then updated the .Net run time on her system to 4.5.2 and updated wwDotNetBridge.dll and wwipstuff.dll to the latest versions and now get this error: "Error #1753 in Setclrversion line 208 - Cannot load 32-bit DLL clrhost.dll" I checked the properties of wwDotNetBridge.dll and there was no "unblock" button.
What should I try next?
-Phil
Yes that's an old error. If I recall this has to do with some missing C++ runtime files.
That's been fixed a while back. It shouldn't happen with the latest release. If it does please report environment.
+++ Rick ---
Rick,
Actually the first error was: Error #1099 in Setclrversion line 182 Procedure canceled.
Line 182 has this line of code: SetClrVersion(lcVersion)
I'll update wwDotnetBridge.prg and have them try again.
Phil
Exact Error Message and line of code your're running please? My code likely won't match your's by line number...
Probably a good idea to get a more recent build of wwDotnetBridge.
+++ Rick ---
Some of my clients are getting an Error #1099 in Init line 106 of wwDotNetBridge.prg. The date on the wwDotNetBridge.prg is 12/19/2013.
Would this be caused by an out of date .Net version? Just wondering what to check.
West Wind Technologies
Making waves on the Web
from Maui
I know it's an old thread... The error happens when VFP loads Microsoft's version of ClrHost.dll from the SysWOW64 or System32 folder. This might be the case when the current directory isn't the folder in which the correct DLL is located. One common reason is using a PDF printer that changes the default directory to the output directory after printing a report.
There shouldn't be any reason to run that DLL out of any system folders. Or any DLL really at this point. Always best to put everything in the app startup folder, but that will also be affected by a change in folder.
However, I'm not sure why System32/SysWow64 folder would not work when the folder is changed - those are in the system path and should always be accessible. If that fails I would think it's a permissions error perhaps the files just get removed by Windows due to file protection of system folders?
+++ Rick ---
There are TWO ClrHost.dll. One is published by Microsoft and therefore resides in the System folder and the other one is your's residing in the application folder.
wwDotNetBridges loads ClrHost.dll only based on the name only, hence relies on the DLL being in the current folder or the search path. When the application changes the current folder to say the Data folder or when a PDF printer driver changes the folder to the output location and the application then attempts to use wwDotNetBridge for the first time, then you get the error.
The Dll isn't found in the current folder, but Microsoft's Dll is sitting their and is loaded.
Ah - Ok. I had no idea there was a ClrHost.dll in system in which case the name is a bad idea 😃 Even though that is kind of an edge case - I recommend loading wwDotnetBridge during application startup to ensure the right runtime is loaded and during startup you can be pretty sure that the local copy is used. After that the method in my ClrHost is already loaded in memory and shouldn't look on disk again for the DLL.
I suppose I could change the name which would be reasonable as the DLLs are supposed to be matched sets anyway so while inconvenient it wouldn't be a huge breaking change. Main issue is updating the docs...
Or better yet - using the version that comes with Client Tools which doesn't use ClrHost.dll
but wwIpstuff.dll
😃
+++ Rick ---