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.
If you have a troubleshooting suggestion that is not described in the list, and you think others will find it helpful, we invite you to send it to us, as described in How to Add Your Problem to the Troubleshooting Guide. We will consider including your problem in a future release of this manual.
Problems:
For details, see Problem: The Server Starts in Safe Mode .
For details, see Problem: EDASTART Window Displays Only a Few Lines.
For details, see Problem: HTTP Listener Does Not Start Or Runs Intermittently.
For details, see Problem: Missing Folders in Web Console Procedure and Metadata Panes.
For details, see Problem: Unexpected EDASHARE Message.
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:
The Access Control pane is displayed on the right.
The Security Mode pane opens on the right.
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.
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.
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.
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.
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.
If you have troubleshooting suggestions that you think others will find helpful, we invite you to send them to us so that we can consider including them in a future release. You can:
Please include your name, phone number, email address, and postal address.
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 server:
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.
Customer Support Services will provide you with additional instructions as your situation requires.
iWay Software |