Welcome to TechNet Blogs Sign in | Join | Help

Microsoft Best Practices Analyzer for WSS 3.0 and MOSS 2007

Overview

The Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System Best Practices Analyzer programmatically collects settings and values from data repositories such as MS SQL, registry, metabase and performance monitor. Once collected, a set of comprehensive ‘best practice’ rules are applied to the topology.

Administrators running this tool will get a detailed report listing the recommendations that can be made to the environment to achieve greater performance, scalability and uptime.
 
Published Wednesday, February 21, 2007 9:52 AM by Stefan_Gossner
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Thursday, February 22, 2007 12:24 PM by Ray

# re: Microsoft Best Practices Analyzer for WSS 3.0 and MOSS 2007

When I run it on a WSS 3 install that has SQL 2005 Express installed on the same server, it gives me this error eight times:

"Error connecting to SQL Server

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

I'm running it with this string:

sharepointbpa.exe -cmd analyze -substitutions SERVER_NAME SharePoint3

Any thoughts?

Thanks,

Ray

Thursday, February 22, 2007 12:39 PM by Stefan_Gossner

# re: Microsoft Best Practices Analyzer for WSS 3.0 and MOSS 2007

Hi Ray,

I don't have more details. On my box the tool worke fine.

For such problems please post into the public newsgroup or open a support case with Microsoft.

Cheers,

Stefan

Thursday, April 23, 2009 9:04 AM by Jeethu Joseph

# re: Microsoft Best Practices Analyzer for WSS 3.0 and MOSS 2007

Hi,

I have found a work around for this try it,

http://sharepointlogics.com/2009/04/error-sharepoint-best-practices.html

HTH

JJ

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker