How do I handle errors when I run the start script?

If running the ./scripts/paw.ps1 script doesn't restart services or returns Host Network Service (HNS) errors, Windows filter errors, or pa-gateway errors, you can try the following solutions.

Symptoms

One of the following messages appears when the ./scripts/paw.ps1 script runs.

  • C:\Program Files\Docker\docker.exe: failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\<id>\UtilityVM: The process cannot access the file because it is being used by another process.
  • Recreating 32bf8925a845_32bf8925a845_32bf8925a845_admintool Error: for <service-Name> Cannot start <service-Name>: hcsshim: PrepareLayer failed in Win32: The handle is invalid. (0x6) layerId=<ID> flavour=1"
  • For pa-gateway Cannot start service pa-gateway: failed to create endpoint pa-gateway on network nat: HNS failed.
  • HNS failed with error: The file cannot be opened because it is in the process of being deleted..
  • Cannot start service <service-Name>: failed to create endpoint <service-name> on network nat: HNS failed with error: The object already exists.
  • Cannot Start service <service-name>: Container is marked for removal and cannot be started.

What to do

Note: All PowerShell commands must be run from an elevated PowerShell session.
  1. If you see a windowsfilter error, it is possible that anti-virus software is preventing your Windows containers from starting. For more information, see Docker for Windows Server fails to pull image or start container. It is also recommended that you get confirmation from your anti-virus vendor that the anti-virus software does support Windows containers. If you need to add exclusions to your anti-virus 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
    • <Planning Analytics Workspace install location>
  2. If the pa-gateway is not starting, make sure that nothing is running on port 80. If port 80 is free and the issue persists or other containers don't start, try the following commands in a PowerShell window:
    • docker container rm <container-name> 
    • ./scripts/paw.ps1
  3. If you see HNS errors, see How do I handle errors with the Host Network Service (HNS)?.