Search found 4439 matches

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.

That last bit is good information.
I'm thinking that maybe the path environment variable is what has changed, and it is changing the order in which comctl32.dll is being searched for, and found.

On a both a working system and an non-working system, open a command prompt and type SET <enter>. This will show all the environment variables for the current user. Do the paths look different? If so, can you post them?
Thanks

Looking deeper into this, I see that the PageGate GUI client does install/update the comctl32.ocx file, but it doesn't update the comctl32.dll file. comctl32.dll is typically protected and only allowed to be updated by windows updates.

Is it possible that the actual issue is being caused by comctl32.ocx?

Similar to what I suggested for the .dll file earlier, you could try copying the comctl32.ocx from a working system onto the problem system. I don't believe comctl32.ocx is protected by Windows, so it should be easier to replace, but you may need to reboot to get all programs to recognize/use the changed version.

What is the version number of the file currently on a working system and what is it on the PageGate Client system?

The PageGate Client does install and register comctl32.dll. It is a VERY commonly used support dll and the vast majority of system already have it install and registered, even before the PageGate Client is installed.

I guess it is possible that HCL Notes wants to use a very specific version of that dll. I think the PG Client may be a bit more forgiving about the exact version.

You could try copying the comctl32.dll from another system that HCL Notes is working properly on and see if that resolves the issue.

Windows tends to protect some of the system dlls so it might revert the comctl32.dll back the previous version after it is replace, so be sure to check after a reboot that the version you want is still there.

Please let us know if that helps.

That usually means the PG related services aren't running. If you open the Services list in Windows on the PageGate server, what is the status of the PageGate service? If it's stopped, what happens when you try to start it?

Open 'Computer Management' in Windows, go to Shared Folders - Open Files and terminate any connection to pagegate.mdb and pagegate.ldb you see in the list.

Also, you'll need to fairly quickly start the upgrade process because the reconnection routines for PGA and PGC can be fairly fast.

We would recommend bringing up the prompt that asks if you want to upgrade, then bring up Computer Management, terminate the connections, then immediately tell the upgrade yes to begin.

Author	Message
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Forum: PageGate Support Posted: Tue Jul 07, 2026 3:30 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Tue Jul 07, 2026 2:51 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Tue Jul 07, 2026 2:01 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Tue Jul 07, 2026 1:30 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Tue Jul 07, 2026 10:14 am Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Thu Jul 02, 2026 2:01 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:35 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:23 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:07 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	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.
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 12:04 pm Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	That last bit is good information. I'm thinking that maybe the path environment variable is what has changed, and it is changing the order in which comctl32.dll is being searched for, and found. On a both a working system and an non-working system, open a command prompt and type SET <enter>. This will show all the environment variables for the current user. Do the paths look different? If so, can you post them? Thanks
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 10:54 am Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Looking deeper into this, I see that the PageGate GUI client does install/update the comctl32.ocx file, but it doesn't update the comctl32.dll file. comctl32.dll is typically protected and only allowed to be updated by windows updates. Is it possible that the actual issue is being caused by comctl32.ocx? Similar to what I suggested for the .dll file earlier, you could try copying the comctl32.ocx from a working system onto the problem system. I don't believe comctl32.ocx is protected by Windows, so it should be easier to replace, but you may need to reboot to get all programs to recognize/use the changed version.
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 10:07 am Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	What is the version number of the file currently on a working system and what is it on the PageGate Client system?
Topic: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	Forum: PageGate Support Posted: Thu Jun 25, 2026 9:35 am Subject: .dll conflict with HCL Notes
Tech Support Replies: 28 Views: 2257	The PageGate Client does install and register comctl32.dll. It is a VERY commonly used support dll and the vast majority of system already have it install and registered, even before the PageGate Client is installed. I guess it is possible that HCL Notes wants to use a very specific version of that dll. I think the PG Client may be a bit more forgiving about the exact version. You could try copying the comctl32.dll from another system that HCL Notes is working properly on and see if that resolves the issue. Windows tends to protect some of the system dlls so it might revert the comctl32.dll back the previous version after it is replace, so be sure to check after a reboot that the version you want is still there. Please let us know if that helps.
Topic: Upgrade to v11
Tech Support Replies: 10 Views: 4278	Forum: PageGate Support Posted: Wed Jun 24, 2026 8:27 am Subject: Upgrade to v11
Tech Support Replies: 10 Views: 4278	That usually means the PG related services aren't running. If you open the Services list in Windows on the PageGate server, what is the status of the PageGate service? If it's stopped, what happens when you try to start it?
Topic: Upgrade to v11 - convert database error
Tech Support Replies: 3 Views: 4629	Forum: General Questions and Announcements Posted: Tue Jun 23, 2026 3:45 pm Subject: Upgrade to v11 - convert database error
Tech Support Replies: 3 Views: 4629	Open 'Computer Management' in Windows, go to Shared Folders - Open Files and terminate any connection to pagegate.mdb and pagegate.ldb you see in the list. Also, you'll need to fairly quickly start the upgrade process because the reconnection routines for PGA and PGC can be fairly fast. We would recommend bringing up the prompt that asks if you want to upgrade, then bring up Computer Management, terminate the connections, then immediately tell the upgrade yes to begin.