NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: Gerrit on September 28, 2010, 06:24:04 AM
-
I've changed one of my sites to be managed through the Multi Site example as an test.
But keep on getting the DLL Caused GPF.
I was wondering what will be the best way to find the problem.
When compiling the web site as an executable, it runs fine.
But when compiling as an DLL, I get the problem above.
My WebServer and Webhandler have been set as export procedures.
If I compile my website as DLL, I get messages that GPF reporter would not work.
In my website the Webserver and Webhandler is set to export.
I've also got debugview switch on in host and website.
Using NT 5.01 with C6.3.9058
Many Thanks
Gerrit
-
-
See the Tab in the host program window which details most likely causes of a GPF.
ie Run the Host Exe, and look at the tabs there. There's one with some docs on it.
Cheers
Bruce
-
Works great now.
It was the name attribute missing in the WebServer and WebHandler procedures as per your notes on Notes tab.
Many Thanks
Gerrit
-
My called sites are not picking up the location of web folder.
I've made 'Web Directory' in the Netsimple Object(3) template prompt a global and hardcoded the path , but no luck.
I can see an self.site.appPath in the Webhandler, not sure what property I should use and if it will be available in the Webserver procedure. This property would be perfect for initializing location of my web folder.
Thanks
Gerrit
-
the location of the web folder is set as a setting in the host.
So when run as a DLL, the setting of the web folder is set by the Host (and your setting for it is ignored.)
Cheers
Bruce
-
Path to web folder works fine now. Thx
In the site1.app example the path of TPS files is set by the self.site.appPath in the Webhandler.
Is this still necessary if I use C6.3 as I saw the following in the code:
! C5.5: file{prop:name} = clip(self.site.appPath) & 'file.tps'
Thanks
Gerrit
-
yes, it's not limited to C5.5. (It doesn't work in Clarion 5).
If you want the TPS files with the DLL, then set it here in WebHandler...
Cheers
Bruce