Windows Server 2012 R2: solving .NET Framework 3.5 installation problems

source link

"


I faced a problem at a customer site last week when I tried to install the .NET Framework 3.5 – a prerequisite for installing SQL Server 2012 on a Windows Server 2012 R2. I opened the Server Manager and then navigated to the Manage, Add Roles and Features section:

I selected the .NET Framework 3.5 Features option:

I specified an alternate source path:

… and surprise! Even though an ISO of Windows Server 2012 R2 was mapped to my D: drive, the installation failed with this strange error: “The source file could not be found…”
After some investigations, I found that this problem is quite common and that Microsoft has published a fix … which unfortunately does not work for me!
I tried the same installation with different ways: command prompt, PowerShel l… but absolutely NO RESULT.
I finally decided to open a PowerShell console to check the Windows Features available on my server with the cmdlet Get-WindowsFeature:

Strangely, the status of the .NET Framework 3.5 is not showing “Available”, but “Removed”!

So, how do I change this state from removed to available?
After some investigations and after having tried some fixes provided by persons who faced to the same problem as me, I finally found the Standalone Offline Installer tool that solved my problem by enabling the .NET Framework 3.5 (many thanks to Abbodi1406).
I downloaded this exe file and executed it on my server.
An installer screen appeared:

After clicking on the Next button, a command prompt screen appeared which showed the completion state of the process.

As soon as the process was finished, I went back to my PowerShell screen to check if my .NET Framework 3.5 is now available – by running my PowerShell cmdlet Get-WindowsFeature:

The .NET Framework 3.5 now was available and I as able to restart the installation process from the beginning by navigating to the server manager, selecting the concerned feature and giving the alternate source path.

I finally succeded in installing my .NET Framework 3.5!
I hope that my blog post will help some of you to resolve this installation problem

"

Unable to start mcafee epolicy orchestrator Event Paser

http://community.mcafee.com/thread/8398

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.