|
|
|
Session Server Does Not Start
Technical Note 10055
Last Reviewed 05-Apr-2007
Applies To
Verastream Host Integrator version 5.5 or higher
Summary
Technical Note 10055
Last Reviewed 05-Apr-2007
Applies To
Verastream Host Integrator version 5.5 or higher
Summary
In some situations the Verastream Session Server may not remain running after attempting to start it. Use this technical note to troubleshoot the problem.
Note: For information about how to check the status of the Session Server service, see Technical Note 10054.
Examining Service Startup Events
Check the operating system log for startup messages generated by the Session Server component. (Startup messages will not appear in the Verastream logs.) The operating system logs can be found in the following locations:
Windows: Control Panel > Administrative Tools > Event Viewer > Application Log
Sun Solaris: /var/adm/messages
Red Hat Linux: /var/log/messages
Troubleshooting AADS Registration Failure
This startup problem can occur if the Session Server is unable to complete runtime registration with the AADS Server component. To determine if this is the problem, check the operating system logs for any of the following messages:
ID 2860: Socket Error – Socket connection refused.ID 3120: Directory services (<aadsname>) connection failed.ID 2542: AADS registration failed.If any of these messages are recorded in the logs, follow the steps below to troubleshoot the issue.
- If you are starting services one at a time, verify that the AADS Server service is running before attempting to start Session Server.
- Verify that the AADS name (indicated in message ID 3120) is resolvable and reachable using a ping utility at the shell command prompt.
- If you are using an AADS failover configuration, verify that the AADS common name has been configured in DNS or the Hosts file, as described in Technical Note 10048 (for UNIX) or 10049 (for Windows).
- If the AADS server is on a different system than the Session Server and is reached through a firewall, verify that the firewall port is open. For port number information, see Technical Note 40012. On UNIX, use the atping utility as described in Technical Note 10054.
- Follow these steps to determine if the problem is caused by a network configuration change.
- On the Administrative WebStation login screen, note the name of the Directory Server you are using.
- If you are able to log into Administrative WebStation, examine the Servers in the left navigation (they appear grey when not started). This shows the Session Server names that were registered with the AADS Server during installation.
- Verify the listed Session Server name is resolvable and reachable using a ping utility.
- On Windows, at the Command Prompt, enter ipconfig /all. Note the Host Name and Primary DNS Suffix. Compare this with the Directory Server and Session Server names noted in steps a and b.
Resolving Problems Caused By Network Configuration Changes
If step 5 above indicates the original Directory Server (AADS) and/or Session Server names do not match the current IP configuration, take the appropriate action below.
- If an IP address was used for the AADS or Session Server name, and the IP address has changed, you must Re-install Host Integrator.
- If a fully-qualified name (such as myhost.usa.mycompany.com) was used for the AADS or Session Server name, and the DNS suffix has changed, either Re-install Host Integrator (preferred) or try the Hosts File Workaround. This situation is common with Development Kit installations on mobile Windows laptops.
- If the AADS or Session Server name is invalid because you are using a cloned installation image, either Re-install Host Integrator (preferred) or try the Hosts File Workaround.
Re-install Host Integrator
If your AADS or Session Server names are no longer valid, use the following steps to reinstall a standalone Development Kit.
- Uninstall Verastream Host Integrator from Add/Remove Programs.
- If you are reinstalling Verastream on a mobile Windows laptop system, and you are installing from the CD-ROM (rather than from a network location), disconnect the system from the network. This releases any dynamic IP configuration.
- Start the Verastream installation. Choose to do a Custom installation.
- When prompted for AADS Server and Session Server names, enter only the computer name (the value of the Windows COMPUTERNAME environment variable). Do not use a fully-qualified name or IP address.
- Complete the installation.
- Reapply any appropriate Service Pack patches.
Hosts File Workaround
If the AADS or Session Server name is no longer valid, you can try editing the local Hosts file to add the original name and new IP address (or loopback address 127.0.0.1 for a standalone installation). On Windows systems, the Hosts file is typically C:\Windows\System32\drivers\etc\HOSTS.
Note: This workaround is recommended for temporary use only. Interoperability issues and security vulnerabilities can result from simultaneously using the same installation image on multiple systems. It is recommended you Re-install Host Integrator with the actual system name so unique security fingerprints can be generated.
