Symptoms

When you use the Command Line Builder to generate a command line for a report that uses explicit login credentials (user ID and password), the generated command line may not include the credentials.

More Information

When you edit a database login in the Command Line Builder and specify a user ID and password, the command line should include a "-login" parameter similar to the following:

-login!=username:pGNXQoGmNboLH/UtHMMong==

However, in some cases the Command Line Builder generates an "empty" login parameter:

-login!=: 

This occurs if you specify only the password (not the user ID), or if the user ID you enter is the same as the user ID saved in the report.

Workaround

Use a fake user ID in the Command Line Builder to force it to generate the login parameter, then change the user ID in the generated command line.

For example, suppose that the report is configured to use the user ID "bobuser" and you don't want to change this--you just want to set the password. When you edit the login, set the user ID to "fakeuser" and enter the password for "bobuser". This will produce a command line containing a login similar to the following:

-login!=fakeuser:pGNXQoGmNboLH/UtHMMong==

After pasting the generated command line into your batch file, script, etc., edit it to change the user ID portion of the login parameter to the correct user ID:

-login!=bobuser:pGNXQoGmNboLH/UtHMMong==

Do not change the password portion of the parameter.

Status

• Report Commander 2
  This issue has been resolved. Resolved in version 2.3.