Search found 13 matches

Thanks for all your assistance.

That worked thanks. I suspect that the person that initially installed it created a special database folder and that was affecting it's ability to find the database using its default path. I looked on our old server, and a database folder did not exist. Am I correct that the default install does NOT have a database folder?

I just have a bad feeling that this is going to present problems down the road. It seems like the path of least resistance might be to change the folder path setup and the PageGate file share on the server.

As an example, the old server was setup as E:\apps\pagegate\database, and the 'Apps' level was shared out. So when \\server\apps was mapped, the default was P:\pagegate, it would see the database folder.

The problem is now the path is C:\PageGateData\database (the PageGateData folder is shared out as 'PageGate'. Now when the drive is mapped, it is mapped as \\server\Pagegate, so when the client opens, it looks for P:\PageGate, which does not exist. I don't want to share out the whole C drive (and would have to rename the PageGateData folder to PageGate anyhow.

My concern is that renaming a folder path will break untold things, unless you can guide me through this. I notice in the PageGate Admin, there are multiple paths in the Programs > Settings tab. What else do I need to change? Anything manually in the registry?

I am thinking about changing the database path to C:\NotePage\PageGate\Database, then when I map the NotePage folder, the P:\PageGate path will be valid at that point.

Version 7.0. Running on Windows Server 2012 R2 Standard.

I entered the new path in regedit as an admin. After I made the change, I closed regedit and opened it again to confirm the correct path was there. Then I logged in as a standard user account, and it shows the old path when I try to launch the client. I logged back into the admin account and checked the registry and it reverted to the old path.

On my Windows profile, in the PageGate client setup, I set a default path of P:\database, but when a new user logs in to Windows, it reverts to P:\PageGate for their profile. I did select 'Use these setting for all local users' under my initial profile. How do I fix this?

It's working now. Thanks for your assistance.

I have confirmed the GetAscii directory path is correct. It wasn't enabled though, so I enabled it. GetAscii was checked under the 'Run on this Server' section. I restarted the server and verified that the GetAscii Windows service was running, and tried the sendpage32 command again and nothing is happening. The Interfaces > GetAscii log is showing nothing when I run the .bat file. Am I doing something wrong with my command line? Using the command prompt, I tried manually typing 'sendpage32.exe <recipient> <sender> "message..." and hit enter. The recipient is the 'Recipient' name. For the sender, I presume you can type anything in there? If not, what in PageGate are you supposed to use as sender? Thanks

I am migrating from a physical Windows 2003 32 bit server running PageGate v5 to a virtual 2012 running PageGate v7 that uses a Lantronix CPR for its virtual com and points to the IP address of the Lantronix UDS1100 device (paging groups and recipients works fine). On the 2003 box, someone had setup sendpage to send out a page every 2 minutes which is received by our LogPage monitoring software. That way if LogPage doesn't receive the page, it sends us an email to alert us that PageGate is down. I am trying to get this working on the new 2012 64 bit, and from what I read on the forum, I am supposed to use sendpage32.exe. When changing the .bat file on 2012 from:

@ECHO OFF
CALL SENDPAGE.EXE 1182910 ME "PAGEGATE KEEP ALIVE NORMAL"

to

@ECHO OFF
CALL SENDPAGE32.EXE 1182910 ME "PAGEGATE KEEP ALIVE NORMAL"

Nothing happens when triggering the .bat file.

One thing to mention is that I copied over the GetASCII folder that contained the sendpage32 and bat file from the v5 server to the v7 server. I didn't see it on v7, so I put it in a similar location (c:\PageGateData\GetASCII on v7, but was c:\pagegate\GetASCII on v5). Don't think that matters, but figured I would ask. Any ideas on how to get this working? Thanks

Good to know. Thank you very much for your assistance.

Thank you for that info. One final thing I need cleared up. Since we are migrating from a physical Windows server with a fully functional PageGate to a VMware virtual, I mimicked the settings as much as possible. I did notice in Device Manager on the physical com port it showed 9600, 8, none, 1. However in PageGate it shows 9600, 7, even, 1 in the carriers>DirectComm1 settings. So my question is what takes precedence? I would guess it uses the physical com port settings in Windows and ignores what Pagegate has configured under DirectComm1. So in the case of the new virtual server, if it follows the pattern, the virtual com port settings in Windows device manager would also take precedence? If this is the case, why would the Carriers settings even have com port settings if the physical takes precedence?

That worked going from Putty on the server to Putty on my laptop, which is connected via serial to the Lantronix. After further investigation, I learned that it is due to how TAP communicates. Since my laptop wasn't responding to the <cr>, that the server just sitting there waiting to hear back from it. Since it was just putty, it wasn't returning anything to setup the session. Switching Pagegate from TAP to RawSerial allowed Putty > Putty traffic just fine. So apparently when I connect it to the actual paging terminal it should function just fine. Thanks for your help.

I am unable to get Pagegate client test messages flowing from serial to ethernet.

I have a VMware Windows 2012 virtual machine that has the Lantronix virtual Com Port Redirector software installed and pointing to a Lantronix UDS1100.

In Pagegate, I have a Carrier of DirectComm1 setup as TAP, 9600, Even, 7, 1. My Connector points to Dedicated Carrier > DirectComm1, serial port 3, direct connect is checked.

In the Device Manager on Windows 2012, it show Lantronix CPR Port (COM3) with 9600,e,7,1.

In the Lantronix CPR Manager software, it shows Com 3 points to IP 192.168.1.14 TCP 10001, Com Status=Open Network, Status=Connected to 192.168.1.14.

When running a test from the Pagegate client (installed on the same server as the Pagegate admin), I select a recipient that has the DirectComm1 carrier assigned, and I just see the Pending counter increasing after hitting send. I am unable to see my Pagegate client test message in Wireshark, rather just periodic keep-alives between the Windows vm and the Lantronix going back and forth on TCP 10001, so I know the IP connectivity is good.

That being said, I am new to Pagegate, so perhaps I am missing something simple.

Here is the connector log:

6/29/2017 1:54:00 PM Start connection to carrier: DirectComm1
6/29/2017 1:54:00 PM Connect using TAP protocol
6/29/2017 1:54:00 PM Setting communication parameters (9600,e,7,1)
6/29/2017 1:54:00 PM Connected to carrier
6/29/2017 1:54:00 PM Waiting for protocol initialization
6/29/2017 1:54:00 PM Sent:<CR>
6/29/2017 1:54:02 PM Sent:<CR>
6/29/2017 1:54:05 PM Sent:<CR>
6/29/2017 1:54:09 PM Sent:<CR>
6/29/2017 1:54:14 PM Carrier retry limit reached. Marking pending messages as bad
6/29/2017 1:54:14 PM FAILED Stn:10 To:1310026 Frm:Administrator Msg:test

Also, I have tried 4 different serial to ethernet applications without success. Any suggestions are greatly appreciated. Thank you.

Author	Message
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Thu Aug 31, 2017 11:25 am Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Thanks for all your assistance.
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Thu Aug 31, 2017 11:09 am Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	That worked thanks. I suspect that the person that initially installed it created a special database folder and that was affecting it's ability to find the database using its default path. I looked on our old server, and a database folder did not exist. Am I correct that the default install does NOT have a database folder?
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Wed Aug 30, 2017 3:16 pm Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	I just have a bad feeling that this is going to present problems down the road. It seems like the path of least resistance might be to change the folder path setup and the PageGate file share on the server. As an example, the old server was setup as E:\apps\pagegate\database, and the 'Apps' level was shared out. So when \\server\apps was mapped, the default was P:\pagegate, it would see the database folder. The problem is now the path is C:\PageGateData\database (the PageGateData folder is shared out as 'PageGate'. Now when the drive is mapped, it is mapped as \\server\Pagegate, so when the client opens, it looks for P:\PageGate, which does not exist. I don't want to share out the whole C drive (and would have to rename the PageGateData folder to PageGate anyhow. My concern is that renaming a folder path will break untold things, unless you can guide me through this. I notice in the PageGate Admin, there are multiple paths in the Programs > Settings tab. What else do I need to change? Anything manually in the registry? I am thinking about changing the database path to C:\NotePage\PageGate\Database, then when I map the NotePage folder, the P:\PageGate path will be valid at that point.
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Wed Aug 30, 2017 2:52 pm Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Version 7.0. Running on Windows Server 2012 R2 Standard.
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Wed Aug 30, 2017 1:35 pm Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	I entered the new path in regedit as an admin. After I made the change, I closed regedit and opened it again to confirm the correct path was there. Then I logged in as a standard user account, and it shows the old path when I try to launch the client. I logged back into the admin account and checked the registry and it reverted to the old path.
Topic: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	Forum: PageGate Support Posted: Wed Aug 30, 2017 1:03 pm Subject: PageGate client default Server Database path
nonsense Replies: 10 Views: 12511	On my Windows profile, in the PageGate client setup, I set a default path of P:\database, but when a new user logs in to Windows, it reverts to P:\PageGate for their profile. I did select 'Use these setting for all local users' under my initial profile. How do I fix this?
Topic: sendpage32
nonsense Replies: 4 Views: 7986	Forum: PageGate Support Posted: Mon Aug 28, 2017 4:01 pm Subject: sendpage32
nonsense Replies: 4 Views: 7986	It's working now. Thanks for your assistance.
Topic: sendpage32
nonsense Replies: 4 Views: 7986	Forum: PageGate Support Posted: Mon Aug 28, 2017 3:32 pm Subject: sendpage32
nonsense Replies: 4 Views: 7986	I have confirmed the GetAscii directory path is correct. It wasn't enabled though, so I enabled it. GetAscii was checked under the 'Run on this Server' section. I restarted the server and verified that the GetAscii Windows service was running, and tried the sendpage32 command again and nothing is happening. The Interfaces > GetAscii log is showing nothing when I run the .bat file. Am I doing something wrong with my command line? Using the command prompt, I tried manually typing 'sendpage32.exe <recipient> <sender> "message..." and hit enter. The recipient is the 'Recipient' name. For the sender, I presume you can type anything in there? If not, what in PageGate are you supposed to use as sender? Thanks
Topic: sendpage32
nonsense Replies: 4 Views: 7986	Forum: PageGate Support Posted: Mon Aug 28, 2017 1:31 pm Subject: sendpage32
nonsense Replies: 4 Views: 7986	I am migrating from a physical Windows 2003 32 bit server running PageGate v5 to a virtual 2012 running PageGate v7 that uses a Lantronix CPR for its virtual com and points to the IP address of the Lantronix UDS1100 device (paging groups and recipients works fine). On the 2003 box, someone had setup sendpage to send out a page every 2 minutes which is received by our LogPage monitoring software. That way if LogPage doesn't receive the page, it sends us an email to alert us that PageGate is down. I am trying to get this working on the new 2012 64 bit, and from what I read on the forum, I am supposed to use sendpage32.exe. When changing the .bat file on 2012 from: @ECHO OFF CALL SENDPAGE.EXE 1182910 ME "PAGEGATE KEEP ALIVE NORMAL" to @ECHO OFF CALL SENDPAGE32.EXE 1182910 ME "PAGEGATE KEEP ALIVE NORMAL" Nothing happens when triggering the .bat file. One thing to mention is that I copied over the GetASCII folder that contained the sendpage32 and bat file from the v5 server to the v7 server. I didn't see it on v7, so I put it in a similar location (c:\PageGateData\GetASCII on v7, but was c:\pagegate\GetASCII on v5). Don't think that matters, but figured I would ask. Any ideas on how to get this working? Thanks
Topic: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Forum: PageGate Support Posted: Fri Jun 30, 2017 11:40 am Subject: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Good to know. Thank you very much for your assistance.
Topic: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Forum: PageGate Support Posted: Fri Jun 30, 2017 11:12 am Subject: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Thank you for that info. One final thing I need cleared up. Since we are migrating from a physical Windows server with a fully functional PageGate to a VMware virtual, I mimicked the settings as much as possible. I did notice in Device Manager on the physical com port it showed 9600, 8, none, 1. However in PageGate it shows 9600, 7, even, 1 in the carriers>DirectComm1 settings. So my question is what takes precedence? I would guess it uses the physical com port settings in Windows and ignores what Pagegate has configured under DirectComm1. So in the case of the new virtual server, if it follows the pattern, the virtual com port settings in Windows device manager would also take precedence? If this is the case, why would the Carriers settings even have com port settings if the physical takes precedence?
Topic: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Forum: PageGate Support Posted: Thu Jun 29, 2017 6:22 pm Subject: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	That worked going from Putty on the server to Putty on my laptop, which is connected via serial to the Lantronix. After further investigation, I learned that it is due to how TAP communicates. Since my laptop wasn't responding to the <cr>, that the server just sitting there waiting to hear back from it. Since it was just putty, it wasn't returning anything to setup the session. Switching Pagegate from TAP to RawSerial allowed Putty > Putty traffic just fine. So apparently when I connect it to the actual paging terminal it should function just fine. Thanks for your help.
Topic: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	Forum: PageGate Support Posted: Thu Jun 29, 2017 4:21 pm Subject: Pagegate over virtual com port VMware
nonsense Replies: 6 Views: 10307	I am unable to get Pagegate client test messages flowing from serial to ethernet. I have a VMware Windows 2012 virtual machine that has the Lantronix virtual Com Port Redirector software installed and pointing to a Lantronix UDS1100. In Pagegate, I have a Carrier of DirectComm1 setup as TAP, 9600, Even, 7, 1. My Connector points to Dedicated Carrier > DirectComm1, serial port 3, direct connect is checked. In the Device Manager on Windows 2012, it show Lantronix CPR Port (COM3) with 9600,e,7,1. In the Lantronix CPR Manager software, it shows Com 3 points to IP 192.168.1.14 TCP 10001, Com Status=Open Network, Status=Connected to 192.168.1.14. When running a test from the Pagegate client (installed on the same server as the Pagegate admin), I select a recipient that has the DirectComm1 carrier assigned, and I just see the Pending counter increasing after hitting send. I am unable to see my Pagegate client test message in Wireshark, rather just periodic keep-alives between the Windows vm and the Lantronix going back and forth on TCP 10001, so I know the IP connectivity is good. That being said, I am new to Pagegate, so perhaps I am missing something simple. Here is the connector log: 6/29/2017 1:54:00 PM Start connection to carrier: DirectComm1 6/29/2017 1:54:00 PM Connect using TAP protocol 6/29/2017 1:54:00 PM Setting communication parameters (9600,e,7,1) 6/29/2017 1:54:00 PM Connected to carrier 6/29/2017 1:54:00 PM Waiting for protocol initialization 6/29/2017 1:54:00 PM Sent:<CR> 6/29/2017 1:54:02 PM Sent:<CR> 6/29/2017 1:54:05 PM Sent:<CR> 6/29/2017 1:54:09 PM Sent:<CR> 6/29/2017 1:54:14 PM Carrier retry limit reached. Marking pending messages as bad 6/29/2017 1:54:14 PM FAILED Stn:10 To:1310026 Frm:Administrator Msg:test Also, I have tried 4 different serial to ethernet applications without success. Any suggestions are greatly appreciated. Thank you.