IShareEngine fails in a Windows Home Server-based computer when you publish a share

Consider the following scenario:

• You have a computer that is running Windows Home Server.
• You�join the computer to HomeGroup.
• You create a share by using the NetShare APIs in process�A in Windows Home Server.
• You call the IShareEngine�function and try to publish the share that was previously shared to process�A in process�B. Process B�contains a stable cache of server message block (SMB) shares.

In this scenario, the share-publishing operation fails.

This issue occurs because the IShareEngine->PublishItems function does not query the latest share cache. Instead, it tries to share a folder that is already shared. This behavior causes a failure to occur during the publishing process.

Notes

• When you try to publish a share, the IShareEngine::Share�function is called. This function determines whether a share already exists through the SMB share cache. If a share exists, the function sets access control lists (ACLs). Otherwise, the function tries to create a share by using the�NetShareAdd function.
• After the share is created in process A, the SMB share cache of process B is not updated. Then, the system calls _CreateShare to create the share again because the cache informs the function that the share does not exist.
• NetShareAdd fails because a share already exists. Therefore, CShareEngine does not add the share to the list of items to be published.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Home Server.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Home Server file information notes

• The MANIFEST files (.manifest) that are installed for each environment are listed separately�in the "Additional file information for Windows Home Server" section. MANIFEST files and the associated security catalog (.cat) files, are very important for maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Home Server

For all supported x64-based versions of Windows Home Server

For all supported IA-64-based versions of Windows Home Server

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information

Additional file information for Windows Home Server

Additional files for all supported x86-based versions of Windows Home Server

Additional files for all supported x64-based versions of Windows Home Server

Additional files for all supported IA-64-based versions of Windows Home Server