Troubleshooting for OpenVMS

How to:

Reference:

To troubleshoot an installation problem, identify your problem in the following list, and follow the link to a description of the solution.

If you cannot find your problem described in the list, and cannot resolve it yourself, contact Customer Support Services as described in Information You Should Have and Customer Support.

Problems:


Top of page

x
Reference: Problem: The Server Starts in Safe Mode

Problem: The server starts in safe mode. The Web Console home page displays a message stating that the server is in safe mode and describing what triggered it.

Cause: A common cause for the server starting in safe mode is a problem with the server administrator ID password. For example, the password may have been updated on the operating system but not on the server, so the encrypted copy of the password stored by the server is out of synchronization with the password on the operating system.

Solution: The server administrator can click the fix hyperlink, which is displayed under the problem description, to display the relevant pane and resolve the problem.

For example, if the problem is that the server administrator password is out of synchronization:

  1. Click the fix hyperlink displayed under the problem description.
  2. In the left pane, open the Users folder, then the Server Administrator folder.
  3. Click your user ID and select Properties from the pop-up menu.

    The Access Control pane is displayed on the right.

  4. Type the correct operating system password in the Password field, and type it again in the Confirm Password field.
  5. Click Save and Restart.

    The Security Mode pane opens on the right.

  6. Click the Home icon in the menu bar to return to the Web Console home page.

Top of page

x
Reference: Problem: EDASTART Window Displays Only a Few Lines

Problem: Issuing the edastart command without the -start option displays only a few lines in the terminal session, even though the server starts and EDAPRINT.LOG is complete.

Cause: This is a file contention problem that generally happens on very fast systems. It does not affect creating and updating the EDAPRINT.LOG file.

Solution: Start the server by issuing the edastart -start command, immediately followed by the edastart -console command to display the edaprint log.


Top of page

x
Reference: Problem: HTTP Listener Does Not Start Or Runs Intermittently

Problem: The HTTP Listener does not start, or runs intermittently, unless traces are on (edastart -traceon option).

Cause: This is caused by a TCP/IP socket synchronization problem on fast systems.

Solution: Briefly delay the socket logic by setting a delay variable intended for this purpose. To define the delay, add the following statement to the iadmin ID LOGIN.CON before starting the server:

DEFINE VMS_RECV_DELAY 1

The unit of measurement is the microsecond. A value of 1 usually resolves the problem. However, the value is likely to be affected by system load, so you will need to experiment to find the correct value for your system.


Top of page

x
Reference: Problem: Missing Folders in Web Console Procedure and Metadata Panes

Problem: The Web Console Procedure and Metadata panes do not display any folders.

Cause: This is caused by a TCP/IP socket synchronization problem on fast systems.

Solution: Briefly delay the socket logic by setting a delay variable intended for this purpose. To define the delay, add the following statement to the iadmin ID LOGIN.CON before starting the server:

DEFINE VMS_RECV_DELAY 1

The unit of measurement is the microsecond. A value of 1 usually resolves the problem; however, the value is likely to be affected by system load, so you will need to experiment to find the correct value for your system.


Top of page

x
Reference: Problem: Unexpected EDASHARE Message

Problem: After the server starts, you receive an unexpected EDASHARE message.

Cause: EDASHARE may have been declared manually in an earlier release.

Solution: Remove the manual EDASHARE declaration.


Top of page

x
Reference: Problem: Java Tasks Fail When Using Oracle

Problem: Java tasks fail when using Oracle.

Cause: Newer Oracle releases use Java. When you call Oracle setup scripts (for example, in edaenv.com) and then start the server.

Solution: Call the standard Java setup environment after calling any Oracle setup scripts.


Top of page

x
Procedure: How to Install and Activate the Debuggable Version of the Server

In core dump or crash situations, the stack information may or may not provide enough information for a problem to be resolved. Debugging software will generally provide that information, but will not normally be installed nor used due to the disk overhead they take. They are also not optimized for performance.

If diagnostic is determined to not have enough information and the use of debugging software is warranted, Customer Support Services will inform you to install and activate the debuggable version of the server. You will then re-run the reproduction to capture a new diagnostic with the detailed stack to help troubleshoot the problem.

Caution: Do not activate the debuggable version unless explicitly requested to by Customer Support Services.

To install and activate the debuggable version of the software:

  1. Log on with the administrator ID (often referred to as iadmin).
  2. Download the iserverd archive file (for example, .tar, .zip, or .bck) from the FTP site to a local directory. Debuggables for OpenVMS environments are not normally shipped on the original CD media, but can be made available on CD by special request to Customer Support Services and requires a lead time of approximately one week. IF CD media is being used, mount the media.
  3. Run the isetup installation program (located in EDAHOME bin if download was used or in a root directory of the CD media).
  4. At the isetup main menu, select option 4, Install Debuggables to the Installation Directory and follow the steps supplying information similar to when the original install was performed.
  5. After completion of isetup, the software may be run in debug mode with the following steps.

    edastart -stop

    Copy the edastart.com to edastartdbg.com and on TSCOM symbol set up line edit bin]tscom300.exe to be dbg]tscom300.exe and save.

    edastart -dbgon
    edastartdbg -start

    The debugger starts and the user is required to type GO and GO for the actual executable to start (run until repro is completed).

    edastart -stop
    edastart -dbgoff
    edastart -start

    The debugger GO/GO step may be avoided by creating a text file with the words GO and GO on separate lines and issuing a logical for DBG$INPUT before starting the server.

  6. If the debug version is no longer needed, the debuggables may be removed. If a service pack is being installed, the debuggables must be removed to prevent mismatches with the new release. To remove the debuggables, change the directory to the home directory of EDAHOME and issue DELETE [.DBG...]*.*;* and then DELETE DBG.DIR;*.

Customer Support Services will provide you with additional instructions as your situation requires.


iWay Software