Hi,
Installing px on Windows XP service pack 2
I am having problem with the installation.
##I TFCN 000001 17:27:08(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved
##I TOSH 000002 17:27:08(001) <main_program> orchgeneral: loaded
##I TOSH 000002 17:27:08(002) <main_program> orchsort: loaded
##I TOSH 000002 17:27:08(003) <main_program> orchstats: loaded
##W TCOS 000049 17:27:08(004) <main_program> Parameter specified but not used in
flow: DSProjectMapName
##I TFSC 000001 17:27:08(009) <main_program> APT configuration file:
C:/Ascential/DataStage/Configurations/default.apt
Toolkit\mksnt\sh.exe: Toolkit\mksnt\sh.exe: not found
>##E TFPM 000152 17:27:38(000) <main_program> Accept timed out retries = 4
>##E TFPM 000153 17:27:38(001) <main_program> The section leader on HSTTD027
died
>##E TFPM 000356 17:27:38(002) <main_program>
>
>**** Parallel startup failed ****
>
>This is usually due to a configuration error, such as
>not having the Orchestrate install directory properly
>mounted on all nodes, rsh permissions not correctly
>set (via /etc/hosts.equiv or .rhosts), or running from
>a directory that is not mounted on all nodes. Look for
>error messages in the preceding output.
>
>
##I TFPM 000177 17:27:38(003) <main_program> Step started on node HSTTD027; it
uses 1 nodes.
The program running the step is /C=/Ascential/DataStage/PXEngine/bin/osh.exe.
##I TFPM 000178 17:27:38(004) <main_program> The ORCHESTRATE startup program in
/C=/Ascential/DataStage/PXEngine/etc/standalone.sh is being used.
##I TFPM 000181 17:27:38(005) <main_program> A startup script is not being used.
##I TFPM 000183 17:27:39(000) <main_program> The TCP port being used for startup
is 10000; the associated socket number is 3.
##I TFPM 000184 17:27:39(001) <main_program>
Node status:
##I TFPM 000185 17:27:39(002) <main_program> HSTTD027 -
##I TFPM 000187 17:27:39(003) <main_program> rsh issued, no response received
>##E TFPM 000247 17:27:39(004) <main_program> Unable to contact one or more
Section Leaders.
>Probable configuration problem; contact Orchestrate system administrator.
>
>##E TFSR 000011 17:27:39(005) <main_program> Step execution finished with
status = FAILED.
##I TCOS 000026 17:27:39(006) <main_program> Startup Time 0:30 Production Run
Time 0:00
Kindly give some inputs on solving this.
Regards,
Prabu
Problem with the installation
Moderators: chulett, rschirm, roy
I have heard some clients complain of issues getting DataStage to interact with MKS properly when MKS and DataStage are installed on different drives.
I have also heard that the MKS installation likes to install itself to local C drive.
You should check to see if MKS and DataStage are installed on same drive in your environment, as they may be the issue.
- Greg
I have also heard that the MKS installation likes to install itself to local C drive.
You should check to see if MKS and DataStage are installed on same drive in your environment, as they may be the issue.
- Greg
Prabu,
According to your notes, you are only having problems to install 7.5X2 Windows EE to the server on the network.
When you said that you have installed the MKS Toolkit, you sounded like that the MKS Toolkit was already installed separately before the 7.5x2 EE installation? If this is true, then you must un-install the MKS Toolkit first before you re-install the 7.5x2 EE.
As you said that you don't have any problem to install on the local machine, the only thing that I can suggest you is to make sure:
1. .NET 2003 C++ compiler is installed on the server before the DS installation.
2. No existing or older version of MKS Toolkit on the server.
According to your notes, you are only having problems to install 7.5X2 Windows EE to the server on the network.
When you said that you have installed the MKS Toolkit, you sounded like that the MKS Toolkit was already installed separately before the 7.5x2 EE installation? If this is true, then you must un-install the MKS Toolkit first before you re-install the 7.5x2 EE.
As you said that you don't have any problem to install on the local machine, the only thing that I can suggest you is to make sure:
1. .NET 2003 C++ compiler is installed on the server before the DS installation.
2. No existing or older version of MKS Toolkit on the server.