Support Notes

******************

PageMaster/ex Knowledge Base Articles

Q0001
Event Log Error "Failed to Initialize Global Conversion Engine Data" After Starting PageMaster/ex Service

The information in this article applies to:

  • PageMaster/ex, version 1. 0
  • PageMaster/ex, version 2. 0

Last Reviewed: March 15, 2002

Symptoms

After starting the PageMaster/ex service, the service fails to start due to a login failure. The following event is then generated in the event log:

"Failed to initialize global conversion engine data. Error code -2147467259 was received."

The service at this point stops with an error message:

Could not start the PageMasterEX service on \\SERVERNAME Error: 1069: The service did not start due to login failure.

Cause

There are invalid entries in the registry related to MAPI conversion engines. These invalid entries are likely the result of the removal of a third-party connector that did not clean up its registry entries.

Resolution

Using the registry editor (Regedt32. exe), look at the key ""HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MAPI Conversions"". In this key will be several subkeys for MAPI conversion engines. The entries for ""IPM_IN"" and ""IPM_OUT"" are for PageMaster/ex. Check for other entries related to connectors that have since been removed from the server. Delete any such keys and reboot the server. Be sure that you do not delete any subkeys for connectors that are still installed.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Omnitrend cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Status

This problem has been fixed in PageMaster/ex 3. 0.

******************

Q0002
USER32. DLL Initialization Failure when Starting PageMaster/ex Service

The information in this article applies to:

  • PageMaster/ex, version 1. 0
  • PageMaster/ex, version 2. 0
  • PageMaster/ex, version 3. 0
  • PageMaster/ex, version 4. 0
  • PageMaster/ex, version 4. 5

Last Reviewed: July 30, 2002

Symptoms

When you try to start the PageMaster/ex service, a pop-up dialog box appears with the following message:

PageMasterEX - DLL initialization failure. Initialization of the dynamic link library c:\windows\system32\user32. dll failed. The process is terminating abnormally.

Cause

The system has run out of memory to create a new desktop heap for the service being started.

Resolution

Fixing this problem requires editing of the Registry and restarting the computer concerned.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Omnitrend cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Run the Registry Editor(Regedt32. exe).

Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey: \System\CurrentControlSet\Control\Session Manager\ SubSystems\Windows

The default data for this value will look something like the following (all on one line):

%SystemRoot%\system32\csrss. exe ObjectDirectory=\Windows SharedSection=1024,3072 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

You will need to make the following change to this value:

Scan along the line until you reach the part that defines the SharedSection values and add "",512"" after the second number. This value should now look something like the following:

%SystemRoot%\system32\csrss. exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

After making this change, close Regedt32 and restart the server. This change will limit the size of desktop heaps created by non-interactive services to 512 KB, which should be ample for most services.

Status

Microsoft has confirmed this to be a problem in Windows NT version 4. 0.

******************

Q0003
GroupShield 4. x Conflicts with the PageMaster/ex Connector

The information in this article applies to:

  • PageMaster/ex, version 1. 0
  • PageMaster/ex, version 2. 0
  • PageMaster/ex, version 3. 0
  • PageMaster/ex, version 4. 0

Last Reviewed: January 7, 2002

Symptoms

No paging even though the PageMaster/ex service is running and no non-delivery reports are received. No entries are made in the page log file, and no events are generated in the event log.

Cause

Network Associates GroupShield 4. x is installed and is interfering with the operation of the paging connector. This is due to a bug in GroupShield 4. x that applies anti-virus wrappers around the page messages.

Resolution

Using the Exchange Administrator program, bring up the properties page for GroupShield. This is located under Configuration\Servers\ServerName.

Choose the ""On Access (Mailboxes)"" tab. At the bottom of the dialog box is an Exclusion List. Choose the Add button and add the PageMaster/ex mailbox to the Exclusion List.

The GroupShield services will restart. After the restart, paging should work properly. A reboot of the server is not required.

******************

Q0004
Service Drop List Empty when Administering a Pager

The information in this article applies to:

  • PageMaster/ex, version 3. 0
  • PageMaster/ex, version 4. 0

Last Reviewed: May 23, 2001

Symptoms

When creating a new pager or editing an existing pager, the Service drop list is empty even though service providers were configured on the properties page for the connector.

Cause

The local registry parameter that contains the server name on which PageMaster/ex is installed is missing or invalid. Since the local administrator software can't access the proper server, the services data file cannot be read.

Resolution

If the properties page for the pager is already visible, close it. Create a new page or edit an existing pager. Hold down the CTRL key before choosing the ""Pager"" tab. This will force the software to prompt you for the name of the server on which the connector is installed. Enter the server name (all in caps with no leading ""\\"") and choose OK. The Service drop list should now contain the list of configured service providers. "

******************

Q0005
Unable to Create or Administer a Pager from a Remote Workstation

The information in this article applies to:

  • PageMaster/ex, version 1. 0
  • PageMaster/ex, version 2. 0

Last Reviewed: January 18, 2002

Symptoms

When creating a new pager or editing an existing pager, the pager address never changes from "NEW".

Cause

The administrator program is unable to locate the pager entry in the Exchange Directory.

Resolution

Using the Registry Editor on the workstation, add a key named PageMasterEX under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services. This key should have no class.

Under the new PageMasterEX key, create another classless key named Parameters. Under the new Parameters key, create a value of type REG_SZ named HomeDSA. The value should contain the name of the server on which PageMaster/ex is installed. Note that this name should be specified without the leading "\\".

******************

Q0006
Unable to Create a Pager

The information in this article applies to:

  • PageMaster/ex, version 3. 0
  • PageMaster/ex. version 4. 0
  • PageMaster/ex. version 4. 5

Last Reviewed: March 15, 2002

Symptoms

When creating a new pager , an error occurs "Unable to set the Email address for the pager. The newly created pager cannot be found. Be sure you are creating this pager as a custom recipient according to the documentation under "Adding Pagers". This error may also be caused due to delays in directory replication. It is recommended that this pager be created on the Exchange Server on which PageMaster/ex is installed. If you have multiple servers with PageMaster/ex, the pager should be created on the primary PageMaster/ex server. "

Cause

The administrator program is unable to locate the newly created pager entry in the Exchange Directory. This is likely because the Exchange Administrator is connected to a server other than the server on which the paging connector is installed. As such, the newly created entry is made on another Exchange Server. When the administrator then tries to modify properties for the new pager, it cannot be found on the server on which PageMaster/ex is installed. Eventually, Exchange will replicate the pager to the other Exchange Server(s) through normal directory replication, but this takes some time.

Resolution

In the Exchange Administrator program, close all server connections. Open a connection to the server on which PageMaster/ex is installed. Exit and restart the Exchange Administrator. You should now be able to create new pagers. ******************

PageMaster/ex FAQ

  1. Can PageMaster/ex run on a machine other than an Exchange Server?
  2. Will PageMaster/ex cause a performance hit?
  3. If I am using the TAP or DTMF protocols, do the modems have to be connected to the Exchange Server?
  4. What kind of messaging volume can PageMaster/ex handle?
  5. Does any software need to be installed on the client end?
  6. Do I have to enter separate recipients for each pager even though the user has an Exchange mailbox?
  7. What if I want to increase the number of devices in my license?
  8. Are there any issues running PageMaster/ex on Windows 2000?
  9. Why do I need PageMaster/ex? My service providers already supplies an SMTP email address for each device.

Can PageMaster/ex run on a machine other than an Exchange Server?

No. PageMaster/ex integrates as a component of Exchange, so it must be installed on an Exchange Server.

Back to Top

Will PageMaster/ex cause a performance hit?

No, the connector will not cause any noticeable decrease in performance of the Exchange Server. Only one component of PageMaster/ex is actually executed on the server. . . that is the paging service. The paging service spends most of its time idle, waiting for page requests or communication on a modem port.

Back to Top

If I am using the TAP or DTMF protocols, do the modems have to be connected to the Exchange Server?

Not necessarily, but it is preferred. There is no security risk in installing paging modems on the Exchange Server, as these modems are not configured for RAS, and are not set for auto answer.

If desired, however, modems can be remotely located and a redirector installed on the Exchange Server to redirect the communications to the remote modems. There are many third-party packages to accomplish this (e. g. WinPort).

Back to Top

What kind of messaging volume can PageMaster/ex handle?

This question is difficult to answer, as there are several variables that come into play; The number of modems used, the number of PageMaster/ex connectors used, the number of different service providers, the baud rates at which each service provider operates, and so on.

As a general rule, PageMaster/ex was designed to be scalable, and paging volumes of up to 30,000 pages per day are easily obtainable.

Back to Top

Does any software need to be installed on the client end?

No. Any Exchange mail client (e. g. Outlook) can be used to send text messages. The device will simply show up on the GAL (global address list) just as do any other Exchange mailbox. Users can then pick one or more devices as recipients and send the text message just as they would any other Email.

PageMaster/ex does include a custom "Send Page" form. This form provides a character counter which can be used in installations where users need to limit the number of characters they are sending. However, use of this form is completely optional.

Back to Top

Do I have to enter separate recipients for each device even though the user has an Exchange mailbox?

Yes. If the device information were to be attached to the users Exchange mailbox, Exchange would have no way of knowing what messages were intended for the device (pager or cell phone) and what messages were intended for the users normal mailbox.

In addition, there are many advantages to keeping the devices as separate recipients. As separate recipients, you can:

  • Allow users to set up mail forwarding rules using the Out of Office Assistant or Rules Wizard. Since the devices are separate entries, they may be selected as destinations for a forwarding rule.
  • Configure a separate SMTP address for each device, allowing the device to be reached directly from the Internet.
  • Set up delivery restrictions on each device, allowing messages to be sent only from selected individuals
  • Set up distribution lists of devices, allowing a text message to be sent to a group of devices at once.

Back to Top

What if I want to increase the number of devices in my license?

You can upgrade your license at any time by purchasing a license upgrade from Omnitrend. The cost of a license upgrade is posted on the pricing table (see also the pricing table for PageMaster/ex 2000 for Exchange 2000).

To order a license upgrade, contact Omnitrend Sales.

Back to Top

Are there any issues running PageMaster/ex on Windows 2000?

No, all versions of PageMaster/ex are fully compatible with Windows 2000.

Back to Top

Why do I need PageMaster/ex? My service provider already supplies an SMTP email address for each device.

SMTP is an email protocol. Text messaging protocols were created to allow direct, 2-way access to the text messaging terminals at the service provider.

There are several disadvantages to using SMTP for text messaging:

Speed
SMTP mail can often be timely, but inherent delays in routing and mail server congestion can often cause the SMTP message containing the text message to be delayed getting to the service provider. Text messaging protocols provide a direct connection to the equipment that issues the messages to the transmission equipment.

Reliability
SMTP mail is not 100% guaranteed delivery. If the message is delayed, or fails to get to the service provider, you will never know. Text messaging protocols provide a 2-way communication between PageMaster/ex and the service provider to insure the message was received. In addition, most service providers support multiple protocols giving you a backup path should the primary fail. This failover is automatic with PageMaster/ex, insuring you of the highest reliability for your text messaging.

Security
SMTP mail is not secure, so the content of your text messages are subject to interception by unwanted parties. Internet-based text messaging protocols are much less subject to intercept as they are direct TCP/IP connections to the service provider. . . messages are not bounced from server to server. In addition, modem based protocols, leased line connections, and dedicated frame relay connections can be used to insure complete privacy.

Content Control
Sending text messages via SMTP does not allow for control over the content of the text message. PageMaster/ex allows you to define what and how much of the message is delivered to the device.

Throughput
For larger enterprise applications, SMTP simply is not sufficient to handle a large volume of text messaging. PageMaster/ex is quite scalable. Volumes of 30,000+ text messages per day are easily achievable using text messaging protocols.

Back to Top

Latest News

PageMaster/ex 2019 v1 now supporting Exchange 2019 has been released and is available for download. Please contact sales for further information or to obtain an evaluation.