A few general guidelines will help when troubleshooting the Internet
Reservation Module (IRM)
| Topic |
Description |
| Verify Terminal Services Pervasive
Security Setting |
Always establish a terminal services connection to the IRM and login as
the administrator. From the IRM establish a terminal services
connection to the data server, again logging in as administrator.
The terminal services connection to both the IRM and Data server, with
full administrator rights to both, provides the tools for RDP support to
troubleshoot the IRM. Without these tools it is not
possible. It is critical to verify
that the Terminal Services Security Key is set to "0",
which allows full control of Pervasive. If this is not set it is
impossible to use Terminal Services to fix any Pervasive problems.
See:
Changing
Pervasive Terminal Services Security with Regedt32
|
| Verify Configuration Chart |
Complete and verify the Server configuration chart in IRM
Installation Document - RDP Support Steps. It is critical to
verify all configuration data. For example, make sure there
is only one network card in the IRM and Data Server with the same subnet as the data
server. |
| Email Problems
from IRM or RDPWin |
For problems related to Email sent from the IRM
or from RDPWin, see 'Installation,
configuration, and troubleshooting of an Internal Outgoing SMTP Email
Server"
|
|
Re-Install IRM in "Repair
Mode" |
Re-install the latest version of the IRM with the following
procedure:
- Login to the IRM server as Administrator
- Start a command prompt and navigate to C:\INETPUB\WWWROOT\IRM.
Then enter the following command to make sure all IRM files are
read-write::
ATTRIB *.* /S -R
- Re-run the latest IRM update file and select the
"Repair" mode.
- Always reboot after re-installation, even if
not prompted. The "repair mode" of the installation helps
assure all IRM files are correctly copied.
|
| Use IRMTOOLS.HTM |
Use "IRMTools" to test, which has additional troubleshooting
information available. See "Testing
and Troubleshooting the IRM with IRMTools.HTM" |
| Test with IIS
Anonymous
Set to Administrator |
When troubleshooting security, use the administrator account
as the anonymous user in IIS for the IRM. Make sure the passwords
are the same for Administrator in all places (IRM server, IIS, and Data
Server). Always reboot the IRM after changing the passwords.
See "IRM
Installation Document - RDP Support Steps" for information on
changing the anonymous user. |
| Use FILMON and REGMON
Utilities |
Use the FILMON and REGMON utilities to troubleshoot security
issues See: "Using Filemon.exe and
Regmon.exe to find security problems with IRM and Data Server" |
| Additional IRM
Troubleshooting Links |
See the additional IRM Troubleshooting Links Below |