Van Laan on Sharepoint and all things Microsoft

Set an SPS 2003 portal to read-only or to do a “content freeze”

To set an SPS 2003 portal to read-only or to do a “content freeze” for purposes of migration:

From here:

http://www.microsoft.com/technet/prodtechnol/office/sharepoint/2003/deploy/inwsssps.mspx

Follow these steps:

If you are migrating a site based on Windows SharePoint Services to a new location, you can set the site to read-only by locking the site. For more information about locking a site, see “Configuring Site Quotas and Locks” in the Administrator's Guide for Windows SharePoint Services.

1.	On your server computer, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
2.	On the SharePoint Central Administration page, in the Virtual Server Configuration section, click Configure virtual server settings.
3.	On the Virtual Server List page, click the virtual server you want to set as read-only.
4.	On the Virtual Server Settings page, in the Security Settings section, click Manage user rights for virtual server.
5.	On the Manage User Rights for Virtual Server page, in the Rights section, clear all of the check boxes except for the View Items, Browse Directories, and View Pages check boxes.
6.	You can select all rights by selecting the Select All check box. You can clear all rights by clearing the Select All check box.
7.	Click OK.

So, like this:

This should then allow you to perform any administrative duties necessary, including migration or backup, etc, with the administration account, since it does not use site groups to determine authority.

Using the SMS 2003 Toolkit Trace Log Viewer to dynamically watch Sharepoint Server 2007 or SQL Server logs as they’re written

Using the SMS 2003 Toolkit Trace Log Viewer to dynamically watch Sharepoint Server 2007 logs as they’re written

First, go to

Systems Management Server 2003 Toolkit 2

http://technet.microsoft.com/en-us/sms/bb676787.aspx

And download and install the toolkit.

Then you’ll have an option available to run:

Pull it up and browse to your Log file location Path, which you can find by going to Central Administration, Opreations, and select Diagnostic Logging:

I’ve placed them on the D: drive, like this:

But the default value is:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

Once you’ve browsed there one time, the program will save that location for ease of getting back there.

Anyways, pull it up and you can dynamically watch the Sharepoint Server 2007 Trace Logs get populated on the fly. Red highlights mean errors, yellow means warnings.

Here’s an error:

And you can get the full detail of the line at the bottom. Very useful for troubleshooting specific issues or demonstrating that they can be recreated.

It’s also quite useful for watching your SQL Server 2000 and SQL Server 2005 Logs, too.

If you click the last line at the bottom and highlight it, the program will continue to keep the last line highlighted, moving events up the screen as they come in, effectively giving you a real-time log viewer.