Out Of The Box Sharepoint (?)

April 30, 2011

Configure service accounts: Application Pools

Filed under: Sharepoint — Peter Kruisman @ 10:49 am

Sharepoint2010 manages the service accounts in one place. This is a great plus but has some gotcha’s. 
Today I experienced a page not found after changing the application pool credentials from within IIS.

Although I used a managed account this action does NOT update the association in the Sharepoint service accounts configuration page. This results in the page not found error.
Use the Service Account page to associate a managed account with a service. Do not use IIS to configure services credentials.

Also do not delete such a managed account in AD. De-associate the account from services and then delete it.

Update – Gary Lapointe posting of the managed accounts complications 




April 29, 2011

Powershell, parameter suggestions

Filed under: powershell, Sharepoint — Peter Kruisman @ 8:47 am

Configuring Sharepoint 2010 can be done using the Central Administration and / OR using powershell.

 For example we can use the  Central Administration for configuring the data collection of events. This is done in “Configuring web analytics and health data collection” by selecting an event.

1. Central administration, events that can be logged

Using Central Administration you cannot change the default retentionperiod, which is 30 days. It can be done using one of the many sharepoint powershell cmdlet’s (.Net framework instances) and accompanying parameters. For configuring the retention period the SPUsageDefinition instance can be used. Powershell can provide the accompanying parameters and examples using the Get-Help and -Full switches like:

2. Get-Help and -Full switches

From the provided information I conclude you can use the event names in Central Administration(see the printscreen 1. ) for the -Id parameter

Powershell script to alter the retention period:

3. Setting the retention period for an event


4. Getting the retention period for an event

Examining cmdlet parameters

April 28, 2011

SMS Alert

Filed under: powershell, Sharepoint — Peter Kruisman @ 8:06 pm

With the use of a SMS testaccount from Red Oxygen testing the Text Message settings in Sharepoint2010 Central Administration resulted in a long wait


At first configuring this service seemed trivial but this wait without resulting in an error message or directions of possible causes was somewhat frustrating.  
After reading the instructions  in this Technet  article I concluded that the long wait was the result of a missing certificate. I continued the configuration with importing the certificate  of the  Office Mobile Service (OMS)  page from Red Oxygen.

Service page

After this Install of the certificate (Go Daddy ) start the MMC shell. Add/ Open the certificate snapin

Export the imported certificate authority to for example C:\sms.cer

Use this Powershell script to register this trusted root authority
$cert = Get-PfxCertificate c:\sms.cer
New-SPTrustedRootAuthority -Name GoDaddy -Certificate $cert

After this the SMS service is functional

Setting the alert


April 19, 2011

The specified user or domain group was not found – The user does not exist or is not unique

Filed under: Sharepoint — Peter Kruisman @ 2:35 pm

This week I configured the object cache of the Sharepoint2010 web applications with a superuser and superreader account.  For this I initially used these domain user accounts: spObjectcacheSuperUser, spObjectcacheSuperReader.
These accounts errored out when running this powershell script as “The specified user or domain group was not found”.  Ultimately I tested these account by logging on to a win7 computer, this produced the same error.  Shortened the accounts to spSuperUser and spSuperReader and running the powershell script again was successfull.  Testing this scenario with an other long accountname (spObjectcacheThisSuperUser) did produce the same error.

– Win2008 R2 X64 domain controller
– Sharepoint2010
– Powershell 1.0

I’ve no clue what is going on here!

The side effect of running the script again with a “bad” username and thereby (obviously?) messing up the configuration of the object cache is that I could not logon to Sharepoint. The error is “The user does not exist or is not unique”

Running the script with the account that successfully configured the object cache before fixed this error.

– PS

I’ve found an answer to this.  “A user can logon either with their user principal name or their “pre-Windows 2000 logon” name. If you use the user principal name, you must include the DNS suffix: veryverylongprincipalname@yourdomain.somewhere (read the replys to this question) I was in the assumption that using w2008 the “pre-Windows 2000 logon” character name limit would not have an impact.

April 13, 2011

SLK continued

Filed under: Education, Learning Kit — Peter Kruisman @ 9:01 am

I’ve blogged before about the Sharepoint learning Kit. Version 1.5 (stable) is out and can be used in Sharepoint2010 (Foundation)
Review from Marco van Wieren about this version http://www.sharepointappmarket.com/2011/03/a-sharepoint-learning-kit-primer 
Because in the past year I’ve read about performance issues with the dropbox this discussion between Richard Willis (slk coordinator/ developer) and marco van Wieren is probably more interesting. From what I’ve read and observed in version 1.4 this drop box is a custom list in which user uploaded assignments are placed. During this placement a breakroleinheritance (used in DropBoxManager.cs) is  utilized. This can be a perfomance issue like encountered by a (forgot the name..) school in the VS when there are many assignments and many users.. In the reply from Richard in the discussion  about using Sharepoint lists versus database tables and permission on items it seems to be handled different in the 1.5 version(?) Well I’ve to install it and look at the DropBoxManager.cs to be sure. To be continued..    

Visual studio extension (VSEWSS) projects in VS2010 – VS2010 SDK

Filed under: VisualStudio — Peter Kruisman @ 8:01 am

VSEWSS projects are deployed at Sharepoint 2007 ( WSS3 ).  Importing these projects in VisualStudio 2010 do not succeed because the VSEWSS templates are not recognized ( assuming that VisualStudio 2010 is used for Sharepoint 2010 development, the VSEWSS templates cannot be installed due to the fact that 2010 uses WSS4  )  Kirk Evans blogged about the VSEWSS import tool that can be used to overcome this: http://blogs.msdn.com/b/kaevans/archive/2010/06/16/import-sharepoint-projects-from-visual-studio-2008-to-visual-studio-2010.aspx  There is a gotcha in this concerning the installation of the SDK. There is the possibility that this will fail with a very misleading error message “You must have Microsoft Visual Studio 2010 installed on your computer before proceeding”. My reaction was something like %$#@!!!!! .. have that… used it and now )(*&^!!!.
The solution is to check if the VS2010 SP1 is installed. If so use the SP1 version of the SDK:  http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=21307C23-F0FF-4EF2-A0A4-DCA54DDB1E21&displaylang=en 


Create a free website or blog at WordPress.com.