FiveTech Support Forums

Hola,

Estoy intentanto probar los ejemplos de conexion y apps del webinar pero cuando me conecto al sashboard y voy a cualquier otra aplicacion el servidor Hix me aborta con estos errores

Application Internal Error - C:\hix\hix.exe
Terminated at: 2026-01-04 07:25:22
Unrecoverable error 6005: Exception error:

Exception Code:C0000005 ACCESS_VIOLATION
Exception Address:00007FFB1F2365B6
RAX:0000000000000000  RBX:000002A556C99E78  RCX:0000000000000000  RDX:000002A556C99E48
RSI:0000000000000001  RDI:00007FFB1F2365B0  RBP:000000EDAA7FE860
R8 :0000000000000001  R9 :000002A556BFC048  R10:00007FF600060000  R11:00007FF6003139F4
R12:0000000000000000  R13:0000000000000015  R14:0000000000000000  R15:0000000000100015
CS:RIP:0033:00007FFB1F2365B6  SS:RSP:002B:000000EDAA7FE730
DS:002B  ES:002B  FS:0053  GS:002B
Flags:00010206
Exception Parameters: 0000000000000000 0000000000000010

Modules:
00007FF600060000 0000000000554000 C:\hix\hix.exe
00007FFBA3D60000 0000000000267000 C:\WINDOWS\SYSTEM32\ntdll.dll
00007FFBA2F20000 00000000000C9000 C:\WINDOWS\System32\KERNEL32.DLL
00007FFBA1010000 00000000003EF000 C:\WINDOWS\System32\KERNELBASE.dll
00007FFBA1620000 000000000014B000 C:\WINDOWS\System32\ucrtbase.dll
00007FFBA3760000 00000000001C5000 C:\WINDOWS\System32\USER32.dll
00007FFBA18A0000 0000000000027000 C:\WINDOWS\System32\win32u.dll
00007FFB86B00000 00000000000CE000 C:\hix\libssl-3-x64.dll
00007FFB2C150000 000000000049E000 C:\hix\libcrypto-3-x64.dll
00007FFB65790000 00000000000C4000 C:\WINDOWS\SYSTEM32\ODBC32.dll
00007FFBA3960000 000000000002B000 C:\WINDOWS\System32\GDI32.dll
00007FFBA1C00000 0000000000074000 C:\WINDOWS\System32\WS2_32.dll
00007FFBA1E60000 00000000000A9000 C:\WINDOWS\System32\msvcrt.dll
00007FFBA1770000 000000000012C000 C:\WINDOWS\System32\gdi32full.dll
00007FFBA3410000 00000000000B4000 C:\WINDOWS\System32\ADVAPI32.dll
00007FFBA2D30000 0000000000118000 C:\WINDOWS\System32\RPCRT4.dll
00007FFBA0F60000 00000000000A3000 C:\WINDOWS\System32\msvcp_win.dll
00007FFBA2FF0000 00000000000A6000 C:\WINDOWS\System32\sechost.dll
00007FFBA1410000 0000000000177000 C:\WINDOWS\System32\CRYPT32.dll
00007FFBA1B00000 00000000000F0000 C:\WINDOWS\System32\COMDLG32.dll
00007FFB86A60000 0000000000095000 C:\hix\libcurl.dll
00007FFBA3990000 0000000000385000 C:\WINDOWS\System32\combase.dll
00007FFBA1F10000 00000000000F5000 C:\WINDOWS\System32\shcore.dll
00007FFBA3580000 0000000000066000 C:\WINDOWS\System32\SHLWAPI.dll
00007FFB94320000 0000000000035000 C:\WINDOWS\SYSTEM32\WINMM.dll
00007FFBA2580000 0000000000753000 C:\WINDOWS\System32\SHELL32.dll
00007FFB7D390000 000000000001E000 C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
00007FFBA1990000 000000000016A000 C:\WINDOWS\System32\wintypes.dll
00007FFBA3120000 0000000000197000 C:\WINDOWS\System32\ole32.dll
00007FFBA2010000 00000000000D6000 C:\WINDOWS\System32\OLEAUT32.dll
00007FFB78DA0000 00000000000B4000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.26100.7309_none_87ef0e2f7a2c9771\COMCTL32.dll
00007FFB9F660000 0000000000034000 C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
00007FFB82E60000 00000000000B1000 C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
00007FFB99680000 000000000001A000 C:\hix\zlib1.dll
00007FFBA0DA0000 000000000002A000 C:\WINDOWS\SYSTEM32\bcrypt.dll
00007FFB85D70000 0000000000021000 C:\WINDOWS\SYSTEM32\MPR.dll
00007FFBA0AA0000 000000000000A000 C:\WINDOWS\SYSTEM32\DPAPI.DLL
00007FFBA0A20000 0000000000057000 C:\WINDOWS\SYSTEM32\cfgmgr32.dll
00007FFBA2CF0000 0000000000031000 C:\WINDOWS\System32\IMM32.DLL
00007FFB9FC20000 000000000001B000 C:\WINDOWS\SYSTEM32\kernel.appcore.dll
00007FFBA0170000 000000000006B000 C:\WINDOWS\system32\mswsock.dll
00007FFBA0EB0000 00000000000A5000 C:\WINDOWS\System32\bcryptPrimitives.dll
00007FFB9DC80000 00000000000AB000 C:\WINDOWS\system32\uxtheme.dll
00007FFBA2E50000 00000000000B0000 C:\WINDOWS\System32\clbcatq.dll
00007FFB65540000 000000000004E000 C:\WINDOWS\system32\wbem\wbemdisp.dll
00007FFB90900000 000000000007A000 C:\WINDOWS\SYSTEM32\wbemcomn.dll
00007FFB8CC30000 0000000000012000 C:\WINDOWS\system32\wbem\wbemprox.dll
00007FFBA0C20000 00000000000A2000 C:\WINDOWS\SYSTEM32\sxs.dll
00007FFB8BF80000 000000000001F000 C:\WINDOWS\system32\wbem\wmiutils.dll
00007FFB8BFB0000 0000000000015000 C:\WINDOWS\system32\wbem\wbemsvc.dll
00007FFB8C070000 00000000000F2000 C:\WINDOWS\system32\wbem\fastprox.dll
00007FFB8BD50000 000000000001D000 C:\WINDOWS\SYSTEM32\amsi.dll
00007FFBA0220000 000000000002B000 C:\WINDOWS\SYSTEM32\USERENV.dll
00007FFBA0DD0000 0000000000029000 C:\WINDOWS\SYSTEM32\profapi.dll
00007FFB47810000 00000000000A2000 C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.25110.6-0\MpOav.dll
00007FFB98600000 000000000000B000 C:\WINDOWS\system32\version.dll
00007FFB9DA20000 000000000000D000 C:\WINDOWS\SYSTEM32\secur32.dll
00007FFB9FEC0000 0000000000049000 C:\WINDOWS\SYSTEM32\SSPICLI.DLL
00007FFB9F700000 000000000012C000 C:\WINDOWS\SYSTEM32\DNSAPI.dll
00007FFBA2CE0000 000000000000A000 C:\WINDOWS\System32\NSI.dll
00007FFB92A10000 000000000000B000 C:\Windows\System32\rasadhlp.dll
00007FFB93650000 0000000000086000 C:\WINDOWS\System32\fwpuclnt.dll
00007FFB9FA50000 00000000000C4000 C:\WINDOWS\system32\schannel.DLL
00007FFBA06B0000 0000000000030000 C:\WINDOWS\SYSTEM32\ncrypt.dll
00007FFBA0660000 000000000003F000 C:\WINDOWS\SYSTEM32\NTASN1.dll
00007FFB801D0000 0000000000042000 C:\WINDOWS\system32\ncryptsslp.dll
00007FFB9EA90000 000000000085E000 C:\WINDOWS\SYSTEM32\Windows.Storage.dll
00007FFB9BA40000 0000000000103000 C:\WINDOWS\SYSTEM32\PROPSYS.dll
00007FFB85DA0000 00000000001E0000 C:\WINDOWS\SYSTEM32\urlmon.dll
00007FFB85940000 00000000002C5000 C:\WINDOWS\SYSTEM32\iertutil.dll
00007FFB9F5D0000 000000000000D000 C:\WINDOWS\SYSTEM32\netutils.dll
00007FFB8BA70000 0000000000029000 C:\WINDOWS\SYSTEM32\srvcli.dll
00007FFB997E0000 000000000001F000 C:\Windows\System32\Windows.Shell.ServiceHostBuilder.dll
00007FFB92AD0000 000000000064F000 C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
00007FFB7E140000 000000000017A000 C:\Windows\System32\Windows.System.Launcher.dll
00007FFB8D0A0000 000000000001A000 C:\WINDOWS\SYSTEM32\windows.staterepositorycore.dll
00007FFB89480000 0000000000293000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.26100.7309_none_3e05feeae336a044\comctl32.dll
00007FFB925C0000 0000000000044000 C:\WINDOWS\SYSTEM32\MLANG.dll
00007FFB88C70000 0000000000288000 C:\WINDOWS\SYSTEM32\WININET.dll
00007FFB8B950000 00000000000C4000 C:\Windows\System32\Windows.StateRepositoryPS.dll
00007FFB838C0000 0000000000046000 C:\WINDOWS\SYSTEM32\windows.staterepositoryclient.dll
00007FFB87830000 0000000000118000 C:\WINDOWS\SYSTEM32\mrmcorer.dll
00007FFB877A0000 0000000000034000 C:\WINDOWS\SYSTEM32\bcp47mrm.dll
00007FFB8BDB0000 0000000000152000 C:\Windows\System32\Windows.UI.dll
00007FFB7E830000 0000000000029000 C:\WINDOWS\SYSTEM32\edputil.dll
00007FFB1F220000 0000000000581000 c:\hix\libmysql64.dll
00007FFB940C0000 0000000000018000 C:\WINDOWS\system32\napinsp.dll
00007FFB940A0000 0000000000012000 C:\WINDOWS\System32\winrnr.dll
00007FFB93EF0000 0000000000022000 C:\WINDOWS\system32\nlansp_c.dll
00007FFB93ED0000 0000000000016000 C:\WINDOWS\system32\wshbth.dll

Called from HB_DYNCALL(0)
Called from MYSQL_FETCH_ROW(426) in pcode.hrb
Called from FETCHROWARRAY(376) in pcode.hrb
Called from RENDERFULLUI(277) in pcode.hrb
Called from MAIN(60) in pcode.hrb
Called from HB_HRBDO(0)
Called from UEXECUTEPRG(2750) in src\uhttpd2\umain.prg
Called from UPROCFILES(2553) in src\uhttpd2\umain.prg
Called from (b)UHTTPD2_SETDIRFILES(298) in src\uhttpd2\umain.prg
Called from PROCESSREQUEST(1505) in src\uhttpd2\umain.prg

Called from PROCESSCONNECTION(1271) in src\uhttpd2\umain.prg

Hola,

No se como conectas, en principo esta versión aun no esta preparado para conectar con mysql.

Si pones un ejemplo de como realizas la conexion te podre contestar.

C.

Hello Charly,

Maybe a question / idea for discussion:

Instead of connecting SQL directly inside the HIx process, could it be an option to add a small socket (WebSocket / JSON) adapter layer?

The idea would be:

existing Harbour SQL applications remain unchanged the SQL logic still runs in Harbour only the execution is moved into a separate Harbour service process

HIx communicates with this service via a simple socket adapter This would keep all proven SQL code and business logic intact, while gaining: crash isolation (no native DLL crashes inside HIx)

clearer separation of responsibilities easier debugging and maintenance

From an architectural point of view this feels like a small, evolutionary step on solid ground, not a rewrite.

I would be interested in your thoughts if such an adapter approach could make sense for HIx in the long run.

Best regards, Otto

Hello Otto,

For me, this doesn't make sense.

From Harbour we can perfectly manage all these resources. All languages have their connections to modern databases, be it mysql, sqlite, progress, … If you notice, for example, php has its native connections via mysqli in its own core, python has its library integrated, Java its jdbc connector,… node uses its packages to manage its databases.

Why do we have to use from Harbour these connections you mention or experiment with if we can manage everything directly like other languages? And why create tunnels using php, websockets, json, node, services,…? Do we have to make things so complicated?

I read that now you want to separate the logic of data process execution into an external service,… seriously?

All these languages I mentioned that have their own database managers, just like Harbour, generally work the same way. Why should Harbour be different and complicate everything?

If we're talking about HIX, you simply enter the following code and click "start" and it works; nothing else is needed.

This simplicity we currently have with Harbour works perfectly.

o := WDO_MYSQL():New( 'localhost', 'root', '', 'dbharbour', 3306 )
	
IF ! empty( hRes := o:Query( 'select * from sellers' ) )
	
     aData := o:FetchAll( hRes )
	
ENDIF

If a native DLL ever fails, it will be because the DLL is not being used correctly, just as it would be on an external site.

My humble opinion, I think your idea is, honestly, to add complexity to everything…

And if we want Harbour to be a great language… perhaps we shouldn't use other external tools and languages ​​if we can do it just as well with Harbour itself, don't you agree? :D

C.

Hello Charly, You’re right — and I want to be very clear about this: I genuinely don’t care which tools people choose to use. ADO, native libraries, ODBC, services — all of these can be valid choices, depending on context.

What makes me uneasy is not the tool choice itself, but the impression that there is only one acceptable direction, and that questioning it is somehow unnecessary or even wrong.

For long-running systems, I think it is healthy to explicitly name the doubts that come with any architectural choice. Not to block progress, but to make decisions conscious and transparent.

There are also other dimensions to consider besides technical correctness — especially personal learning, long-term maintainability, and individual growth. When those factors are taken into account, alternative approaches can make a lot of sense, even if they are not the simplest path in the short term.

So this is not about replacing one “right” solution with another. It’s about acknowledging that multiple paths can coexist, and that choosing one does not invalidate the others — especially when learning and future relevance are part of the equation. Best regards, Otto

La pregunta más directa es usar un servidor harbour o mod_harbour que atienda solicitudes API REST o webSocket y así separar el FrontEnd del Backend