2 replies to this topic

[Jim]

Hello,

I'm having an issue on a customer site and wanted to ping the forum to see if it rang any bells / any similar experiences - insights welcome. The site in question is running version 5.5 on Windows Server 2003. The administrator at this site restarted the ProIV Service recently to clear some runaway users that were unkillable from within the ProIV Service Manager. The service appeared to restart correctly, but when users tried to connect using the Windows Client they received the 'Host Closed Connection' dialog box. The only way to get around this was another service restart. In itself this does not appear to be worrying, but we always like to keep tabs on any unusual behaviour in the production environment. The ProIV Service could also not be connected to from the server itself, using a local ProIV Client, so we are eliminating network issues as a possible cause. Has anyone previously seen similar behaviour or should this just be written off as a one-off, that the service appeared to start but that something internal didn't start up properly? It's a difficult environment to turn on trace / try to reproduce in.

On a related note, to clear down these occasional runaway sessions without manual intervention, we are considering using the Windows Scheduler to schedule a weekly 'NET STOP/START "PROIV NT Server"' when the active users are logged out - I was under the impression that even the best written software (ahem, and ProIV!) benefits from the occasional restart to clear the cobwebs / leaks - any opinions? Thanks.

Regards,
Jim.

[Fred Marker]

We are running 5.5 rev 543 on Windows 2003 Server and have experienced a similar problem, very intermittently, where ProIV kernel did not fully start after a server restart. No errors, logs or other evidence to explain the reason/cause.

Many years and ProIV versions ago, we did run a weekly scheduled restart of our ProIV server which seemed to help keep ProIV running smoothly. Since abandoning that practice, our ProIV server has been stable. There have been a few times when only a server restart would correct a ProIV kernel problem.

[Jim]

We are running 5.5 rev 543 on Windows 2003 Server and have experienced a similar problem, very intermittently, where ProIV kernel did not fully start after a server restart. No errors, logs or other evidence to explain the reason/cause.

Many years and ProIV versions ago, we did run a weekly scheduled restart of our ProIV server which seemed to help keep ProIV running smoothly. Since abandoning that practice, our ProIV server has been stable. There have been a few times when only a server restart would correct a ProIV kernel problem.

Thanks for the reply Fred.