This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 93%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Going through my system logs today I discovered that both my Server 2019 Virtual Domain Controllers seem to have this error firing off every 2 minutes or so:
==
The Network Connectivity Assistant service terminated with the following service-specific error:
The request is not supported.
==
It seems to have started in the middle of the month (16th March), but gives me no more detail than the above to go on. Google doesn't seem to turn up anything revealing. I did not make any config changes on the 16th (last was the installation of the monthly OS patch on the 11th).
I'm not sure how to even begin to track this down - the event itself gives nothing and there does not appear to be another regular event pre-empting it other than that service entering the stopped state. Has anyone any insight into what may be the problem here? These are Hyper-V VMs running Windows Server 2019's usual cast of AD components and basically nothing else.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
What other roles are installed? Hopefully not RRAS vpn / direct access. Direct access would be a conflicting role, the multi-homing would also cause no end to grief for active directory DNS.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hello,
The only roles installed are:
Ok, what is the startup type? It should be set to Manual startup
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
DSPatrick,
It is set to Manual (Trigger Start).
Seems you'll need to get to the bottom of what is triggering it to run. As far as I know it's used for Direct Access (RRAS role). Procmon may help you in this regard.
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thanks; I have never used this before but I will see what it can turn up.
Looking at more recent logs, I actually have "Event 40" being flagged a second beforehand on these machines. It claims "The event logging service encountered an error when attempting to apply one or more policy settings." May be the cause (or related at least).
That's really vague and may or may not be related. In my opinion for these one-off unexplained issues; the much simpler / safer / quicker resolution is to stand up a new one for replacement.
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Process Monitor does not appear to run unfortunately!
Also, in my org getting anything new stood up is a lengthy process, precluding just making a new one.
Ah turns out if I run the exe through powershell it runs. Clicking does nothing.
I don't seem to be able to make sense of Process Monitor, but I did find that there seems to be a way to query the service to see its triggers. I get this:
sc qtriggerinfo NcaSvc
[SC] QueryServiceConfig2 SUCCESS
SERVICE_NAME: NcaSvc
START SERVICE
GROUP POLICY : 659fcae6-5bdb-4da9-b1ff-ca2a178d46e0 [MACHINE POLICY PRESENT]
START SERVICE
DOMAIN JOINED STATUS : 1ce20aba-9851-4421-9430-1ddeb766e809 [DOMAIN JOINED]
STOP SERVICE
DOMAIN JOINED STATUS : ddaf516e-58c2-4866-9574-c3b615d42ea1 [NOT DOMAIN JOINED]
Unfortunately nothing useful - those aren't GPO GUIDs, but some kind of status GUID.
I do get the same trigger results but do not have the event log errors. Seems something may be broken. When I run on to this sort of situation it is just too simple to stand up a new one for replacement so I don't ever bother or waste time trying to fix something like this.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Sounds good then, it's by far the simplest solution, after patching it should only take 30 mins or so to have the new one stood up. Might also take the opportunity to split the file server role off to another virtual machine which makes administration tasks less complex.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Can that be split? It selects automatically when I installed the role for AD.
Depends on what you meant I guess, it sounded like File / Print services.