SharePoint 2010 – error – removing SQL Server – wss_administration reference

by

Symptoms:

When you try to remove a not used SQL Server from Sharepoint in the Central admin:

An object in the SharePoint administrative framework, "SPDatabaseServiceInstance Name= could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation. The dependant objects are as follows: SPWebService Name=WSS_Administration

Workaround:

You have switched to a new SQL server but SharePoint kept a reference. You can use an existing correct Web application to update Central admin with the good one:

$centralAdmin=Get-SPWebApplication -IncludeCentralAdministration | ? {$_.DisplayName -match ‘SharePoint Central Administration’}
$goodExample=Get-SPWebApplication -identity ‘http://mygoodwebapp’
$centralAdmin.Parent.DefaultDatabaseInstance=$goodExample.Parent.DefaultDatabaseInstance
$centralAdmin.Parent.Update()
$centralAdmin.Update()

Use SQL Alias for the next time 🙂

SharePoint 2013 – Add Managed Account – Access denied

by

 

Problem:

When you add a Managed Account:

Explaination:

The declared account during configuration wizard run the SharePoint Timer Service. This account need local admin privilege.

Even with this error message, the account is added. Nevertheless, if you try to go to the Managed account page from central admin, the page doesn’t work anymore (Object reference not set to an instance of an object):

So you have to:

  • Remove the added account through PowerShell : Remove-spManagedAccount -identity mydomainnewaccount
  • Add the timer account local admin
  • Restart SharePoint Timer Service so it get the privilege
  • iisreset
  • Add again the account.

Internet Information Services (IIS) Manager. Bad Data. (Exception from HRESULT: 0x80090005)

by

Problem:

When you try to use the IIS console, you get the following error:

Bad Data. (Exception from HRESULT: 0x80090005)

Why:

You have copied the configuration file of IIS from one computer to the other (C:WindowsSystem32inetsrvconfigapplicationHost.config)

This file contains Windows account for the applications pools. The password is encrypted using a local key on the computer so the other server can’t decrypt the password.

Modifying the applications pools password doesn’t fix the issue.

Workaround:

2 ways:

  • Rollback the configuration on the destination computer. By default, IIS keep the last 10 configurations (C:inetpubhistory)
  • Use the supported way to copy the configuration.

Export configuration:

aspnet_regiis -px "iisConfigurationKey" "C:iisConfigurationKey.xml" -pri 
aspnet_regiis -px "iisWasKey" "c:iisWasKey.xml" –pri

Import on target:

aspnet_regiis -pi "iisConfigurationKey" "C:iisConfigurationKey.xml" 
aspnet_regiis -pi "iisWasKey" "C:iisWasKey.xml"

A bit of reading…

by

 

A bit of reading to enjoy your holidays…If you don’t know these stories yet 😉

Switching a bit of subject with company related one…

 

Le principe de Peter

http://en.wikipedia.org/wiki/Peter_Principle

Les 75 lois de Fox (found only in french)

http://www.amazon.fr/Les-75-lois-Fox-Jeffrey/dp/2841872742

Big rocks story:

http://www.callipygia600.com/callnugget/lessons/handouts/big_rock.htm

Story of the three letters:

http://www.hmtk.com/archives/33-the-three-letters.html

20 Ways to Find Your Calling

http://www.forbes.com/sites/jessicahagy/2012/06/26/20-ways-to-find-your-calling/2/

The 6 People You Need in Your Corner

http://www.forbes.com/sites/jessicahagy/2012/07/17/the-6-people-you-need-in-your-corner/

 

Thanks to Bertie for the stories 🙂

SharePoint 2010 – The super user account utilized by the cache is not configured

by

You may already have seen this SharePoint warning:

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.

I use the following script (all my web Applications are in claim):
foreach ($a in (Get-SPWebApplication))
{
   $a;
   $a.Properties[“portalsuperuseraccount“];
   $a.Properties[“portalsuperreaderaccount“];
   $a.Properties[“portalsuperuseraccount“] =“i:0#.w|mydomainSharePointAdminAccount“;
   $a.Properties[“portalsuperreaderaccount“] =“i:0#.w|mydomainSharePointDedicatedReadAccount“;
   $a.Update();
}

But none of them had an incoorect value. To find out quickly, just need to switch on the detail of the event:

You will find the PID (Process ID) which generated the error:

You then just have to use  Process Explorer for example to identify the web site:

In this case it was the Central admin, who shouldn’t be in claim anyway

TechEd 2012 Europe: best session

by

TechED are now over… Here is my prefered session:Windows Azure Internals

Mark Russinovich (sure you know about him) shows up the Azure backstage.

Facts highlights:

  • ~10 people to admin around 100 000 servers!
  • Demo of one of the Azure admin interface,
  • Graphical view of racks with VM,
  • Demo on platform self healing,
  • Explain on leap day bug (29th of february), with even source code line that broke everything

You are warned, heavy stuff 🙂

Video and slides available here: http://channel9.msdn.com/events/TechEd/Europe/2012/AZR302