none
PCNS Service (pcnssvc.exe) is crashing after configuring target RRS feed

  • Question

  • Hi,

    I am having some difficulty setting up the PCNS. I noticed every time I configure or add the PCNS target, the PCNS service (pcnssvc.exe) is crashing. If I remove the target, PCNS service will run just fine. Any one has experience this?

    Looking at the event viewer this is what I can see. Not much of information telling what is the reason for service to crash.

    Faulting application name: pcnssvc.exe, version: 4.1.3114.0, time stamp: 0x50ad5a0d
    Faulting module name: pcnssvc.exe, version: 4.1.3114.0, time stamp: 0x50ad5a0d
    Exception code: 0xc0000005
    Fault offset: 0x0000000000027880
    Faulting process id: 0x1af4
    Faulting application start time: 0x01d0f50ec3aa1c95
    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: 028a4c56-6102-11e5-80d3-3ca82a2117f7
    Faulting package full name: 
    Faulting package-relative application ID: 


    Appreciate any help here.

    Thanks!

    Gerard

    Tuesday, September 22, 2015 8:30 AM

All replies

  • Hi,

    as I can see you are deploying a very old build of the component.

    Is that the version your FIM is also running ?

    also what Version is our DC running ?

    /Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Tuesday, September 22, 2015 8:55 AM
  • Hi Peter,

    The DC is running on Windows 2012 R2 and the FIM version is  4.1.3419.0. I have installed latest PCNS version 4.1.3634.0 but getting the same result.

    Regards,

    Gerard

    Tuesday, September 22, 2015 9:06 AM
  • Hi,

    ok, that latest version is supporting 2012 R2 now.

    Hard to say from that error message, and I dont remember to had such a issue.
    Maybe someone other had that issue once and could help

    /Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Tuesday, September 22, 2015 9:16 AM
  • hello Gerard,

    Could you tell us what command are you using to configure PCNS? Maybe there's something (of course change names if you wish)


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Wednesday, September 23, 2015 7:13 AM
  • Hi Dominik,

    This is the command I run to configure the PCNS.

    pcnscfg.exe ADDTARGET /N:servername /A:FQDN /S:PCNSCLNT/FQDN /FI:"Domain Users" /FE:"Domain Admins" /F:1 /I:600 /D:False /WL:20 /WI:60

    Thanks!

    Gerard

    Wednesday, September 23, 2015 3:55 PM
  • I have same issue with version: 4.1.3634.0 (both PCNS and FIM are same version).

    DC OS: Windows Server 2012 R2

    FIM OS: Windows Server 2008 R2 (7601)

    Faulting application name: pcnssvc.exe, version: 4.1.3634.0, time stamp: 0x5522f510
    Faulting module name: pcnssvc.exe, version: 4.1.3634.0, time stamp: 0x5522f510
    Exception code: 0xc0000005
    Fault offset: 0x0000000000027880
    Faulting process id: 0x934
    Faulting application start time: 0x01d0f9d89bbdcc42
    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: d997a832-65cb-11e5-80ca-00155d5c163e

    Configuration:

    Pcnscfg.exe addtarget /n:PCNS /a:FIM.domain.com /s:PCNS/FIM.domain.com /fi:PasswordSyncUsers /f:3


    Jason

    Monday, September 28, 2015 10:39 AM
  • I found same error using MIM (and PCNS distributed with MIM) installed on Win 2012 R2 (DC is as well on Win 2012 R2).

    Borys Majewski, Identity Management Solutions Architect (Blog: IDArchitect.NET)

    Friday, October 2, 2015 10:32 AM
  • Just an update, I tried isolating the issue. It seems that the issue is only happening in one specific AD server. In the other AD server, the PCNS service is running fine after adding the target server and verified password sync is working as expected. 

    Still trying to figure out what is causing the issue on the other AD server.

    Thursday, October 8, 2015 2:06 AM
  • Hi Peter,

    The DC is running on Windows 2012 R2 and the FIM version is  4.1.3419.0. I have installed latest PCNS version 4.1.3634.0 but getting the same result.

    Regards,

    Gerard

    This week I faced the same with exactly the same versions. But now (nearly seconds ago) when upgraded FIM to 4.1.3646.0, PCNS started working.

    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Thursday, October 15, 2015 7:12 PM
  • I have same issue with version: 4.1.3634.0 (both PCNS and FIM are same version).

    DC OS: Windows Server 2012 R2

    FIM OS: Windows Server 2008 R2 (7601)

    Faulting application name: pcnssvc.exe, version: 4.1.3634.0, time stamp: 0x5522f510
    Faulting module name: pcnssvc.exe, version: 4.1.3634.0, time stamp: 0x5522f510
    Exception code: 0xc0000005
    Fault offset: 0x0000000000027880
    Faulting process id: 0x934
    Faulting application start time: 0x01d0f9d89bbdcc42
    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: d997a832-65cb-11e5-80ca-00155d5c163e

    Configuration:

    Pcnscfg.exe addtarget /n:PCNS /a:FIM.domain.com /s:PCNS/FIM.domain.com /fi:PasswordSyncUsers /f:3


    Jason

    Jason, all,

    try updating your FIM to build 4.1.3646.0. For me - worked and solved.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Thursday, October 15, 2015 7:13 PM
  • I tried upgrading FIM to version 4.1.3646 but PCNS is still having the same issue.

    Monday, October 19, 2015 5:06 AM
  • Just an update, I tried isolating the issue. It seems that the issue is only happening in one specific AD server. In the other AD server, the PCNS service is running fine after adding the target server and verified password sync is working as expected. 

    Still trying to figure out what is causing the issue on the other AD server.


    The easiest way to figure this out is going to be to get a support case open with Microsoft. You can collect a crash dump when the process dies and someone can debug that.

    Monday, October 19, 2015 5:43 PM
    Moderator
  • Hi Borys,

    I get the same error with MIM 2016 and Windows Server 2012R2 . Once I add a target the sevices crashes. Did you found a solution for it? I have a Lab, same Versions, but Patchlevel 2/2015 and it workes fine. There are many different DLL Versions between the Crash dump in the Lab and the Production. So I will patch my Lab now.

    Update

    I patched my Lab. Now all Fileversion from the Dump are in the Lab and Production exactly the same. Lab works fine, so i think a part of the Configuration generate this error.

    • Edited by Junior_DD Thursday, October 22, 2015 11:59 AM
    Thursday, October 22, 2015 10:40 AM
  • Hi,

    Can you upload crash dumps somewher?

    I had a quick look at MIM's pcnssvc.exe, offset 0x27880 is referenced in PcnsSvc!CountServicePrincipalNameAssignments

    PcnsSvc!CPCNSConfig::CountServicePrincipalNameAssignments+0x3a9:
    00000000`00450cf9 488bce          mov     rcx,rsi
    00000000`00450cfc ff15064a0000    call    qword ptr [PcnsSvc!GetParent+0x1b18 (00000000`00455708)]
    00000000`00450d02 4885c0          test    rax,rax
    00000000`00450d05 741d            je      PcnsSvc!CPCNSConfig::CountServicePrincipalNameAssignments+0x3d4 (00000000`00450d24)qword ptr [PcnsSvc!GetParent+0x1b18 (00000000`00455708)]

    qword ptr [PcnsSvc!GetParent+0x1b18 (00000000`00455708)] holds a pointer to ldap_first_entry

    0:000> ln poi(00000000`00455708)
    (00007ff8`6b6515d0)   WLDAP32!ldap_first_entry   |  (00007ff8`6b651650)   WLDAP32!strlenW
    Exact matches:
        WLDAP32!ldap_first_entry (<no parameter info>)

    So I would probably look around SPNs and permissions.

    Cheers,
    Csaba


    Csaba

    Thursday, October 22, 2015 1:03 PM
  • I followed this document. http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-65-37/1323.25-_2D00_-Implementing-Password-Synchronization-with-PCNS.docx

    Here are the dumps

    Version=1
    EventType=APPCRASH
    EventTime=130900087813818831
    ReportType=2
    Consent=1
    ReportIdentifier=f0dd90ec-78e2-11e5-80c4-00155d50c90e
    IntegratorReportIdentifier=f0dd90eb-78e2-11e5-80c4-00155d50c90e
    NsAppName=pcnssvc.exe
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=pcnssvc.exe
    Sig[1].Name=Application Version
    Sig[1].Value=4.3.1935.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=55906014
    Sig[3].Name=Fault Module Name
    Sig[3].Value=pcnssvc.exe
    Sig[4].Name=Fault Module Version
    Sig[4].Value=4.3.1935.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=55906014
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=000000000001cc5c
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.400.8
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1031
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=e5a7
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=e5a77f0c4ef6a6f7f2b493df4466398f
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=72b4
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=72b41fbd0295d3e42ad88608bce2157e
    UI[2]=C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=PcnsSvc stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: pcnssvc.exe
    P2: 4.3.1935.0
    P3: 55906014
    P4: pcnssvc.exe
    P5: 4.3.1935.0
    P6: 55906014
    P7: c0000005
    P8: 000000000001cc5c
    P9: 
    P10: 

    Thanks a lot.

    Thursday, October 22, 2015 5:49 PM
  • I am getting this same crash in a MIM lab using version 4.3.1935 with PCNS of the same version.  I have tried a variety of versions of the PCNS service but they all crash as soon as I configure a target.

    I have no easy means of opening a case with Microsoft.

    My lab is a single computer that hold AD DS, SQL and MIM.  This always worked in the past with ILM and FIM.  Is there a problem with MIM and PCNS running on a DC?

    Randy

    Wednesday, August 3, 2016 1:32 PM
  • please try moving files under 

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

    out of that folder and reboot your server


    Jason

    • Proposed as answer by Randy Wiemer Monday, August 8, 2016 7:51 PM
    Wednesday, August 3, 2016 3:49 PM
  • That made a difference. 

    What does that file and folder path have to do with the PCNS service? 

    There was one file in the folder of type "sch" which the file properties GUI reports it to be a "SQL Server Replication Snapshot Schema Script"

    Randy


    Monday, August 8, 2016 3:39 PM
  • Great! Many Thanks!

    ***********************************

    please try moving files under 

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

    out of that folder and reboot your server


    Jason

    ************************************
    Thursday, August 18, 2016 2:22 AM
  • Wow, this work fine for me!! Thanks a lot!
    Friday, February 17, 2017 5:13 PM
  • Works wonders and thanks for this tip!
    It's an outdated Schema Cache.
    https://blogs.technet.microsoft.com/fieldcoding/2014/11/12/the-adsi-schema-cache-revealed/

    Was using PCNS v4.4.1302.0


    Danny Alvares, Senior Technology Consultant

    Monday, March 20, 2017 2:05 PM