Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup Exec 2010 R2 Agent On Hyper V Server (Free Version) will not install

Created: 15 Dec 2010 | 9 comments

The agent will not install b/c it will not detect the server as core.  It then requires .net to be installed which it can't be. 

On a normal 2008 Server Core server I get this:

  <msg>GetProductInfo returned success.  Checking for CORE OS values.</msg>
   <msg>This is a CORE OS.  Product type: 0xe</msg>

But on the Hyper-V Server i get this:

   <msg>GetProductInfo returned success.  Checking for CORE OS values.</msg>
   <msg>The correct version of .NET was not detected</msg>

What do I do?

Comments 9 CommentsJump to latest comment

ZacTech's picture

If I try to run SetupCore.exe manually I get: "This utility can only be run on Windows Core operating systems. Run Setup.exe instead."

I am trapped!  The 2010 version installed fine earlier this year, but not this R2.

RahulG's picture

Install .net framework 3.5 sp1 manully and then attempt to run the install for remote agent

AmolB's picture

Please post bkupinst.htm file its located at X:\Program Files\Symantec\Backup Exec\Raws\logs.

ZacTech's picture

For the 2008 Server Core the Product Type is 0xe

For 2008 Hyper-V Server the Procut Type is 0x2a (Also for Hyper-V Server R2)

The agent needs to recognize that 0x2a is a core OS. Even if I could (I tried many times) I do not want to install .net, that is the whole point of having a core os.

bkupinst is not there. only RAWSINST.HTM 

(Non Working Server:)
Symantec Backup Exec Remote Agent (TM) 13 Installation Log

12-15-2010,23:49:11 : Windows Operating System Version: 6.0
12-15-2010,23:49:11 : GetProductInfo returned success. Checking for CORE OS values.
12-15-2010,23:49:11 : The correct version of .NET was not detected
12-15-2010,23:49:11 : The .NET file C:\Agent\DotNetFx\dotnetfx35.exe was not found, installlation cannot continue.
12-15-2010,23:49:11 : WARNING: Installation has been canceled.

Working Server:

12-15-2010,16:24:06 : Windows Operating System Version: 6.0
12-15-2010,16:24:06 : GetProductInfo returned success. Checking for CORE OS values.
12-15-2010,16:24:06 : This is a CORE OS. Product type: 0xe
12-15-2010,16:24:06 : "/ADVRT:UCB-NAS-2; /DEST:C:\PROGRAM FILES\SYMANTEC\BACKUP EXEC\RAWS /S: "
12-15-2010,16:24:06 : Executing alternate Core OS executable:
12-15-2010,16:24:06 : C:\BEW-100ce6723eb24e7b9a2ca4e7232e25b8\VxPushRA\RAWSX64\Install\setupcore.exe

Dev T's picture

Unfortunately, the .Net framework will not be a part of Windows Server 2008 Core. I understand that it would be inconvenient for you to use the Windows 2008 Server Core without .Net framework.

In addition, the .Net framework will be available in Windows Server 2008 Core R2.

Hope this helps...

Its a best practice to have a "Support Contract" with Symantec...
 

Dev T's picture

For Windows Server 2008 R2 Core Edition , you will be able to install .Net Framework on it.

You can perform the following steps:

1.    Use the following command to displays a list of features and their status:

DISM /Online /Get-Features

Note: You will find some features named like NetFx2-ServerCore and NetFx3-ServerCore

2.    Enables the NetFx2-ServerCore feature:

DISM /Online /Enable-Feature /FeatureName:NetFx2-ServerCore

Its a best practice to have a "Support Contract" with Symantec...
 

ZacTech's picture

Thank you for your rapid responses But I don't have hyper-v r2 so I can't install .net. Furthermore I do not want .net on the core. Especially since I know it will install with out it; if it is recognized as core. I feel like i need to trick the agent to think it is server core. I treys changing the registry to 0xe but it doesn't register

thegoolsby's picture

Please call into and open a support case. There is a beta fix that support can give you that will allow you to upgrade the agent. For the time being, you can continue to run the R1 remote agent.

Reference Etrack 2106505 and ask for your case to be escalated to the backline team so you can get the fix.