NTWS sometimes exits without error! Help!

[ccordes]

PMFJI

Are you using messagebox to take care of messages?
Do you have messagebox set to time out and use the default button?
Are you compiled with debug turned on?

ABFILE has a bunch of Asserts for file errors.
In particular -
     ASSERT(FALSE, 'You are calling CLOSE(' & NAME(SELF.File) & ') instead of FileManager.Close()')

This pops up a message and the default button is - GPF.

You will get no message from the server - it just seems to disappear.

HTH
Chris

[Jeffrey Kuijt]

Hi Chris,

> Are you using messagebox to take care of messages?
Yes, ALL messages are saved in a TPS file.
So when NTWS is starting, when NTWS is closing (normally), when user logs in, when user logs out.
And all other (error) messages.

> Do you have messagebox set to time out and use the default button?
All messages are completely hidden and immediately written to the log file (tps).
Yes, use the default button.

Are you compiled with debug turned on?
No.

Best regards
Jeffrey

[ccordes]

So far that has been the only reason I have found for what you are describing.
I do not recall if the messagebox reports the error or not because the default button causes a halt.
I'll be interested to see what you find.

chris

[Jeffrey Kuijt]

Hi Chris,

I have tested that messages which halt (for example "Invalid Record Declaration") ARE logged in my tps file with CS MessageBox.
But I think a GPF is another type of "beast". 

Best regards
Jeffrey

[Jeffrey Kuijt]

Hi Bruce,

Just got a call from my customer:
NTWS "disappeared" again, this time it's the test version I sent them, bound to 1 core.
So that's also not the solution.

I mentioned earlier that they load the NTWS exe from a Synology NAS with a drive mapping, for example:
H:\APPLICATION\app.exe

I think that the network connection between the Windows 2003 Server and the Synology NAS is sometimes (for just a second or so) broken.
And if that happens, boom, the NTWS exe is shut down (by Windows I think).

So I think it's important to install the NTWS exe as a service so that it can restart if it "disappears"...

Best regards
Jeffrey

[Bruce]

while I agree with your assessment - I'm not sure about the last part. Restarting programs has nothing to do with them being a service. Just write a program to monitor the program, and start it if it's not running.

[ccordes]

Jeffrey,

As a test, you could move the server's folder from the NAS drive to a local drive and run it. Depending on how often this happens, you would have more information on the problem pretty quickly.
The network connection outage sounds like a possible trigger if the server were trying to access a file and got the file not found - abort message. If that's the case, restarting the server doesn't solve the real problem - a wonky network connection. The end user's session still gets trashed and you then have to deal with half a transaction somewhere.

Chris

[Jeffrey Kuijt]

Hi Chris,

Thanks.
The only problem is that their data must stay on the NAS.
So I can only move the NTWS exe to the local disk of the Windows 2003 Server, but that won't help if the network connection is lost with the data on the NAS.

Best regards
Jeffrey

[Bruce]

>> So I can only move the NTWS exe to the local disk of the Windows 2003 Server, but that won't help if the network connection is lost with the data on the NAS.

it might. certainly worth a try. especially if the files are TPS.

cheers
Bruce