Jamik

A while ago Microsoft has released the “Office Developer Tools for Visual Studio”. If you’re installing those tools in a Microsoft SharePoint 2013 environment the installer also will update the “Service Bus” and “Workflow Manager” to CU 1. If you can remember, you have to install those components under the WF Account. Same goes for the update.
Install the developer tools under the WF Service Account and it will run fine. Otherwise the update will fail.

Problem:

You have installed SharePoint with the integrated Database option. You now want to connect to the databaseserver but are getting error messages.

Solution:

Use

\\.\pipe\MSSQL$MICROSOFT##SSEE\SQL\query

as Servername in the connection dialog.

To safe time for new SharePoint Installations it’s a common way to integrate released service packs and CU’s to the rtm disc set. The process is very similar to the 2007/WSS 3.0 process. It’s recommended that you also integrate the foundation SP even if you use SharePoint Server. If you only use foundations you can skip the server download.

Slipstream SP1 (Foundation & Server)

1. Extract the Server or Foundation ISO disc image
2. Download SP1 for Foundation
3. Download SP1 for SharePoint Server
4. Locate the “update” folder of the extracted iso image
5. Extract the foundation service pack to the update folder (in my case it’s located at D:\SPISO\EN\Updates)

   sharepointfoundation2010sp1-kb2460058-x64-fullfile-en-us.exe /extract:D:\SPISO\EN\Updates

6. Extract the SharePoint Server service pack to the update folder

   officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe /extract:D:\SPISO\EN\Updates

7. Done. If you install SharePoint Server the update folder will automatically applied.

You can skip step 3 and 6 if you only have a foundation installation.

Problem:
Periodical errors in the event log of a SharePoint 2010 server with the following error event descriptions:
Failure trying to synch site <ID> for ContentDB <ID> WebApp <ID>. Exception message was Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'. The statement has been terminated.


Cause:
Old references to non existing content databases in the synchronization job list.

Fix:
List databases which are not synced for more than two days
stsadm -o sync -listolddatabases 2

Delete old database references from the config db
stsadm -o sync -deleteolddatabases 2

References:

• Technet

1. Open SharePoint Designer 2010 and open the site with the library
2. Click on [All Files] Link
   
3. Select the desired library (PublishingImages in this example)
4. Rename it

Yes, it is that simple.

Bunch of library updates were published last week:

• Microsoft SharePoint Server 2010 Technical Library in Compiled Help format
• Microsoft FAST Search Server 2010 for SharePoint Technical Library in Compiled Help format
• Microsoft Project Server 2010 Technical Library in Compiled Help format
• Microsoft SharePoint Foundation 2010 Technical Library in Compiled Help format

A while ago a participated in the beta exams for 70-667 (TS: Microsoft SharePoint 2010, Configuring).
The exam contained about 70 Question about

• Backup & Restore
• Policies
• Monitoring
• Upgrading
• Service Applications
• Solutions
• Application Management (AAM, Content Databases, host headers)

More information about the measured skills can be found on the Microsoft Learning Site.
The exam was quite doable if you have played around a little with the Beta and RTM versions of SPS 2010. Experience in MOSS 2007 wouldn’t also do any harm.

Because it was a beta exam cycle i didn’t get any results after finishing the exam.
Nevertheless last weekend i’ve got the confirmation mail from Microsoft which means…… i’m one of the first MCITP’s for SharePoint 2010 – at least in germany.

Activate SharePoint CmdLets in PowerShell:

Add-PSSnapin Microsoft.Sharepoint.Powershell

Permanently register the SharePoint CmdLets in your ISE profile:

if (!(test-path $profile ))
{
    new-item -type file -path $profile -force
} 
 
$cmd = 'if((Get-PSSnapin | Where-Object {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null)
{
    Add-PSSnapIn "Microsoft.SharePoint.Powershell"
}'
 
out-file -FilePath $profile -InputObject $cmd -Append

via Points to Share

Problem:
If you’re trying to open an Office Document in SharePoint 2010 with the included WebApps you might encounter the following error in the diag log/screen:

Corresponding diag log entry:
System.Data.SqlClient.SqlException: Cannot open database "CONTENTDB" requested by the login. The login failed. Login failed for user 'DOMAIN\ACCOUNT'.

Description:
If you’ve not used the Farm Configuration Wizzard the service accounts you’re using for the Web App Service Applications might not be provisioned correctly and have not the neccessary rights to connect to the content database.

Fix:
Grant at least read/write permissions to the service application account at the corresponding content database.

PS: There might be an PowerShell CmdLet for this operation – this post will get updated if i have found a better solution.

Update:
As promised – the PowerShell Script:

$w = Get-SPWebApplication -identity  http://URL
$w.GrantAccessToProcessIdentity("DOMAIN\SERVICEAPP")

The session state service is an application service in SharePoint 2010 which is used by many components (eg Infopath Forms Service) to store temporary data accross related http requests. If you’ve used the farm configuration wizzard the state service is installed and configured automatically. Otherwise you have to activate the state service with PowerShell CmdLets.

The following snippet creates a state service application and the corresponding proxy group with the name “State Service Application” and associates them to the default proxy group:

$serviceApp = New-SPStateServiceApplication -Name "State Service Application"
New-SPStateServiceDatabase -Name "StateServiceDatabase" -ServiceApplication $serviceApp
New-SPStateServiceApplicationProxy -Name "State Service Application" -ServiceApplication $serviceApp -DefaultProxyGroup

Get-Command *spstate*

gives you a complete list of state service related CmdLets.