While connecting to Administrator error

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
Ravarku
Participant
Posts: 1
Joined: Wed Dec 15, 2010 8:46 pm
Location: HYDERBAD

While connecting to Administrator error

Post by Ravarku »

Unknowingly did some change ,while working on a project, DataStage got crashed. I tried to re-connect getting below errors:

While connecting to Datastage Client
Error calling subroutine: DSR_NLS (Action=14); check DataStage is set up correctly in project Proj01
(Unable to load subroutine on host (30107))


While connecting to Administrator
Error calling subroutine: DSR_ADMIN (Action=36); check DataStage is set up correctly in project Proj01
(Unable to load subroutine on host (30105))


May anybody tell me how to fix it?

Thanks in advance
suresh
Suresh Ravirala
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard.

There is no real information about what is wrong, though it might be in the NLS subsystem. Try re-starting the engine tier. Otherwise restore the project from backup. You DO have a backup, don't you?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

I realize you said "unknowingly" but can you tell us where you were working and what you were working on / doing? Maybe that would help get us the information Ray was looking for...
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Can you connect to any other project using Administrator?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply