Http.sys not start on 15.3

[max7575]

I have an application type http.sys on windows server 2022 core version. With IW15.2.69 everything works well but after rebulit the project with 15.3 the application don't start. When I try to start the service, after a few second an error raise. The error message is: "The service not respond at control function". I check the windows log and the error details is:

"The file could not be accessed for one of the following reasons:
 There is a problem with the network connection, the disk where the
 files or drivers storage installed on your computer or the disk is missing.
 The Project1.exe program was closed due to the error."


The project files are stored in the main disk of the server.

I also tried to create an empty project but the result is the same.

How can I fix?

Thanks

[Alexandre Machado]

Check the folder where the Project1.exe file is for a log file. IntraWeb creates a log file when things like that happen and the application can't start.

[max7575]

Check the folder where the Project1.exe file is for a log file. IntraWeb creates a log file when things like that happen and the application can't start.

I checked but there is no log file in the folder.

[Alexandre Machado]

Can you please create an empty Http.sys application from scratch, build and install it? See how it behaves

[max7575]

I done. The behavior is the same as I described in the first post.

[Jose Nilton Pace]

Hi, verify in your DPR:

Code:

program MyProgram;

uses
  FastMM4,
  IWRtlFix,
  IWJclDebug,
  IWJclStackTrace,
  IWStartHSys,

  ...;

{$R *.res}

begin
{$IFDEF DEBUG}
  TIWStartHSys.Execute(True);
{$ELSE}
  TIWStartHSys.Execute(False);
{$ENDIF}
end.

You need the fastmm dll, inside iw installation folder you have it. Mine is located:
C:\Program Files (x86)\IntraWeb 15\FastMM4\FullDebugMode DLL\Precompiled

Build your application in DEBUG mode and execute. Don't install. Whats happen ?
Share all infomation and prints, please.

[max7575]

I put the file FastMM_FullDebugMode64.dll in the folder application. The result is always the same.
If I compile in debug mode and I lunch the application by command line of cmd of windows (windows is the core version) nothing happen. If I compile in release mode and start it as service the error is the same.

In both cases in the windows log the error is: error 100, "The file could not be accessed.....".

I tried to copy also the file borlandmm.dll from intraweb folder but nothing change.

[Alexandre Machado]

Try to run it as SA, not service. What happens?

Also, check the windows system log (not only the application log). It should have an entry showing which file is that

[Alexandre Machado]

I would suggest a couple of tests:

1- Run it as SA (with the visible main window) as administrator. See what you get

2- Run it in another computer, first as SA and then as a service. See what happens

[max7575]

I made some tests:

1 - In SA mode nothing happen, when I run the application nothing appear on the screen.
2 - In another computer (with windows 11, not windows server) is all ok.

I tried to compile a new project with Indy and all works well also in windows server.

This is the windows server log detail of the error:

PS C:\Users\Administrator> get-eventlog application | where index -eq 53576 | format-list *


EventID : 1005
MachineName : SERVER-MAIN
Data : {}
Index : 53576
Category : Eventi di arresto anomalo dell'applicazione
CategoryNumber : 100
EntryType : Error
Message : Impossibile accedere al file per uno dei motivi seguenti:
Si è verificato un problema relativo alla connessione di rete, al disco in cui è archiviato il
file o ai driver
di archiviazione installati nel computer oppure il disco è assente.
Il programma Project1.exe è stato chiuso a causa dell'errore.

Programma: Project1.exe
File:

Il valore dell'errore è indicato nella sezione Dati aggiuntivi.
Azione utente
1. Aprire nuovamente il file.
Potrebbe trattarsi di un problema temporaneo che si risolverà automaticamente rieseguendo il
programma.
2.
Se il file risulta comunque non accessibile e:
- Si trova in rete,
è necessario che l'amministratore della rete verifichi la presenza di eventuali problemi di rete
e che sia possibile contattare il server.
- Si trova in un disco rimovibile, ad esempio un disco floppy o un CD, verificare che il disco
sia inserito correttamente nel computer.
3. Controllare e ripristinare il file system eseguendo CHKDSK. Per eseguire CHKDSK, fare clic sul
pulsante Start, scegliere Esegui, digitare CMD, quindi scegliere OK. Al prompt dei comandi,
digitare CHKDSK /F, quindi premere INVIO.
4. Se il problema persiste, ripristinare il file da una copia di backup.
5. Determinare se è possibile aprire altri file nello stesso disco. Se non è possibile, il disco
potrebbe essere danneggiato. Se si tratta di un disco rigido, contattare l'amministratore o il
fornitore dell'hardware
del computer per ottenere assistenza.

Dati aggiuntivi
Valore errore: 00000000
Tipo disco: 0
Source : Application Error
ReplacementStrings : {, Project1.exe, 00000000, 0}
InstanceId : 3221226477
TimeGenerated : 21/04/2023 16:30:34
TimeWritten : 21/04/2023 16:30:34
UserName :
Site :
Container :

Later I will try in another computer with windows server.
I will post the result.