http://www.emailcashpro.com

ERROR: McAfee Common Framework returned error fffff95b @ 2 (issue: FrameworkManifest.xml corrupt)

Source link


Corporate KnowledgeBase
ERROR: McAfee Common Framework returned error fffff95b @ 2 (issue: FrameworkManifest.xml corrupt)
Corporate KnowledgeBase ID:  KB54520
Published: August 08, 2008

Environment

McAfee Common Management Agent 3.60
McAfee Common Management Agent 3.5x
McAfee VirusScan Enterprise 8.5i
McAfee VirusScan Enterprise 8.0i

Problem 1

The following errors occur after initiating an AutoUpdate:
McAfee Common Framework returned error fffff95b @ 2. (FrameworkManifest.xml corrupt)

Failed to initialize common updater subsystem

Make sure the McAfee Framework Services is running

Problem 2


Subsequent errors when trying to start the McAfee Framework Service:
Could not start the McAfee Framework Service on Local Computer

The system cannot find the file specified

Problem 3


Any of the following update methods will result in the AutoUpdate error:


  • Right-clicking the McShield icon in the system tray and selecting Update Now




  • Right-clicking the AutoUpdate in the VirusScan Console and clicking Start




  • Creating a new scheduled task




  • Editing the properties of the existing AutoUpdate task


Cause

FrameworkManifest.xml has become corrupted.

Solution 1

McAfee Agent 4.0

Changes in the design of the McAfee Agent 4.0 will prevent the corruption of the FrameworkManifest.xml file.
To download the McAfee Agent from the www.mcafee.com website, see KB54808 .

Solution 2


Common Management Agent

Solution 1 - Obtain FrameworkManifest.xml from another computer:


  1. Locate another VirusScan Enterprise (VSE) computer where the updates are working without error.




  2. Copy the FrameworkManifest.xml from the following path:

    For VSE 8.5i  (running on Windows Vista)
    x:\Program Data\McAfee\Common Framework

    For VSE 8.5i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\McAfee\Common Framework

    For VSE 8.0i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework





  3. Paste the file to portable media or network share that can be accessed by both computers.




  4. Click Start, Run, type services.msc, and click OK.




  5. Right-click McAfee Framework Service and select Stop.




  6. Copy FrameworkManifest.xml to the Common Framework directory.




  7. Right-click McAfee Framework Service and select Start.




  8. Update the product.



Solution  2 - Delete FrameworkManifest.xml and reinstall the Common Management Agent (CMA)
It is necessary to delete FrameworkManifest.xml because it may not be removed or replaced when an uninstall/re-install is undertaken.
Step 1 - Allow VSE files and settings to be modified (VirusScan Enterprise 8.5i and higher only)


  1. Click Start, Programs, McAfee, VirusScan Console.




  2. Right-click Access Protection, then select Properties.




  3. Select Common Standard Protection.




  4. Select Prevent modification of McAfee files and settings and disable this option.




  5. Click OK.



Step 2 - Delete FrameworkManifest.xml and reinstall CMA:


  1. Delete FrameworkManifest.xml from the following path:

    For VSE 8.5i (running on Windows Vista)
    x:\Program Data\McAfee\Common Framework

    For VSE 8.5i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\McAfee\Common Framework

    For VSE 8.0i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework





  2. Restart your computer.




  3. Re-install the Common Management Agent (CMA) / ePO agent.


    NOTE: CMA is available for download from the McAfee Downloads site. See KB54808.


Memory Limits for Windows Releases



Memory Limits for Windows Releases

This topic describes memory limits for supported Windows releases:

Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.
Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows.
Memory typeLimit in 32-bit WindowsLimit in 64-bit Windows
User-mode virtual address space for each 32-bit process
2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process
Not applicable
With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):

x64:  8 TB
Intel IPF:  7 TB
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space
2 GB
From 1 GB to a maximum of 2 GB with 4GT
8 TB
Paged pool
Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value.
Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.
Windows Home Server and Windows Server 2003:  530 MB
Windows XP:  490 MB
Windows 2000:  350 MB
128 GB
Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.
Windows 2000:  Not applicable
Nonpaged pool
Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory.
Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000:  256 MB, or 128 MB with 4GT.
75% of RAM up to a maximum of 128 GB
Windows Vista:  40% of RAM up to a maximum of 128 GB.
Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.
Windows 2000:  Not applicable
System cache virtual address space (physical size limited only by physical memory)
Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.
Always 1 TB regardless of physical RAM
Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM.
Windows 2000:  Not applicable

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows 7 Ultimate 4 GB
192 GB
Windows 7 Enterprise 4 GB
192 GB
Windows 7 Professional 4 GB
192 GB
Windows 7 Home Premium 4 GB
16 GB
Windows 7 Home Basic 4 GB
8 GB
Windows 7 Starter 2 GB
2 GB

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.
VersionLimit in 64-bit Windows
Windows Server 2008 R2 Datacenter 2 TB
Windows Server 2008 R2 Enterprise 2 TB
Windows Server 2008 R2 for Itanium-Based Systems 2 TB
Windows Server 2008 R2 Foundation 8 GB
Windows Server 2008 R2 Standard 32 GB
Windows HPC Server 2008 R2 128 GB
Windows Web Server 2008 R2 32 GB

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Server 2008 Datacenter 64 GB
2 TB
Windows Server 2008 Enterprise 64 GB
2 TB
Windows Server 2008 HPC Edition Not applicable
128 GB
Windows Server 2008 Standard 4 GB
32 GB
Windows Server 2008 for Itanium-Based Systems Not applicable
2 TB
Windows Small Business Server 2008 4 GB
32 GB
Windows Web Server 2008 4 GB
32 GB

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Vista Ultimate 4 GB
128 GB
Windows Vista Enterprise 4 GB
128 GB
Windows Vista Business 4 GB
128 GB
Windows Vista Home Premium 4 GB
16 GB
Windows Vista Home Basic 4 GB
8 GB
Windows Vista Starter 1 GB
Not applicable

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition
128 GB
64 GB with 4GT
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition
64 GB
2 TB
Windows Storage Server 2003, Enterprise Edition
8 GB
Not applicable
Windows Storage Server 2003
4 GB
Not applicable
Windows Server 2003 R2 Datacenter Edition
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition
128 GB
16 GB with 4GT
1 TB
Windows Server 2003 R2 Enterprise Edition
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition
64 GB
16 GB with 4GT
1 TB
Windows Server 2003 R2 Standard Edition
Windows Server 2003, Standard Edition SP1
Windows Server 2003, Standard Edition SP2
4 GB
32 GB
Windows Server 2003, Datacenter Edition
128 GB
16 GB with 4GT
512 GB
Windows Server 2003, Enterprise Edition
32 GB
16 GB with 4GT
64 GB
Windows Server 2003, Standard Edition
4 GB
16 GB
Windows Server 2003, Web Edition
2 GB
Not applicable
Windows Small Business Server 2003
4 GB
Not applicable
Windows Compute Cluster Server 2003
Not applicable
32 GB

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows XP 4 GB
128 GB
Windows XP Starter Edition 512 MB
Not applicable

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.
VersionLimit in 32-bit Windows
Windows 2000 Professional 4 GB
Windows 2000 Server 4 GB
Windows 2000 Advanced Server 8 GB
Windows 2000 Datacenter Server 32 GB

HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.

Error: HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.

Solution:


SUPPORT COMMUNICATION - CUSTOMER NOTICE
Document ID: c01684544
Version: 4
Notice: (Revision) HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server - First Update to Version 4.6.16.0 To Avoid Message "HP Virtual Bus Device Installation Requires a Newer Version. Version 4.6.16.0 is Required."
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.
Release Date: 2009-07-29
Last Updated: 2009-07-29

DESCRIPTION
Document Version
Release Date
Details
4
07/29/2009
Updated Details section to change "Windows 2003 x64 Editions" to "Windows Server 2008 x64 Editions" for cp009684.exe.
3
03/31/2009
Added note stating reboot is required after driver upgrade.
2
03/06/2009
Driver name updated.
1
03/04/2009
Original Document Release.
On a ProLiant server running Windows Server 2003 or Windows Server 2008, if a version of the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server earlier than version 4.6.16.0 is installed and an attempt to upgrade the driver to a version later than version 4.6.16.0 is made, the following message is displayed and is written to the cpqsetup.log:
HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.
This will not occur if running a version of the driver later than version 4.6.16.0. This only occurs when running a driver earlier than version 4.6.16.0 and attempting to update the driver beyond version 4.6.16.0.
DETAILS
The HP NC-Series Broadcom 1GbE Multifunction Driver update does not complete, and the above message is displayed to ensure compatibility.
When running a driver version earlier than version 4.6.16.0, two driver updates are required for the driver to be updated to a version later than version 4.6.16.0. Install version 4.6.16.0 and then upgrade the driver beyond version 4.6.16.0 as follows:
  1. Install the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server Version 4.6.16.0, located at the following URLs:
    For Windows Server 2003, use cp009681.exe, located at the following URL:

    For Windows Server 2003 x64 Editions, use cp009682.exe, located at the following URL:

    For Windows Server 2008, use cp009683.exe, located at the following URL:
    For Windows Server 2008 x64 Editions, use cp009684.exe, located at the following URL:

  2. After updating to Version 4.6.16.0, the driver can be updated to a version later than version 4.6.16.0. Perform the following steps to obtain the latest version of the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server:
    Note: After upgrading the driver to Version 4.6.16.0 (or later), reboot the server.
  1. Click on the following URL:
  2. Under Select a product category, select Servers .
  3. Select ProLiant/tc Series Servers .
  4. Select the desired ProLiant model.
  5. Select the appropriate operating system.
  6. Select the Driver-Network category.
  7. Select the HP NC-Series Broadcom 1GbE Multifunction Driver and click the "Download" button.