NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: hkalmbach on July 20, 2022, 12:36:07 AM

Title: Nettalk File Error 33 with SQL Express
Post by: hkalmbach on July 20, 2022, 12:36:07 AM

Hello,
I am using NetTalk 12.41 and SQL Express.
I have a browse with an Edit in Place Checkbox.
If I check some lines in the browse fast the WebServer produces an error message (error 33) and also DebugView gets error messages.

67   29.923422   15280   MagWeb.exe   [st] [netTalk][thread=4] NETTALK FILE ERROR: 33 Satz nicht verf?gbar! :: 0
68   29.931760   15280   MagWeb.exe   [st] [netTalk][thread=4] NETTALK FILE ERROR: 33 Satz nicht verf?gbar! :: 0
69   29.932107   15280   MagWeb.exe   [st] [netTalk][thread=4] NETTALK FILE ERROR: 33 Satz nicht verf?gbar! :: 0
70   29.932671   15280   MagWeb.exe   [st] [netTalk][thread=4] NETTALK FILE ERROR: 33 Satz nicht verf?gbar! :: 0

The problem is, the error messages appear on the server, mostly the webserver runs as windows service and nobody sees them. Then the web server hangs.

Does someone know how to trap these file error messages to get no message boxes in the web server?

Thanks in advance

Cheers
Heinz

Title: Re: Nettalk File Error 33 with SQL Express
Post by: Bruce on July 20, 2022, 02:45:41 AM

Do you have your driver strings set to
busyHandling=2
and (perhaps?) MARS on? (Some have success with it on, others with it off.)

Cheers
Bruce

Title: Re: Nettalk File Error 33 with SQL Express
Post by: hkalmbach on July 20, 2022, 04:02:59 AM

Hi Bruce,

I don't see any effect with these driverstring options.

Is there a way to trap and ignore this errors?
That there is no message box in the webserver?

Cheers
Heinz

Title: Re: Nettalk File Error 33 with SQL Express
Post by: Bruce on July 20, 2022, 06:56:36 AM

Using CapeSoft MessageBox you can suppress the errors.
https://www.capesoft.com/accessories/mesboxsp.htm

Title: Re: Nettalk File Error 33 with SQL Express
Post by: Alberto on July 20, 2022, 11:34:40 AM

Hi,
Try this:

GLO:DriverOptions = '/VERIFYVIASELECT=true ; /BUSYHANDLING=2 ; /LOGONSCREEN=FALSE'

Regards