| View previous topic :: View next topic |
| Author |
Message |
PageGateNewb
Joined: 01 Feb 2012
Posts: 6
Location: Lansing, MI
|
 Posted: Wed Feb 01, 2012 1:47 pm Post subject: Version 5.0.0.92 |
 |
|
| We are currently running version 5.0.0.92. Do you recommend upgrade to version 5.0.0.95 ?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Feb 01, 2012 1:51 pm Post subject: |
|
|
| Yes, especially if you're using Windows Vista, 7, Server 2003 or Server 2008. |
|
| Back to top |
|
PageGateNewb
Joined: 01 Feb 2012
Posts: 6
Location: Lansing, MI
|
| Posted: Wed Feb 01, 2012 2:24 pm Post subject: Random restarts |
|
|
So is there any point in me asking about seemingly random application stops and restarts before we upgrade? For example, at present, we will see all services stop and then restart about 12 seconds later multiple times per day. Here's an example in the logs from 2:57am this morning:
2/1/2012 2:57:13 AM PGSched Message scheduled. Recipient: *filtered*
2/1/2012 2:57:20 AM PGDial10 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:21 AM Log ping...
2/1/2012 2:57:22 AM PGDial16 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:22 AM PGDial16 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:23 AM PGDial16 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:24 AM PGDial16 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:23 AM Asking PGSched service to start
2/1/2012 2:57:24 AM PGDial16 SUCCESSFUL Stn:2 To:*filtered*
2/1/2012 2:57:24 AM PGDial10 SUCCESSFUL Stn:2 To:*filtered*
2/1/2012 2:57:25 AM PGDial16 SUCCESSFUL Stn:2 To:*filtered*
2/1/2012 2:57:25 AM PGSched start detected
2/1/2012 2:57:29 AM PGDial10 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:28 AM Module paused
2/1/2012 2:57:28 AM Running cleanup routine
2/1/2012 2:57:34 AM PGDial10 SUCCESSFUL Stn:2 To: *filtered*
2/1/2012 2:57:52 AM Time synchronized with scheduler
2/1/2012 2:57:52 AM Asking PGGAscii service to start
2/1/2012 2:57:54 AM Asking PGGMail service to start
2/1/2012 2:57:55 AM Asking PGGWeb service to start
2/1/2012 2:57:57 AM Asking PGGTap service to start
2/1/2012 2:57:58 AM Asking Connector1 service to start
2/1/2012 2:58:00 AM Asking Connector2 service to start
2/1/2012 2:58:01 AM Asking Connector3 service to start
2/1/2012 2:58:02 AM PGSched Message scheduled. Recipient: 40774 from:
2/1/2012 2:58:03 AM Asking Connector4 service to start
2/1/2012 2:58:04 AM Asking Connector5 service to start
2/1/2012 2:58:06 AM Asking Connector6 service to start
2/1/2012 2:58:07 AM Asking Connector7 service to start
2/1/2012 2:58:09 AM Asking Connector8 service to start
2/1/2012 2:58:11 AM Asking Connector9 service to start
2/1/2012 2:58:12 AM Asking Connector10 service to start
2/1/2012 2:58:14 AM Asking Connector11 service to start
2/1/2012 2:58:15 AM Asking Connector12 service to start
2/1/2012 2:58:17 AM Asking Connector13 service to start
2/1/2012 2:58:18 AM Asking Connector14 service to start
2/1/2012 2:58:20 AM Asking Connector15 service to start
2/1/2012 2:58:21 AM Asking Connector16 service to start
2/1/2012 2:58:23 AM Asking PGMailServer service to start
2/1/2012 2:58:27 AM PGGAscii start detected
2/1/2012 2:58:27 AM PGGMail start detected
2/1/2012 2:58:27 AM PGGWeb start detected
2/1/2012 2:58:27 AM PGGTap start detected
2/1/2012 2:58:27 AM Connector1 start detected
2/1/2012 2:58:27 AM Connector2 start detected
2/1/2012 2:58:27 AM Connector3 start detected
2/1/2012 2:58:27 AM Connector4 start detected
2/1/2012 2:58:27 AM Connector5 start detected
2/1/2012 2:58:27 AM Connector6 start detected
2/1/2012 2:58:27 AM Connector7 start detected
2/1/2012 2:58:27 AM Connector8 start detected
2/1/2012 2:58:27 AM Connector9 start detected
2/1/2012 2:58:27 AM Connector10 start detected
2/1/2012 2:58:27 AM Connector11 start detected
2/1/2012 2:58:27 AM Connector12 start detected
2/1/2012 2:58:27 AM Connector13 start detected
2/1/2012 2:58:27 AM Connector14 start detected
2/1/2012 2:58:27 AM Connector15 start detected
2/1/2012 2:58:27 AM Connector16 start detected
2/1/2012 2:58:27 AM PGMailServer start detected
According to the PC event log:
2:57:16 PGSched is stopped
2:57:25 PGSched is started
2:57:32-41 All PageGate connector services (20) are stopped.
2:57:54-2:58:22 All 20 connectors are started.
Is this normal? Is there any why to know WHY this happened?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Feb 01, 2012 2:28 pm Post subject: |
|
|
If you would, please email all of the .log files in the c:\pagegatedata\logs\ folder as well as the Windows Event Viewer Application and System logs to support at notepage dot com
I don't know why that would happen right off the top of my head but hopefully there will be some indication as to what the problem is in the logs. |
|
| Back to top |
|
PageGateNewb
Joined: 01 Feb 2012
Posts: 6
Location: Lansing, MI
|
| Posted: Wed Feb 01, 2012 2:33 pm Post subject: Database Error |
|
|
I think I found it. In the PGSched log, I found this:
2/1/2012 2:57:13 AM Message scheduled. Recipient: *filtered*
2/1/2012 2:57:16 AM Program Halted. Database error: 3167 Record is deleted. in Procedure: sched_dialers
2/1/2012 2:57:16 AM Restarting
2/1/2012 2:57:16 AM Module Stopped
2/1/2012 2:57:25 AM Module Started
2/1/2012 2:57:26 AM Running cleanup routine
2/1/2012 2:57:26 AM Waiting for server module to pause
2/1/2012 2:57:30 AM Server module paused
2/1/2012 2:57:30 AM Waiting for connectors to pause
2/1/2012 2:57:42 AM Connectors paused
2/1/2012 2:57:42 AM Waiting for interfaces to pause
2/1/2012 2:57:42 AM Interfaces paused
2/1/2012 2:57:42 AM Attempting to compact database
2/1/2012 2:57:47 AM Database in use, unable to compact
2/1/2012 2:57:47 AM Trimming log files
2/1/2012 2:57:47 AM Checking database for null values
2/1/2012 2:57:48 AM Checking database for invalid group entries and dups
2/1/2012 2:57:49 AM Updating archive database
2/1/2012 2:57:49 AM Creating recipients archive file
2/1/2012 2:57:49 AM 2925 recipient records archived
2/1/2012 2:57:49 AM Creating group headers archive file
2/1/2012 2:57:50 AM 155 group header records archived
2/1/2012 2:57:50 AM Creating group members archive file
2/1/2012 2:57:50 AM 3840 group member records archived
2/1/2012 2:57:50 AM Creating carrier archive file
2/1/2012 2:57:50 AM 15 carrier records archived
2/1/2012 2:57:50 AM Creating messages archive file
2/1/2012 2:57:50 AM 0 message records archived
2/1/2012 2:57:50 AM Removing old messages from database
2/1/2012 2:57:50 AM Removing old files from badmsg folder
2/1/2012 2:57:51 AM Checking for invalid mailboxes
2/1/2012 2:57:51 AM Resetting database flags
2/1/2012 2:57:51 AM Module resumed
Looks like a database error, and then it failed to compact the database. So should the system be manually shut down, compacted, and restarted?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Feb 01, 2012 2:42 pm Post subject: |
|
|
| Yes. If that doesn't work, you'll want to open the database in access and purge the contents of the messages table, then do a manual compact and repair. |
|
| Back to top |
|
PageGateNewb
Joined: 01 Feb 2012
Posts: 6
Location: Lansing, MI
|
| Posted: Wed Feb 01, 2012 3:02 pm Post subject: Database repair |
|
|
| I have been warned if we open the database in Access, clear the messages table, compact and repair, that we will lose data required for reporting. Is this the case?
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Feb 01, 2012 3:09 pm Post subject: |
|
|
| Ah... yes, that's true. If you do purge the messages table, the data won't be available for reporting. You don't necessarily have to clear the messages table, though. If doing the PageGate Admin database repair doesn't work, open the database in Access and do the Access "Compact and Repair" function. It should remove the ghost record causing the database error without having to purge the table. I'd recommended purging the table initially just to be on the safe side of guaranteeing that the error would go away. |
|
| Back to top |
|
|
