Force the docker daemon to use a new data directory ( to host the images and containers of the new PAW version ) before you install the new PAW version:
Going forward I assume your C:\ drive has a free disk space of at least 100 GB.
Create a new empty new data directory for instance C:\ProgramData\dockernew
Is there a docker configuration file daemon.json in the old data directory ?
By default it is C:\ProgramData\docker\config\daemon.json
If not create one using a text-editor.
Using it, point the docker daemon to the new data directory:
{
"data-root": "C:\\ProgramData\\dockernew"
}
After creating the docker configuration file daemon.json stop and start the docker daemon ( aka the Docker Engine running as a Windows Service ) using the Windows Services (services.msc).
Now install the new PAW version using the PAW PowerShell script start.ps1
It will deploy the images and containers of the new PAW version into the new data directory whose size will increase accordingly.
Link:
https://www.ibm.com/support/pages/how-change-docker-images-and-containers-location-windows-2016-server
How to change docker images and containers location with Windows 2016 Server?
------------------------------
Bernd Siebert
------------------------------
Original Message:
Sent: Sat August 10, 2024 09:30 AM
From: Faisal Kamal
Subject: Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images'
Hi Ted,
I've been struggling with this issue since yesterday and am eager to find a solution while waiting for IBM Support's response.
I'm in the process of updating PAW version 2.0.95 on my Virtual Machine running Windows Server 2016. However, the update stops when the Docker images begin installing or updating, and I encounter an error message.
Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images'
rename C:\ProgramData\docker\image\windowsfilter\layerdb\tmp\write-set-965581994 C:\ProgramData\docker\image\windowsfilt
er\layerdb\sha256\75d50a46f4611e207d60b2feae1a15f475f849167fd51c5c034f14010bdf7c2d: Access is denied.
For context, the network and antivirus whitelist policies are identical to those on another Virtual Machine, which successfully runs PAW version 2.0.95.
This server is intended as a backup and is a clone of the other server.
I've already added a new registry folder named RestrictAnonymous (which didn't exist before) and created a QWORD key with a value of 0. I then ran gpupdate /force, and it completed successfully. However, the same error message still appears when I run ./Start.ps1 in the installation folder.
If anyone has suggestions on what to do next, I would greatly appreciate a prompt response.
Regards,
Faisal
------------------------------
Faisal Kamal
Original Message:
Sent: Thu February 04, 2021 10:57 AM
From: Theodore Johnson
Subject: Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images'
I wanted to share some information as I didn't want anyone else to spend day's looking for a solution.
The error message that I was running into:
We are installing PAW 2.0.60 on our development server (Win 2016). Updating current install of PAW 2.0.53
The script ran with all the checks ticked but was stuck at "Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images. rename D:\ProgramData\Docker\image\windowsfilter\layerdb\tmp\write-set-906360939 D:\ProgramData\Docker\windowsfilter\layerdb\sha256\9805c96771a355f8eacf4ec4f7daaf8f67d1b3f7cd5780556085a4db507ddba6: Access Denied'".
The client has MS Defender disabled and all of the AV software was put in to "Passive" mode.
The resolution to my problem above was the "hardening" of Active Directory. Many customers will setup Group Policies to restrict actions and functions on the local system. For this instance LSA (Local Security Authority) Network access: Do not allow anonymous enumeration of SAM account and shares was set to "Enable"
and the Registry key is
HKLM\system\currentcontrolset\control\lsa\restrictanonymous
Setting the value of the QWORD to 0 and running gpupdate /force from command line will then allow the update of Planning Analytics workspace.
If you have a single GPO domain you will need to just modify the registry prior to running the .\Start.ps1
Hope this will save someone some time.
Thanks,
Ted
------------------------------
Theodore Johnson
Original Message:
Sent: Thu February 13, 2020 03:42 PM
From: Gaby Y
Subject: Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images'
Hi All,
We are installing PAW 2.0.48 on our development server (Win 2016).
The script ran with all the checks ticked but was stuck at "Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images. re-exec error: exit status 1: output: ProcessUtilityVMImage \\?\C:\ProgramData\docker\windowsfilter\9805c96771a355f8eacf4ec4f7daaf8f67d1b3f7cd5780556085a4db507ddba6\UtilityVM: The process cannot access the file'".
I found this post which has the same error message so I stopped the Symantec 12.1.6 and ran the script again. Stil stuck.
https://www.ibm.com/support/pages/installation-issues-paw-windows-2016-when-symantec-antivirus-running
Tried Prune the docker, deleted all the installation files and re-extracted them somewhere else. Still stuck at the same issue.
Has anyone ever come across that? How do I resolve this?
Regards
Gaby
------------------------------
Gaby Yuan
------------------------------
#PlanningAnalyticswithWatson