Page 1 of 1

Unable to get into Designer & Director

Posted: Tue Jun 23, 2009 4:22 am
by Prashantoncyber
All of sudden ,we are not able to log in Designer & Director client (both from the clients on my machine as well as the clients on the server) after rebooting the server in post automatic install update of the .net & SDK from Microsoft.

Coming across the following errors:

On designer and director clients:

Error calling subroutine: *DataStage*DSR_PROJECT (Action=1); check DataStage is set up correctly in project Dbmig
(Subroutine failed to complete successfully (30107))

But can see the dropdown list of projects from Designer.

While login to Admin coming across following massage

Error calling subroutine: *DataStage*DSR.ADMIN (Action=36); check DataStage is set up correctly in project UV
(Subroutine failed to complete successfully (30107))

Error calling subroutine: *DataStage*DSR_PROJECT (Action=1); check DataStage is set up correctly in project ANALYZERPROJECT
(Subroutine failed to complete successfully (30107))

Search fetched the following post

viewtopic.php?t=120746&highlight=Subrou ... ly+(30107)

But need bit of elaboration on it..

Any help shall be appreciated.....

Posted: Tue Jun 23, 2009 4:32 am
by ArndW
from DOS, try to "TELNET {YourServer}" - does that work? If not, your DataStage did not start correctly.

Posted: Tue Jun 23, 2009 4:59 am
by Prashantoncyber
Telnet is disabled in this company....however Datastage did start correctly...

Can log into through IBM webconsole from client machine...

Can you please let me know where can find PATH variable just to make sure that this is correct based upon the response of above post link...

Posted: Tue Jun 23, 2009 4:56 pm
by ray.wurlod
Control Panel > System > Environment

Posted: Tue Jun 23, 2009 6:18 pm
by Prashantoncyber
found variable path as
D:\oracle\product\10.2.0\client_1\bin;D:\IBM\InformationServer\Server\DSComponents\bin;C:\PROGRA~1\MKS Toolkit\mksnt;C:\PROGRA~1\MKS Toolkit\bin;C:\PROGRA~1\MKS Toolkit\bin\X11;C:\PROGRA~1\MKS Toolkit\mksnt;D:\IBM\InformationServer\ASBNode\apps\jre\bin\classic;D:\IBM\InformationServer\ASBNode\lib\cpp;D:\IBM\InformationServer\ASBNode\apps\proxy\cpp\vc60\MT_dll\bin;C:\Program Files\Support Tools\;C:\Program Files\HP\NCU;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;C:\Program Files\Symantec\pcAnywhere\;D:\IBM\SQLLIB\BIN;D:\IBM\SQLLIB\FUNCTION;D:\IBM\SQLLIB\SAMPLES\REPL;D:\IBM\SQLLIB\BIN

Posted: Wed Jun 24, 2009 12:51 am
by ArndW
Even if TELNET is disabled by policy, you can still try to connect to this DS server machine as DS installs it's own telnet listener.

try "TELNET {YourServer}" - does that work?

Posted: Wed Jun 24, 2009 1:22 am
by ray.wurlod
It may be listening on port #2300 (because the MKS Toolkit telnetd listens on port #23). Try

Code: Select all

telnet servername 2300