DCOM's tag archives

61738644-F196-11D0-9953-00C04FD919C1 Launch Permissions - Event 10016 on Windows Server 2008 R2 (SharePoint 2007 & SharePoint 2010)

If you are running Windows Server 2003 or a pre Windows Server 2008 R2 build then please refer to this article: http://www.sharepointassist.com/2009/01/27/61738644-f196-11d0-9953-00c04fd919c1-launch-permissions/ . However, if you are running Windows Server 2008 R2 or higher follow the steps below to correct the Event 10016 DCOM error 61738644-F196-11D0-9953-00C04FD919C1 related to the IIS-WAMREG Admin Service. Always test these changes in your development and staging environment!!! The DCO...
READ THE FULL ARTICLE >>

Configuring Kerberos Authentication for SharePoint

When you install SharePoint you have a choice to use NTLM and Kerberos authentication. There's pros and cons for each and I'm not going to get into that here, let's just go through the steps for configuring Kerberos on a SharePoint site running on port 80. Prerequisites Download and install the Windows Server 2003 Service Pack 2 32-bit Support Tools Note that they will still run on a 64 bit machine. Install the Windows 2003 Admin Pack (AdminPak.msi) located in your server's %\windows\sys...
READ THE FULL ARTICLE >>

Osearch {3D42CCB1-4665-4620-92A3-478F47389230} DCOM Error

Problem You SharePoint Front end or Index servers present the following error in the application event log.  The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} Explanation Your office search doesn’t have rights to execute. Resolution Osearch is our culprit, grant it permissions
READ THE FULL ARTICLE >>

61738644-F196-11D0-9953-00C04FD919C1 Launch Permissions

Enhanced Instructions for Windows Server 2008 R2 Users Problem You're seeing dcom messages in your event log referencing the object 61738644-F196-11D0-9953-00C04FD919C1. Probably with event ID 10016 or 27745. Or Explanation Simply put, your SharePoint app pool account does not have rights to trigger this service. You'll see errors every 4-8 hours and sometimes more often. Solution DISCLAIMER: DO THIS AGAINST YOUR DEVELOPMENT AND STAGING ENVIRONMENTS FIRST!!! Grant rights...
READ THE FULL ARTICLE >>