Consider the following scenario:

• You run one of the versions of Microsoft Word, of Microsoft Excel, or of Microsoft PowerPoint that are mentioned in the "Applies to" section.
• You click the Microsoft Office Button or the File tab in Word, in Excel, or in PowerPoint and then click Open.
• In the Open dialog box, you click Show the preview pane.
• You take one of the following actions:
  • In Word, you select a Word document to preview.
  • In Excel, you select an Excel workbook to preview.
  • In PowerPoint, you select a PowerPoint presentation to preview.

In this scenario, a preview is not displayed. Instead, you receive an error message that resembles one of the following in the Preview pane:

In Microsoft Word:

In Microsoft Excel:

In Microsoft PowerPoint:

This problem occurs because of a problem in the Word previewer, in the Excel previewer, and in the PowerPoint previewer.

There is no resolution or workaround for this problem.

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

When you try to add a new Microsoft Exchange Server 2010 Mailbox server to an existing Database Availability Group (DAG), the operation times out when it tries to install the Failover Clustering component. Additionally, you receive the following status message:

When the time-out occurs, you receive the following error message:

However, the installation of the Failover Clustering component continues and succeeds after several minutes. If you run the Add-DatabaseAvailabilityGroupServer task again, the task finishes successfully.

When the Add-DatabaseAvailabilityGroupServer task runs, Exchange checks whether the target server already has the Failover Clustering component installed. If the Failover Clustering component is not installed, Exchange starts the installation of this component. During this process, the Microsoft Failover Cluster Virtual Driver (netft.sys) is also installed.

If Symantec Endpoint Protection is running on this computer, a driver that is named Teefer2 Miniport (teefer2.sys) is also installed. The installation of this third-party driver causes the network connection to drop out for a few minutes. This outage causes the connection between PowerShell.exe and the PowerShell application pool in Internet Information Services to be dropped. When the PowerShell application pool completes the Failover Clustering installation, it cannot notify PowerShell.exe that the installation is successful. Eventually, PowerShell.exe reaches the WinRM time-out value and fails.

To resolve this problem, use of the following methods before you add the server to the DAG:

• Install the Failover Clustering component manually.
• Work with the third-party vendor for help to remove and reinstall Symantec Endpoint Protection.

For information about how to contact Symantec, visit the following Microsoft website:

This article describes the compatibility of Microsoft SQL Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

Single Label Domains

loadTOCNode(2, 'moreinformation');
For a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab3)

Disjoint Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab1)

Discontiguous Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Discontiguous Namespaces, also known as a non-contiguous namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab2)

Microsoft SQL Server

loadTOCNode(2, 'moreinformation');

Single Label Domains

loadTOCNode(3, 'moreinformation');
SQL Server products are designed to run on the Windows Server platform. Because the use of SLDs is not a recommended practice, SQL Server products are not tested in this scenario. Therefore, there may be incompatibilities when SQL Server products are implemented in an SLD environment.

Impacted SQL Server products include SQL Server 2008
(http://www.microsoft.com/sqlserver/2008/en/us/default.aspx)
. For a full list of related SQL products, please click here
(http://support.microsoft.com/ph/2852#tab6)
.

Product Compatibility page on the DNS Namespace Planning Solution Center
(http://support.microsoft.com/gp/gp_namespace_master#tab4)

This article describes the compatibility of Microsoft System Center products with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

Single Label Domains

loadTOCNode(2, 'moreinformation');
For a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab3)

Disjoint Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab1)

Discontiguous Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Discontiguous Namespaces, also known as a non-contiguous namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab2)

Microsoft System Center

loadTOCNode(2, 'moreinformation');

Single Label Domains

loadTOCNode(3, 'moreinformation');
System Center products are designed to run on the Windows Server platform. Because the use of SLDs is not a recommended practice, System Center products are not tested in this scenario. Therefore, there may be incompatibilities when System Center products are implemented in an SLD environment.

Product Compatibility page on the DNS Namespace Planning Solution Center
(http://support.microsoft.com/gp/gp_namespace_master#tab4)

This article describes the compatibility of Microsoft Biztalk Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

Single Label Domains

loadTOCNode(2, 'moreinformation');
For a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab3)

Disjoint Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab1)

Discontiguous Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Discontiguous Namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab2)

BizTalk Server

loadTOCNode(2, 'moreinformation');

Single Label Domains

loadTOCNode(3, 'moreinformation');
Because the use of SLDs is not a recommended practice, BizTalk Server is not extensively tested in this scenario. Therefore, there may be incompatibilities when BizTalk Server is implemented in an SLD environment.

Affected BizTalk
(http://www.microsoft.com/biztalk/en/us/default.aspx)
 products include Microsoft BizTalk Server 2009. 

Product Compatibility page on the DNS Namespace Planning Solution Center
(http://support.microsoft.com/gp/gp_namespace_master#tab4)

This article describes the compatibility of Microsoft Office Communications Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

Single Label Domains

loadTOCNode(2, 'moreinformation');
For a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab3)

Disjoint Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab1)

Discontiguous Namespaces

loadTOCNode(2, 'moreinformation');
For a description of Discontiguous Namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
(http://support.microsoft.com/gp/gp_namespace_master#tab2)

loadTOCNode(2, 'moreinformation');

Office Communications Server

loadTOCNode(2, 'moreinformation');

Single Label Domains

loadTOCNode(3, 'moreinformation');
Because the use of SLDs is not a recommended practice, Office Communications Server and Office Live Communications Server products are not tested in this scenario. Therefore, there may be incompatibilities when these products are implemented in an SLD environment.

Affected Office Communications Server and Office Live Communications Server products include the following:

• Office Communications Server 2007 R2
  (http://www.microsoft.com/communicationsserver/en/us/default.aspx)
  
• Office Communications Server 2007
  (http://www.microsoft.com/uc/en/us/products.aspx)
  
• Office Live Communications Server 2005
  (http://www.microsoft.com/downloads/details.aspx?familyid=836ECEC8-961D-4F6D-8397-58105013CEFD&displaylang=en)
  

Product Compatibility page on the DNS Namespace Planning Solution Center
(http://support.microsoft.com/gp/gp_namespace_master#tab4)

Microsoft Office Communications Server 2007 R2

Things You Must Know Before Completing Your Topology Design
(http://technet.microsoft.com/en-us/library/dd425370(office.13).aspx)

On a computer that is running Windows 7 or Windows Server 2008 R2, an error that resembles the following is logged in the Application log:

Or, on a computer that is running Windows Vista or Windows Server 2008, an error that resembles the following is logged in the Application log:

This error occurs because the certificate "Microsoft Certificate Trust List Publisher" expired. A copy of the expired certification exists in the CryptnetUrlCache folder.

To resolve the problem, follow these steps:

1. Start a command prompt. To do this, click Start
   Collapse this imageExpand this image

   

   , click All Programs, click Accessories, and then click Command Prompt.

2. At the command prompt, type the following command and then press ENTER:
   certutil -urlcache * delete

   Note If the expired certificate is cached in the system profile, you must run the certuil command in the system context. To do this, follow these steps:

   1. Download the PSExec tool from the following Microsoft Web site:
      http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
      (http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx)
      
   2. Extract the tool.
   3. Start a command prompt and change to the directory where you save PSExec, and run the following command:
      psexec -i -s cmd.exe
   4. Run the certutil -urlcache * delete command

�

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Consider the following scenario:

• You have a computer that is running an x86-based version of Windows Server 2003 Service Pack 2 (SP2).
• You start an application that does the following:
  • The application allocates a large block of a contiguous memory buffer. For example, the application allocates a memory buffer that is more than 700 MB. 
  • The application uses the Open Database Connectivity (ODBC) driver to connect to a database.

In this scenario, the block of the contiguous memory buffer may not be allocated. Therefore, the application may not start. Or, random application failures occur after the application starts. 

Note When you run this application on a computer that is running Windows Server 2003 Service Pack 1 (SP1), this issue does not occur.

This issue occurs because the Odbc32.dll module is rebased at the address 0x48890000. When the Odbc32.dll module is loaded at this address, memory fragmentation of the Windows user address space occurs. Therefore, the issue that is mentioned in the "Symptoms" section occurs.

Hotfix information

loadTOCNode(2, 'resolution');
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 Web site:

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

loadTOCNode(3, 'resolution');
To apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

loadTOCNode(3, 'resolution');
To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

loadTOCNode(3, 'resolution');
You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

loadTOCNode(3, 'resolution');
This hotfix does not replace a previously released hotfix.

File information

loadTOCNode(3, 'resolution');
The English (United States) 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 Server 2003 file information notes

loadTOCNode(4, 'resolution');

• In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2003

loadTOCNode(4, 'resolution');

To work around this issue, allocate small blocks of a memory buffer instead of a large block. For example, allocate the memory of some small discontinuous memory buffers into a list, and then use this memory as a large memory buffer.

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

If a Windows 7 client does not have a WSD subscription and a WSD print job is sent while the printer is in a "User Intervention Required" state, the job will not complete until the device is powered down or the spooler is restarted.�

This issue is due to the Windows 7 client not having a WSD subscription to the WSD printer. Some WSD devices have a subscription limit on active connections to the printer. When a client does not have a subscription to the printer (exceeded the number of available subscriptions for the printer), it will not receive notification that the printer has changed status from "User Intervention Required" to "Ready" causing the print job to remain in the print queue. If the printer power cycles, or the spooler is restarted, Windows will then recognize that the “User Intervention Required” condition has been cleared and the print job will process as expected. Windows clients that do have a subscription to the printer will recognize the change in status automatically. 

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.