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)
- Extract the Server or Foundation ISO disc image
- Download SP1 for Foundation
- Download SP1 for SharePoint Server
- Locate the “update” folder of the extracted iso image
- 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 |
- Extract the SharePoint Server service pack to the update folder
officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe /extract:D:\SPISO\EN\Updates |
- 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:
- Open SharePoint Designer 2010 and open the site with the library
- Click on [All Files] Link
- Select the desired library (PublishingImages in this example)
- Rename it
Yes, it is that simple.
Bunch of library updates were published last week:
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. 
Another undocumented SP in Microsoft SQL Server is the ‘sp_MSForEachDB‘ procedure. This procedure enumerates every database on a Microsoft SQL Server Instance and let you perform different actions on every database. This can be quite useful in several situations. For example the following two scripts are
- creating database backups of all databases on a SQL Server Instance
- creating a restore script for those databases
To use those scripts you may want to modify the paths (‘c:\#Backup’, ‘C:\MS SQL Data\MSSQL.1\MSSQL\Data\?.mdf’,….) to match your environment:
Backup
EXEC sp_MSForEachDB
'IF DB_NAME((SELECT dbid FROM sysdatabases WHERE [Name]= ''?'')) NOT IN (''tempdb'',''master'',''model'',''msdb'')
BACKUP DATABASE [?] TO DISK = N''C:\#BACKUP\?.bak'' WITH NOFORMAT, NOINIT, NAME =
N''?-Full Database Backup'', SKIP, NOREWIND, NOUNLOAD' |
Restore
EXEC sp_MSForEachDB
'IF DB_NAME((SELECT dbid FROM sysdatabases WHERE [Name]= ''?'')) NOT IN (''tempdb'',''master'',''model'',''msdb'')
PRINT "RESTORE DATABASE [?] FROM DISK =N''C:\#BACKUP\?.bak'' WITH FILE =1,
MOVE N''?'' TO N''C:\MS SQL Data\MSSQL.1\MSSQL\Data\?.mdf'',
MOVE N''?_log'' TO N''C:\MS SQL Data\MSSQL.1\MSSQL\Data\?.ldf'',
NOUNLOAD, REPLACE, STATS = 10
GO"
' |
Microsoft has released the feature pack for SQL Server 2008 R2. The feature pack is a collection of stand alone packages which extends the functionality of SQL Server in several ways. Among other things the package contains:
- Microsoft® SQL Server Report Builder 3.0 for Microsoft® SQL Server 2008 R2
- Microsoft® SQL Server® PowerPivot for Microsoft® Excel
- Microsoft® SQL Server® 2008 R2 Reporting Services Add-in for Microsoft® SharePoint® Technologies 2010
- Microsoft® SQL Server® 2008 Reporting Services Add-in for Microsoft® SharePoint® Technologies 2007
Get it from here.
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
