PCNS V.4.3.1935.0 Microsoft identity Manager Password Change notification service failes when starting

stiana used Ask the Experts™
We are having isssues with PCNS (version 4.3.1935.0 of Microsoft Identity Manager Password Change Notification Service) on a Windows Server 2012 R2 domain controller against MIM 2016 (version 4.3.2064.0) that also runs on a Windows 2012 R2. PCNS-service stops when we are trying to start it.

This is the event id after service crash:

Log Name:      Application
Source        Application Error
Date:          29.03.2016 21:34:07
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EDU-DC01.elev.local
Faulting application name: pcnssvc.exe, version: 4.3.1935.0, time stamp: 0x55906014
Faulting module name: pcnssvc.exe, version: 4.3.1935.0, time stamp: 0x55906014
Exception code: 0xc0000005
Fault offset: 0x000000000001cbcc
Faulting process id: 0xeec
Faulting application start time: 0x01d189f1f5c5a2db
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: 3395f1bf-f5e5-11e5-80c1-0050569c7665
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2016-03-29T19:34:07.000000000Z" />
    <Security />
    <Data>C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe</Data>
    <Data>C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe</Data>
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
bbaoIT Consultant

any related log items found in Windows System Logs?

also what are the services that depending on  this service? you may check the list by right clicking the service name and choosing Properties.
Distinguished Expert 2018
The logs clearly saying that service is getting crashed

I guess that PCNS component you used is not compatible with 2012 R2 servers

Do you have any 2008 / 2008 R2 domain controllers? If so, please try to configure PCNS on that DC
Also make sure SPN is getting registered properly on PCNS service account
setspn -A PCNSCLNT/FIMsrv.Domain.com Domain\FIMSyncAccount

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial