Search found 4445 matches

It sounds like you have multiple workstations or monitoring programs that will need to send messages and I would strongly recommend using PageGate rather than NotePager Pro.

The style of messaging and escalation you've described is something PageGate can definitely handle.

As for recommendations for how to organize recipients and groups and their routing, how do you send your messages? Do you have people manually selecting recipients and groups to message them? Are you using a network monitoring program like Solarwinds, Splunk, PRTG or similar?

The PG Server, Client, Workstation Admin and Workstation Monitor are all packaged in that single installation file. When you run it, it will extract and provide a menu with each option.

The only one(s) you'll want to do on the server are 'Install PageGate Server' and, if it's installed, 'Install PageGate GUI Client'. The other two options are meant for workstations and shouldn't be installed on the server.

PageGate version 8 has fallen out of support and is no longer receiving updates; you'll definitely want to upgrade to a more modern version.

We do have a fix for the PGv10 installation options available at https://www.notepage.net/download/dev/pgv10setup.zip

That holds the installers for PG Admin, PG Client, PG Server, and PG Monitor.

Run the main installer (pgsetup.exe) and stop on the first screen.

Then go into your temp folder (just type %temp% into the windows search field on the task bar) and change into the PGSetup folder.

Copy the contents of the .zip file into that folder, replacing the existing files.

You will then be able to continue the setup process from the GUI installer, or you could copy the contents of that folder elsewhere to use the commandline installation options.

Please send a screenshot of the 'Registration' section in PG admin to support at notepage dot com, please!

Let's try an interface reset to see if that helps:

1) Open PG Admin

2) Go to Interfaces - GetAscii - Settings

3) Uncheck Enabled, click apply and tell it No.

4) Check Enabled, click Apply and tell it Yes

5) On the left hand side, right click on the word 'GetAscii' and select Start.

That's great!

Please let us know if you run into any other problems.

My best guess it that you are experiencing some sort of conflict between applications in regards to suppport files (i.e. dll's, ocx's etc.).

The PageGate client will first look in it's local program folder for those files, before resorting to searching for them on the system. So, here are steps to put the support files that PG Client requires, into its program folder.

1. Run the PageGate installer (pgsetup.exe or pgv11.exe)
2. You will get an initial screen which has choices as to which program to install (i.e. server, admin, client, etc.)
3. Stop and leave that up on the screen.
4. Open a command prompt and type: set
and hit enter
5. Make note of the value for TEMP
6. Open a file browser and change into the TEMP folder location
7. Open the PGSetup folder found there
8. Copy the following files from that folder, into your PageGate Client program folder (typically c:\program files (x86)\notepage\PageGate Client\
psvince.dll
flp32x20.ocx
sgpview4.ocx
vbaledit2.ocx
dao360.dll
comdlg32.ocx
mscomctl.ocx
msjet40.dll
msjint40.dll
msjter40.dll
msjtes40.dll
msrd3x40.dll
msrepl40.dll
msvbvm60.dll
msvcrt.dll
msvcrt40.dll
mswdat10.dll
mswstr10.dll
ole32.dll
oleaut32.dll
olepro32.dll
vb5db.dll
vbajet32.dll
stdole2.tlb
9. After you have copied the files, you can quit out of the PageGate installer

Try running PageGate Client again and let us know the results
Thanks

Do all of those come back as "NAME NOT FOUND", or just the netmsg.dll?

There are a couple of things you can try:
1. Install PageGate Admin and see if you get the same error.

2. Unfortunately our error reporting can't detect what .dll file is failing, so external tools must be used.
The most reliable method is to watch the filesystem in real-time using Microsoft's free Process Monitor (ProcMon) utility. This captures the exact file path that the application attempts to access right before crashing.
Download Process Monitor from Microsoft Sysinternals.
Launch Procmon.exe and pause data capture by clicking the Capture icon (or press Ctrl + E).
Clear the current log using the Clear icon (or press Ctrl + X).
Click the Filter icon (or press Ctrl + L) and add a rule:
Process Name is pgc.exe
Click Add, then OK.
Start capturing again (Ctrl + E).
Run PageGate Client and trigger Error 48.
Stop capturing immediately (Ctrl + E) to prevent log overflow.
Look at the bottom of the log list.
Look for results labeled NAME NOT FOUND or PATH NOT FOUND on files ending in .dll

The msjtes40.dll registration error from that utility is actually expected on more current Windows computers. the windows update: September 9, 2025—KB5065426 (OS Build 26100.6584) updates most of the Jet database files and it no longer allows msjtes40.dll to be registered manually. That is ok, because Windows does register it, it just can't be registered by anyone else.

Do you get the error #48 if you right-click on the PageGate Admin shortcut and choose 'run as administrator'?

Hi,
We have a some utilities that you can download that will:
1. Verify that all the files that the PageGate installer is meant to install, are actually installed on the computer.
2. Verify that all the PageGate support files that need to be registered with Windows, are registered.

Download this file:
https://www.notepage.net/download/dev/pg-checks.zip

Unzip the contents into the PageGate program folder (typically C:\Program Files (X86)\NotePage\PageGate\

Open a command prompt using 'run as administrator'

Run pgserver-checkfiles.bat to verify that the proper files exist in the correct locations

Run pgserver-registerfiles.bat to verify that the support files are registered

Please let us know how that goes.

The only real change between PageGate v10 and PageGate v11 as far as support files goes, is that version 11 requires the Microsoft Visual C++ redistributable files.

vcredist_x86.exe is the official Microsoft Visual C++ Redistributable installer
and
vcredist_x64.exe is the official Microsoft Visual C++ Redistributable installer

Both are run during the installation. They can be downloaded from here if you want to try reinstalling them:

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Downloads are under the section:
Latest supported redistributable version

What is really odd is that the fact that Notes was loading the .dll from C:\windows\winsxs\amd64_microsoft... which would signify that it is a 64-bit application and loading the 64-bit dll
After it is loading the .dll from C:\windows\winsxs\x86_microsoft... which would signify that it is a 32-bit application and loading the 32-bit dll
I don't see how Notes would have changed from being a 64-bit application to being a 32-bit application.

Maybe Notes uses some sort of launcher that is 32-bit and that is failing, where a running Notes program has gone beyond the 32-bit launcher and is now running it's main code as a 64-bit application so you see it using the 64-bit dll

We haven't seen anything like this before, so I am struggling with a quick solution.

Were these same systems running an earlier version of PageGate, or is PageGate v11 the first version being installed?

Another thought is that applications typically look for support dlls in their application folder first. You could try copying the correct .dll into the program folder of Notes and it should look there first.

Author	Message
Topic: How to Send Different Alerts to Different Teams Using NotePa
Tech Support Replies: 1 Views: 370	Forum: NotePager Pro Support Posted: Wed Oct 14, 2026 8:07 am Subject: How to Send Different Alerts to Different Teams Using NotePa
Tech Support Replies: 1 Views: 370	It sounds like you have multiple workstations or monitoring programs that will need to send messages and I would strongly recommend using PageGate rather than NotePager Pro. The style of messaging and escalation you've described is something PageGate can definitely handle. As for recommendations for how to organize recipients and groups and their routing, how do you send your messages? Do you have people manually selecting recipients and groups to message them? Are you using a network monitoring program like Solarwinds, Splunk, PRTG or similar?
Topic: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	Forum: PageGate Support Posted: Wed Sep 30, 2026 3:42 pm Subject: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	The PG Server, Client, Workstation Admin and Workstation Monitor are all packaged in that single installation file. When you run it, it will extract and provide a menu with each option. The only one(s) you'll want to do on the server are 'Install PageGate Server' and, if it's installed, 'Install PageGate GUI Client'. The other two options are meant for workstations and shouldn't be installed on the server.
Topic: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	Forum: PageGate Support Posted: Thu Sep 24, 2026 1:22 pm Subject: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	PageGate version 8 has fallen out of support and is no longer receiving updates; you'll definitely want to upgrade to a more modern version.
Topic: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	Forum: PageGate Support Posted: Wed Sep 23, 2026 2:25 pm Subject: msjtes40.dll error installing GUI Admin Win 11
Tech Support Replies: 7 Views: 4167	We do have a fix for the PGv10 installation options available at https://www.notepage.net/download/dev/pgv10setup.zip That holds the installers for PG Admin, PG Client, PG Server, and PG Monitor. Run the main installer (pgsetup.exe) and stop on the first screen. Then go into your temp folder (just type %temp% into the windows search field on the task bar) and change into the PGSetup folder. Copy the contents of the .zip file into that folder, replacing the existing files. You will then be able to continue the setup process from the GUI installer, or you could copy the contents of that folder elsewhere to use the commandline installation options.
Topic: Upgrade to version 11 from 10 - PGGAscii Message rejected
Tech Support Replies: 3 Views: 14469	Forum: PageGate Support Posted: Wed Jul 22, 2026 8:43 am Subject: Upgrade to version 11 from 10 - PGGAscii Message rejected
Tech Support Replies: 3 Views: 14469	Please send a screenshot of the 'Registration' section in PG admin to support at notepage dot com, please!
Topic: Upgrade to version 11 from 10 - PGGAscii Message rejected
Tech Support Replies: 3 Views: 14469	Forum: PageGate Support Posted: Wed Jul 22, 2026 8:25 am Subject: Upgrade to version 11 from 10 - PGGAscii Message rejected
Tech Support Replies: 3 Views: 14469	Let's try an interface reset to see if that helps: 1) Open PG Admin 2) Go to Interfaces - GetAscii - Settings 3) Uncheck Enabled, click apply and tell it No. 4) Check Enabled, click Apply and tell it Yes 5) On the left hand side, right click on the word 'GetAscii' and select Start.
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Tue Jul 07, 2026 3:30 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	That's great! Please let us know if you run into any other problems.
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Tue Jul 07, 2026 2:51 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	My best guess it that you are experiencing some sort of conflict between applications in regards to suppport files (i.e. dll's, ocx's etc.). The PageGate client will first look in it's local program folder for those files, before resorting to searching for them on the system. So, here are steps to put the support files that PG Client requires, into its program folder. 1. Run the PageGate installer (pgsetup.exe or pgv11.exe) 2. You will get an initial screen which has choices as to which program to install (i.e. server, admin, client, etc.) 3. Stop and leave that up on the screen. 4. Open a command prompt and type: set and hit enter 5. Make note of the value for TEMP 6. Open a file browser and change into the TEMP folder location 7. Open the PGSetup folder found there 8. Copy the following files from that folder, into your PageGate Client program folder (typically c:\program files (x86)\notepage\PageGate Client\ psvince.dll flp32x20.ocx sgpview4.ocx vbaledit2.ocx dao360.dll comdlg32.ocx mscomctl.ocx msjet40.dll msjint40.dll msjter40.dll msjtes40.dll msrd3x40.dll msrepl40.dll msvbvm60.dll msvcrt.dll msvcrt40.dll mswdat10.dll mswstr10.dll ole32.dll oleaut32.dll olepro32.dll vb5db.dll vbajet32.dll stdole2.tlb 9. After you have copied the files, you can quit out of the PageGate installer Try running PageGate Client again and let us know the results Thanks
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Tue Jul 07, 2026 2:01 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Do all of those come back as "NAME NOT FOUND", or just the netmsg.dll?
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Tue Jul 07, 2026 1:30 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	There are a couple of things you can try: 1. Install PageGate Admin and see if you get the same error. 2. Unfortunately our error reporting can't detect what .dll file is failing, so external tools must be used. The most reliable method is to watch the filesystem in real-time using Microsoft's free Process Monitor (ProcMon) utility. This captures the exact file path that the application attempts to access right before crashing. Download Process Monitor from Microsoft Sysinternals. Launch Procmon.exe and pause data capture by clicking the Capture icon (or press Ctrl + E). Clear the current log using the Clear icon (or press Ctrl + X). Click the Filter icon (or press Ctrl + L) and add a rule: Process Name is pgc.exe Click Add, then OK. Start capturing again (Ctrl + E). Run PageGate Client and trigger Error 48. Stop capturing immediately (Ctrl + E) to prevent log overflow. Look at the bottom of the log list. Look for results labeled NAME NOT FOUND or PATH NOT FOUND on files ending in .dll
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Tue Jul 07, 2026 10:14 am Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	The msjtes40.dll registration error from that utility is actually expected on more current Windows computers. the windows update: September 9, 2025—KB5065426 (OS Build 26100.6584) updates most of the Jet database files and it no longer allows msjtes40.dll to be registered manually. That is ok, because Windows does register it, it just can't be registered by anyone else. Do you get the error #48 if you right-click on the PageGate Admin shortcut and choose 'run as administrator'?
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Thu Jul 02, 2026 2:01 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Hi, We have a some utilities that you can download that will: 1. Verify that all the files that the PageGate installer is meant to install, are actually installed on the computer. 2. Verify that all the PageGate support files that need to be registered with Windows, are registered. Download this file: https://www.notepage.net/download/dev/pg-checks.zip Unzip the contents into the PageGate program folder (typically C:\Program Files (X86)\NotePage\PageGate\ Open a command prompt using 'run as administrator' Run pgserver-checkfiles.bat to verify that the proper files exist in the correct locations Run pgserver-registerfiles.bat to verify that the support files are registered Please let us know how that goes.
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:35 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	The only real change between PageGate v10 and PageGate v11 as far as support files goes, is that version 11 requires the Microsoft Visual C++ redistributable files. vcredist_x86.exe is the official Microsoft Visual C++ Redistributable installer and vcredist_x64.exe is the official Microsoft Visual C++ Redistributable installer Both are run during the installation. They can be downloaded from here if you want to try reinstalling them: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 Downloads are under the section: Latest supported redistributable version
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:23 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	What is really odd is that the fact that Notes was loading the .dll from C:\windows\winsxs\amd64_microsoft... which would signify that it is a 64-bit application and loading the 64-bit dll After it is loading the .dll from C:\windows\winsxs\x86_microsoft... which would signify that it is a 32-bit application and loading the 32-bit dll I don't see how Notes would have changed from being a 64-bit application to being a 32-bit application. Maybe Notes uses some sort of launcher that is 32-bit and that is failing, where a running Notes program has gone beyond the 32-bit launcher and is now running it's main code as a 64-bit application so you see it using the 64-bit dll We haven't seen anything like this before, so I am struggling with a quick solution. Were these same systems running an earlier version of PageGate, or is PageGate v11 the first version being installed?
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:07 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 87065	Another thought is that applications typically look for support dlls in their application folder first. You could try copying the correct .dll into the program folder of Notes and it should look there first.