none
PCNS 4.1.3114.0 and Windows Server 2016 Core RRS feed

  • Question

  • Hi,

    Is PCNS v 4.1.3114.0 supported on Windows Server 2016 Core?

    Also, if there's a resource online with this type of information about PCNS, I would greatly appreciate a link.

    Thank you!

    Wednesday, March 15, 2017 6:40 PM

Answers

  • I'm not aware of at reason it shouldn't work, but I don't believe there's a formal support statement for this thus far.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    • Proposed as answer by Thomas Houston Thursday, March 16, 2017 5:30 AM
    • Marked as answer by SamiVV Thursday, March 16, 2017 2:03 PM
    Wednesday, March 15, 2017 11:22 PM
    Moderator

All replies

  • I'm not aware of at reason it shouldn't work, but I don't believe there's a formal support statement for this thus far.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    • Proposed as answer by Thomas Houston Thursday, March 16, 2017 5:30 AM
    • Marked as answer by SamiVV Thursday, March 16, 2017 2:03 PM
    Wednesday, March 15, 2017 11:22 PM
    Moderator
  • Thank you!
    Thursday, March 16, 2017 2:03 PM
  • Hi, I noticed that PCNS is NOT working on Server 2016 Core, 10.0.14393 N/A Build 14393. The PCNS service crashed right after service startup with the obsurest of events:

    Faulting application name: pcnssvc.exe, version: 4.4.1302.0, time stamp: 0x580f1f96
    Faulting module name: pcnssvc.exe, version: 4.4.1302.0, time stamp: 0x580f1f96
    Exception code: 0xc0000005
    Fault offset: 0x000000000001cc5c
    Faulting process id: 0x138
    Faulting application start time: 0x01d3e6c59fc4d2b4
    Faulting application path: C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe
    Faulting module path: C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe
    Report Id: 150a9964-b0e8-4d0c-b71a-959b5b05904f
    Faulting package full name: 
    Faulting package-relative application ID: 

    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: pcnssvc.exe
    P2: 4.4.1302.0
    P3: 580f1f96
    P4: pcnssvc.exe
    P5: 4.4.1302.0
    P6: 580f1f96
    P7: c0000005
    P8: 000000000001cc5c
    P9: 
    P10: 

    Attached files:
    \\?\C:\Windows\Temp\WER21AF.tmp.appcompat.txt
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21DE.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_pcnssvc.exe_424b942b1258d2ba47c5059a91583aaf78aa4d_3c137965_cab_52df21ec\memory.hdmp
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_pcnssvc.exe_424b942b1258d2ba47c5059a91583aaf78aa4d_3c137965_cab_52df21ec\triagedump.dmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_pcnssvc.exe_424b942b1258d2ba47c5059a91583aaf78aa4d_3c137965_cab_52df21ec

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 150a9964-b0e8-4d0c-b71a-959b5b05904f
    Report Status: 4
    Hashed bucket: 

    Tuesday, May 8, 2018 12:12 PM
  • please try moving files under 

    C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\SchCache

    out of that folder and reboot your server

    source : https://social.technet.microsoft.com/Forums/en-US/4623edae-683c-4549-860d-9728044259ef/pcns-service-pcnssvcexe-is-crashing-after-configuring-target?forum=ilm2

    this worked for me for 3 distinct domain servers in a big project i am running

    Tuesday, April 16, 2019 7:21 AM
  • Has anyone validated this is a required step to get the PCNS service to work properly on Server 2016 Core?
    Friday, July 19, 2019 6:49 PM