Bad data sent to NetWebserverworker

[terryd]

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]

[Stu]

Terry,

Bruce knows about it (cause I logged it with him a few days ago <g>).

Stu

[terryd]

Thanks
Is this general or just with the NT5_PR26 build?

[Alberto]

Same Pb here with PR26

[Bruce]

it seems to be just in the PR26 build - sorted for PR27.
cheers
Bruce

[Alberto]

same Pb in PR27

[terryd]

Major show stopper./ I've had to revert to PR25. Any idea when this will be fixed?

[britech]

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

[Larry Sand]

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

[Bruce]

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

[zdpl0a]

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

[Larry Sand]

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

[zdpl0a]

Larry,

I got it.....

Thanks so much for your time and effort.

Guess I got to get to work this afternoon

Take Care

Dave

[zdpl0a]

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

[Alberto]

Still in PR28
After a long period of time runing, lets say some hours, the messages appears again.
Had to comment the stop.

Alberto