Microsoft KB Archive/185722

= SFM Rebuilds Indexes upon Restarting of Windows NT =

Article ID: 185722

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q185722





SYMPTOMS
Services for Macintosh (SFM) on a Windows NT Server computer has had the ability to rebuild indexes upon startup of the server but if the server fails to shut down properly, the SFM indexes may not get written and old directory information may not get updated.



CAUSE
When Windows NT is shut down normally, Services for Macintosh will write all the volume indexes to the computer hard disk. If the Windows NT Server computer is shut down improperly, SFM may not have the opportunity to properly write an index.



RESOLUTION
SFM will now rebuild all indexes upon restart if the server is unable to close SFM down properly. Installing the latest Hotfix will give SFM the ability to handle such cases.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/sfm-fix/



STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Services for Macintosh (SFM) on a Windows NT Server computer has had the ability to rebuild indexes upon startup of the server but if the server fails to shut down properly, the SFM indexes may not get written and old directory information may not get updated. To determine if the index was rebuilt you can examine event viewer and see if you find event logs with the 12035 Event ID:

  Event ID: 12035 Description: Volume information for could not be loaded. Setting defaults.



MORE INFORMATION
The event message below will be logged for each volume upon restart with the new binaries in cases where SFM failed to shut down properly.

  Event ID: 12035 Description: Volume information for could not be loaded. Setting defaults.

For more information, please see the following articles in the Microsoft Knowledge Base:

ARTICLE-ID: 166571

TITLE : Creating an SFM Volume on Large Partition Causes a Stop 0x24

ARTICLE-ID: 170956

TITLE : SFM Time and Date Stamp Change Copying Between Volumes Locally

ARTICLE-ID: 172511

TITLE : Stop 0x0000000A w/ Services for Macintosh & McAfee Anti- Virus

ARTICLE-ID: 177644

TITLE : Commenting Macintosh File Changes Date and Time Stamp

ARTICLE-ID: 178364

TITLE : Macintosh Clients See Files on WinNT Server Constantly Moving

ARTICLE-ID: 180622

TITLE : STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in Sfmsrv.sys

ARTICLE-ID: 180716

TITLE : SFM Fails to Accept Associations with Two-Character Extensions

ARTICLE-ID: 180717

TITLE : SFM: File Date and Time Stamp Change with Get Info

ARTICLE-ID: 180718

TITLE : SFM: Disconnect Macintosh Clients before Dismounting Volume

Additional query words: afp afp_idindex

Keywords: kbbug kbfix KB185722

-

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

© Microsoft Corporation. All rights reserved.