Hi Thierry (again),
What does this error mean ?
awajax.lSuccess(.f.): Erreur détectée à la ligne n° [no, di de la méthode 'awajax.propsrestore' "La table ne peut être ouverte sous l'alias" C:\Program Files (x86)\Abaque\VHdev\appli\Dooxi\Temp\5C90ISP2X_5c90isp2x_awfrmlogerror_Old.DBF ANTE Call stack: 1 .processhit (n/a) > 2 .process (n/a) > 3 .routerequest (n/a) > 4 dooprocess.process (n/a) > 5 wwprocess.process (n/a) > 6 dooprocess.domevent (n/a) > 7 dooprocess.ajaxformrequest (n/a) > 8 awajax.formrequest (n/a) > 9 awajax.propsrestore (n/a)
Exe: "C:\Program Files (x86)\Abaque\VHdev\appli\Dooxi\dooBS.exe", version 2018.1.482 of 2018-11-12 01:38:24 PM (il y a 27 minutes) Process ID: 5336 Client: 109.134.32.97 userID: 5C90ISP2X URL: http://dooxi.fr/DOMEvent.doo?&Event=click&ObjAddr=awfrmlogerror-grd-chkerror&UserID=5C90ISP2X&PageInit=&nReq=7&Value=0&ValueType=number Form variables: &nKeyCode= &nButton=1 &nShiftAltCtrl=0 &nXcoord=26 &nYcoord=405 &nRow=471 &nCol=56 &ValueType=number &Value=0 &lastKey=0 &version=2.28.0-beta.9 &sync=false &vpw=1922 &vph=914 &userID=5C90ISP2X &reqID=0708_5CA0TXNQN-001 &nInet=0.000 &nCli=0.000 FAS version: 2.28.0-beta.8 of 2018-10-05 08:57:00 AM GMT (il y a 1 mois) Table New: 'C:\Program Files (x86)\Abaque\VHdev\appli\Dooxi\Temp\5C90ISP2X_5c90isp2x_awfrmlogerror_New.DBF' can't be found
Hello Vincent On your server, does the Windows OS run in a virtual box? I've noticed, and other users, that these types of VFP-specific errors are common when the operating system is running in a virtual box.
Cordialement Gilles
Thanks Gilles, yes we have.
Is there any issue ?
My website is down !
The response of status is:
Server1: ClassID for dooBS.dooTestServer not found. Err code = 800401f3: Chaîne de classe incorrecte
Help please ...
Hi Vincent,
First, I did not find a workaround for VFP file access bugs when the OS is virtualized!
Second Have you completely restarted the server machine? As soon as OS security updates regularly disrupt the smooth running of my VFP / FoxInCloud applications on my virtualized Windows 2012 servers. The only solution is a complete restart of the machines so that the updates do not disturb the current operation any more (I think that these updates disrupt especially IIS)
Cordialement Gilles