I’ll putting aside the obvious red flag for a second. If you’re running a stand alone FactoryPMI installation it will be obvious on all client machines if the Gateway is down. The clients will revert to an overlay screen that periodically attempts to reconnect. Eventually the session expires and the FactoryPMI Client reverts to the login screen.
You can create an Action Item in FactorySQL that runs an SQL query against your SQLTags datasource. You can then Alert on that item, which can be configured to send email(s) (text message) and log to the database. Colby, Carl, Travis, Bobby - any ideas on the “best” one to use?
Could you elaborate on the thread locking problem and why a memory upgrade will fix it? Please check the FactoryPMI logs for critical exceptions.
[quote=“mrtweaver”]Until we receive the memory upgrade for our server, currently it resides at 2gig we are taking it to 4gig, our prject occasionally shuts down on a thread locked issue. In an effort to make all mgmt aware that something has taken down the FPMI service I was wondering if and how one could use the getSystemFlags or something like that but use it in FSQL. FSQL does not shut down and continues to function properly so if I had someway to monitor the gateway of FPMI in the FSQL program then send an alert message out it would be great. I seem to recall such a thread posted before but could not quite locate it and maybe it might be much easier now with the getSystemFlags.
Thanks and have a great day.[/quote]