Microsoft KB Archive/939203

= The Microsoft SharePointPS Search service in SharePoint Portal Server 2003 is supported on 32-bit versions of SQL Server in WOW mode on 64-bit systems =

Article ID: 939203

Article Last Modified on 10/31/2007

-

APPLIES TO


 * Microsoft Office SharePoint Portal Server 2003

-



INTRODUCTION
This article discusses a supported configuration for the Microsoft SharePointPS Search service (Mssearch.exe) in server farm deployments of Microsoft Office SharePoint Portal Server 2003 that use 32-bit versions of Microsoft SQL Server as the database back end. Running a 32-bit version of SQL Server in Microsoft Windows on Windows 64 (WOW) mode on a 64-bit system is a supported configuration. We have determined that the Microsoft SharePointPS Search service performs as expected in this configuration.



MORE INFORMATION
WOW is a 32-bit Windows subsystem that enables you to run 32-bit applications on 64-bit versions of Microsoft Windows. Microsoft SQL Server 2000 (32-bit) and Microsoft SQL Server 2005 (32-bit) support WOW mode. WOW mode extends the virtual memory space that is available to the search services in SQL Server. The virtual memory space is extended from 2 gigabytes (GB) to 4 GB.

We have confirmed that the Microsoft SharePointPS Search service in SharePoint Portal Server 2003 performs as expected in WOW mode on a 64-bit system, even when memory consumption is more than 2 GB. In a server farm deployment of SharePoint Portal Server 2003, running a 32-bit version of SQL Server in WOW mode on a 64-bit system is a supported configuration.

For example, you may want to use this configuration if the following conditions are true:  In a server farm deployment of SharePoint Portal Server 2003, you are running a 32-bit version of SQL Server 2000. You experience an out-of-memory condition in the virtual address space. You find that catalogs are corrupted or are not populated correctly. Additionally, you receive exception error messages that resemble the following:

0x80010105

The server threw an exception.



Notes
 * If you plan to upgrade to SQL 2005 (64-bit), you can use this configuration as a workaround until you are ready to upgrade.
 * When you use this configuration, an out-of-memory condition reoccurs if memory consumption exceeds the 4-GB virtual address space limit. Symptoms that you may experience include corrupted catalogs and exception error messages. This is expected behavior. Consider upgrading to a 64-bit version of SQL Server. The 64-bit versions of SQL Server have a much larger virtual address space than 32-bit versions of SQL Server.

Additional query words: platform supportability access violation oom excessive usage db fails failure

Keywords: kbhowto kbinfo kbexpertiseinter KB939203

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.