Search found 2 matches

Thanks for the reply. I solved the problem with the delay by moving the server and database to a 2k3 dedicated server. Now everything has been up and running without any downtime (used to restart the server every few days).

Unfortunately it seems like the video refresh problem is not so easily solved eh? (closing the program is very easy, but to the end-user it's an unnecessary step).

Thanks for all your help,
Javier Rodriguez
VCHCA IT

I have recently installed PageGate v5 in our network and have run into some issues. I'm hoping someone here will be able to help me or point me in the right direction.

Server is running on XP machine with the database stored on a Novell cluster. PageGate clients connect to the database through a mapped drive. There are two hospitals each experiencing a different issue, both issues are preventing the paging staff from fully embracing the software.

Hospital 1 is where the PageGate server is physically located. We have a lot of recipients on the list with 40 characters (max allowed). After an hour or two the recipients list will shift to the left. The beginning character of each name on the list will be missing, then the next. Eventually some of the names will completely disappear from the list (an empty space where they should be). We can still click on the space where the recipient is and page them, but this is not good when paging codes or other emergencies. If we close and reopen the client, the names come back. Is there a way to prevent this from happening? This is a 24-hour paging office, no downtime is the goal.

Hospital 2 is located in a different city but uses the same acecss method as Hospital 1. The problem we're running into is delay. A doctor is paged, and the page sits in pending for at least .5 hours. We can navigate to the drive where the database is stored, so we know the network is functioning. There are no problems reported in PageGate, the pages will just sit pending for a half hour before they're sent.

Any help and/or suggestions is greatly appreciated.

Javier Rodriguez
VCHCA IT

Author	Message
Topic: PageGate client delays & display issues
VCHCA Replies: 3 Views: 12362	Forum: PageGate Support Posted: Fri Dec 26, 2008 1:12 pm Subject: PageGate client delays & display issues
VCHCA Replies: 3 Views: 12362	Thanks for the reply. I solved the problem with the delay by moving the server and database to a 2k3 dedicated server. Now everything has been up and running without any downtime (used to restart the server every few days). Unfortunately it seems like the video refresh problem is not so easily solved eh? (closing the program is very easy, but to the end-user it's an unnecessary step). Thanks for all your help, Javier Rodriguez VCHCA IT
Topic: PageGate client delays & display issues
VCHCA Replies: 3 Views: 12362	Forum: PageGate Support Posted: Wed Dec 10, 2008 1:55 pm Subject: PageGate client delays & display issues
VCHCA Replies: 3 Views: 12362	I have recently installed PageGate v5 in our network and have run into some issues. I'm hoping someone here will be able to help me or point me in the right direction. Server is running on XP machine with the database stored on a Novell cluster. PageGate clients connect to the database through a mapped drive. There are two hospitals each experiencing a different issue, both issues are preventing the paging staff from fully embracing the software. Hospital 1 is where the PageGate server is physically located. We have a lot of recipients on the list with 40 characters (max allowed). After an hour or two the recipients list will shift to the left. The beginning character of each name on the list will be missing, then the next. Eventually some of the names will completely disappear from the list (an empty space where they should be). We can still click on the space where the recipient is and page them, but this is not good when paging codes or other emergencies. If we close and reopen the client, the names come back. Is there a way to prevent this from happening? This is a 24-hour paging office, no downtime is the goal. Hospital 2 is located in a different city but uses the same acecss method as Hospital 1. The problem we're running into is delay. A doctor is paged, and the page sits in pending for at least .5 hours. We can navigate to the drive where the database is stored, so we know the network is functioning. There are no problems reported in PageGate, the pages will just sit pending for a half hour before they're sent. Any help and/or suggestions is greatly appreciated. Javier Rodriguez VCHCA IT