When trying to setup Kerberos to work with SharePoint you need to setup the app pool account as trusted for delegation. you may find that the delegation tab is missing in AD in Windows Server 2008, this is "as designed", the delegation tab will appear only after an SPN is created for the service account.
So do setspn -A HTTP/intranet.domain.local DOMAIN\Account from a command prompt in the famr and then go to AD and search for the DOMAIN\ACcount and you will see the delegation tab appear.
Wednesday, 21 April 2010
Tuesday, 20 April 2010
WSP Stuck on deploying or retracting in Solution Management
If your solution package is stuck on deploying or retracting status for a long time on the "Solution Management" page in SharePoint Central Admin then check that the "Windows SharePoint Services Timer" windows service is started on ALL the web front end machines.
Thursday, 25 March 2010
SharePoint Server 2010 VS SharePoint Foundation 2010 Features
Microsoft have a good feature list available in the new SharePoint release.
Sharepoint foundation is the free version, was called WSS in 2007 version.
Features can be found here..
http://msdn.microsoft.com/en-us/library/ee539826(office.14).aspx
SharePoint Server 2010 is the licened version, was called MOSS in 2007
Features can be found here…
http://msdn.microsoft.com/en-us/library/ee557323(office.14).aspx
Sharepoint foundation is the free version, was called WSS in 2007 version.
Features can be found here..
http://msdn.microsoft.com/en-us/library/ee539826(office.14).aspx
SharePoint Server 2010 is the licened version, was called MOSS in 2007
Features can be found here…
http://msdn.microsoft.com/en-us/library/ee557323(office.14).aspx
Error when adding web part solution package An object in the SharePoint administrative framework
You sometimes may recieve the error below when trying to do stsadm -o addsolution -filename "wspname.wsp"
An object in the SharePoint administrative framework, "SPSolutionLanguagePack Name=0 Parent=SPSolution Name=il.sharepoint.workflows.wsp", depends on other objects which do not exist. Ensure that all of the objects dependencies are created and retry this operation.
wspname.wsp: The Solution installation failed.
This is especially the case if you have just done a retract/uninstall and you try to add straight away. If you try again in a few seconds it will work. Basically this is because when you delete a wsp from solution management and then immediately run this stsadm command, there will still be clean up operations going on in the background. So just leave a slight delay between uninstall of solution packages and re-deploys.
An object in the SharePoint administrative framework, "SPSolutionLanguagePack Name=0 Parent=SPSolution Name=il.sharepoint.workflows.wsp", depends on other objects which do not exist. Ensure that all of the objects dependencies are created and retry this operation.
wspname.wsp: The Solution installation failed.
This is especially the case if you have just done a retract/uninstall and you try to add straight away. If you try again in a few seconds it will work. Basically this is because when you delete a wsp from solution management and then immediately run this stsadm command, there will still be clean up operations going on in the background. So just leave a slight delay between uninstall of solution packages and re-deploys.
Tuesday, 23 March 2010
SharePoint Search Crawl Returns Access Denied
Our SharePoint search suddenly stopped working last week and on googling found out that if the Default Content Access Account in SSP - Search Administration - Default Content Access Account is of the format domain\username it seems to fail but once changed to the format of username@domain.local it works!
"Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".
"Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".
Friday, 26 February 2010
Restricting access to mysites in SharePoint
You may come accross the requirment where you would want only certain group of people to be able to create my sites. This is possible by modifying permissions on Shared Services Provider, to do so follow these steps
1. Logon to Central Admin
2. Click on the Shared Services Provider that hosts my sites
3. Click on "Personalization services permissions" under the group "User Profiles and My Sites"
4. Click on the group "NT AUTHORITY\Authenticated Users" if it exists in that list and untick the option "Create Personal Site" and click save.
5. Using the menu on the permissions page, add the SharePoint group that you want to give permissions to
6. Click on the Group that you just added and select the permissions "Create Personal Site" and jobs done!
1. Logon to Central Admin
2. Click on the Shared Services Provider that hosts my sites
3. Click on "Personalization services permissions" under the group "User Profiles and My Sites"
4. Click on the group "NT AUTHORITY\Authenticated Users" if it exists in that list and untick the option "Create Personal Site" and click save.
5. Using the menu on the permissions page, add the SharePoint group that you want to give permissions to
6. Click on the Group that you just added and select the permissions "Create Personal Site" and jobs done!
Friday, 19 February 2010
Modify Web Part Properties window very small
When editing a SharePoint publishing page or my site page and if the "modify shared web part" window appears very small or not visible then the short cut fix is to set the below style in your css file that is referenced from your Master Page
#MSO_tblPageBody {
height:600px !important;
}
#MSO_tblPageBody {
height:600px !important;
}
Subscribe to:
Posts (Atom)