IBM Support

Fail to connect to all the projects from Information Server clients with "Error calling subroutine: *DataStage*DSR_PROJECT (Action=1); check DataStage is set up correctly in project <name>. (Subroutine failed to complete successfully (30107))"

Technote (troubleshooting)


Fail to connect all the projects from Information Server clients: Designer, Director and Administrator with the following error:

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

Diagnosing the problem

Here following steps to troubleshoot this issue:

  • Create an empty file called errlog under DSEngine directory. Make sure it does not have an extension and all users have read and write permission to it.

    For example, the errlog has:
    program "*DataStage*DSR_TRACE*; Line 222, Message [046019]

    This means it is reporting Invalid GCI subroutine.
  • Make sure all the GCI libraries and dependent libraries do exist. You can run the following program to see which GCI libraries report errors:
    1. start a command window on the DataStage server
    2. cd c:\IBM\InformationServer\Server\DSEngine
    3. .\bin\uvsh.exe
    6. COMO OFF

      press N to stop paging the results are captured in DSEngine\&COMO&\GCI.NTMAP.B.OUT

      For exmaple, here are some possible errors:
      COMO GCI.NTMAP.B.OUT established 08:38:42 26 MAY 2011
      Error 126 loading GCI library
      The specified module could not be found.
      Error 126 loading GCI library
      The specified module could not be found.
      Error 126 loading GCI library
      The specified module could not be found.
      Error 126 loading GCI library E:\IBM\InformationServer\Server\DSEngine\bin\DSOLEint.dll.
      The specified module could not be found.
      [2JGCI libraries currently loaded
  • Check the PATH system variable and verify it includes the following. Information server is looking at the following path for those libraries and their dependent libraries.

    C:\IBM\InformationServer\Server\DSEngine\bin\dsdgci.dll. C:\IBM\InformationServer\Server\DSEngine\bin\dsradmin.dll C:\IBM\InformationServer\Server\DSEngine\bin\DSPlugin.dll C:\IBM\InformationServer\Server\DSEngine\bin\DSOLEint.dll
  • If the PATH is set correctly. Use Dependency Walker to check to make sure those dependent libraries exist.

    Obtain the program called Dependency Walker via the internet (free version) to determine if any dlls or components are missing that are required for the software to function. Once down loaded extract to a local folder and run the depends.exe program. Once the program comes up go to File Open and navigate to the .dll file that appears problematic. For example navigate to the folder C:\IBM\InformationServer\Server\DSEngine\bin. Select dsdgci.dll and then select Open. A report will be generated that will list any missing components that are required for use with the software.
  • If there are no errors GCI subroutines can be called in two different ways one of which requires a catalog entry. The error message Invalid GCI subroutine suggests that something might be wrong with the catalog entry.

    To check the catalog start a command window on the DataStage server:
    1. cd c:\IBM\InformationServer\Server\DSEngine
    2. .\bin\uvsh.exe
    4. MAP
    5. COMO OFF

      Press N to stop paging. The results are captured in DSEngine\&COMO&\MAP.OUT
  • Problems can also happen if important directories are not near the start of very large PATH. For example, in cases where path is more than 1024 bytes, and Information Server directories C:\IBM\InformationServer\Server\DSEgine\bin or C:\IBM\InformationServer\Server\PXEngine\bin occurred late in path, either after 1024 bytes or after other PATH directories which have access failures, DataStage user logins may fail with the same 30107 error due to unable to load libraries from those directories. Examine system PATH and confirm if size is greater than 1024 and whether the above 2 directories are near the start of path.

Resolving the problem

In this case the PATH environment variable had to be updated so it contained the Information Server path(s) listed below:


    After the PATH was changed DataStage services were stopped and restarted to resolve the issue.

    In another case the PATH did contain the following 2 directories, but they were at the end of a very long PATH string:

    Moving those 2 directories to the start of System PATH and then rebooting the machine solved the issue.

Document information

More support for: InfoSphere Information Server

Software version: 8.0.1, 8.1, 8.5, 8.7

Operating system(s): Windows

Reference #: 1501033

Modified date: 25 October 2014

Translate this page: