SharePoint Short #11
If you’re trying to install SharePoint 2013 and during the installation of the prerequisites it fails with the message “Error: The tool was unable to install Microsoft SQL Server 2008 R2 SP1 Native Client” and the error code 0X654=1620, try the following:
To resolve this, download the client and manually install it before running the prerequisite installer again.
The download for the client can be found here: http://download.microsoft.com/download/9/1/3/9138773A-505D-43E2-AC08-9A77E1E0490B/1033/x64/sqlncli.msi
SharePoint Short #10
Excellent resource listing the best practices for SharePoint 2010:
SharePoint 2010 Best Practices
Details things from planning, deployment, development and lots more.
Definitely worth bookmarking for future reference.
SharePoint Short #9
When using SharePoint Designer, especially in a development environment where content and assemblies can frequently change, SPD can start to behave erratically, sometimes loading content that has been removed from the web site, or using an older version of an assembly. This is due to how SPD caches content, which thankfully, is easy enough to clear.
First, close SPD and then remove all files from the following folder:
%APPDATA%\Microsoft\Web Server Extensions\Cache
This contains things like page caches.
Then, do the same for this folder:
This contains cached items such as assemblies used and lots of other xml configuration files.
Restart SPD and all should be good in the world 🙂
This is no doubt one of the many thousand posts on this subject – the beta release of SharePoint Server 2013.
Download it here.
and to accompany the install, have a read through this installation guide – http://www.microsoft.com/en-us/download/details.aspx?id=30384
Minimum software requirements for the preview are the 64 bit versions of Windows and SQL 2008 R2 with SP1.
Nothing too complicated today but something that some people aren’t aware of and ask if it can be done – having more than one content database so they can, for example, keep sensitive data separate from their general day to day content.
It’s simple enough to create multiple content databases in Central Administration:
Within Application Management, click the Manage Content Databases link. This will take you to the /_admin/CNTDBADM.aspx page.
From that page, click the Add a content database link. Ensure the Web Application is set to the one where you want new site collection to be created in, fill in the new content database form and click OK. After a short while your new content database will be ready to use.
There are a couple of ways to setup the content database as the default database for new site collections. The first is: