Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace IBM i
Categories IBM i Access Family
Created by Guest
Created on Mar 28, 2017

ACS install crashes during the installation in Windows

During installation of the latest version of ACS we encountered a crash during the installation in Windows.
I investigated the install_acs_32_allusers.js and install_acs_32.js scripts and discovered the error to have the same reason.

In install_acs_32_allusers.js it fails in line 579 where the following code is found:

// Create the IBM directory if it does not exist
if (!fso.FolderExists(log_target)) {
fso.CreateFolder(log_target); // <<- line 579
Further study showed that the variable log_target had the value H:\

So how did it get this value?
It is initiated in the beginning of the script where HomePath and HomeDrive is retrieved from the DOS environment variables with the same name.
The code is here (commented lines are dropped):

HomePath = Shell0.ExpandEnvironmentStrings("%HOMEPATH%");
HomeDrive = Shell0.ExpandEnvironmentStrings("%HOMEDRIVE%");
HomePath = (HomeDrive + HomePath);

// Set all users install path
InstallPath = "C:\\Users\\Public";
DesktopPath = "C:\\Users\\Public\\Desktop";

target1 = (InstallPath + "\\IBM");
target2 = (InstallPath + "\\IBM\\ClientSolutions");

// Set log path
log_target = (HomePath + "\\IBM");

In our system the DOS environment variables HOMEPATH and HOMEDRIVE does not contain the default values that are normally found in a Windows 7 environment. This causes the error.
We do not have the possibility to change these settings.

I would suggest that log_target (log path) is set equal to the target2 so that the log file is located in the same directory as the installed programs.
So the line
log_target = (HomePath + "\\IBM");

Should be changed to
// Set log path
log_target = target2;

Use Case:

log_target = target2;

so that the log file is located in the same directory as the installed programs. And the installation script will not crash.

Idea priority Urgent
  • Guest
    Jul 21, 2017

    A solution to the reported issue is available in the July 2017 update.

  • Guest
    Apr 14, 2017

    A solution to the reported issue will be available in the July 2017 update.

  • Guest
    Apr 11, 2017

    IBM has received this requirement and is evaluating it. A response will be provided when evaluation is complete.