This problem occurs only with certain combinations of applications and printer drivers. For example, this problem may occur when you print a graphics document in Adobe Photoshop in booklet mode by using a monochrome printer driver that supports Hewlett-Packard Graphics Language 2 (HPGL2).

Note This issue is not caused by the applications or printer drivers.

Back to the top

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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

To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 (SP1) installed.

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

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008.
• The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Back to the top

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

Back to the top

Back to the top

List of issues that are fixed

This hotfix fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

•

In the German version of SharePoint Server 2007, you try to add a picture to a SharePoint page in the Foto section. In this section, the title of the button to select the picture that you want to use is Grafik schließen. In German, this means, Close picture. However, this could also be interpreted to mean, Remove picture.

Back to the top

Hotfix information

A supported hotfix is now 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 this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next 2007 Microsoft Office servers service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

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

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

32-bit version

The German version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb944710-fullfile-x86-de-de.exe	12.0.6300.5000	2,971,336	01-Feb-2008	04:19	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
OSRCHMUI-de-de.msp	Not Applicable	1,825,280	31-Jan-2008	18:38	Not Applicable
Spsmui-de-de.msp	Not Applicable	1,638,400	31-Jan-2008	18:38	Not Applicable

After the hotfix is installed, the German version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

OSRCHMUI-de-de.msp

File name	File version	File size	Date	Time	Platform
Cssportalstyle.css	Not Applicable	27,003	07-Dec-2007	09:49	Not Applicable
Mssmsg.dll	12.0.6300.5000	276,000	14-Dec-2007	14:20	Not Applicable
Notesstp.exe.oss	12.0.6300.5000	234,528	14-Dec-2007	14:20	Not Applicable
Oss.search.data.sql	Not Applicable	362,539	14-Dec-2007	13:04	Not Applicable
Oss.search.intlr.dll	12.0.6300.5000	177,184	14-Dec-2007	14:20	Not Applicable
Oss.search.sql	Not Applicable	343,527	14-Dec-2007	13:04	Not Applicable
Spsintlr.dll	12.0.6300.5000	1,156,176	07-Dec-2007	12:42	Not Applicable

Spsmui-de-de.msp

File name	File version	File size	Date	Time	Platform
Cssportalstyle.css	Not Applicable	27,003	07-Dec-2007	09:49	Not Applicable
Editmenu.js	Not Applicable	11,844	24-Jan-2008	07:56	Not Applicable
Htmledtr.js	Not Applicable	290,203	24-Jan-2008	07:56	Not Applicable
Ptdlg.js	Not Applicable	2,319	24-Jan-2008	07:56	Not Applicable
Sm.js	Not Applicable	52,671	24-Jan-2008	07:55	Not Applicable
Spsintlr.dll	12.0.6300.5000	1,156,176	07-Dec-2007	12:42	Not Applicable

64-bit version

The German version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb944710-fullfile-x64-de-de.exe	12.0.6300.5000	2,908,368	01-Feb-2008	04:19	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
OSRCHMUI-de-de.msp	Not Applicable	1,761,792	31-Jan-2008	18:50	Not Applicable
Spsmui-de-de.msp	Not Applicable	1,638,400	31-Jan-2008	18:50	Not Applicable

After the hotfix is installed, the German version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

OSRCHMUI-de-de.msp

File name	File version	File size	Date	Time	Platform
Cssportalstyle.css	Not Applicable	27,003	07-Dec-2007	09:49	Not Applicable
Mssmsg.dll	12.0.6300.5000	279,584	14-Dec-2007	14:55	Not Applicable
Oss.search.data.sql	Not Applicable	362,539	14-Dec-2007	13:04	Not Applicable
Oss.search.intlr.dll	12.0.6300.5000	177,184	14-Dec-2007	14:55	Not Applicable
Oss.search.sql	Not Applicable	343,527	14-Dec-2007	13:04	Not Applicable
Spsintlr.dll	12.0.6300.5000	1,156,176	07-Dec-2007	13:18	Not Applicable

Spsmui-de-de.msp

File name	File version	File size	Date	Time	Platform
Cssportalstyle.css	Not Applicable	27,003	07-Dec-2007	09:49	Not Applicable
Editmenu.js	Not Applicable	11,844	24-Jan-2008	07:56	Not Applicable
Htmledtr.js	Not Applicable	290,203	24-Jan-2008	07:56	Not Applicable
Ptdlg.js	Not Applicable	2,319	24-Jan-2008	07:56	Not Applicable
Sm.js	Not Applicable	52,671	24-Jan-2008	07:55	Not Applicable
Spsintlr.dll	12.0.6300.5000	1,156,176	07-Dec-2007	13:18	Not Applicable

Back to the top

Back to the top

Back to the top

Back to the top

install.exe
install.res.1028.dll
install.res.1031.dll
install.res.1033.dll
install.res.1036.dll
install.res.1040.dll
install.res.1041.dll
install.res.1042.dll
install.res.2052.dll
install.res.3082.dll
vcredist.bmp
globdata.ini
install.ini
eula.1028.txt
eula.1031.txt
eula.1033.txt
eula.1036.txt
eula.1040.txt
eula.1041.txt
eula.1042.txt
eula.2052.txt
eula.3082.txt
vc_redist.msi
vc_redist.cab

Back to the top

Back to the top

Back to the top

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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

To apply this hotfix, you must have Subsystem for UNIX-based Applications installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Back to the top

Back to the top

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

Back to the top

In this scenario, Windows Vista cannot obtain an IP address.

Back to the top

Back to the top

To resolve this issue, disable the DHCP BROADCAST flag in Windows Vista. To do this, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then click regedit in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip Parameters Interfaces {GUID} In this registry path, click the (GUID) subkey that corresponds to the network adapter that is connected to the network.
3.	On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4.	In the New Value #1 box, type DhcpConnEnableBcastFlagToggle, and then press ENTER.
5.	Right-click DhcpConnEnableBcastFlagToggle, and then click Modify.
6.	In the Value data box, type 1, and then click OK.
7.	Close Registry Editor.

Back to the top

Note A data value of 0 disables this registry entry. You can use this registry entry to prevent Windows Vista from using the DHCP BROADCAST flag. After you set this registry entry, Windows Vista never uses the DHCP BROADCAST flag.

Back to the top

• Users of Microsoft Office Outlook 2003 Service Pack 1 (SP1) connect to an Exchange 2007 server and then download the OAB.
• Users of Outlook 2003 Service Pack 2 (SP2) clients or of later versions of Outlook 2003 clients connect to a Microsoft Exchange Server 2003 SP1 server to download the OAB. After this, the mailboxes of these clients are migrated to an Exchange 2007 server. Then, these users download the OAB again.
• The OAB is located on an Exchange 2003 SP1 server, and then it is moved to an Exchange 2007 server. After that, the users of the Exchange 2003 SP1 server download the OAB again.

Back to the top

For more information about Update Rollup 5 for Exchange 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

• Home users:
  http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx)

  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:

  http://update.microsoft.com/microsoftupdate/ (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/MS08-069.mspx (http://www.microsoft.com/technet/security/bulletin/MS08-069.mspx)

Back to the top

How to obtain help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site:

North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

Back to the top

Known issues with this security update

• When you install this security update on a computer that is running Windows Vista or Windows Server 2008, you may have to restart the computer two times to complete the installation. This issue may occur if you install an XML Core Services 4.0–based update together with an update that contains inbox drivers. For example, the following updates contain inbox drivers:
  956697  (/Feedback.aspx?kbNumber=956697/ ) Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
  938371  (/Feedback.aspx?kbNumber=938371/ ) A software update is available for the Windows Vista installation components

  This issue occurs because Microsoft Windows Installer (MSI)-based installations will not continue while inbox drivers are updating. This is because inbox drivers set the impactful transaction flag and the reboot required flag at the servicing stack level for Windows Vista and Windows Server 2008. Therefore, the update for XML Core Services 4.0 will fail during installation if an update that contains an inbox driver is applied first. After the inbox driver has installed, and then the computer is restarted, the installation of security update for XML Core Services 4.0 will succeed. However, an additional restart is required to complete the installation.

  To avoid this issue, install the security update for XML Core Services 4.0 before you install the update that contains inbox drivers.

• This security update may repeatedly appear in the update list on Microsoft Update or on Windows Update if one of the system files is corrupted or if it has not been updated correctly.For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941729  (/Feedback.aspx?kbNumber=941729/ ) Security updates for Microsoft XML Core Services 4.0 Service Pack 2 may repeatedly appear in the update list on Microsoft Update or on Windows Update
• After you install security update 954430, certain application compatibility issues and reliability issues may occur in Microsoft XML Core Services 4.0 SP2 on a Windows Vista-based computer. To resolve these issues, install the update that is described in Microsoft Knowledge Base article 941833.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941833  (/Feedback.aspx?kbNumber=941833/ ) An update is available that improves the compatibility and the reliability of Microsoft XML Core Services 4.0 Service Pack 2 on a Windows Vista-based computer

  An update is available that improves the compatibility and the reliability of Microsoft XML Core Service 4.0 Service Pack 2 on a Windows Vista-based computer

• The following security updates do not support the complete removal of MSXML 4.0:
  • Security update 954430 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for MSXML 4.0 Service Pack 1 (SP1)
  • Security update 936181 for MSXML 4.0 Service Pack 2 (SP2)

  This situation occurs because this version of MSXML is installed in side-by-side mode. To work around this issue, follow these steps:

  1. Remove security update 954430 by using the Add or Remove Programs item in Control Panel.
  2. Delete the Msxml4.dll file from the %SystemRoot% System32 folder.
  3. Repair the previous installation of MSXML 4.0 by using the Add or Remove Programs item in Control Panel.

  The earlier versions of the Msxml4.dll file and of the Msxml4r.dll file are restored to the side-by-side folder and to the %SystemRoot% System32 folder.

• You may receive the following error message when you install security update 954430 from Windows Update:
  Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.

  When this error occurs, you may also notice information that resembles the following in the log file:

  Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  MSI (s) (20:18) [17:52:31:612]: Product: MSXML 4.0 SP2 (KB954430) — Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  === Logging stopped: 11/10/2006 17:53:07 ===
  MSI (c) (34:20) [17:53:07:252]: Note: 1: 1708
  MSI (c) (34:20) [17:53:07:260]: Product: MSXML 4.0 SP2 (KB954430) — Installation failed.
  MSI (c) (34:20) [17:53:07:267]: Windows Installer installed the product. Product Name: MSXML 4.0 SP2 (KB954430). Product Version: 4.20.9839.0. Product Language: 1033. Installation success or error status: 1603.
  MSI (c) (34:20) [17:53:07:313]: Grabbed execution mutex.
  MSI (c) (34:20) [17:53:07:319]: Cleaning up uninstalled install packages, if any existMSI (c) (34:20) [17:53:07:331]: MainEngineThread is returning 1603
  === Verbose logging stopped: 11/10/2006 17:53:07 ===

  To work around this problem, manually install the security update from the Microsoft Download Center, and then click Ignore when the error message is displayed. To confirm that the installation was successful, verify that the version of the Msxml4.dll file in the %SystemRoot% System32 folder is 4.20.9870.0.

Back to the top

File information

The English (United States) version of this security update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Back to the top

In this scenario, Event ID 1699 is logged many times in the Directory Service event log of the writable domain controller. These events resemble the following event:

Source: NTDS Replication
Date: Date
Event ID: 1699
Level: Error
Keywords: Classic
User: user name
Computer: computer name
Description:
This directory service failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send change requests to the directory service at the following network address.

Directory partition: Distinguished Name (DN)
Network address: address

Additional Data
Error value: 8453 Replication access was denied.

Sometimes, Event ID 2041 may also be logged. The event that is logged resembles the following event:

Event Type: Information
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 2041
Date: date
Time: time
User: N/A
Computer: computer name
Description:
Duplicate event log entries were suppressed.
See the previous event log entry for details. An entry is considered a duplicate if the event code and all of its insertion parameters are identical. The time period for this run of duplicates is from the time of the previous event to the time of this event.

Event Code: c00006a3
Number of duplicate entries: 1

These events fill the Directory Service event log and prevent administrators from troubleshooting issues according to the event logs.

Back to the top

Back to the top

Back to the top

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 this specific problem. 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

T o apply this hotfix, you must have Windows Server 2008 installed on the writable domain controller.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, x86-based versions

Windows Server 2008, x64-based versions

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1080
Date: 1/14/2008
Time: 5:39:42 PM
Description: Cluster service could not write to a file (C: DOCUME~1 CLUSAD~1 LOCALS~1 Temp CLS1627.tmp). The disk may be low on disk space, or some other serious condition exists.

The syntax of the Set-ExchangeServer command resembles the following.

Set-ExchangeServer cluster_mailbox_server_name -staticExcludedDomainControllers domain_controller_name -staticDomainControllers -staticGlobalCatalogs -id  -staticConfigDomainController 

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

If you restore the configuration database, data in the configuration database will not be synchronized with data in other SharePoint Server 2007 or Windows SharePoint Services 3.0 databases.If this data is not synchronized, users may experience various random errors.

For example, a Windows SharePoint Services 3.0 content database may contain data about a newer site. If the configuration database does not contain information about this site, the site is orphaned.

For more information about data protection and recovery in small to medium-sized deployments of SharePoint Server 2007, visit the following Microsoft TechNet Web site:

In this scenario, the application may crash.

Back to the top

Back to the top

Windows Vista 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 this specific problem. 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

Windows Vista with Service Pack 1, x86-based versions

Windows Vista, x64-based versions

Windows Vista with Service Pack 1, x64-based versions

Windows Vista with Service Pack 1, Itanium-based versions

Back to the top

Windows Server 2008 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 this specific problem. 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, x86-based versions

Windows Server 2008, Itanium-based versions

Windows Server 2008, x64-based versions

Back to the top

Back to the top

For more information about how an application can provide performance counter data by using the performance counter version 2.0 APIs, visit the following Microsoft Web site:

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

Back to the top

Back to the top

Back to the top

Method 1

Delete the IP address entry by using the ALT+E keyboard shortcut to the Delete button (This button is called Elimina in Italian). This will delete the Notification Server from the list. To do this, follow these steps:

1.	Click Start, point to Administrative Tools, and then click DNS. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	In the console tree, click Host name. Note Host name represents the host name of the DNS server.
3.	In the console tree, click Forward Lookup Zones.
4.	Under Forward Lookup Zones, right-click the zone that you want, and then click Properties.
5.	Click the Zone Transfers tab.
6.	If Allow zone transfers is not enabled, click to select the check box next to Allow zone transfers, and then click Notify.
7.	Click the server IP address that you want to delete from the list, and then press ALT+E.
8.	Click OK to confirm the changes.

Back to the top

Method 2

Remove the Notification Server by using the Dnscmd.exe command-line tool. To do this, follow these steps:

1.

Click Start , type cmd in the Start Search box, right-click cmd in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.

2.

At the command prompt, type the following command, and then press ENTER. Dnscmd.exe <ServerName> /ZoneResetSecondaries <ZoneName> /NotifyList <List of IPs> Note In this command, <ServerName> is the name of the DNS server, <ZoneName> is the name of the DNS zone, and <List of IPs> is the space-separated list of the Notification Server IPs. The list of IPs must include the IPs of all the existing Notification Servers, and the list must exclude the IP address for the Notification Server that the user wishes to have removed.

Back to the top

• You install the Hyper-V role on a server that is running Windows Server 2008.
• You create a virtual machine that is running Microsoft Windows 2000 Service Pack 4 (SP4).
• You install Integration Services on the Windows 2000 SP4-based virtual machine.
• In Hyper-V Manager, you click Shut Down on the Action menu to shut down the Windows 2000 SP4-based virtual machine.

In this scenario, the Windows 2000 SP4-based virtual machine may not shut down as expected. You may receive an error message that resembles the one of the following:

Back to the top

Feature information

A supported feature that modifies the product’s default behavior is now available from Microsoft. However, it is intended to modify only the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next software update that contains this feature.

To obtain this feature immediately, contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Prerequisites

To apply this feature, you must be running Windows Server 2008 on the computer.

Restart requirement

You must restart the computer after you apply this feature.

Feature replacement information

This feature does not replace any other updates.

How to synchronize the DSRM Administrator password on a Windows Server 2008-based domain controller with the password of a domain user account

After you apply this feature, you can synchronize the DSRM Administrator password on a Windows Server 2008-based domain controller with the password of a domain user account. To do this, run the following command on the Windows Server 2008-based domain controller:

Note In this command, <AccountName> is a placeholder for the name of the domain user account that you want to use.

This command synchronizes the DSRM Administrator password one time. If you want to perform another synchronization, you must run this command again.

File information

The English version of this feature has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

Back to the top

Additional file information for Windows Server 2008

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

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

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

Back to the top

For more information about Update Rollup 6 for Exchange 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For more information about the PR_MESSAGE_CLASS class, visit the following Web site:

Back to the top

Back to the top

Back to the top

Back to the top

In this scenario, a handle leak may occur. Specifically, when you run the Net Session command, invalid session information is returned. This session information may indicate in the Opens column that this session has an invalid count.

After the issue occurs, you must restart the SMB service or the computer that is running this service.

Note This issue also occurs in Windows Server 2008.

Back to the top

Back to the top

Hotfix information

A supported hotfix is now 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 this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Vista service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008, x86-based versions

Windows Vista and Windows Server 2008, x64-based versions

Windows Vista and Windows Server 2008, IA-64-based versions

Back to the top

Back to the top

Back to the top

Back to the top

Note The range is set separately for each transport and for each version of IP. The port range is now truly a range with a starting point and with an endpoint. Microsoft customers who deploy servers that are running Windows Server 2008 may experience problems with RPC communication between servers if firewalls are used on the internal network. In these cases, we recommend that you reconfigure the firewalls to allow for traffic between servers in the dynamic port range of 49152 through 65535. This range is in addition to well-known ports that are used by services and by applications. Or, the port range that is used by the servers can be modified on each server. You adjust this range by using the netsh command, as follows:

This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. The following are sample commands:

•	netsh int ipv4 set dynamicport tcp start=10000 num=1000
•	netsh int ipv4 set dynamicport udp start=10000 num=1000
•	netsh int ipv6 set dynamicport tcp start=10000 num=1000
•	netsh int ipv4 set dynamicport udp start=10000 num=1000

The examples set your dynamic port range to start at port 10000 and to end at port 11000 (1000 ports). The minimum range of ports you can set is 255. The minimum starting port that you can set is 1025. The maximum end port that is based on the range you set cannot exceed 65535. To duplicate the default behavior of Windows Server 2003, use 1025 as your start port, and then use 3975 as your end port for both TCP and UDP.

Back to the top

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Back to the top

Back to the top