Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 972894 - Last Review: July 31, 2009 - Revision: 1.0
List of changes to the rule files for the Microsoft Best Practices Analyzer (BPA) for Windows SharePoint Services (WSS) 3.0 and for the 2007 Microsoft Office system
This article describes all the changes that are made to the
rule files for the Microsoft Best Practices Analyzer (BPA) for Windows
SharePoint Services (WSS) 3.0 and for the 2007 Microsoft Office
system.
Changes to the rule files for the Microsoft Best Practices Analyzer (BPA) for WSS 3.0 and for 2007 Microsoft Office system
- A nonzero value for the DataTimeout registry setting is not detected
The Microsoft Best Practices Analyzer for Windows
SharePoint Services 3.0 and the 2007 Microsoft Office system does not detect a
nonzero value for the WSS 3.0 search DataTimeout registry setting. If the
DataTimeout registry setting is set to a nonzero value, you have to be aware of
this issue when you are troubleshooting certain search issues. However, no
immediate action is necessary in this case as the DataTimeout registry setting
is only for reporting. - A nonzero value for the ConnectTimeout registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search ConnectTimeout registry setting. If the ConnectTimeout registry
setting is set to a nonzero value, you have to be aware of this issue when you
are troubleshooting certain search issues. However, no immediate action is
necessary in this case as the ConnectTimeout registry setting is only for
reporting. - A nonzero value for the MaxGrowFactor registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search MaxGrowFactor registry setting. If the MaxGrowFactor registry
setting is set to a nonzero value, you have to be aware of this issue when you
are troubleshooting certain search issues. However, no immediate action is
necessary in this case as the MaxGrowFactor registry setting is only for
reporting. - A nonzero value for the PerformanceLevel registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search PerformanceLevel registry setting. If the PerformanceLevel registry
setting is set to a nonzero value, you have to be aware of this issue when you
are troubleshooting certain search issues. However, no immediate action is
necessary in this case as the PerformanceLevel registry setting is only for
reporting. - A nonzero value for the RetryLimit registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search RetryLimit registry setting. If the RetryLimit registry setting is
set to a nonzero value, you have to be aware of this issue when you are
troubleshooting certain search issues. However, no immediate action is
necessary in this case as the RetryLimit registry setting is only for
reporting. - A nonzero value for the DedicatedFilterProcessMemoryQuota registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search DedicatedFilterProcessMemoryQuota registry setting. If the
DedicatedFilterProcessMemoryQuota registry setting is set to a nonzero value,
you have to be aware of this issue when you are troubleshooting certain search
issues. However, no immediate action is necessary in this case as the
DedicatedFilterProcessMemoryQuota registry setting is only for
reporting. - A nonzero value for the FilterProcessMemoryQuota registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect a nonzero value for the WSS
3.0 search FilterProcessMemoryQuota registry setting. If the
FilterProcessMemoryQuota registry setting is set to a nonzero value, you have
to be aware of this issue when you are troubleshooting certain search issues.
However, no immediate action is necessary in this case as the
FilterProcessMemoryQuota registry setting is only for reporting. - Changes to the default debugger are not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office system does not detect changes to the default
debugger on the server that is running WSS 3.0.
- A nonzero value for the RobotThreadsNumber registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office System does not detect a nonzero value for the WSS
3.0 search RobotThreadsNumber registry setting. When the RobotThreadsNumber
registry setting is set to zero, multiple search threads are enabled. When the
RobotThreadsNumber registry setting is set to a nonzero value, such as 1, a
single search thread is enabled.
- A nonzero value for the DebugFilters registry setting is not detected
The Microsoft Best Practices Analyzer for WSS 3.0 and
the 2007 Microsoft Office System does not detect a nonzero value for the WSS
3.0 search DebugFilters registry setting. If the DebugFilters registry setting
is set to a nonzero value, the Mssearch.exe application does not correctly
manage the filtering daemon (Mssdmn.exe) processes when the processes stop
responding. 940308Â
(http://kbalertz.com/Feedback.aspx?kbNumber=940308/
)
A new rule is not applied as
expected when you run the Microsoft Best Practices Analyzer for Windows
SharePoint Services 3.0 tool
For more information
about the Microsoft Best Practices Analyzer (BPA) for WSS 3.0 and for 2007
Microsoft Office system, click the following article number to view the article
in the Microsoft Knowledge Base:
942271Â
(http://kbalertz.com/Feedback.aspx?kbNumber=942271/
)
Description of the update for the
Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the
2007 Microsoft Office System: January 22, 2008
APPLIES TO
- Microsoft Windows SharePoint Services 3.0
- Microsoft Office Basic 2007
- Microsoft Office Enterprise 2007
- Microsoft Office Home and Student 2007
- Microsoft Office Professional 2007
- Microsoft Office Professional Plus 2007
- Microsoft Office Small Business 2007
- Microsoft Office Standard 2007
- Microsoft Office Ultimate 2007
| kbinfo kbhowto kbsurveynew kbexpertiseinter KB972894 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate