IBM Support

DataStage login error: Invalid account name supplied (39129).

Troubleshooting


Problem

When DataStage clients attempt to login to a specific project, the login fails with the following error: "Failed to connect to host: hostname, project: project_name (Invalid account name supplied (39129))"

Resolving The Problem

If the login error only occurs when connecting to a newly created project, or only affects a new user of the project, and the operating system is a AIX, Linux, or other Unix OS, then examine file permissions in the project directory to ensure that the OS userid attempting to login has Read, Write, and Execute permission (either via ownerid, group, or public permissions) to all files and directories within that project.

If instead the login errors occur for a project which was previously useable, but now login fails for all users, then the most likely cause is that the project name is now missing from the UV.ACCOUNTS file in the DSEngine directory. The UV.ACCOUNTS file contains the location of all project directories. If you attempt to login to a project name that is not listed in the account file, then error "Invalid account name supplied (39129)" will occur.

To confirm if the project is missing from UV.ACCOUNT, use the following steps:

  1. Open a command prompt on the DataStage server machine.
  2. Change to the DSEngine directory, i.e.:
    cd /Ascential/DataStage/DSEngine
    or
    cd /opt/IBM/InformationServer/Server/DSEngine
  3. If not using Windows, enter the following command including the leading period:
    . ./dsenv
  4. Start the UV shell:
    bin/uvsh
    (on Windows, bin\uvsh)
  5. Enter shell command:
    LIST UV.ACCOUNT
    and see if the name of project with problem appears in list. If site has a large number of projects, use the following alternate command but specify the project name as parameter (the project name is case sensitve and must match exactly the case of the actual project name):
    LIST UV.ACCOUNT project_name

If the project directory exists, but the UV.ACCOUNT file is missing the project entry, then you may need to restore UV.ACCOUNT (if backup was recent and no other projects were created after that backup). The alternative is to manually delete the project, re-add a new project with the same name, and then import copies of saved jobs (from dsx files for example).

For DataStage v7.5, you could simply rename the original project directory, delete UV.ACCOUNT and scheme references (see manual project delete steps below), create a new project with same name as deleted project, and then swap in the saved contents from the original project.

Note that if you recover the UV.ACCOUNT from a backup prior to removing the project, it may be out of sync with UV_SCHEMA which also contains a reference to the project. To check if a project reference exists in the UV_SCHEMA, you can issue the following command:
LIST UV_SCHEMA

If the UV_SCHEMA is out of sync with the UV.ACCOUNT file (entry exists in schema that does not exist in account file or vice versa) you can attempt to get the 2 back in sync with the following 2 commands:
VERIFY.SQL SCHEMA
project_name FIX

The above steps assume that you still wish to recover and use the project. If instead the error is the result of an incomplete project removal (for example, project reference was removed from account file, but still exists in the xmtea repository) and you actually wish to remove all references to the project, then use the steps in the following technote to manually delete a project (ignoring the xmeta/dstagewrapper steps if using DataStage 7.5 or earlier):
How do you manually delete an IBM InfoSphere DataStage project?

[{"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.1;8.0;7.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21457422