PageGate Client ver 5 fails to show page status.

[keiths]

Our PageGate client programs now do not show page status. When initiating a page, the Send button will respond, but the pending, sent, and bad indicators do not show the page status. The page does send successfully, but no status is indicated. Also, the date/time indicator turns 'red' as the page is apparently being sent. Any thoughts as to why this has occurred. Our PageGate system has been in service since 2004, so this is not a new installation. Any assistance is certainly appreciated. Thanks!

[Tech Support]

That's really odd, especially since this isn't a new installation. If you look on the server, specifically in the PageGate Scheduler log, do you see multiple instances of the cleanup routine running or the scheduler going offline? Also, if you would, please email all of the .log files from the c:\pagegatedata\logs\ directory to support at notepage dot com so I can have a look at things.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[OzCom]

Did you say 2004? Is this a PageGate v4 or PageGate v5 installation?

_________________
Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate

[keiths]

Thanks for the reply. We're running version 5. As I had already left for the day, I will forward the log files first thing Monday morning. Thanks.

[keiths]

I did check the PGSched log and no new entries since 05/2010.

[OzCom]

RE: "I did check the PGSched log and no new entries since 05/2010."

Good clue - Sounds like there may be some issues with your installation and file path

Your PGSched log, by default, resides on the PGServer machine at c:/pagegatedata/logs

Whhat file location is your GUIClient pointing at?

_________________
Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate

[keiths]

The clients point to a network drive location where the PageGate DB resides. I can view PageGate's MDB file on this network drive with no problems as this is where I can go to verify if a page was successfully sent. Are there thoughts that there may be a problem with the PageGate folder information at this network drive location?

[Tech Support]

Well, sort of. Maybe. The thing is, if your Scheduler log hasn't been updated since mid-2010, something is very, very wrong. Well, either that or you disabled the logging in PageGate.

If you would, open the PageGate Admin on the Server itself. What does the Server Copy of the Admin say that the Logging directory is?

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[keiths]

C:\PageGateData\Logs\ is the location.
Here is log information from over the weekend:
02/11/2011 00:00:01 Module Stopped
02/11/2011 00:00:07 Module Started
02/11/2011 00:00:08 Running cleanup routine
02/11/2011 00:00:30 Time synchronized with scheduler
02/11/2011 12:57:19 Message accepted. Station: 10 Recipient: keith from: keiths
02/11/2011 12:57:19 Message accepted. Station: 10 Recipient: keiths from: keiths
02/11/2011 14:49:21 Message accepted. Station: 10 Recipient: keith from: CharlieT
02/11/2011 14:49:21 Message accepted. Station: 10 Recipient: keiths from: CharlieT
02/12/2011 Module Stopped
02/12/2011 00:00:03 Module Started
02/12/2011 00:00:05 Running cleanup routine
02/12/2011 00:00:26 Time synchronized with scheduler
02/13/2011 00:00:01 Module Stopped
02/13/2011 00:00:05 Module Started
02/13/2011 00:00:07 Running cleanup routine
02/13/2011 00:00:26 Time synchronized with scheduler
02/14/2011 00:00:01 Module Stopped
02/14/2011 00:00:04 Module Started
02/14/2011 00:00:05 Running cleanup routine
02/14/2011 00:00:26 Time synchronized with scheduler

Program use over the weekend was minimal, but no errors noted. Again, the program works, it just does not show the user client the status of a sent message.

[keiths]

Here is the Scheduler Log from over the weekend:

02/11/2011 00:00:01 Initiating cleanup routines
02/11/2011 00:00:01 Module Stopped
02/11/2011 00:00:07 Module Started
02/11/2011 00:00:08 Running cleanup routine
02/11/2011 00:00:08 Waiting for server module to pause
02/11/2011 00:00:12 Server module paused
02/11/2011 00:00:12 Waiting for connectors to pause
02/11/2011 00:00:16 Connectors paused
02/11/2011 00:00:16 Waiting for interfaces to pause
02/11/2011 00:00:16 Interfaces paused
02/11/2011 00:00:16 Attempting to compact database
02/11/2011 00:00:24 Database compacted
02/11/2011 00:00:24 Trimming log files
02/11/2011 00:00:27 Checking database for null values
02/11/2011 00:00:29 Checking database for invalid group entries and dups
02/11/2011 00:00:29 Removing old messages from database
02/11/2011 00:00:29 Removing old files from badmsg folder
02/11/2011 00:00:29 Resetting database flags
02/11/2011 00:00:30 Module resumed
02/11/2011 00:35:05 Log ping...
02/11/2011 01:35:05 Log ping...
02/11/2011 02:35:05 Log ping...
02/11/2011 03:35:05 Log ping...
02/11/2011 04:35:05 Log ping...
02/11/2011 05:35:05 Log ping...
02/11/2011 06:35:05 Log ping...
02/11/2011 07:35:05 Log ping...
02/11/2011 08:35:05 Log ping...
02/11/2011 09:35:06 Log ping...
02/11/2011 10:35:05 Log ping...
02/11/2011 11:35:05 Log ping...
02/11/2011 12:35:05 Log ping...
02/11/2011 12:57:19 Message scheduled. Recipient: keith from: keiths
02/11/2011 12:57:19 Message scheduled. Recipient: keiths from: keiths
02/11/2011 13:35:05 Log ping...
02/11/2011 14:35:05 Log ping...
02/11/2011 14:49:21 Message scheduled. Recipient: keith from: CharlieT
02/11/2011 14:49:21 Message scheduled. Recipient: keiths from: CharlieT
02/11/2011 15:35:05 Log ping...
02/11/2011 16:35:05 Log ping...
02/11/2011 17:35:05 Log ping...
02/11/2011 18:35:05 Log ping...
02/11/2011 19:35:05 Log ping...
02/11/2011 20:35:05 Log ping...
02/11/2011 21:35:05 Log ping...
02/11/2011 22:35:05 Log ping...
02/11/2011 23:35:05 Log ping...
02/12/2011 Initiating cleanup routines
02/12/2011 Module Stopped
02/12/2011 00:00:03 Module Started
02/12/2011 00:00:05 Running cleanup routine
02/12/2011 00:00:05 Waiting for server module to pause
02/12/2011 00:00:09 Server module paused
02/12/2011 00:00:09 Waiting for connectors to pause
02/12/2011 00:00:17 Connectors paused
02/12/2011 00:00:17 Waiting for interfaces to pause
02/12/2011 00:00:17 Interfaces paused
02/12/2011 00:00:17 Attempting to compact database
02/12/2011 00:00:24 Database compacted
02/12/2011 00:00:24 Trimming log files
02/12/2011 00:00:24 Checking database for null values
02/12/2011 00:00:25 Checking database for invalid group entries and dups
02/12/2011 00:00:25 Removing old messages from database
02/12/2011 00:00:25 Removing old files from badmsg folder
02/12/2011 00:00:25 Resetting database flags
02/12/2011 00:00:26 Module resumed
02/12/2011 00:22:05 Log ping...
02/12/2011 01:22:05 Log ping...
02/12/2011 02:22:05 Log ping...
02/12/2011 03:22:05 Log ping...
02/12/2011 04:22:05 Log ping...
02/12/2011 05:22:05 Log ping...
02/12/2011 06:22:05 Log ping...
02/12/2011 07:22:05 Log ping...
02/12/2011 08:22:05 Log ping...
02/12/2011 09:22:05 Log ping...
02/12/2011 10:22:06 Log ping...
02/12/2011 11:22:05 Log ping...
02/12/2011 12:22:05 Log ping...
02/12/2011 13:22:05 Log ping...
02/12/2011 14:22:05 Log ping...
02/12/2011 15:22:05 Log ping...
02/12/2011 16:22:05 Log ping...
02/12/2011 17:22:05 Log ping...
02/12/2011 18:22:05 Log ping...
02/12/2011 19:22:05 Log ping...
02/12/2011 20:22:05 Log ping...
02/12/2011 21:22:05 Log ping...
02/12/2011 22:22:05 Log ping...
02/12/2011 23:22:05 Log ping...
02/13/2011 00:00:01 Initiating cleanup routines
02/13/2011 00:00:01 Module Stopped
02/13/2011 00:00:05 Module Started
02/13/2011 00:00:07 Running cleanup routine
02/13/2011 00:00:07 Waiting for server module to pause
02/13/2011 00:00:11 Server module paused
02/13/2011 00:00:11 Waiting for connectors to pause
02/13/2011 00:00:18 Connectors paused
02/13/2011 00:00:18 Waiting for interfaces to pause
02/13/2011 00:00:18 Interfaces paused
02/13/2011 00:00:18 Attempting to compact database
02/13/2011 00:00:25 Database compacted
02/13/2011 00:00:25 Trimming log files
02/13/2011 00:00:25 Checking database for null values
02/13/2011 00:00:25 Checking database for invalid group entries and dups
02/13/2011 00:00:25 Removing old messages from database
02/13/2011 00:00:26 Removing old files from badmsg folder
02/13/2011 00:00:26 Resetting database flags
02/13/2011 00:00:26 Module resumed
02/13/2011 00:22:05 Log ping...
02/13/2011 01:22:05 Log ping...
02/13/2011 02:22:05 Log ping...
02/13/2011 03:22:05 Log ping...
02/13/2011 04:22:05 Log ping...
02/13/2011 05:22:05 Log ping...
02/13/2011 06:22:05 Log ping...
02/13/2011 07:22:05 Log ping...
02/13/2011 08:22:05 Log ping...
02/13/2011 09:22:05 Log ping...
02/13/2011 10:22:05 Log ping...
02/13/2011 11:22:05 Log ping...
02/13/2011 12:22:05 Log ping...
02/13/2011 13:22:05 Log ping...
02/13/2011 14:22:05 Log ping...
02/13/2011 15:22:05 Log ping...
02/13/2011 16:22:05 Log ping...
02/13/2011 17:22:05 Log ping...
02/13/2011 18:22:05 Log ping...
02/13/2011 19:22:05 Log ping...
02/13/2011 20:22:05 Log ping...
02/13/2011 21:22:05 Log ping...
02/13/2011 22:22:05 Log ping...
02/13/2011 23:22:05 Log ping...
02/14/2011 00:00:01 Initiating cleanup routines
02/14/2011 00:00:01 Module Stopped
02/14/2011 00:00:04 Module Started
02/14/2011 00:00:05 Running cleanup routine
02/14/2011 00:00:05 Waiting for server module to pause
02/14/2011 00:00:09 Server module paused
02/14/2011 00:00:09 Waiting for connectors to pause
02/14/2011 00:00:17 Connectors paused
02/14/2011 00:00:17 Waiting for interfaces to pause
02/14/2011 00:00:17 Interfaces paused
02/14/2011 00:00:17 Attempting to compact database
02/14/2011 00:00:24 Database compacted
02/14/2011 00:00:24 Trimming log files
02/14/2011 00:00:24 Checking database for null values
02/14/2011 00:00:25 Checking database for invalid group entries and dups
02/14/2011 00:00:25 Removing old messages from database
02/14/2011 00:00:25 Removing old files from badmsg folder
02/14/2011 00:00:25 Resetting database flags
02/14/2011 00:00:26 Module resumed
02/14/2011 00:55:05 Log ping...
02/14/2011 01:55:05 Log ping...
02/14/2011 02:55:05 Log ping...
02/14/2011 03:55:05 Log ping...
02/14/2011 04:55:05 Log ping...
02/14/2011 05:55:05 Log ping...
02/14/2011 06:55:05 Log ping...
02/14/2011 07:55:05 Log ping...

[Tech Support]

Okay, that looks more like what we'd expect. Though, if I'm reading this correctly, no messages were sent out at all on the 12th or 13th, correct?

As for the client not showing why messages are cleared, it should be. We can see from the scheduler log that Pagegate itself, the server, isn't going offline unexpectedly. It's staying online and waiting for data and when it receives a message, it's processing it.

So, my question is... on the client, does it ever show the date/time going red, do you get any errors regarding the scheduler that pop up or does the client just... hold the message in pending until you close and re-open it?

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[keiths]

That's correct, no pages were generated on the 12th or 13th.
After opening up a client, yes, the day/time indicator does change to red, less than a minute after opening up the client and connecting to the DB server.
No errors are generated while a client program is active and thus far, any pages initiated, are sent successfully, even though the day/time indicator is the color red or not.
Question: Where do the client program page status indicators originate their information and since the day/time indicator changing to red has no apparent bearing on a page being successfully sent, where is this status information being generated from?...The client's local root program files or from the PageGate server's DB network folder?
Thanks!

[keiths]

To clear this problem, I elected to move the PageGate server from its previous WinXP to a Win7 PC and relocated the database from its previous network location to the Win7 PC. Backup DB copies are auto-created every evening. Now all PageClients access the DB via a shared configuration with the Win7 PC. Thanks for all your inputs on this original trouble case!