Microsoft Support

Page 41 of 711« First...102030...3940414243...506070...Last »

You cannot uninstall Exchange Server 2010 RTM after you install Update Rollup 2, Update Rollup 3, or Update Rollup 4 for Exchange Server 2010

The following error was generated when “$error.Clear(); uninstall-MsiPackage -PackagePath ($RoleInstallPath + “MailboxMSFTE.MSI”) -Log
File ($RoleSetupLoggingPath + “InstallSearch.msilog”)” was run: “Couldn’t open package ‘C: Program FilesMicrosoftExchange ServerV14Mail
boxMSFTE.MSI’. Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. Error code is 1638.”.

The Exchange Server setup operation did not complete. Visit http://support.microsoft.com

(http://support.microsoft.com/)

and enter the Error ID to find more information.
Exchange Server setup encountered an error.

Continued here:
You cannot uninstall Exchange Server 2010 RTM after you install Update Rollup 2, Update Rollup 3, or Update Rollup 4 for Exchange Server 2010

Description of Update Rollup 3 for Exchange Server 2007 Service Pack 2

Microsoft has released Update Rollup 3 for Microsoft Exchange Server 2007 Service Pack 2 (SP2). This article describes the following information about the update rollup:
  • The issues that the update rollup fixes
  • How to obtain the update rollup

Issues that the update rollup fixes

Update Rollup 3 for Exchange Server 2007 SP2 fixes the issues that are described in the following Microsoft Knowledge Base articles:

976108

(http://support.microsoft.com/kb/976108/
)

“451 4.4.0 DNS Query Failed” status message in an Exchange Server 2007 Edge Transport server

976460

(http://support.microsoft.com/kb/976460/
)

Later updates do not match a calendar item that an Exchange Server 2007 user updates by using Exchange ActiveSync on a mobile device

977179

(http://support.microsoft.com/kb/977179/
)

You receive an “0x800423f0″ error message when you perform system state backups on the passive node of Windows Server 2008-based Exchange Server 2007 CCR clusters

977531

(http://support.microsoft.com/kb/977531/
)

An external recipient misses the last occurrence of a recurring meeting request or a recurring appointment that is sent from an Exchange Server 2007 user

977923

(http://support.microsoft.com/kb/977923/
)

The Edgetransport.exe process crash when it process meeting requests in Exchange Server 2007

978137

(http://support.microsoft.com/kb/978137/
)

The subject of a confirmation message is garbled for certain languages when a remote device wipe operation is performed in Exchange Server 2007

978200

(http://support.microsoft.com/kb/978200/
)

The sender address of a forwarded meeting request does not include “on behalf of” as expected in an Exchange Server 2003 organization and an Exchange Server 2007 organization mixed environment

978253

(http://support.microsoft.com/kb/978253/
)

A SSL certificate validation error is generated on an Exchange Server 2007 server when you run any test commands after you run the Test-SystemHealth command

978469

(http://support.microsoft.com/kb/978469/
)

A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook

978517

(http://support.microsoft.com/kb/978517/
)

The Microsoft Exchange Information Store service stops responding on an Exchange Server 2007 server

978521

(http://support.microsoft.com/kb/978521/
)

The synchronization and the reconciliation between Microsoft Office Outlook and a BlackBerry mobile device fails when a mailbox is moved around between two Exchange Server 2007

978528

(http://support.microsoft.com/kb/978528/
)

The Microsoft Exchange Information Store service crashes on a Microsoft Exchange Server 2007 server when a user tries to access a specific calendar item

978832

(http://support.microsoft.com/kb/978832/
)

Read items are marked incorrectly as unread items in an Exchange Server 2007 public folder

979055

(http://support.microsoft.com/kb/979055/
)

A delegate cannot save three settings of Resource Settings for an Exchange Server 2007 resource mailbox in OWA

979170

(http://support.microsoft.com/kb/979170/
)

You receive an error message when you use ExBPA to schedule a scan on an Exchange Server 2007 SP2 server

979219

(http://support.microsoft.com/kb/979219/
)

The store.exe process hangs on an Exchange Server 2007 server

Update rollup information

To download and to install Update Rollup 3 for Exchange Server 2007 SP2, visit the following Microsoft Update Web site: Note Update rollups for Exchange 2007 are not detected on clustered Exchange 2007 systems by Microsoft Update.
You may want to deploy Update Rollup 3 for Exchange Server 2007 SP2 to multiple computers that are running Exchange Server 2007. Or, you may want to deploy Update Rollup 3 for Exchange Server 2007 SP2 to clustered servers that are running Exchange Server 2007. The update rollup is also available from the Microsoft Download Center.

The following file is available for download from the Microsoft Download Center:

Release Date: March 11, 2010

Important Before you install an update rollup or a service pack, visit the following Microsoft Web site:

For more information about prerequisites, installation instructions, and known issues, visit the following Microsoft Web site: For more information about the Exchange 2007 servicing model, visit the following Microsoft Web site:
This update rollup does not apply to Exchange Server 2007 release to manufacturing (RTM) version or to Exchange 2007 Service Pack 1 (SP1). The series of update rollup packages for Exchange Server 2007 SP2 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM or Exchange 2007 SP1.
For a list of update rollups that apply to Exchange Server 2007 RTM or to Exchange Server 2007 SP1, visit the following Microsoft Web site:

Restart requirement

The required services are automatically stopped and then restarted when you apply this update rollup.

Removal information

To remove Update Rollup 3 for Exchange Server 2007 SP2, use Add or Remove Programs in Control Panel. Then, remove update 979784.

For more information about terminology that Microsoft uses to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 979784 – Last Review: June 21, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Server 2007 Service Pack 2, when used with:
    • Microsoft Exchange Server 2007 Enterprise Edition
    • Microsoft Exchange Server 2007 Standard Edition
kbsurveynew kbexpertiseinter kbhotfixrollup kbfix kbqfe KB979784

Read this article:
Description of Update Rollup 3 for Exchange Server 2007 Service Pack 2

When you run the Forefront Client Security (FCS) client setup tool (ClientSetup.exe), MOM agent components appear in the "Add or Remove Programs" dialog box

When you run the Microsoft Forefront Client Security (FCS) client setup tool (ClientSetup.exe), you may experience one or more of the following symptoms:
  • Microsoft Operations Manager (MOM) agent components appear in the Add or Remove Programs dialog box. However, these components did not previously appear in this dialog box.
  • When you run the SetActionAccount.exe tool from the InstallationDirectoryMicrosoft ForefrontClient SecurityServerMicrosoft Operations Manager folder, a MOM action account appears. However, this account is not the MOM action account that you specified when you set up FCS. The SetActionAccount.exe tool is configured to run as the service identity account.
  • The hourly script on the MOM server automatically approves new FCS client computers that reside in the Pending-Approval state.
  • In the Client Security console, the 14-day History chart and some historical reports that appear on the Dashboard tab may not be displayed correctly.
This problem occurs because the FCS client setup tool cannot detect an evaluation edition of MOM 2005 SP1 that has been installed for FCS. Therefore, when the FCS client setup tool runs, it tries to reinstall the MOM agent on the FCS collection server. Then, MOM no longer functions correctly.
If you have already installed the FCS client on the FCS collection server by running the FCS client setup tool, follow these steps to resolve the problem:
  1. Uninstall the FCS collection server, MOM server, and MOM agent components from the list in the Add or Remove Programs dialog box.
  2. Reinstall the collection server role on FCS by using the FCS ServerSetup.exe tool.

Note If FCS collection server has other roles, you do not have to make any changes to these roles.

If you have not installed the FCS client on the FCS collection server by running the FCS client setup tool, work around this problem by using the /NOMOM switch.

Note When you install the FCS client, we recommend that you install the full version of MOM 2005 SP1 instead of the evaluation version.

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

Article ID: 941881 – Last Review: June 21, 2014 – Revision: 3.0


Applies to
  • Microsoft Forefront Client Security
kbprb kbtshoot kbexpertiseinter kbsecurity kbbug fep2010swept KB941881

Read More:
When you run the Forefront Client Security (FCS) client setup tool (ClientSetup.exe), MOM agent components appear in the "Add or Remove Programs" dialog box

MS10-017: Description of the security update for Excel 2007: March 9, 2010

Microsoft has released security bulletin MS10-017. To view the complete security bulletin, visit one of the following Microsoft Web sites:

How to obtain help and support for this security update

Help installing updates:
Support for Microsoft Update

(http://support.microsoft.com/ph/6527)

Security solutions for IT professionals:
TechNet Security Troubleshooting and Support

(http://technet.microsoft.com/security/bb980617.aspx)

Help protect your computer that is running Windows from viruses and malware:
Virus Solution and Security Center

(http://support.microsoft.com/contactus/cu_sc_virsec_master)

Local support according to your country:
International Support

(http://support.microsoft.com/common/international.aspx)

Known issues with this security update

After you install this security update, you may receive an error message that resembles the following when you try to save a shared workbook:

The file is no longer shared

This problem can occur if the file is saved to a network location and then configured as a shared workbook.

To work around this problem, use either of the following methods:

  • To avoid this problem when you create a workbook that must be shared, turn on the shared workbook option before you save the workbook to a network share.
  • If the problem has already occurred, follow these steps:
    1. Open the shared workbook, and then save it to a local drive.
    2. Turn on the shared workbook option.
    3. Save the workbook on the network share.

    For more information about how to share a workbook, visit the following Microsoft Web page:

    To resolve this problem, install hotfix 982308.

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

    982308

    (http://support.microsoft.com/kb/982308/
    )

    MS10-038 and MS10-036: Description of the security update for Excel 2007: June 8, 2010

Prerequisites to apply this security update

To install this security update, you must have one of the following installed:

  • 2007 Microsoft Office suite Service Pack 2 (SP2)
  • 2007 Microsoft Office suite Service Pack 1 (SP1)

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

949585

(http://support.microsoft.com/kb/949585/
)

How to obtain the latest service pack for the 2007 Office suite

Security update replacement information

This security update replaces the following security update:

973593

(http://support.microsoft.com/kb/973593/
)

MS09-067: Description of the security update for Excel 2007: November 10, 2009

Removal information

To remove this security update, use the Add or Remove Programs item or use the Programs and Features item in Control Panel.

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.

Security update for Microsoft Office Excel 2007 (KB978382)

Collapse this tableExpand this table

File name File version File size Date Time
Excel.exe 12.0.6524.5003 18,343,272 15-Jan-2010 08:57
Excel.man Not Applicable 791 26-Feb-2009 19:58
Xlcall32.dll 12.0.6500.5000 10,120 26-Feb-2009 21:09

Article ID: 978382 – Last Review: June 21, 2014 – Revision: 7.0


Applies to
  • Microsoft Office Excel 2007
kbexpertisebeginner kbsurveynew kbsecvulnerability kbsecurity kbsecbulletin kbfix kbexpertiseinter kbbug atdownload KB978382

Read More:
MS10-017: Description of the security update for Excel 2007: March 9, 2010

Forefront Client Security anti-malware engine error codes

This article lists the error codes that are available for the Microsoft Forefront Client Security anti-malware engine.
The following table lists the anti-malware engine error codes. Each error code has a 0×8050 prefix. Therefore, an ERROR_MP_BAD_SCANID error corresponds to error code 0×80508012. Additionally, an ERR_MP_REMOVE_FAILED error corresponds to error code 0×80508017.

Anti-malware engine error codes

Collapse this tableExpand this table

Symbolic name Error number
ERROR_MP_UI_CONSOLIDATION_BASE    0×80501000
ERROR_MP_ACTIONS_FAILED           0×80501001
ERROR_MP_BAD_INIT_MODULES         0×80508001
ERROR_MP_BAD_DATABASE             0×80508002
ERROR_MP_BAD_UFS                  0×80508004
ERROR_MP_NO_MEMORY                0×80508007
ERROR_MP_BAD_INPUT_DATA           0x8050800C
ERROR_MP_BAD_GLOBAL_STORAGE       0x8050800D
ERROR_MP_OBSOLETE                 0x8050800E
ERROR_MP_NOT_SUPPORTED            0x8050800F
ERROR_MP_NO_MORE_ITEMS            0×80508010
ERROR_MP_DUPLICATE_SCANID         0×80508011
ERROR_MP_BAD_SCANID               0×80508012
ERROR_MP_BAD_USERDB_VERSION       0×80508013
ERROR_MP_RESTORE_FAILED           0×80508014
ERROR_MP_FAILED_TO_SPYNET         0×80508015
ERROR_MP_BAD_ACTION               0×80508016
ERROR_MP_REMOVE_FAILED             0×80508017
ERROR_MP_SCAN_ABORTED             0×80508018
ERROR_MP_NOT_FOUND                0×80508019
ERROR_MP_BAD_CONFIGURATION        0×80508020
ERROR_MP_QUARANTINE_FAILED        0×80508021
ERROR_MP_REBOOT_REQUIRED          0×80508022
ERROR_MP_THREAT_NOT_FOUND         0×80508023
ERROR_MP_FULL_SCAN_REQUIRED       0×80508024
ERROR_MP_MANUAL_STEPS_REQUIRED    0×80508025
ERROR_MP_REMOVE_NOT_SUPPORTED     0×80508026
ERROR_MP_REMOVE_LOW_MEDIUM_DISABLED 0×80508027
ERROR_RELO_BAD_EHANDLE            0×80509001
ERROR_RELO_KERNEL_NOT_LOADED      0×80509003
ERROR_MP_BADDB_OPEN               0x8050A001
ERROR_MP_BADDB_HEADER             0x8050A002
ERROR_MP_BADDB_OLDENGINE          0x8050A003
ERROR_MP_BADDB_CONTENT            0x8050A004
ERROR_MP_BADDB_NOTSIGNED          0x8050A005
ERR_MP_RESCAN_REQUIRED      0×80508029

Article ID: 939359 – Last Review: June 21, 2014 – Revision: 4.0


Applies to
  • Microsoft Forefront Client Security
kbhowto kbexpertisebeginner kbinfo fep2010swept KB939359

Visit site:
Forefront Client Security anti-malware engine error codes

Games for Windows LIVE: How to change your gamertag through Games for Windows – LIVE

This article describes how to change your Gamertag in Games for Windows – LIVE.
You can easily change your Gamertag in exchange for 800 Microsoft Points.

For more information about how to purchase Microsoft Points for Games for Windows – LIVE, click the following article number to view the article in the Microsoft Knowledge Base:

959446

(http://support.microsoft.com/kb/959446/
)

How to access billing and points management for Games for Windows – LIVE

For more information about how to change a gamertag on your Xbox 360 console, click the following article number to view the article in the Microsoft Knowledge Base:

908658

(http://support.microsoft.com/kb/908658/
)

How to change your Xbox LIVE Gamertag

To change your Gamertag, follow these steps:

  1. Start a Games for Windows – LIVE game.
  2. Do one of the following things:
    • Press the Home key on your keyboard.
    • Press the Guide button on the Xbox controller.
    • Select LIVE from the game menu.

    The Games for Windows – LIVE Guide will be displayed at the top of screen.

  3. Sign in to the Games for Windows – LIVE client in the game.
  4. Select the Gamertag.

    Collapse this imageExpand this image

  5. Select Edit Gamer Profile on the Gamer Profile page.

    Collapse this imageExpand this image

  6. Select Gamertag on the Edit Gamer Profile page to continue to the next page.

    Collapse this imageExpand this image

  7. If you have an insufficient Points balance to pay for the Gamertag change, you are prompted to Add Microsoft Points. Select Change Gamertag to continue.

    Collapse this imageExpand this image

  8. Enter a new Gamertag of up to 15 characters into the empty field, and then select Submit to continue.

    If your Gamertag is unique, the change will be successful. If the Gamertag that you selected is already being used, you will be prompted to select another Gamertag.

    Collapse this imageExpand this image

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.

Article ID: 977901 – Last Review: June 21, 2014 – Revision: 1.0

kbsurveynew kbPubTypeKC kbinfo KB977901

See the article here:
Games for Windows LIVE: How to change your gamertag through Games for Windows – LIVE

FIX: SQL connections to BizTalk databases are not cleaned up or reused when you use the BiztalkOperations class in BizTalk Server 2006 R2 or BizTalk Server 2009

Consider the following scenario:

  • You have a computer that is running Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009.
  • You develop a program to access information that is displayed on the Group Hub page in the BizTalk Administration Management Console by using the BizTalkOperations class.

In this scenario, you run the program, and many SQL connections to the various BizTalk databases are opened. However, these SQL connections are not cleaned up or reused. They are only removed when you exit the program. Therefore, after the program is running for some time, the memory usage by SQL Server increases. When this problem occurs, the program experiences poor performance.

Note You can monitor SQL connections in SQL Server Management Studio by using the Activity Monitor.

For example, you write the following code to extract the IBaseMessage.BodyPart property of messages from the BizTalk MessageBox database (BizTalkMsgBoxDb) by using the BizTalkOperations.GetMessages() method:

BizTalkOperations operation = new BizTalkOperations();
IEnumerable bizTalkMsgs = operation.GetMessages();
foreach (BizTalkMessage msg in bizTalkMsgs)

string hostname=msg.HostName;
IBaseMessagePart bodyPart = msg.BodyPart;
...

When you run the program, a SQL connection is created every time that a bodyPart property is accessed.

This problem occurs because there is an error in the connection string that theBizTalkOperations class uses to connect to the BizTalk MessageBox database.
After you apply this hotfix, connection pooling is enabled when you use the BizTalkOperations class to access the BizTalk databases. SQL connections can be reused and the performance is improved.

Cumulative updated information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2429050

(http://support.microsoft.com/kb/2429050/
)

Cumulative update package 1 for BizTalk Server 2009

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2006 R2 service pack that contains this hotfix.

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Microsoft.biztalk.dbaccessor.dll 3.6.1549.2 18,288 20-Oct-2009 16:12 x86

Prerequisites

You must have BizTalk Server 2006 R2 installed to apply this hotfix.

Restart information

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

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about the BizTalkOperations class and the BizTalkOperations.GetMessage method, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about the IBaseMessage.BodyPart property, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about SQL Server Connection Pooling, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about how to install BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907

(http://support.microsoft.com/kb/2003907/
)

Information on BizTalk Server hot fixes

Article ID: 976927 – Last Review: June 21, 2014 – Revision: 3.0


Applies to
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
kbfix kbbug kbbtsadmin kbbiztalk2006r2presp2fix kbexpertiseinter kbsurveynew kbqfe KB976927

Read More:
FIX: SQL connections to BizTalk databases are not cleaned up or reused when you use the BiztalkOperations class in BizTalk Server 2006 R2 or BizTalk Server 2009

A hotfix is available to resolve some problems with the Forefront Client Security client

You experience the following symptoms when you are using Microsoft Forefront Client Security.

Symptom 1

On a computer that is running Microsoft Windows 2000 Service Pack 4, the Anti-malware user interface cannot open when you log on to the computer by using a non-administrator account.

Symptom 2

In the notification area, the Forefront Client Security icon becomes orange to indicate that an issue has occurred. When you open the Forefront Client Security client to view the issue, the client incorrectly reports that a product update is available for the Forefront Client Security client. A product update is not available.

Note In this scenario, the new product update notification differs from the new definition update notification.

Symptom 3

When you save a Microsoft Office Word document that already exists on a FAT32 volume, the file disappears unexpectedly. This occurs only when antivirus real-time protection (RTP) is enabled.

Symptom 4

The Microsoft Forefront Client Security Anti-malware Service stops unexpectedly. Then, this service does not recover automatically. This symptom occurs if the signature or the engine update is invalid.

Cause 1

Symptom 1 occurs because of a permission issue that is specific to Windows 2000. In Windows 2000, a non-administrator user is denied access to the RegisterGPNotification function. This function is used to monitor policy changes.

Cause 2

Symptom 2 occurs because a registry value is not reset as expected after a successful upgrade. To determine the current state of Forefront Client Security Agent, the Forefront Client Security client queries the following registry entry:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft ForefrontClient Security1.0AMProductUpdateAvailable

Note A value of 0 indicates that new updates are not needed. A value of 1 indicates that new updates are needed.

However, the Forefront Client Security client update package did not reset this registry value to 0 after the last upgrade.

Cause 3

Symptom 3 occurs for one of the following reasons:

  • Word sometimes deletes files when the temporary backup file cannot be accessed.
  • The I/O manager does not close a file correctly on a FAT32 volume if the Object Manager rejects the open action during security checks when the file is accessed.

Cause 4

Symptom 4 occurs because the Microsoft Forefront Client Security Anti-malware Service registers with the Service Control Manager (SCM) to automatically start two times after a failure. If an invalid signature causes the service to stop repeatedly, the SCM makes only two restart attempts and does not continue to restart the service.

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.
Note This hotfix is available from Microsoft Update or from Windows Server Update Services. If you want to obtain the file for deployment by using a different method, follow these steps:

  1. Visit the following Microsoft Update Catalog Web site:
  2. Type 938054 in the Search box, and then click Search.
  3. Click Add to add the hotfix to the basket.
  4. Near the search bar at the top, click the view basket link.
  5. Locate and then click the Download button.
  6. Click Browse, specify the folder to download the hotfix to, and then click OK.
  7. Click Continue, and then accept the EULA. The hotfix will start to download.

Prerequisites

There are no prerequisites for installing this hotfix.

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 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.
Forefront Client Security, x64-based versions

Collapse this tableExpand this table

FileName FileSize Version Date Time
AMHelp.chm 65,216 March 8, 2007 1:43:26 AM
Mpasbase.vdm 572,720 1.0.0.0 March 8, 2007 1:44:44 AM
MpAsDesc.dll 53,136 1.5.1941.0 August 2, 2007 1:24:14 AM
Mpasdlta.vdm 9,008 1.0.0.0 March 8, 2007 1:44:44 AM
Mpavbase.vdm 204,624 1.0.0.0 March 8, 2007 1:44:44 AM
Mpavdlta.vdm 9,040 1.0.0.0 March 8, 2007 1:44:44 AM
MpAvRtm.dll 154,512 1.5.1941.0 August 2, 2007 1:12:12 AM
MpClient.dll 549,264 1.5.1941.0 August 2, 2007 1:12:18 AM
MpCmdRun.exe 494,992 1.5.1941.0 August 2, 2007 1:12:18 AM
MpEngine.dll 3,758,984 1.1.2701.0 July 4, 2007 1:18:14 AM
Mpevmsg.dll 27,024 1.5.1941.0 August 2, 2007 1:23:32 AM
Mpfilter.cat 10,672 July 7, 2007 12:09:12 AM
Mpfilter.inf 2,941 March 8, 2007 1:44:42 AM
Mpfilter.sys 89,488 1.5.1941.0 July 7, 2007 12:09:12 AM
MpOAv.dll 121,232 1.5.1941.0 August 2, 2007 1:12:08 AM
MpRtMon.dll 1,184,656 1.5.1941.0 August 2, 2007 1:12:22 AM
MpSigDwn.dll 183,184 1.5.1941.0 August 2, 2007 1:12:12 AM
MpSoftEx.dll 795,024 1.5.1941.0 August 2, 2007 1:12:22 AM
MpSvc.dll|MpSvc.dll 406,928 1.5.1941.0 August 2, 2007 1:12:18 AM
MpUtil.dll 250,256 1.5.1941.0 August 2, 2007 1:12:14 AM
MSASCui.exe 1,640,336 1.5.1941.0 August 2, 2007 1:12:24 AM
MsMpCom.dll 309,136 1.5.1941.0 August 2, 2007 1:12:18 AM
MsMpEng.exe|MsMpEng.exe 18,320 1.5.1941.0 August 2, 2007 1:12:08 AM
MsMpLics.dll 12,688 1.5.1941.0 August 2, 2007 1:12:02 AM
MsMpRes.dll 767,888 1.5.1941.0 August 2, 2007 1:24:48 AM

Forefront Client Security, x86-based versions

Collapse this tableExpand this table

FileName FileSize Version Date Time
AMHelp.chm 65,216 March 8, 2007 1:43:26 AM
Mpasbase.vdm 572,720 1.0.0.0 March 8, 2007 1:44:44 AM
MpAsDesc.dll 52,624 1.5.1941.0 August 1, 2007 11:52:44 PM
Mpasdlta.vdm 9,008 1.0.0.0 March 8, 2007 1:44:44 AM
Mpavbase.vdm 204,624 1.0.0.0 March 8, 2007 1:44:44 AM
Mpavdlta.vdm 9,040 1.0.0.0 March 8, 2007 1:44:44 AM
MpAvRtm.dll 128,912 1.5.1941.0 August 1, 2007 11:19:44 PM
MpClient.dll 369,552 1.5.1941.0 August 1, 2007 11:19:54 PM
MpCmdRun.exe 341,904 1.5.1941.0 August 1, 2007 11:19:52 PM
MpEngine.dll 2,783,624 1.1.2701.0 July 3, 2007 1:18:18 AM
Mpevmsg.dll 27,024 1.5.1941.0 August 1, 2007 11:51:40 PM
Mpfilter.cat 10,672 July 7, 2007 12:09:12 AM
Mpfilter.inf 2,941 March 8, 2007 1:44:42 AM
Mpfilter.sys 70,928 1.5.1941.0 July 7, 2007 12:09:12 AM
MpOAv.dll 95,632 1.5.1941.0 August 1, 2007 11:19:42 PM
MpRtMon.dll 734,608 1.5.1941.0 August 1, 2007 11:19:56 PM
MpSigDwn.dll 133,520 1.5.1941.0 August 1, 2007 11:19:46 PM
MpSoftEx.dll 521,616 1.5.1941.0 August 1, 2007 11:19:56 PM
MpSvc.dll 299,920 1.5.1941.0 August 1, 2007 11:19:52 PM
MpUtil.dll 180,624 1.5.1941.0 August 1, 2007 11:19:46 PM
MSASCui.exe 1,037,200 1.5.1941.0 August 1, 2007 11:19:58 PM
MsMpCom.dll 225,168 1.5.1941.0 August 1, 2007 11:19:50 PM
MsMpEng.exe 18,832 1.5.1941.0 August 1, 2007 11:19:38 PM
MsMpLics.dll 12,688 1.5.1941.0 August 1, 2007 11:19:30 PM
MsMpRes.dll 769,936 1.5.1941.0 August 1, 2007 11:53:50 PM

Workaround 1

To work around symptom 1, log on to the Windows 2000-based computer by using an administrator account.

Workaround 2

To work around symptom 2, follow these steps:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/
)

How to back up and restore the registry in Windows

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft ForefrontClient Security1.0AM

  3. Right-click the AM registry subkey, and then click Permissions.
  4. Click Advance.
  5. On the Owner tab, click Other Users or Groups.
  6. In the Select User, Computer, or Group dialog box, add the Administrators group, and then click OK.
  7. Click OK to exit the Advanced Security Settings dialog box.
  8. Click OK to exit the Permissions dialog box.
  9. Under the AM registry subkey that you located in step 2, right-click the ProductUpdateAvailable registry entry, and then click Modify.
  10. In the Value data box, type 0, and then click OK.
  11. Exit Registry Editor.

Note When the next Forefront Client Security client update becomes available, this problem will disappear because the update will reset the ProductUpdateAvailable registry entry to 0. The current resolution is for users who want to resolve the status immediately.

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:
824684

(http://support.microsoft.com/kb/824684/LN/
)

Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 938054 – Last Review: June 21, 2014 – Revision: 4.0

kbautohotfix kbbug kbfix kbqfe kbHotfixServer kbexpertiseinter kbprb fep2010swept KB938054

Read the original post:
A hotfix is available to resolve some problems with the Forefront Client Security client

Over time, client computers that obtain updates from Windows Server Update Services 2.0 take longer to scan for updates and to apply updates

You use Microsoft Windows Server Update Services (WSUS) 2.0 to deploy software updates to client computers. However, over time, the client computers that obtain updates from WSUS 2.0 take longer to scan for updates and to apply updates. Sometimes, the client computers stop responding (hang) during the installation of updates.

You experience this problem if WSUS 2.0 is configured as follows:

  • On the Automatic Approval Options page of the WSUS administration tool, the following option is selected under Revisions to Updates:

    Continue using the older revision and manually approve the new update revision

  • On the Synchronization Options page of the WSUS administration tool, the Definition Updates check box is selected in the Add/Remove Classifications — Web Page Dialog box.

    Note If you have Microsoft Forefront Client Security or Windows Defender installed, the Definition Updates check box appears in this dialog box

This problem occurs because approval is not automatically removed from earlier definition updates if the following option is selected in WSUS 2.0:

Continue using the older revision and manually approve the new update revision

Definition updates are frequently updated. In this situation, the earlier definitions expire. We recommend that you approve the latest version of a definition update and, at the same time, remove approval from the expired version of a definition update.

If the Automatically approve the latest revision of the update option is selected in WSUS 2.0, approval is automatically removed from the expired version of the definition update. However, if the Continue using the older revision and manually approve the new update revision option is selected, approval is not automatically removed from expired definition updates.

Therefore, over time, many definition updates may remain approved for installation by WSUS clients. Therefore, client computers may experience longer scan times. Or, client computers may stop responding during the installation of updates.

To work around this issue, use one of the following methods.

Method 1: Install WSUS 3.0

Obtain WSUS 3.0, and then install it. For more information about how to obtain WSUS 3.1, visit the following Microsoft Web site:Important The problem that is described in the “Symptoms” section no longer occurs after you install WSUS 3.0. However, if you experience this problem, you must manually remove approval from the existing expired definition updates. For more information about how to do this, see the “More Information” section.

Method 2: Enable automatic approval of the latest update revisions

In WSUS 2.0, enable automatic approval of the latest version of updates. To do this, follow these steps:

  1. Start the Microsoft Windows Server Update Services administration tool. To do this, click Start, point to All Programs, point to Administrative Tools, and then click Microsoft Windows Server Update Services.
  2. On the Home page, click Options, and then click Automatic Approval Options.
  3. Click Automatically approve the latest revision of the update, and then click Save settings.
  4. When you are prompted with a message that states that the settings have been saved, click OK.

Method 3: Create a custom tool to automatically approve definition updates

Create a tool that uses the WSUS 2.0 API. Configure this tool to automate the process for removing approval from expired definition updates. Additionally, configure this tool to automate the process for approving new definition updates.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
If you experience the problem that is described in the “Symptoms” section, you must manually remove approval from the expired definition updates. Additionally, you may have to resolve a problem in which one or more client computers stop responding during an update scan. To do this, follow these steps.

Step 1: Remove approval from expired definition updates

  1. On the computer that is running WSUS 2.0, start the Windows Server Update Services administration tool.
  2. On the Home page, click Updates.
  3. Create a custom filter to return all the definition updates. To do this, follow these steps:
    1. In the Products and classifications list, click Custom.
    2. Click Change custom view, type Definition updates in the Custom view name box, click to clear all the check boxes under Classifications, click to select the Definition Updates check box, and then click Save.
    3. In the Approval list, click Any approval.
    4. In the Synchronized list, click Any time, and then click Apply.
  4. Examine the returned results for definition updates that are approved for installation. In these results, look for definition updates that have an exclamation mark (!) next to them. These definition updates are expired.
  5. Select all the definition updates that have an exclamation mark next to them, and then click Change approval.
  6. In the Approval list, click Not approved, and then click OK.
  7. If you are prompted to replace existing approvals, click OK.

Step 2: Troubleshoot stuck client computers

To resolve an issue in which a client computer stops responding during an update scan, follow these steps:

  1. On the affected client computer, set the startup type for the Automatic Updates service (Wuauserv) to Disabled.
  2. Restart the computer.
  3. Delete the %WINDIR%SoftwareDistribution folder.
  4. Set the startup type for the Automatic Updates service to Automatic, and then start the Automatic Updates service.

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

927891

(http://support.microsoft.com/kb/927891/
)

You receive an access violation error and the system may appear to become unresponsive when you try to install an update from Windows Update or from Microsoft Update

Article ID: 938220 – Last Review: June 21, 2014 – Revision: 5.0


Applies to
  • Windows Server Update Services 2.0
  • Microsoft Forefront Endpoint Protection 2010
  • Microsoft System Center 2012 Endpoint Protection
kbenv kbpending kbbug kbtshoot kbprb fep2010swept KB938220

Follow this link:
Over time, client computers that obtain updates from Windows Server Update Services 2.0 take longer to scan for updates and to apply updates

Description of the Access 2007 hotfix package (Access.msp, Mso.msp): June 30, 2009

This article describes the Microsoft Office Access 2007 issue that is fixed in the hotfix package that is dated June 30, 2009.

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 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

You must have 2007 Microsoft Office suite Service Pack 1 or 2007 Microsoft Office suite Service Pack 2 installed to apply this hotfix package.

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

949585

(http://support.microsoft.com/kb/949585/
)

How to obtain the latest service pack for the 2007 Office suite

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you must either create a registry key or modify a registry key.

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 issue that is listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. 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

Collapse this tableExpand this table

File name File version File size Date Time Platform
Office-kb972570-fullfile-x86-glb.exe 12.0.6510.5000 12,935,144 23-Jun-2009 12:45 x86

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Access.msp Not Applicable 5,336,064 23-Jun-2009 02:31 Not Applicable
Mso.msp Not Applicable 10,779,136 23-Jun-2009 02:31 Not Applicable

Access.msp information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Accwiz.dll 12.0.6500.5000 161,648 26-Feb-2009 13:12 x86
Acwzlib.accde Not applicable 1,933,312 28-Feb-2009 18:50 Not applicable
Msaccess.exe 12.0.6510.5000 10,223,472 22-Jun-2009 03:49 x86
Soa.dll 12.0.6501.5000 501,648 12-Mar-2009 22:51 x86

Mso.msp information

Collapse this tableExpand this table

File name File version File size Date Time Platform
Mso.dll 12.0.6510.5000 16,498,560 17-Jun-2009 15:43 x86
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

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.

Article ID: 972570 – Last Review: June 21, 2014 – Revision: 1.0


Applies to
  • Microsoft Office Access 2007
kbsurveynew kbexpertiseinter kbqfe kbhotfixrollup kbautohotfix kbhotfixserver KB972570

See the article here:
Description of the Access 2007 hotfix package (Access.msp, Mso.msp): June 30, 2009

Page 41 of 711« First...102030...3940414243...506070...Last »

Recent Comments

    Archives

    Categories