My name is Phil Izod and I have been working with Microsoft 365 and related technologies (with a lot of SharePoint) since 2005. I thought it might be helpful to the community if I shared some of my experiences. Feel free to leave comments if you wish; it’s great to know whether the information is helpful or not.
Wednesday, 8 February 2012
SharePoint 2010 Service Packs and Cumulative Updates
A mental note to myself.
The latest SPs and CUs for SharePoint can be found on the Update Center for Microsoft Office, Office Servers, and Related Products page.
Hopefully this page is constantly updated by the boys and Microsoft to keep us all up to date.
Tuesday, 31 January 2012
SharePoint 2010 : Item has already been added. Key in dictionary: 'domain\account' Key being added: 'domain\account'
Scenario
The client was migrating from one domain to another. As such the servers in the their SharePoint farm would no longer sit on domainA, they would site on domain. There were many steps to this which I hope to outline in another blog post. A problem occurred when looking at service account migration.
The farm service account had been updated to “domainB\farm” using stsadm as had other service accounts.
Problem
The problem arose when we navigated to http://CentralAdmin/_admin/ManagedAccounts.aspx and http://intranetstg:1111/_admin/FarmCredentialManagement.aspx. In certain scenarios the following error would be displayed:
Item has already been added. Key in dictionary: 'domain\account' Key being added: 'domain\account'
There seemed to be multiple entries for the same account. This was confirmed by running PowerShell “Get-spmanagedaccount” to list them all. I attempted to delete the accounts using “Remove-spmanagedaccount” but the same error occurred
Solution explanation
I found a number of articles explaining ways to fix it but none of the worked for me. The idea of re-installing the farm seemed over the top. I decided to configure the farm to only use one account throughout as a temporary measure. A new account was created and all components where a previous account had been set were configured to use the temporary account. This was set via http://centraladmin/_admin/FarmCredentialManagement.aspx. (The account for each component was noted so they could be reapplied once the troublesome accoutns were removed). Occasionally the error would occur again after applying but an IIS reset seemingly resolved this. Once all the components (including farm account) were using the temporary account I could then view all the managed accounts again with PowerShell “Get-spmanagedaccount”. It was then just a matter of deleting all the managed accounts other than the temporary one with “Remove-spmanagedaccount”. It is worth noting here that after each delete an IISreset is required. SharePoint seems to get confused as to what accounts are still present and to which domain they belong to without this. Once only one account was left, new accounts were reregistered and applied to the relevant components via http://centraladmin/_admin/FarmCredentialManagement.aspx. Great.
Solution steps
The client was migrating from one domain to another. As such the servers in the their SharePoint farm would no longer sit on domainA, they would site on domain. There were many steps to this which I hope to outline in another blog post. A problem occurred when looking at service account migration.
The farm service account had been updated to “domainB\farm” using stsadm as had other service accounts.
Problem
The problem arose when we navigated to http://CentralAdmin/_admin/ManagedAccounts.aspx and http://intranetstg:1111/_admin/FarmCredentialManagement.aspx. In certain scenarios the following error would be displayed:
Item has already been added. Key in dictionary: 'domain\account' Key being added: 'domain\account'
There seemed to be multiple entries for the same account. This was confirmed by running PowerShell “Get-spmanagedaccount” to list them all. I attempted to delete the accounts using “Remove-spmanagedaccount” but the same error occurred
Solution explanation
I found a number of articles explaining ways to fix it but none of the worked for me. The idea of re-installing the farm seemed over the top. I decided to configure the farm to only use one account throughout as a temporary measure. A new account was created and all components where a previous account had been set were configured to use the temporary account. This was set via http://centraladmin/_admin/FarmCredentialManagement.aspx. (The account for each component was noted so they could be reapplied once the troublesome accoutns were removed). Occasionally the error would occur again after applying but an IIS reset seemingly resolved this. Once all the components (including farm account) were using the temporary account I could then view all the managed accounts again with PowerShell “Get-spmanagedaccount”. It was then just a matter of deleting all the managed accounts other than the temporary one with “Remove-spmanagedaccount”. It is worth noting here that after each delete an IISreset is required. SharePoint seems to get confused as to what accounts are still present and to which domain they belong to without this. Once only one account was left, new accounts were reregistered and applied to the relevant components via http://centraladmin/_admin/FarmCredentialManagement.aspx. Great.
Solution steps
- Create new temporary domain account (domain\temp)
- Set this account to be farm account with stsadm -o updatefarmcredentials -userlogin domain\temp -password temp.
- Set all other components to use this account in http://centraladmin/_admin/FarmCredentialManagement.aspx (iis resets if error reoccurs)
- List and remove accounts other that temp account with powershell ” Get-spmanagedaccount” and Remove-spmanagedaccount” (iis resets if error reoccurs – also watch for domain name changes after reset).
- Recreate managed accounts and assign to relevant components again.
- Tidy up permissions in SQL (temporary account is probably still hanging around which can be removed).
- Relax with Coffee if before 4pm otherwise potentially have a beer.
Friday, 30 December 2011
Search crawl stuck on "Crawling full" and crawl log returns nothing
After setting up a new SSP in a new farm we kicked of the search crawl from the standard "Local Office SharePoint Server sites" content source. We had a lot of content to crawl so we anticipated it lasting a couple of hours. What we did not anticipate was it still running in the morning when we had come in the night before.
When checking the crawl log there was nothing returned.
The crawler appeared to be stuck on "Crawling Full".
Solution:
A glorious IIS reset and a recrawl. I appreciate this might be a somewhat trivial point but if you have neglected to do one recently it might be worth giving it a try before you attempt some of the more elaborate solutions online.
SharePoint is a state of mind.
When checking the crawl log there was nothing returned.
The crawler appeared to be stuck on "Crawling Full".
Solution:
A glorious IIS reset and a recrawl. I appreciate this might be a somewhat trivial point but if you have neglected to do one recently it might be worth giving it a try before you attempt some of the more elaborate solutions online.
SharePoint is a state of mind.
Wednesday, 2 November 2011
Sharepoint 2010 : Content type hub not publishing name change
I was trying out the content type hub amazingly for the first time the other day. I found some nice posts on how to configure it which was reasonably straight forward.
Once I had created a content type in the hub I was able to publish it to another site collection successfully after running the "Content type hub" and appropriate "Content site subscriber" timer jobs.
After this point I though I would try an update to the source content type. I changed the name and re-run the timer jobs. My subscribed content type name was not updated.
It turns out that content types must be republished once they have been changed. This is available under the "Manage publishing for this content type" link. Once I had done this and re-run the services my subscribed content type updated making me feel much better about life in general.
Once I had created a content type in the hub I was able to publish it to another site collection successfully after running the "Content type hub" and appropriate "Content site subscriber" timer jobs.
After this point I though I would try an update to the source content type. I changed the name and re-run the timer jobs. My subscribed content type name was not updated.
It turns out that content types must be republished once they have been changed. This is available under the "Manage publishing for this content type" link. Once I had done this and re-run the services my subscribed content type updated making me feel much better about life in general.
Tuesday, 25 October 2011
Microsoft Certified in SharePoint 2010
So today I completed my 4th SharePoint 2010 exam. This allows me to call myself both an MCITP (Microsoft Certified IT Professional) and an MCPD (Microsoft Certified Professional Developer).
Now I must admit I am not the biggest fan Microsoft exams as a way of testing ones knowledge but in an attempt to inflate my own ego I thought I would blog it anyway.
So now to become a master.....maybe next year.
Now I must admit I am not the biggest fan Microsoft exams as a way of testing ones knowledge but in an attempt to inflate my own ego I thought I would blog it anyway.
So now to become a master.....maybe next year.
Tuesday, 18 October 2011
SharePoint 2010 : Could not find feature BizAppsListTemplates
Hola,
My requirement was to back up a sub site (ie SPWeb) from one environment and restore it to another environment (which had the same features / site content types etc). I exported a site (SPWeb) from the source environment utilizing the granular back up capabilities accessible from the central admin GUI.
The import to the destination environment was conducted using the following command:
Import-SPWeb -identity http://mywebsite -path C:\mypath\myfile.cmp
After a short time the import failed and displayed the following message:
"Could not find feature BizAppsListTemplates."
There were a number of posts out there relating to this but not one had the solution I required so I thought I would blog it. One post suggested rebooting and so after trying that I decided to follow my heart and look for the actual feature.
I saw that the feature was located in the 14 hive so wanted to check that it was installed correctly.
I fired a reinstall command for the feature:
stsadm -o installfeature -name BizAppsListTemplates
This solved the reported issue.
Great news all round. I love you SharePoint once more. I know what you are all thinking though....why wasn't the feature installed in the first place? I have no idea yet......... if I ever find out I will let you know.
My requirement was to back up a sub site (ie SPWeb) from one environment and restore it to another environment (which had the same features / site content types etc). I exported a site (SPWeb) from the source environment utilizing the granular back up capabilities accessible from the central admin GUI.
The import to the destination environment was conducted using the following command:
Import-SPWeb -identity http://mywebsite -path C:\mypath\myfile.cmp
After a short time the import failed and displayed the following message:
"Could not find feature BizAppsListTemplates."
There were a number of posts out there relating to this but not one had the solution I required so I thought I would blog it. One post suggested rebooting and so after trying that I decided to follow my heart and look for the actual feature.
I saw that the feature was located in the 14 hive so wanted to check that it was installed correctly.
I fired a reinstall command for the feature:
stsadm -o installfeature -name BizAppsListTemplates
This solved the reported issue.
Great news all round. I love you SharePoint once more. I know what you are all thinking though....why wasn't the feature installed in the first place? I have no idea yet......... if I ever find out I will let you know.
Wednesday, 31 August 2011
Sharepoint Dev TIP: Windows 7 services with SharePoint 2010
Hey all,
so we all have SharePoint 2010 with SQl on our 8GB dev machines (yay). A lot of the time I don't require this functionality (due to remoting to other environments) so it would be good to be able to stop a load of things to free up resources.
I have created two simple scripts which I use to turn services on and off. I appreciate that these are simple and are probably not necessarily definitive but its a good start.
Copy the commands, save as a .bat file and you are off.
StopServices.bat
echo Stopping sql server
C:\Windows\System32\net.exe stop mssqlserver
echo sql server stopped
Echo stopping Sharepoint timer (OWSTIMER)
C:\Windows\System32\net.exe stop SPTimerV4
Echo Sharepoint timer (OWSTIMER) stopped
echo Stopping iis
C:\Windows\System32\iisreset.exe /stop
echo iis stopped
pause
StartServices.bat
echo Starting Forefront Identity Manager Service (Cos it got shut down in the sql stop
C:\Windows\System32\net.exe start FIMService
echo Forefront Identity Manager Service Started
echo Starting sql server
C:\Windows\System32\net.exe start mssqlserver
echo sql server started
Echo Starting Sharepoint timer (OWSTIMER)
C:\Windows\System32\net.exe start SPTimerV4
Echo Sharepoint timer (OWSTIMER) started
echo Starting iis
C:\Windows\System32\iisreset.exe /start
echo iis started
pause
so we all have SharePoint 2010 with SQl on our 8GB dev machines (yay). A lot of the time I don't require this functionality (due to remoting to other environments) so it would be good to be able to stop a load of things to free up resources.
I have created two simple scripts which I use to turn services on and off. I appreciate that these are simple and are probably not necessarily definitive but its a good start.
Copy the commands, save as a .bat file and you are off.
StopServices.bat
echo Stopping sql server
C:\Windows\System32\net.exe stop mssqlserver
echo sql server stopped
Echo stopping Sharepoint timer (OWSTIMER)
C:\Windows\System32\net.exe stop SPTimerV4
Echo Sharepoint timer (OWSTIMER) stopped
echo Stopping iis
C:\Windows\System32\iisreset.exe /stop
echo iis stopped
pause
StartServices.bat
echo Starting Forefront Identity Manager Service (Cos it got shut down in the sql stop
C:\Windows\System32\net.exe start FIMService
echo Forefront Identity Manager Service Started
echo Starting sql server
C:\Windows\System32\net.exe start mssqlserver
echo sql server started
Echo Starting Sharepoint timer (OWSTIMER)
C:\Windows\System32\net.exe start SPTimerV4
Echo Sharepoint timer (OWSTIMER) started
echo Starting iis
C:\Windows\System32\iisreset.exe /start
echo iis started
pause
Subscribe to:
Posts (Atom)