Links to some good SharePoint 2010 tips

• remove 'view all site content' in sharepoint for anonymous users

Restore MOSS content database

1. After the new server is installed, no content database.
2. In central admin, Create a new web application at port 80, named wss_content (default)
configurable username and password: pxxxadmin/xxxxx
3. In SQL management studio, r-click databases and select restore database and select wss_content
4. point to bk file and ok to restore
5. got error

6. stop sql service, rename wss_content.mdf and wss_content_log.ldf and try (see screenshot, error1)
7. remove content datbase in central admin>app mgt>content database
8 then i got another error (see screenshot error2)


once removed content db from central admin
stop sql services and delte wss_content.mdf and ldf
restore again and make sure go to options to select overwrite
restored successfully this time

STSADM –o addcontentdb –url <URL name> -databasename <database name> -databaseserver <database server name>
but got error

The specified SPContentDatabase Name=WSS_CONTENT Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

verison is 12.0.6425.1000 on both servers!??
run config wizard again

verison on new moss is 12.0.0.6421
on old server is 12.0.0.6565
http://insomniacgeek.com/how-to-determine-the-installed-sharepoint-version/
requested and installed KB2553020 - failed as well
try KB2596541 - 12.0.0.6653 - WTF
well "Operation completed successfully"

Shrink WSS3.0 Log.ldf size

WSS 3.0 server was running low on C drive. Only 2MB was available. I then ran the FolderInfo - my favorite disk space tool - so easy to use to find out "SharePoint_Config_xxx_log.LDF" has grown over 30GB.



 

Then I followed this article on web to shrink the file and it went down to 500KB only.



 

My Upgrade: from WSS3.0 to SharePoint 2010 Foundation

This is my upgrade experience by using "Attach databases and upgrade to SharePoint 2010". It's quite straight forward but since it was my first time upgrading a farm and I had created two new OS so it took me two days to figure out.

Source:
Single WSS3.0 server on a Windows 2003 server, 32bit standard with embedded SQL.

Target:
WFE: SharePoint 2010 Foundation farm on Windows 2008 standard server, 64 bit.
Database: SQL 2008 SP2 (64 bit) on Windows 2008 standard server, 64 bit.

Steps I took:

1. Follow this article, Attach databases and upgrade to SharePoint Server 2010

 

Ran STSADM.EXE -o preupgradecheck first on source WSS server.

Ran into the first problem while installing SP2010. The error is "Cannot connect to database master at SQL server at <SQL_server_name>. The database might not exist, or the current user does not have permission to connect to it.



Then I made sure the followings..

1. Both SharePoint and SQL ware assigned the static IP address, and SP server can PING SQL and DC without problem


2. Enable 'dbcreator' and 'securityadmin' Server Roles for the SP admin in Security/Logins in SQL Server Management Studio.


3. Enable TCP/IP in "Protocols for MSSQLSERVER"

2. I got the new SharePoint set up without problem and I could browse to the default home page at port 80, but what I needed was the restored content database instead of a blank new site. So I went to "Manage Content Databases" in the Central Administration and deleted the default WSS_Content database, and deleted the WSS_Content SQL database from SQL management studio.

3. Run Mount contentt database command again below.

Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL>

It went ok with the message below. Then I was able to see the "WSS_Restored" was created in my content database page.


4. Try to browse to the SharePoint website and all my old WSS3.0 root site shown ok, but not the subsites.