Search found 7 matches

Thanks for the quick answer. That is what I needed to know.

Don

Is there any special process for updating to 5.0.9 from 5.0.1 other than the usual closing all clients and backing up the database as a precaution?

I am guessing that the new setup file is executed and everything is updated automatically. If so, it should be easy - right?

Thanks,
Don

Yes, it is all on the same computer running Server 2003.

Running PageGate 5.0.0.1 (will be doing minor version upgrade) with no problems until last Friday night.

At 9:00:27 PM, the PageGate program stopped. The log entry from PageGate.log is: 1/4/2008 09:00:27 PM Program Halted. Database error: 3046 Could not save; currently locked by another user, in Procedure: repeat_timer.

I was unable to find any pertinent entries in Windows event log and have really no idea as to what caused this and who/what the other user was.

The program did not try and restart. Can you explain what went wrong and what we need to do to keep it from happening again?

Thanks in advance for your help.
Don Sebastianelli
Warren County Dept of Emergency Services

I just upgraded from V4 to V5. The following are some points you may be interested in.

1. The instructions don't tell one to remove any security before updating. I didn't and could not log in to V5. Had to uninstall V5, reinstall V4, clear security, uninstall V4 again, and reinstall V5. Then all worked.

2. The arrow for context help in PGAdmin says it cannot find the file PG.HLP. The only help file I could find was pg.chm.

There are several other small points that I haven't been able to recreate consistently yet. I will forward them when I can.

Don

The log has been sent.

Concerning #2, sorry for the confusion. We do not want the GUI Client to be able to change to the network list. The network list has more entries and that is what could cause confusion of the operator. The manual indicates a switch to limit display to the local list only. That is what we would like to do.

Concerning #3, the reason for the ability to change the name is primarily sorting in the Admin program. If a persons name changes, the entry would have to be deleted and reentered or left with the old name which would be hard to remember over time.

Thanks again.
Don

Being a new user, hopefully some of these issues are easily fixed.

1. We have one dialer. We send weather alerts to local Emergency Service agencies via alpha paging and SMS. The old program we used would take maybe 15 minutes to send all messages via modem (SMS not available). The first time we used PageGate it took 27 minutes to send pages and SMS. Not a good start for a much more expensive program. First off, the dialer sends modem pages first then SMS. This makes no sense since SMS can be sent much more rapidly. In our case the SMS messages would have been gone in 1 1/2 minutes based upon the dialer log, but instead had to wait 25 minutes. The most messages delivered in the shortest time is our goal. How does one set PageGate to send fast messages first and slow messages last?

2. Concerning the GUI Client, we have created a local recipent list to limit what certain terminals can see. There is no option called "Local Recipient List Only" as stated in the manual so the user can switch to the network list at will. Not a major issue, but it could cause confusion among users (that is why we created the list).

3. The recipient, carrier, and group name fields cannot be changed short of deleting the entry and reentering it. This is not fun especially when group memberships are involved. Why not use the index number in the database to track it (don't sort by it though) and allow the name field to be changed or even dropped altogether? The full name field would serve user purposes.

4. Our users that have a cell phone can be contacted by page(modem) or SMS. We had to enter each in the Admin program. Since we did not want to confuse our senders in which entry to pick when sending a message to these users, we created a group for these individuals and put their pager and SMS entries in the group. We then hid the individual entries from the GUI Client prior to creating the local list in #2 above. This seemed to work until we tried to send a me ...

Author	Message
Topic: Updating PageGate 5.0.1 to 5.0.9
wcdes Replies: 2 Views: 7051	Forum: PageGate Support Posted: Wed Nov 04, 2009 7:07 am Subject: Updating PageGate 5.0.1 to 5.0.9
wcdes Replies: 2 Views: 7051	Thanks for the quick answer. That is what I needed to know. Don
Topic: Updating PageGate 5.0.1 to 5.0.9
wcdes Replies: 2 Views: 7051	Forum: PageGate Support Posted: Tue Nov 03, 2009 1:45 pm Subject: Updating PageGate 5.0.1 to 5.0.9
wcdes Replies: 2 Views: 7051	Is there any special process for updating to 5.0.9 from 5.0.1 other than the usual closing all clients and backing up the database as a precaution? I am guessing that the new setup file is executed and everything is updated automatically. If so, it should be easy - right? Thanks, Don
Topic: Pagegate Crash Error Message
wcdes Replies: 3 Views: 8917	Forum: PageGate Support Posted: Mon Jan 07, 2008 10:21 am Subject: Pagegate Crash Error Message
wcdes Replies: 3 Views: 8917	Yes, it is all on the same computer running Server 2003.
Topic: Pagegate Crash Error Message
wcdes Replies: 3 Views: 8917	Forum: PageGate Support Posted: Mon Jan 07, 2008 10:12 am Subject: Pagegate Crash Error Message
wcdes Replies: 3 Views: 8917	Running PageGate 5.0.0.1 (will be doing minor version upgrade) with no problems until last Friday night. At 9:00:27 PM, the PageGate program stopped. The log entry from PageGate.log is: 1/4/2008 09:00:27 PM Program Halted. Database error: 3046 Could not save; currently locked by another user, in Procedure: repeat_timer. I was unable to find any pertinent entries in Windows event log and have really no idea as to what caused this and who/what the other user was. The program did not try and restart. Can you explain what went wrong and what we need to do to keep it from happening again? Thanks in advance for your help. Don Sebastianelli Warren County Dept of Emergency Services
Topic: Version 5 Issues
wcdes Replies: 3 Views: 8887	Forum: PageGate Support Posted: Wed Jul 11, 2007 10:49 am Subject: Version 5 Issues
wcdes Replies: 3 Views: 8887	I just upgraded from V4 to V5. The following are some points you may be interested in. 1. The instructions don't tell one to remove any security before updating. I didn't and could not log in to V5. Had to uninstall V5, reinstall V4, clear security, uninstall V4 again, and reinstall V5. Then all worked. 2. The arrow for context help in PGAdmin says it cannot find the file PG.HLP. The only help file I could find was pg.chm. There are several other small points that I haven't been able to recreate consistently yet. I will forward them when I can. Don
Topic: PageGate Issues
wcdes Replies: 3 Views: 8587	Forum: PageGate Support Posted: Wed May 02, 2007 2:30 pm Subject: PageGate Issues
wcdes Replies: 3 Views: 8587	The log has been sent. Concerning #2, sorry for the confusion. We do not want the GUI Client to be able to change to the network list. The network list has more entries and that is what could cause confusion of the operator. The manual indicates a switch to limit display to the local list only. That is what we would like to do. Concerning #3, the reason for the ability to change the name is primarily sorting in the Admin program. If a persons name changes, the entry would have to be deleted and reentered or left with the old name which would be hard to remember over time. Thanks again. Don
Topic: PageGate Issues
wcdes Replies: 3 Views: 8587	Forum: PageGate Support Posted: Wed May 02, 2007 12:55 pm Subject: PageGate Issues
wcdes Replies: 3 Views: 8587	Being a new user, hopefully some of these issues are easily fixed. 1. We have one dialer. We send weather alerts to local Emergency Service agencies via alpha paging and SMS. The old program we used would take maybe 15 minutes to send all messages via modem (SMS not available). The first time we used PageGate it took 27 minutes to send pages and SMS. Not a good start for a much more expensive program. First off, the dialer sends modem pages first then SMS. This makes no sense since SMS can be sent much more rapidly. In our case the SMS messages would have been gone in 1 1/2 minutes based upon the dialer log, but instead had to wait 25 minutes. The most messages delivered in the shortest time is our goal. How does one set PageGate to send fast messages first and slow messages last? 2. Concerning the GUI Client, we have created a local recipent list to limit what certain terminals can see. There is no option called "Local Recipient List Only" as stated in the manual so the user can switch to the network list at will. Not a major issue, but it could cause confusion among users (that is why we created the list). 3. The recipient, carrier, and group name fields cannot be changed short of deleting the entry and reentering it. This is not fun especially when group memberships are involved. Why not use the index number in the database to track it (don't sort by it though) and allow the name field to be changed or even dropped altogether? The full name field would serve user purposes. 4. Our users that have a cell phone can be contacted by page(modem) or SMS. We had to enter each in the Admin program. Since we did not want to confuse our senders in which entry to pick when sending a message to these users, we created a group for these individuals and put their pager and SMS entries in the group. We then hid the individual entries from the GUI Client prior to creating the local list in #2 above. This seemed to work until we tried to send a me ...