Category | WSS 3.0



Unable to browse SharePoint locally or Search Service Fails to Index Content

Date: 11 Feb 2010 | 1 Comment | Tags: ,,,,,,, | 2008,2008 R2,Installation,MOSS,SharePoint 2010,Windows Server,WSS 3.0 | 
1

This is an alternative to the "disable loopback check" which is no longer recommended by Msft due to security concerns related to local activation. Problem You are able to browse SharePoint normally from external sources, but when you attempt to access SharePoint on the local server for anything other than the machine name you are presented with multiple login prompts that ultimately result in a login error Explanation The http request fails because a loopback check runs and fails preventing Kerberos from succeeding (because there's no SPN for the url you are using to access SharePoint)...



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

Date: 04 Feb 2010 | 7 Comments | Tags: ,,,,,, | 2008,2010,MOSS,SharePoint,SharePoint 2010,Windows Server,WSS 3.0 | 
7

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 DCOM Errors will appear in the System event log as Event 10016 Normally, to correct this problem you would...



This form template is browser-compatible, but it cannot be browser-enabled on the selected site.

Date: 24 Jun 2009 | 0 Comment | Tags: ,,,,,,, | InfoPath,MOSS,SharePoint,WSS 3.0 | 
0

Problem You’re receive an error message when publishing a InfoPath form to a SharePoint server with forms services enabled.  Explanation I received this error while working on a web application other than the default (port 80) SharePoint site on the server.  For some reason when I created the new web application, which I verified was associated with an SSP, refused to render any InfoPath forms in a browser. Solution After lots of digging on Microsoft’s websites I cam up with the following solution.  Good luck! Login to your SharePoint server and run the following STSADM...



Restoring a Site Collection to Another Location on the Same Server

Date: 19 Jun 2009 | 0 Comment | Tags: ,,,,,,, | MOSS,SharePoint,Stsadm,WSS 3.0 | 
0

Often times you will want to back up a production SharePoint site collection and restore it to a server (or the same server) that already has one or more site collections defined.  This is very often the case when somebody has corrupted the original site collection but there’s still content you need accessible after you overwrite the original.  What you really need to know here is how to create a managed path then, with an empty managed path you can easily restore your site to that path.  Use the “-overwrite” switch if you want to overwrite a site collection that already...



Configuring Kerberos Authentication for SharePoint

Date: 19 Jun 2009 | 2 Comments | Tags: ,,,,,,,,, | MOSS,Programming,Windows Server,WSS 3.0 | 
2

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\system32 or %\Windows\SysWOW64 directory Locate the app pool account that will run the web application...