Tried moving a simple VFP9SP2 EXE that works fine on my machine to a different machine (remote from me) where I already had a working VFP9SP2 EXE complete with the runtime files. I moved my EXE, its INI, and the ClrHost.dll, wwDotNetBridge.xml, wwDotNetBridge.dll, and a C# file name Onboarding.dll that's used as a go-between for a webservice call. I get this error though when trying to run it: https://www.screencast.com/t/yRQ04qhs4C
My machine is Win7Pro. This remote machine is a Windows 2003 server. I've right-clicked the files to see if there was an Unblock but apparently Win2003Server is too old for that security measure.
Ideas?
Thanks! --Mike
Total WAG....
Did you (or do you need to) register the two DLLs?
Mike
mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Tried moving a simple VFP9SP2 EXE that works fine on my machine to a different machine (remote from me) where I already had a working VFP9SP2 EXE complete with the runtime files. I moved my EXE, its INI, and the ClrHost.dll, wwDotNetBridge.xml, wwDotNetBridge.dll, and a C# file name Onboarding.dll that's used as a go-between for a webservice call. I get this error though when trying to run it: https://www.screencast.com/t/yRQ04qhs4C
My machine is Win7Pro. This remote machine is a Windows 2003 server. I've right-clicked the files to see if there was an Unblock but apparently Win2003Server is too old for that security measure.
Ideas?
Thanks! --Mike
[excessive quoting removed by server]
Looks like the .NET Framework isn't installed.
-- Christof
On Thu 9. Nov 2017 at 05:49 mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Tried moving a simple VFP9SP2 EXE that works fine on my machine to a different machine (remote from me) where I already had a working VFP9SP2 EXE complete with the runtime files. I moved my EXE, its INI, and the ClrHost.dll, wwDotNetBridge.xml, wwDotNetBridge.dll, and a C# file name Onboarding.dll that's used as a go-between for a webservice call. I get this error though when trying to run it: https://www.screencast.com/t/yRQ04qhs4C
As a totally unrelated part: They are using a Win2003 server for production? That's technology- and security- equivalent to WinXP. <gasp>
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox [mailto:profox-bounces@leafe.com] Im Auftrag von mbsoftwaresolutions@mbsoftwaresolutions.com Gesendet: Donnerstag, 9. November 2017 05:50 An: ProFox profox@leafe.com Betreff: WestWind Web ClrHost and wwDotNetBridge error on Win2K3 Server
My machine is Win7Pro. This remote machine is a Windows 2003 server.
On 2017-11-09 04:30, Jürgen Wondzinski wrote:
As a totally unrelated part: They are using a Win2003 server for production? That's technology- and security- equivalent to WinXP. <gasp>
wOOdy
Exactly. Pathetic. We're getting their WebConnection app working on Win 2012 Server now. They've dragged their feet because their tech said the WWWC app could only run on 2K3. My partner (who's been doing WWWC for 20 years) is showing them otherwise (although they're overly protective and hesitant to let him configure the server to work for 2012). It's a mess.
I've had a sort of similar issue with wwDotNetBridge where something else on the machine was loading an earlier version of the CLR (v2.0 in my case) in the same process before my wwDotNetBridge code (which required CLR v4.x). At that point wwDotNetBridge would fail on calls to methods that didn't exist in the earlier .NET.
It's supposedly possible to make wwDotNetBridge load a particular CLR version explicitly but I could never get it to work so I ended up rewriting that part as a regular .NET DLL with the relevant methods COM-visible, and using it in VFP that way.
Maybe Rick Strahl would be of more help on the West Wind forums.
Basically
See
https://support.west-wind.com/Thread4YH0ADK7W.wwt
On 2017-11-09 05:35, Alan Bourke wrote:
See
Client tells me they've had DotNet runtimes version v4.0.30319 since August on that server. They can't go beyond that. (Why, I don't know.)
On 2017-11-09 12:37, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2017-11-09 05:35, Alan Bourke wrote:
See
Client tells me they've had DotNet runtimes version v4.0.30319 since August on that server. They can't go beyond that. (Why, I don't know.)
Now I know why 2K3 can't go beyond 4.0: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-a...
There are some crippled version of the .Net 4 framework out there that won't work.
I don't know how you've implemented your WW stuff (I'm using 6.x of Rick's WW Client Tools) but I was also running into issues where the framework wasn't present. I use it for SMTP and FTP. One thing I changed relatively recently, based on Rick's recommendation, was to load the framework on application startup. Previously I was invoking it when firing up an email object or ftp form. According to Rick, the instance of the framework object is scoped to the application so any attempts to create another one will just refer back to the original instance. Also, based on his samples I added this to my app startup:
TRY LOCAL m.loBridge AS [wwDotnetBridge] DO wwDotnetBridge m.loBridge=CREATEOBJECT([wwDotnetBridge],[V4]) CATCH TO m.loError40 TRY m.loBridge=CREATEOBJECT([wwDotnetBridge],[V2]) CATCH TO m.loError20 FINALLY ENDTRY FINALLY IF VARTYPE(m.loError40)<>[O] AND VARTYPE(m.loError20)<>[O] DEBUGOUT m.loBridge.GetDotnetVersion() ELSE IF _vfp.StartMode=0 MESSAGEBOX([dotnet CLR error],MB_OK+MB_ICONEXCLAMATION,[My Really Cool VFP Application]) ENDIF ENDIF RELEASE m.loBridge ENDTRY
So now when that XP or other ancient version of Windows runs my app, the user gets a little message. Obscure to them but I know right away that they need to install the full version of the framework.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Thursday, November 09, 2017 12:37 PM To: profoxtech@leafe.com Subject: Re: WestWind Web ClrHost and wwDotNetBridge error on Win2K3 Server
On 2017-11-09 05:35, Alan Bourke wrote:
See
Client tells me they've had DotNet runtimes version v4.0.30319 since August on that server. They can't go beyond that. (Why, I don't know.)
_______________________________________________
There are some crippled version of the .Net 4 >framework out there that won't work.
The short lived .Net Client Profile version probably.
Sounds about right, Alan.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Alan Bourke Sent: Thursday, November 09, 2017 2:04 PM To: profoxtech@leafe.com Subject: Re: WestWind Web ClrHost and wwDotNetBridge error on Win2K3 Server
There are some crippled version of the .Net 4 >framework out there that won't work.
The short lived .Net Client Profile version probably.
On 2017-11-09 05:30, Alan Bourke wrote:
Maybe Rick Strahl would be of more help on the West Wind forums.
I went to post on the forum and couldn't log in. The 'forgot my password' retrieval service on his site never sends me the link to reset. He did reply to me and said "check the spam/quarantine" and whitelist his domain, but nothing received yet. Frustrating.
Looks like Rick just got back from a conference. Not to mention the difference in TZ when one lives in Hawaii...
https://weblog.west-wind.com/posts/2017/Nov/08/Dev-Intersection-2017-Session...
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Thursday, November 09, 2017 9:52 AM To: profoxtech@leafe.com Subject: Re: WestWind Web ClrHost and wwDotNetBridge error on Win2K3 Server
On 2017-11-09 05:30, Alan Bourke wrote:
Maybe Rick Strahl would be of more help on the West Wind forums.
I went to post on the forum and couldn't log in. The 'forgot my password' retrieval service on his site never sends me the link to reset. He did reply to me and said "check the spam/quarantine" and whitelist his domain, but nothing received yet. Frustrating.
On 2017-11-08 23:49, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Tried moving a simple VFP9SP2 EXE that works fine on my machine to a different machine (remote from me) where I already had a working VFP9SP2 EXE complete with the runtime files. I moved my EXE, its INI, and the ClrHost.dll, wwDotNetBridge.xml, wwDotNetBridge.dll, and a C# file name Onboarding.dll that's used as a go-between for a webservice call. I get this error though when trying to run it: https://www.screencast.com/t/yRQ04qhs4C
My machine is Win7Pro. This remote machine is a Windows 2003 server. I've right-clicked the files to see if there was an Unblock but apparently Win2003Server is too old for that security measure.
Ideas?
Thanks! --Mike
Once I whitelisted Rick's IP, I got my password and his quick reply. Yeah, 2K3 server is too old without changes.
-
Alan Bourke -
Christof Wollenhaupt -
Jürgen Wondzinski -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Mike -
Richard Kaye