An Error Occurred in Retrieving Update Information Please Try Again Later Docker

Problem

Docker is one of the chief prerequisites for the installation and configuration of IBM Planning Analytics Workspace (Manus). Every so often, it is possible that customers may run into docker-related issues which might prevent functioning of Manus.

This technote aims to assistance y'all through some commonly faced docker issues.

For the purposes of this technote, all Powershell commands mentioned should be run from an elevated Powershell session.

Given beneath is a workflow diagram of the troubleshooting arroyo this technote adopts. The text that follows the diagram walks the reader through each of the steps that they may accept to take and explains the blocks in detail.

Diagram 1: PAW Troubleshooting Workflow

Issue 1: Cannot Access PAW in a browser/ Manus Services not coming upward

Relevant Symptoms:

i. "Planning Analytics Workspace is unavailable. Try again in a few minutes" in web-browser

2. "This site tin't be reached" in web-browser

- Make sure docker is upwards and running. Blazon the following commands in a powershell window to ensure the same:

          - get-go-service docker        

-Besides please check the Windows Services to make sure "Docker Engine" is in running country

- In a Powershell session, navigate to the Manus install directory, and type in./scripts/paw.ps1

- If the effect persists or if the script returns some error, jump toIssue 3

Issue 2: Admintool exits/Cannot launch Admintool

Relevant Symptoms:

one. "Something went incorrect at footstep 'Starting IBM Planning Analytics Administration Tool' Execution failed with leave lawmaking ane"when Showtime.ps1 script is executed

2. "Cannot start service admintool: failed to create endpoint admintool on network nat: HNS failed with error : Element not found.
Encountered errors while bringing up the project." when Start.ps1 is executed

- Open <Hand-install-Location>/log/admintool/up.log and take a await at the mistake message

- If the error message mentions HNS, skip toUpshot ivof this technote

- If the log file error bulletin does not mention HNS, from a powershell session, run ./scripts/paw.ps1

-If the issue persists, spring toIssue 3of this technote

Outcome 3: Running ./scripts/mitt.ps1 fails to restart services/returns HNS errors/Windows Filter Errors/ pa-gateway errors

Relevant Symptoms:

1." Recreating 32bf8925a845_32bf8925a845_32bf8925a845_admintool
Error: for <service-Proper noun> Cannot commencement <service-Proper name>: hcsshim: PrepareLayer failed in Win32: The handle is invalid. (0x6) layerId=<ID> flavor=one" when ./scripts/manus.ps1 is executed

2. "For pa-gateway Cannot start service pa-gateway: failed to create endpoint pa-gateway on network nat: HNS failed" when ./scripts/hand.ps1 is executed

3."HNS failed with fault: The file cannot be opened considering it is in the process of being deleted." when ./scripts/paw.ps1 is executed

4. "Cannot get-go service <service-Proper noun>: failed to create endpoint <service-proper name> on network nat: HNS failed with error: The object already exists."when ./scripts/paw.ps1 is executed

5. "Cannot Get-go service <service-name>: Container  is marked for removal and cannot be started"./scripts/hand.ps1 is executed.

6. "C:\Program Files\Docker\docker.exe: failed to register layer: re-exec error: exit condition 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\<id>\UtilityVM: The procedure cannot access the file because information technology is beingness used by another process" when ./scripts/paw.ps1 is executed

It is also recommended to get confirmation from your AV vendor that the AV does support Windows containers.

Should you accept to add exclusions to your AV scanning protocols, the following locations are recommended:

• C:\ProgramData\docker (Or the docker-root location in the daemon.json file)
• C:\ProgramData\Microsoft\Windows\HNS
• <Paw-Install-Location>

- In case of pa-gateway not starting, make sure aught is running on port lxxx. If port 80 is costless and upshot/error persists or other containers are not coming up, delight try the next footstep every bit below.

•               docker container rm <container-name>            

•               ./scripts/paw.ps1            

-In example of HNS Issues(Relevant symptom #'south 2/iii/4), jump to Issue four of this technote

Issue four: HNS Issues

It is sometimes possible that the docker networks get corrupted, which is where the Host Network Service (HNS comes into play)

-Run the script with the following syntax:

          .\WindowsContainerNetworking-LoggingAndCleanupAide.ps1 -Cleanup -ForceDeleteAllSwitches

- If the script runs successfully, please restart the estimator and and so run the paw.ps1 script from the scripts folder

- If it errors out, please run the following commands from Powershell

•               docker container run hello-earth:nanoserver            

•               docker run -p 80:80 hullo-world:nanoserver            

- If either of the above commands fail, the issue lies at the Docker level as the hello-world container is completely disjoint from any IBM Mitt services

- In that case, it is recommended to contact MS support for Docker bug. You can read more about that hither:

- In extreme cases, it may be required to re-prototype the server because of a docker network abuse at the registry level. Please contact IBM Support to discuss available options or any further troubleshooting.

[{"Business Unit":{"lawmaking":"BU059","label":"IBM Software w\/o TPS"},"Production":{"lawmaking":"SSD29G","characterization":"IBM Planning Analytics"},"Component":"Planning Analytics Workspace","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business concern":{"code":"LOB10","label":"Data and AI"}}]

shibatastals1937.blogspot.com

Source: https://www.ibm.com/support/pages/troubleshooting-planning-analytics-workspace-related-docker-issues

Share this post