HotDates example app in Host.exe

[kingja]

Bruce,

I have recompiled the Hotdates example (12) as a dll and I'm trying to run it in the Host.exe.  The Host reports it as active on the Sites tab.  When I try to run it from a browser, the host.exe reloads a few times and the login and password fields are then blanked.  Then I get a IE screen saying "The Page Cannot be Displayed, check that web address is correct, etc.

I have the prototypes on the webserver/webhandler apps set properly with the name attribute.  The Dynamic DLL support is checked in the global template.  All other hosted apps run just fine.

I did change the default page from index.htm to IndexPage, which is how all my other hosted apps are set.  I'm still on 7.07 of NT, but other templates are at later versions.

Also, I have the host name set as scheduler.mydomainname.org on my ISP, Register.com.  I recently added the "scheduler" host name, perhaps this is not yet available and this is the cause. 

What do you think?

Thanks,

Jeff

[Bruce]

>> Also, I have the host name set as scheduler.mydomainname.org on my ISP, Register.com.  I recently added the "scheduler" host name, perhaps this is not yet available and this is the cause. 

no, that would be the cause if you couldn't reach the site at all, but I don't think you'd get the effect you mentioned above. You can of course test if it's propogated to you by just going to a command line, doing a
PING scheduler.mydomainname.org
and see if an IP address is returned. (That's a good way to make sure you got it right as well.)

What you are seeing when the host restarts (and probably deactivates your DLL at the same time) is a GPF. The most common reason for this is mis-matched NetTalk compiles - the Host, and all DLL's must be on the same NetTalk build.

cheers
Bruce

[kingja]

Bruce,

The Host and all dll's are on NT 7.07.  All other dlls work fine, it is just the hotdates example app that does not. 

So, I updated all required and recommended Capesoft templates for the host.  It is now on NT 7.20, as is the Hotdates example app.  I backed up all original apps and have the host running with just the Hotdates dll.  You are right about the GPF, as the error tab shows "DLL caused GPF - automatically made inactive".

I also see an error message on the server: 

"The procedure entry point _7control__doclip@FR8ClipInfoUI could not be located in the dynamic link library ClaRun.dll".

This seems to be the source of the GPF.  Any ideas what this is and how to correct it?

Thanks,

Jeff

[Bruce]

Hi Jeff,

It's complaining about CLARUN - but the others don't - which I suppose leads one to guess that not everything is being compiled "the same".
Make sure they're all using the same Clarion version - and specifically they're all compiled against the same CLARUN.  Maybe check they're all in the same "mode", debug or release mode.

cheers
Bruce

[kingja]

Bruce,

In this case I have just the host and the hotdates dll app running.  No other dll apps running in the NT 7.20 version of the host.  Both the host and dll are NT 7.20, compiled in release mode, using C8 latest build.

The exe version of the hotdates app does run as expected.  So, I have it running with SSL on another port, along side the original NT 7.07 host and apps.  My version of the hotdates app is only slightly modified from the shipping example app.  Now that I'm on NT 7.20, I'll try the unmodified example and see if that makes a difference.

Jeff

[kingja]

Bruce,

I'm still having trouble with this.  I decided to use the most recent version of the Host app.  It opens in debug mode.  As per your previous response, I tried to set it to Release, to match the dll app mode.  I find I can't change it, it always reverts back to debug mode.  Likewise, I tried to change the dll app to debug, and it reverts back to release. 

Also, I noted that the ClaRun.dll, and a few others, such as ClaTPS.dll, may be off by a C8 version or two.  I tried getting all the ClaXXX.dll to the same C8 version, C8.9759.

So, could one app in debug and the other in release cause the error I get?  Could earlier versions of some of the ClaXXX.dll cause this as well?

I'm really stuck here.  My C8 has NT 7.20 installed.  My current Host and dll apps that do run are all on 7.07.  I can't get any of these upgraded at this point.

Can anyone help?

[kingja]

Bruce,

     I have made some success, by starting with just my app and dct files.  I recompiled a few apps with NT 7.20, along with the newer Host app.  I now have 4 apps rebuilt and running through the host.

     However, one app is causing the error "too many segdef:25, 4000".  This app has a web form that is pretty complicated, with numerous tabs and buttons calling other webform procedures.  This app compiles fine in C8.9759 and NT 7.07.  However, I get the segdef error with NT 7.20.

     I have tried generating file defs in modules, removing a couple of templates and procedures.  Still get the segdef error.  Any thoughts?

Jeff

[kingja]

Bruce,

     I have found the issue.  One of my WebForms, called ROS, has 6 tabs.  Each tab has 4 text fields (@S100) with a lookup.  The lookup form has a series of checkboxes which are filtered for the chosen text field.  Removing this WebForm allows the app to compile without the segdef error.
     My idea is to make a new dll with just the ROS webbrowse/webform.  Note that the main dll app is called from the Host.exe.  Can this dll app called from the Host also call another dll?  If so, will this new secondary dll also cause the segdef error?
     Since this app compiled fine using NT 7.07, I wonder if there are any changes in NT 7.20 (or other recent changes to other capesoft templates) that might cause this. 

Thanks,

Jeff