NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: terryd on July 27, 2010, 06:54:24 AM
-
Any help with this NT5_PR26.
Getting this error on a application after conversion from NT4.49
This message keeps on coming up putting a blank in the webserver window
[attachment deleted by admin]
-
Terry,
Bruce knows about it (cause I logged it with him a few days ago <g>).
Stu
-
Thanks
Is this general or just with the NT5_PR26 build?
-
Same Pb here with PR26
-
it seems to be just in the PR26 build - sorted for PR27.
cheers
Bruce
-
same Pb in PR27
-
Major show stopper./ I've had to revert to PR25. Any idea when this will be fixed?
-
PR26 solved other problems I had, so I can't go back to PR25.
Anxiously awaiting for a resolution to Bad data Error as well.
Brian
-
I too can reproduce the error under PR 27.
One thing you can and should do is to hook all of the procedures, Message(), Stop(), Assert(), Halt(), FatalError(), and perhaps FileDialog() and ColorDialog(), if they could be called. You can then react to the errors in code. You could even set the stop, assert, and halt to restart your server. If you run your server as a service it's essential that you write these hook procedures. Otherwise your server will stop and you won't know what's happening as the dialog displayed is waiting in a hidden window station with no way to respond for the program to continue.
Larry Sand
-
the stop is in \clarion6\libsrc\netweb.clw.
You can remove the stop from the code in PR26. It doesn't fix the underlying problem, but it should sort out your issue for now.
in clarion7 netweb.clw is in \clarion7\accessory\libsrc\win
cheers
Bruce
-
Hi all,
Is there a sequence that produces this problem? I have 13 services and have not seen it in testing, and 26 fixed my other problems.
Also, what does Larry mean in his post above by hook the procedure?
Thanks,
Dave
-
Dave,
In the online help for Clarion, lookup prop:LibHook and you'll see these hooks
{PROP:Libhook, 1} PROP:ColorDialogHook
{PROP:Libhook, 2} PROP:FileDialogHook
{PROP:Libhook, 3} PROP:FontDialogHook
{PROP:Libhook, 4} PROP:PrinterDialogHook
{PROP:Libhook, 5} PROP:HaltHook
{PROP:Libhook, 6} PROP:MessageHook
{PROP:Libhook, 7} PROP:StopHook
{PROP:Libhook, 8} PROP:AssertHook
{PROP:Libhook, 9} PROP:FatalErrorHook
{PROP:Libhook, 12} PROP:SystemPropHook
{PROP:Libhook, 13} PROP:AssertHook2
{PROP:Libhook, 14} PROP:InitAStringHook
{PROP:Libhook, 15) PROP:UnlockThreadHook
{PROP:Libhook, 16) PROP:LockThreadHook
{PROP:Libhook, 17) PROP:ThreadLockedHook
Now you can use that list to lookup the indivial props for more info. For instance: Prop:MessageHook says
A property of the SYSTEM built-in variable that sets the override procedure for the MESSAGE internal Clarion procedure. Equivalent to {PROP:LibHook,6}. Assign the ADDRESS of the overriding procedure, and the runtime library will call the overriding procedure instead of the MESSAGE procedure. Assign zero and the runtime library will once again call its internal procedure. The overriding procedure's prototype must be exactly the same as the MESSAGE procedure found in the BUILTINS.CLW file. (WRITE-ONLY)
You can then open builtins.clw to find the prototype for the Message() procedure and create a procedure in your app to match like this:
MessageHook PROCEDURE(STRING sMsg,<STRING sCaption>, <STRING sIcon> ,<STRING sButton>, UNSIGNED btnDefault=0, UNSIGNED mStyle=0 ),UNSIGNED,PROC
You must ensure that you don't call Message() or any other method or procedure that may call Message() from within this hook procedure. If you do it will be called recursively and GPF when it blows the stack. I log these messages to rotated text log files and send messages to notify an admin of the problem.
To enable the hook, in your program early on you set the system hook property to the address of your hook procedure to prevent the standard Message dialog from displaying:
System{Prop:MessageHook} = Address(MessageHook)
Cheers,
Larry Sand
-
Larry,
I got it.....
Thanks so much for your time and effort.
Guess I got to get to work this afternoon
Take Care
Dave
-
I too, like the folks above, need the product fix. Just don't have the time to mess with this and my production stuff still runs fine. Have a stack of enhancements built under 26 that I'd like to get in .
Dave
-
Still in PR28
After a long period of time runing, lets say some hours, the messages appears again.
Had to comment the stop.
Alberto
-
are you sure it was the same stop?
-
No doubt, I had to comment the line.
I had been changing PR to test the browse refresh...
How can I be sure I´m in PR28?
Thanks
Alberto
-
check the global extension.
cheers
Bruce
-
It seems to me that pr28 fixed the bad data problem. I have had it running on two different o/s platforms for days with out that problem. However I am also having problems with a browse procedure that will not refresh. This started when I upgreaded to pr28 . Driving me really crazy to find out whats going on with this. Any idea's anyone!
-
Ray, look at the template where you define the timer, mey be the drop below is blanked.
I had the same problem.
Set it to Current and its done.
Alberto
-
Bruce, I only see NETtalk 5.0 in the global ext.
-
Thanks Alberto,
I saw your first post on this and tried it but does not work. It is set to blank but will not allow me to change it. That field is dimmed out. Whats really crazy is that I have another browse procedure that works fine. The refresh field is also blanked out. Really strange!