Search found 13 matches

I now see that dialers cost more. How much for additional dialers?

I will download and install the latest version. However, new information has just surfaced...

Previously, I was just looking at the logs of dialer1. Dialers 2 through 16 show an additional message which sheds a bit more light on the problem:

Module stopped. Evaluation version run for [3-5]* days.

* each dialer reports a different number here at exactly the same time. But dialer1 does not report this message.

PageGate.Exe file and product version: 4.00.0009

PageGate.Exe file and product version: 4.00.0009

The PageGate scheduler continues to queue up the incoming pager requests, but the dialer services do not always startup after the cleanup routine runs each night. This is a huge reliability issue.

All sixteen of the dialer services are stopped but the PageGate and Scheduler service remain running. The dialer services are manually individually started and then immediately die. They seem to stay running only after first stopping then starting the PageGate service. But will run only until the cleanup routine runs, when they are stopped, started, and stopped within a few seconds.

Additional information:
=> The dialers do not always synchronize the time with the scheduler [using local time].
=> The dialer services do not fail, they are automatically stopped.

The environment:
=> Microsoft Windows Server 2003 Standard Edition Service Pack 1 + several security updates
=> Dell PowerEdge 1950
=> Intel Xeon 2.8GHz
=> 2GB RAM
=> Member of an 2003 Active Directory Domain

At the risk of hijacking this thread... I will start a new thread if these issues are not related; just let me know...

We are also experiencing this problem with the dialer services (1 through 16).

The dialer services are stopped but the PageGate and Scheduler service remain running. The dialer services are manually individually started and then immediately die. They seem to stay running only after first stopping then starting the PageGate service. But will run only until the cleanup routine runs, when they are stopped, started, and stopped within a few seconds.

The scheduler queues up the incoming pager requests, but the dialers never start to send the page.

Additional information:
=> The dialers do not always synchronize the time with the scheduler [using local time].
=> The dialer services do not fail, they are automatically stopped.

The environment:
=> Microsoft Windows Server 2003 Standard Edition Service Pack 1 + several security updates
=> Dell PowerEdge 1950
=> Intel Xeon 2.8GHz
=> 2GB RAM
=> Member of an 2003 Active Directory Domain

This is still a very serious problem. Is there another way to get support for this product.

I`m not sure why, but NTFS "full control" permissions appeared to have resolved the issue. "Modify" should be sufficient.

The problem occurs with any number of workstations concurrently accessing via additional Admin, but only from the one particular workstation. That workstation was previously running a demo version as an "application" server. I uninstalled it prior to installing "additional Admin".

The default PageGate Monitor Port is TCP 10101, but can be changed via the Admin program under Logging -> Settings -> PG Monitor Port

This is a new installation...

We are running PageGate v4.0 Scheduler, GetMail, GetWeb, and dialers (1-16) on a Windows 2003 server via services using a Local user account that is in the administrators group and has the right to "run as a service".

The program files, database, and log files are all local. The database and log files [which are in a subfolder within database] folder are in a network share. The local users group has "access this computer from network", "bypass traverse checking", NTFS full control access and full control access to this share.

The Program was password protected at all four levels (Master, Admin, Report, and Client); each having a different password. Upon executing the Admin program, I expected to see the following options for each level as follows:

Master: everything - full access
Admin: recipient and group management plus reporting and viewing status (without settings and password options).
Reporting: reporting and viewing status only
Client: access client program

From the server the above is correct. I installed additional admin, monitor and client on two different WindowsXP workstations. On the first workstation the above is correct as well.

However, on the second workstation, the admin password grants master access. How is this possible? Have I misinterpreted the expected behavior?

Please advise,

--Jeff

Are you using Microsoft ISA Proxy server? If so, try installing the firewall client software that comes with ISA. When enabled, all applications on that workstation will go through your ISA server.

Yes, the protocol HTTP uses TCP port 80.

Thank you for your time.

OzCom,

Both the workstation and the server are members of the same domain. The PageGate Admin workstation is using a domain account that is in the server`s local user group.

Tech Support,

What are the exact appropriate rights that differ from what I`ve already stated?

On the server:
> local users group membership includes domain users
> local folder NTFS permissions permit "modify" access to the local users group; permissions are propagated
> local folder is shared and permits "change" access to the local users group
> local user rights assignment permits the local users group:
o ...Access this computer from the network
o ...Bypass traverse checking
> What else is there? What am I missing...?

This is a new installation...

We are running PageGate v4.0 Scheduler, GetMail, GetWeb, and dialers (1-16) on a Windows 2003 server via services using a Local user account that is in the administrators group and has the right to "run as a service".

The program files, database, and log files are all local. The database and log files [which are in a subfolder within database] folder are in a network share. The local users group has "access this computer from network", "bypass traverse checking", NTFS modify access and full control access to this share.

Sending pages works fine from the server.

I installed additional admin, monitor and client on a WindowsXP workstation. When attempting to run PG Admin accessing the database and log files via an UNC or mapped drive letter from this workstation with a user in the servers local user group, we get the following message:

PG Admin Fatal Error: Excessive database errors: 3051 The Microsoft Jet database engine cannot open the file '\\Server\PageGate\pagegate.mdb'. It is already opened exclusively by another user, or you need permission to view its data. in Procedure: main Program Halted.

From reading previous postings regarding this error, I see that this error indicates a permission issue. What have I over looked?

Please advise,

--Jeff

Author	Message
Topic: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	Forum: PageGate Support Posted: Mon Dec 18, 2006 4:33 pm Subject: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	I now see that dialers cost more. How much for additional dialers?
Topic: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	Forum: PageGate Support Posted: Mon Dec 18, 2006 11:39 am Subject: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	I will download and install the latest version. However, new information has just surfaced... Previously, I was just looking at the logs of dialer1. Dialers 2 through 16 show an additional message which sheds a bit more light on the problem: Module stopped. Evaluation version run for [3-5]* days. * each dialer reports a different number here at exactly the same time. But dialer1 does not report this message.
Topic: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	Forum: PageGate Support Posted: Mon Dec 18, 2006 11:19 am Subject: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	PageGate.Exe file and product version: 4.00.0009
Topic: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	Forum: PageGate Support Posted: Fri Dec 15, 2006 2:35 pm Subject: Dialer Services Not Restarting After CleanUp Routine.
Jebez Replies: 7 Views: 23461	The PageGate scheduler continues to queue up the incoming pager requests, but the dialer services do not always startup after the cleanup routine runs each night. This is a huge reliability issue. All sixteen of the dialer services are stopped but the PageGate and Scheduler service remain running. The dialer services are manually individually started and then immediately die. They seem to stay running only after first stopping then starting the PageGate service. But will run only until the cleanup routine runs, when they are stopped, started, and stopped within a few seconds. Additional information: => The dialers do not always synchronize the time with the scheduler [using local time]. => The dialer services do not fail, they are automatically stopped. The environment: => Microsoft Windows Server 2003 Standard Edition Service Pack 1 + several security updates => Dell PowerEdge 1950 => Intel Xeon 2.8GHz => 2GB RAM => Member of an 2003 Active Directory Domain
Topic: PageGate GetWeb not sending messages
Jebez Replies: 8 Views: 22428	Forum: PageGate Support Posted: Tue Dec 12, 2006 6:06 pm Subject: Dialers 1-16 not starting
Jebez Replies: 8 Views: 22428	At the risk of hijacking this thread... I will start a new thread if these issues are not related; just let me know... We are also experiencing this problem with the dialer services (1 through 16). The dialer services are stopped but the PageGate and Scheduler service remain running. The dialer services are manually individually started and then immediately die. They seem to stay running only after first stopping then starting the PageGate service. But will run only until the cleanup routine runs, when they are stopped, started, and stopped within a few seconds. The scheduler queues up the incoming pager requests, but the dialers never start to send the page. Additional information: => The dialers do not always synchronize the time with the scheduler [using local time]. => The dialer services do not fail, they are automatically stopped. The environment: => Microsoft Windows Server 2003 Standard Edition Service Pack 1 + several security updates => Dell PowerEdge 1950 => Intel Xeon 2.8GHz => 2GB RAM => Member of an 2003 Active Directory Domain
Topic: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	Forum: PageGate Support Posted: Wed Aug 23, 2006 4:18 pm Subject: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	This is still a very serious problem. Is there another way to get support for this product.
Topic: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	Forum: PageGate Support Posted: Thu Aug 10, 2006 9:49 am Subject: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	I`m not sure why, but NTFS "full control" permissions appeared to have resolved the issue. "Modify" should be sufficient.
Topic: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	Forum: PageGate Support Posted: Thu Aug 10, 2006 9:44 am Subject: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	The problem occurs with any number of workstations concurrently accessing via additional Admin, but only from the one particular workstation. That workstation was previously running a demo version as an "application" server. I uninstalled it prior to installing "additional Admin".
Topic: What Port is used for page monitor?
Jebez Replies: 6 Views: 21040	Forum: PageGate Support Posted: Thu Aug 03, 2006 3:14 pm Subject: What Port is used for page monitor?
Jebez Replies: 6 Views: 21040	The default PageGate Monitor Port is TCP 10101, but can be changed via the Admin program under Logging -> Settings -> PG Monitor Port
Topic: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	Forum: PageGate Support Posted: Thu Aug 03, 2006 3:09 pm Subject: Application Password Protection is Broken
Jebez Replies: 4 Views: 14354	This is a new installation... We are running PageGate v4.0 Scheduler, GetMail, GetWeb, and dialers (1-16) on a Windows 2003 server via services using a Local user account that is in the administrators group and has the right to "run as a service". The program files, database, and log files are all local. The database and log files [which are in a subfolder within database] folder are in a network share. The local users group has "access this computer from network", "bypass traverse checking", NTFS full control access and full control access to this share. The Program was password protected at all four levels (Master, Admin, Report, and Client); each having a different password. Upon executing the Admin program, I expected to see the following options for each level as follows: Master: everything - full access Admin: recipient and group management plus reporting and viewing status (without settings and password options). Reporting: reporting and viewing status only Client: access client program From the server the above is correct. I installed additional admin, monitor and client on two different WindowsXP workstations. On the first workstation the above is correct as well. However, on the second workstation, the admin password grants master access. How is this possible? Have I misinterpreted the expected behavior? Please advise, --Jeff
Topic: Proxy server
Jebez Replies: 1 Views: 9957	Forum: PageGate Support Posted: Tue Aug 01, 2006 2:08 pm Subject: Proxy server
Jebez Replies: 1 Views: 9957	Are you using Microsoft ISA Proxy server? If so, try installing the firewall client software that comes with ISA. When enabled, all applications on that workstation will go through your ISA server. Yes, the protocol HTTP uses TCP port 80.
Topic: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	Forum: PageGate Support Posted: Tue Aug 01, 2006 2:00 pm Subject: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	Thank you for your time. OzCom, Both the workstation and the server are members of the same domain. The PageGate Admin workstation is using a domain account that is in the server`s local user group. Tech Support, What are the exact appropriate rights that differ from what I`ve already stated? On the server: > local users group membership includes domain users > local folder NTFS permissions permit "modify" access to the local users group; permissions are propagated > local folder is shared and permits "change" access to the local users group > local user rights assignment permits the local users group: o ...Access this computer from the network o ...Bypass traverse checking > What else is there? What am I missing...?
Topic: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	Forum: PageGate Support Posted: Mon Jul 31, 2006 6:04 pm Subject: Excessive database errors - 3051
Jebez Replies: 4 Views: 19389	This is a new installation... We are running PageGate v4.0 Scheduler, GetMail, GetWeb, and dialers (1-16) on a Windows 2003 server via services using a Local user account that is in the administrators group and has the right to "run as a service". The program files, database, and log files are all local. The database and log files [which are in a subfolder within database] folder are in a network share. The local users group has "access this computer from network", "bypass traverse checking", NTFS modify access and full control access to this share. Sending pages works fine from the server. I installed additional admin, monitor and client on a WindowsXP workstation. When attempting to run PG Admin accessing the database and log files via an UNC or mapped drive letter from this workstation with a user in the servers local user group, we get the following message: PG Admin Fatal Error: Excessive database errors: 3051 The Microsoft Jet database engine cannot open the file '\\Server\PageGate\pagegate.mdb'. It is already opened exclusively by another user, or you need permission to view its data. in Procedure: main Program Halted. From reading previous postings regarding this error, I see that this error indicates a permission issue. What have I over looked? Please advise, --Jeff