KC Plug In does not start - did not start in 120 seconds -

Issue

The KC Plug-in Service does not start. The event logs and the KC Plug-In logs don't show any errors. other than to indicate that the service did not start in 120 seconds.

Cause

One of the possible causes is that KIC Plugin is trying to resolve and UNC path and while attempting to start the service it goes in timeout.

Solution

1) Test or try to disable the UNC path that needs name resolutions. 

2) Extend the Service timeout:

• Regedit
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
• Add DWORD: ServicesPipeTimeout
• Set to 300000 (5 minutes)
• Reboot the system

Level of Complexity 

Moderate

Applies to  

References

Add any references to other internal or external articles