[ISS Support Case] Aveva Watchdog Service Failure to Start during Installation

Last updated: December 2nd, 2025

Description

Client called in because during system Platform install the install failed with the error message: "Service 'AVEVA Watchdog' (Watchdog_Service) failed to start. Verify that you have sufficient privileges to start system services."

Author: Kevin Modlin
Published: December 2nd, 2025

Details:

Date Created:	03/22/2024
Case:	86714

Give feedback about this article

Recommended articles

[ISS Support Case] Remote Connection To the IDE are not working

building a new 2023 R2 SP1 really doing 5 virtual nodes. GR App1 App 2 Historian (Tools) Want IDE on the (tools) to access IDE on it. Created a default galaxy. When we get on the IDE to connect to the remote galaxy.

[ISS Support Case] ImpersonateUser failed(0x8000401a). ArchestrA Admin user has not been setup

See FAQ000010453 https://softwaresupportsp.aveva.com/#/okmimarticle/docid/faq000010453

[ISS Support Case] Cannot deploy to one node

Can ping the node in question, and can deploy to other nodes. Deployment in question hangs and never completes. Currently trying a system restore. see case960168375 [Solution] With the platform undeployed and MSIExec.exe process stopped on the remote node, went into C:\Program Files( x86)\ArchestrA\Framework\FileRepository\ and renamed the Galaxy Name folder in here. Deployed the platform again. This folder was recreated and deployment worked. see also 960147737 for res:Added CNA user to be part of Administrators group on GR and remote node. Ran CNA utility on both nodes. Rebooted and we were able to deploy successfully.

[ISS Support Case] What order should I Reboot Galaxy Nodes

Might have an issue but still investigating. Currently trying to confirm a sequence to reboot Galaxy nodes. Has the following: A GR A couple of AOS nodes A Historian Seeing an issue where the historian seems to be not getting data from AOS nodes, then at a later time it back fills the data.