Planning Analytics

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson

Hi Luther, so sorry for the trouble you are having.    Can you provide some more details ? 

What version of PAW are you running ?
What is the exact symptom or error message ?
Are you up to date on Win 16 patches ?
Can you paste the output from the systeminfo  command here (run from a command prompt) ?

Also please note that you are running an older version of Docker, current version is 18.x. I am not recommending you update necessarily, just FYI at this point

------------------------------
Scott WHITEHEAD
------------------------------

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------
#PlanningAnalyticswithWatson

Did your build/version of Windows Server 2016 change due to the Windows Updates?  I believe the main Versions of Windows Server 2016 are 1607(GA), 1709, 1803, 1809 so far. 1903 may just be Windows 10, I'm not sure. Type "WinVer" in a command prompt to see the version/build information. The link below is for an article at Microsoft that talks about compatibility between containers and their OS version, versus the Docker host Windows Server 2016 version.

Anyway, if the version of Windows Server 2016 changed due to applying Windows updates(was 1803 last week and is now 1809), the PAW containers installed with the original host OS version will not start per the article.   The fix might be the equivalent of doing a PAW upgrade, and re-running ./Start.ps1 so that the PAW containers are refreshed under the new host version of Windows Server 2016. 

Getting previously created content may be a challenge since you can't start old PAW so you can't use the Lifecycle Management tool in PA Administration to export workspace assets. I don't know if the /scripts/restore.ps1 (if you have a /scripts/backup.ps1 produced backup file) will reset the refreshed PAW to the original version that is no longer functioning.

So a first step might be getting an old backup of PAW/Docker AND Windows 2016 restored from before the Windows Updates, and extracting the workspace assets. Then doing the Windows Updates and ./Start.ps1 process. That might require some bribery though for a restore like that, unless its a VM.

When reading the following article, I believe that PAW uses "Process Containers", not the "Hyper-V Containers" that Windows also supports on Docker.

I also read somewhere that Microsoft is smoothing this version issue out, but I lost that link.

Windows Container Version Compatibility

Microsoft		remove preview
Windows Container Version Compatibility How Windows can run build and run containers across multiple versions View this on Microsoft >

------------------------------
Walter Coffen
QueBIT Consulting, LLC
------------------------------

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson

Hi,
I owe an explanation and apologies for the delay in writing back to what Scott and Walter have written. 

PAW version--> I got the version associated to PA 2.0.6 --> Part number --> CNWN4ML --> obtained from link https://www-01.ibm.com/support/docview.wss?uid=ibm10729353.
I am giving the whole description because I do not exactly remember the number.

Docker was working. It was PAW that stopped working.
Why I thought Docker was not working was because "Hello-World" failed with the below error.
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImag
e \\?\D:\Docker\windowsfilter\9633f0d248eb6124537eca35ecafc3aed37ab3107eab21b03ecb887eda9d2cf3\UtilityVM: The system can
not find the path specified.
See 'C:\Program Files\Docker\docker.exe run --help'.
I later Found that "Hello-World" was out of date or does not work anymore and was told to run "docker run -it --rm docker/surprise".  This works confirming that it was not docker.

Now to PAW, I have started ".\Start.ps1" and got this error. I am also attaching the log.
Install/Update IBM Planning Analytics Docker images (y/n)? (default n): y
Installing/Updating IBM Planning Analytics Docker images
Loading image file D:\PAW-2.0.6\images\images.tar, this may take a while...
Start the Administration Tool? (default y): y
Starting IBM Planning Analytics Workspace Administration Tool, please wait...Something went wrong at step 'Starting IBM
Planning Analytics Administration Tool...'
Execution failed with exit code 1

How do we recover from here? I am have attached the log. Can someone please let me know where the issue is? I wanted to rebuild the server but having known that Docker is not the problem, want to recover than rebuild. Please let me know if there are questions.

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

Original Message:
Sent: Fri June 14, 2019 09:14 AM
From: Walter Coffen
Subject: Docker stopped working after working for more than 6 months - win 2016

Did your build/version of Windows Server 2016 change due to the Windows Updates?  I believe the main Versions of Windows Server 2016 are 1607(GA), 1709, 1803, 1809 so far. 1903 may just be Windows 10, I'm not sure. Type "WinVer" in a command prompt to see the version/build information. The link below is for an article at Microsoft that talks about compatibility between containers and their OS version, versus the Docker host Windows Server 2016 version.

Anyway, if the version of Windows Server 2016 changed due to applying Windows updates(was 1803 last week and is now 1809), the PAW containers installed with the original host OS version will not start per the article.   The fix might be the equivalent of doing a PAW upgrade, and re-running ./Start.ps1 so that the PAW containers are refreshed under the new host version of Windows Server 2016. 

Getting previously created content may be a challenge since you can't start old PAW so you can't use the Lifecycle Management tool in PA Administration to export workspace assets. I don't know if the /scripts/restore.ps1 (if you have a /scripts/backup.ps1 produced backup file) will reset the refreshed PAW to the original version that is no longer functioning.

So a first step might be getting an old backup of PAW/Docker AND Windows 2016 restored from before the Windows Updates, and extracting the workspace assets. Then doing the Windows Updates and ./Start.ps1 process. That might require some bribery though for a restore like that, unless its a VM.

When reading the following article, I believe that PAW uses "Process Containers", not the "Hyper-V Containers" that Windows also supports on Docker.

I also read somewhere that Microsoft is smoothing this version issue out, but I lost that link.

Windows Container Version Compatibility

Microsoft		remove preview
Windows Container Version Compatibility How Windows can run build and run containers across multiple versions View this on Microsoft >

------------------------------
Walter Coffen
QueBIT Consulting, LLC

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson

Hi Luther, take a look at this Technote that discusses Docker troubleshooting:

https://www-01.ibm.com/support/docview.wss?uid=ibm10881484

Also this from your log:

Cannot start service admintool: container 219f3cf0f096a5513d4e502294f9d8671db15651849321030a9b0934de5844e9 encountered an error during CreateContainer: failure in a Windows system call: The system cannot find the file specified.

Makes me think there may be something to Walter's response.

Failing this you really need to open a support case at IBM Support Community

Ibm		remove preview
IBM Support Community View this on Ibm >

------------------------------
Scott WHITEHEAD
------------------------------

Original Message:
Sent: Wed June 19, 2019 11:45 AM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi,
I owe an explanation and apologies for the delay in writing back to what Scott and Walter have written. 

PAW version--> I got the version associated to PA 2.0.6 --> Part number --> CNWN4ML --> obtained from link https://www-01.ibm.com/support/docview.wss?uid=ibm10729353.
I am giving the whole description because I do not exactly remember the number.

Docker was working. It was PAW that stopped working.
Why I thought Docker was not working was because "Hello-World" failed with the below error.
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImag
e \\?\D:\Docker\windowsfilter\9633f0d248eb6124537eca35ecafc3aed37ab3107eab21b03ecb887eda9d2cf3\UtilityVM: The system can
not find the path specified.
See 'C:\Program Files\Docker\docker.exe run --help'.
I later Found that "Hello-World" was out of date or does not work anymore and was told to run "docker run -it --rm docker/surprise".  This works confirming that it was not docker.

Now to PAW, I have started ".\Start.ps1" and got this error. I am also attaching the log.
Install/Update IBM Planning Analytics Docker images (y/n)? (default n): y
Installing/Updating IBM Planning Analytics Docker images
Loading image file D:\PAW-2.0.6\images\images.tar, this may take a while...
Start the Administration Tool? (default y): y
Starting IBM Planning Analytics Workspace Administration Tool, please wait...Something went wrong at step 'Starting IBM
Planning Analytics Administration Tool...'
Execution failed with exit code 1

How do we recover from here? I am have attached the log. Can someone please let me know where the issue is? I wanted to rebuild the server but having known that Docker is not the problem, want to recover than rebuild. Please let me know if there are questions.

Thanks,
Luther.

------------------------------
Luther Rapaka

Original Message:
Sent: Fri June 14, 2019 09:14 AM
From: Walter Coffen
Subject: Docker stopped working after working for more than 6 months - win 2016

Did your build/version of Windows Server 2016 change due to the Windows Updates?  I believe the main Versions of Windows Server 2016 are 1607(GA), 1709, 1803, 1809 so far. 1903 may just be Windows 10, I'm not sure. Type "WinVer" in a command prompt to see the version/build information. The link below is for an article at Microsoft that talks about compatibility between containers and their OS version, versus the Docker host Windows Server 2016 version.

Anyway, if the version of Windows Server 2016 changed due to applying Windows updates(was 1803 last week and is now 1809), the PAW containers installed with the original host OS version will not start per the article.   The fix might be the equivalent of doing a PAW upgrade, and re-running ./Start.ps1 so that the PAW containers are refreshed under the new host version of Windows Server 2016. 

Getting previously created content may be a challenge since you can't start old PAW so you can't use the Lifecycle Management tool in PA Administration to export workspace assets. I don't know if the /scripts/restore.ps1 (if you have a /scripts/backup.ps1 produced backup file) will reset the refreshed PAW to the original version that is no longer functioning.

So a first step might be getting an old backup of PAW/Docker AND Windows 2016 restored from before the Windows Updates, and extracting the workspace assets. Then doing the Windows Updates and ./Start.ps1 process. That might require some bribery though for a restore like that, unless its a VM.

When reading the following article, I believe that PAW uses "Process Containers", not the "Hyper-V Containers" that Windows also supports on Docker.

I also read somewhere that Microsoft is smoothing this version issue out, but I lost that link.

Windows Container Version Compatibility

Microsoft		remove preview
Windows Container Version Compatibility How Windows can run build and run containers across multiple versions View this on Microsoft >

------------------------------
Walter Coffen
QueBIT Consulting, LLC

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------
#PlanningAnalyticswithWatson

Hi Luther.  The error suggests that something isn't quire right with the image files that you have on the machine, specifically the image file for the admintool.  You could try re-extracting the install files.  That said, if PAW was previously working, there is no need to install/update the images or start the admin tool.  It would be interesting to see what happens if you respond N to both prompts when running Start.ps1.

------------------------------
Tim Fischer
------------------------------

Original Message:
Sent: Wed June 19, 2019 11:45 AM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi,
I owe an explanation and apologies for the delay in writing back to what Scott and Walter have written. 

PAW version--> I got the version associated to PA 2.0.6 --> Part number --> CNWN4ML --> obtained from link https://www-01.ibm.com/support/docview.wss?uid=ibm10729353.
I am giving the whole description because I do not exactly remember the number.

Docker was working. It was PAW that stopped working.
Why I thought Docker was not working was because "Hello-World" failed with the below error.
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImag
e \\?\D:\Docker\windowsfilter\9633f0d248eb6124537eca35ecafc3aed37ab3107eab21b03ecb887eda9d2cf3\UtilityVM: The system can
not find the path specified.
See 'C:\Program Files\Docker\docker.exe run --help'.
I later Found that "Hello-World" was out of date or does not work anymore and was told to run "docker run -it --rm docker/surprise".  This works confirming that it was not docker.

Now to PAW, I have started ".\Start.ps1" and got this error. I am also attaching the log.
Install/Update IBM Planning Analytics Docker images (y/n)? (default n): y
Installing/Updating IBM Planning Analytics Docker images
Loading image file D:\PAW-2.0.6\images\images.tar, this may take a while...
Start the Administration Tool? (default y): y
Starting IBM Planning Analytics Workspace Administration Tool, please wait...Something went wrong at step 'Starting IBM
Planning Analytics Administration Tool...'
Execution failed with exit code 1

How do we recover from here? I am have attached the log. Can someone please let me know where the issue is? I wanted to rebuild the server but having known that Docker is not the problem, want to recover than rebuild. Please let me know if there are questions.

Thanks,
Luther.

------------------------------
Luther Rapaka

Original Message:
Sent: Fri June 14, 2019 09:14 AM
From: Walter Coffen
Subject: Docker stopped working after working for more than 6 months - win 2016

Did your build/version of Windows Server 2016 change due to the Windows Updates?  I believe the main Versions of Windows Server 2016 are 1607(GA), 1709, 1803, 1809 so far. 1903 may just be Windows 10, I'm not sure. Type "WinVer" in a command prompt to see the version/build information. The link below is for an article at Microsoft that talks about compatibility between containers and their OS version, versus the Docker host Windows Server 2016 version.

Anyway, if the version of Windows Server 2016 changed due to applying Windows updates(was 1803 last week and is now 1809), the PAW containers installed with the original host OS version will not start per the article.   The fix might be the equivalent of doing a PAW upgrade, and re-running ./Start.ps1 so that the PAW containers are refreshed under the new host version of Windows Server 2016. 

Getting previously created content may be a challenge since you can't start old PAW so you can't use the Lifecycle Management tool in PA Administration to export workspace assets. I don't know if the /scripts/restore.ps1 (if you have a /scripts/backup.ps1 produced backup file) will reset the refreshed PAW to the original version that is no longer functioning.

So a first step might be getting an old backup of PAW/Docker AND Windows 2016 restored from before the Windows Updates, and extracting the workspace assets. Then doing the Windows Updates and ./Start.ps1 process. That might require some bribery though for a restore like that, unless its a VM.

When reading the following article, I believe that PAW uses "Process Containers", not the "Hyper-V Containers" that Windows also supports on Docker.

I also read somewhere that Microsoft is smoothing this version issue out, but I lost that link.

Windows Container Version Compatibility

Microsoft		remove preview
Windows Container Version Compatibility How Windows can run build and run containers across multiple versions View this on Microsoft >

------------------------------
Walter Coffen
QueBIT Consulting, LLC

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson

To see if the micro services are actually running, run the command
docker ps

If it shows all the services, go to the unzipped install directory and under 'scripts', run the command
./paw.ps1

If it doesn't show any services, under the 'scripts' folder, run the command
./admintool.ps1

If none works, check the folder 'D:\Docker\containers' to see if there're still container objects. Also check the folder 'D:\windowsfilter'. It builds cached files while loading. The log says it couldn't find a particular file there.

If you can access the files but it still doesn't work, then you may want to consider removing the containers and reload.
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_paw_uninstall.html

Hope it helps.

------------------------------
Tom Kim
------------------------------

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson

Typo => 'D:\windows' should change to 'D:\Docker\windowsfilter'.
Also check the antivirus and make sure it's not blocking docker to access this folder and entire Docker folder.

------------------------------
Tom Kim
------------------------------

Original Message:
Sent: Fri June 21, 2019 04:39 PM
From: Tom Kim
Subject: Docker stopped working after working for more than 6 months - win 2016

To see if the micro services are actually running, run the command
docker ps

If it shows all the services, go to the unzipped install directory and under 'scripts', run the command
./paw.ps1

If it doesn't show any services, under the 'scripts' folder, run the command
./admintool.ps1

If none works, check the folder 'D:\Docker\containers' to see if there're still container objects. Also check the folder 'D:\windowsfilter'. It builds cached files while loading. The log says it couldn't find a particular file there.

If you can access the files but it still doesn't work, then you may want to consider removing the containers and reload.
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_paw_uninstall.html

Hope it helps.

------------------------------
Tom Kim

Original Message:
Sent: Wed June 05, 2019 05:13 PM
From: Luther Rapaka
Subject: Docker stopped working after working for more than 6 months - win 2016

Hi all,
Has anyone run into issues where Docker stopped working after windows 2016? Subsequent to this, PAW stopped working.
I called IBM and they say it might be due to windows patches but not confirmed. How can it be confirmed? What's the best alternative?
Can someone help me how you managed the situation and what steps you took from happening again? 

Our Docker version "Docker version 17.06.2-ee-16, build 9ef4f0a". 

Thanks,
Luther.

------------------------------
Luther Rapaka
------------------------------

#PlanningAnalyticswithWatson