Update was not aplied - failure

Hi Sergej,

The Green in the device tree for a device is the health state. It may or may not be directly dependent on the updates. For example: Even if you have a new firmware available for iDRAC firmware, the health state of the server may still be GREEN, if all the components are working properly. If the health state is not showing GREEN, you may want to look in to the hardware logs and that should give you some details on why the health state is not GREEN. Also, you can login to the OMSA console using OME to verify which component is making the health state be non-GREEN.

I hope this helps.

Hi Sergej,

Thanks for your post.

"Video_Driver_08MVF_WN32_4.00.01.004_1.0.EXE" is released to enabled the video driver support for 11G platform with WIN 2012.

So the Video driver DUP "08MVF" only successfully executed with Windows 2012 operating system.

Could you please conform the operating system details.??for you system

The "VIDEO_DRVR_WIN_R276936.EXE" is current available video driver DUP for 11G support with other Windows OS.

Hope this is helpful...

Thanks,

Amit 

It's a 208R2 Machine. This is weird.

I mean not the Device tree. I mean in the Update section, i have conform systems and not conform system. Need i install also the optional Updates, to get a system conform?

gz

Sergej

Tnx for your answer, good to know :)

Yes, we have installed the aplication in german, and its a little strange with the translation. In the productive environment i will install it in English.

So what shoud i do now with the graphic card update mentioned bellow.

(and one question more: which requierments i have for the support assist. Have a system, which is faulty. Need i to do at first all updats, until SupportAssist can send the call?)

Tnx

Sergej

I am assuming you are talking about compliant and non-compliant systems. Yes, it is required to update the optional components as well to view the systems as compliant.

hi all,

i found the answer for my second question: i installed the new OMSA on this machines and it works. Had 7.2 on the server and nothing happened. With 7.3 the support Assist start to work. Is it possible to update the OMSA via OME?

And still no answer to the main question...

gz

Sergej

HI,

tnx for the Answer.

The main question was:  The ome tool want to update the graphikadapter on a system. Your collegues write, that the update is for server 2012. But it's 2008R2 running.

So what should i do now?

gz

Sergej

Hi Sergez,

You can install OMSA using OME. The task to install/upgrade OMSA is located under Manage->Remote Tasks->Create Deployment Task.

Not sure what your main question is.

Regards

Abhijit

Thanks for the update Sergez. I looked at the catalog entry for this update and it does list 2008R2 as an OS supported for this update. If this update does not run on this OS, it may be an issue with the entry in the catalog which is telling OME that the update is applicable.

If you haven't done this before, is it possible for you to try running this update manually outside of OME on the target system and let us know if you see the same error you have mentioned above?

Regards

Abhijit

HI,

thank you for your answer.

You mean the Update which the OME Tool want install?  Video_Driver_08MVF_WN32_4.00.01.004_1.0.EXE

Not the Update from the DELL Site with the ServiceTag?

I'm confused. In one post you(DELL) say, this driver is for 2012, in other for 2008R2 also.

gz

Sergej

Hi Sergez,

OME should not show Video_Driver_08MVF_WN32_4.00.01.004_1.0.EXE as applicable update for Windows 2008 R2. If it's showing up in the compliance report, you can open a support ticket at 800-945-3355 so that they can investigate.

Regards

Abhijit

Hi,

tnx for your answer.

The Ome Tool want to install the Version for 2012.

So should i try to install manually the driver for 2008r2 and look, what happens in OME?

gz

Sergej

Hi Sergej,

VIDEO_DRVR_WIN_R276936.EXE lists Windows 2008 R2 as supported OS in the catalog. Video_Driver_08MVF_WN32_4.00.01.004_1.0.EXE only lists Windows 2012 as supported OS. OME should show the first one as applicable updates for 2008 R2 and second one as applicable for 2012.

Regards

Abhijit

HI,

i suggest, the Hotline is in the USA?

At what time i can call there? Is it possible to open a ticket by mail?

Yesterday i wanted to update another system, and get again error messages. All updates were aplied succesfull, but the networkadapter updates produced the errors.

Its a 2012 OS on this Server.  ST: F5FB95J

PackageCode  1
PackageFileName  C:\Users\A-MILG~1\AppData\Local\Temp\s2vk\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12.EXE
PackageLog  [10/10/13 09:20:59]    Update Package Execution Started

[10/10/13 09:21:00]    Original command line: C:\Users\A-MILG~1\AppData\Local\Temp\s2vk\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12.EXE /f /s /l=C:\Windows\TEMP\DUP.log

[10/10/13 09:21:00]    DUP Framework EXE Version: 3.0.93.1

[10/10/13 09:21:00]    DUP Release: CYKKJX12-00

[10/10/13 09:21:00]    Intializing framework...

[10/10/13 09:21:00]    Server Infastructure Detected...Proceeding with PM Module...

[10/10/13 09:21:00]    Querying if HAPI is Installated...

[10/10/13 09:21:00]    HAPI already Installated...

[10/10/13 09:21:00]    Querying Personality Module for data via ..GetPersonalityInfo()

[10/10/13 09:21:00]    Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()

[10/10/13 09:21:00]    Obtained Personality Information

[10/10/13 09:21:00]    Manufacturers name :

[10/10/13 09:21:00]    Data Location :

[10/10/13 09:21:00]    Copied all Personality Information to Framework

[10/10/13 09:21:00]    Querying Personality Module Succeeded...

[10/10/13 09:21:00]    Retrieving relevant Values from Personality Module...

[10/10/13 09:21:00]    Client Brand Status:- DEFAULT

[10/10/13 09:21:00]    User Command: unattended

[10/10/13 09:21:00]    DUP Capabilities Value: 50331647 (0x2FFFFFF)

[10/10/13 09:21:00]    DUP Vendor Software Version: 17.6.0.0

[10/10/13 09:21:00]    Local System/Model Compatible with this Package? Yes

[10/10/13 09:21:00]    Local System OS Version: 6.2.0.0

[10/10/13 09:21:00]    OS Compatible with this Package? Yes

[10/10/13 09:21:00]    Local System OS Language: DE

[10/10/13 09:21:00]    Language Compatible with this Package? Unknown

[10/10/13 09:21:00]    User Parameter: logfile

[10/10/13 09:21:00]    User Parameter: logfile changed to: c:\windows\temp\dup.log

[10/10/13 09:21:00]    User Parameter: force

[10/10/13 09:21:00]    Identified Behavior : unattended

[10/10/13 09:21:00]    Temporary payload log file name: C:\ProgramData\dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12\DUP7289.tmp

[10/10/13 09:21:00]    Translated Command Line : brcmsetup.exe /s  /v"LOGFILE=\"C:\ProgramData\dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12\DUP7289.tmp\""

[10/10/13 09:21:00]    Path : C:\ProgramData\dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12

[10/10/13 09:21:00]    Identified Behavior : unattended

[10/10/13 09:21:04]    Append Vendor Software Log: C:\ProgramData\dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12\DUP7289.tmp

[10/10/13 09:21:04]    

--- Start of Vendor Software Log ---



[10/10/13 09:21:04]    ASCII payload log file detected.

[10/10/13 09:21:04]     ============== Update Package Started ==============


 Date/Time Executed: Thu Oct 10 09:21:01 2013

 


 Command Parameters: "C:\ProgramData\Dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12\BrcmSetup.exe" /s  /v"LOGFILE=\"C:\ProgramData\dell\drivers\Network_Driver_CYKKJ_WN_17.6.0.0_17.6.0.12\DUP7289.tmp\""


 ====================================================




 Inventory version prior to update: 15.6.4.9


 Update version: 15.6.4.9




 ============== Update Result ==============


 Date/Time Completed: Thu Oct 10 09:21:04 2013

 


 Exit code = 1603 (Fatal error during installation.)


 ====================================================






[10/10/13 09:21:04]    

--- End of Vendor Software Log ---



[10/10/13 09:21:04]    Vendor Software Return Code: 1603

[10/10/13 09:21:04]    Name of Exit Code: ERROR

[10/10/13 09:21:04]    Exit Code set to: 1 (0x1)

[10/10/13 09:21:04]    Result: FAILURE

[10/10/13 09:21:04]    Name of Exit Code: ERROR

[10/10/13 09:21:04]    Execution terminated at date-time 10/10/13 09:21:04

[10/10/13 09:21:04]    ######
PackageReleaseId  Nicht verfügbar
PackageState  complete
PackageStatus  5
PackageCode  1
PackageFileName  C:\Users\A-MILG~1\AppData\Local\Temp\s2vk\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12.EXE
PackageLog  [10/10/13 09:21:04]    Update Package Execution Started

[10/10/13 09:21:04]    Original command line: C:\Users\A-MILG~1\AppData\Local\Temp\s2vk\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12.EXE /f /s /l=C:\Windows\TEMP\DUP.log

[10/10/13 09:21:05]    DUP Framework EXE Version: 3.0.93.1

[10/10/13 09:21:05]    DUP Release: PYKJHX12-00

[10/10/13 09:21:05]    Intializing framework...

[10/10/13 09:21:05]    Server Infastructure Detected...Proceeding with PM Module...

[10/10/13 09:21:05]    Querying if HAPI is Installated...

[10/10/13 09:21:05]    HAPI already Installated...

[10/10/13 09:21:05]    Querying Personality Module for data via ..GetPersonalityInfo()

[10/10/13 09:21:05]    Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()

[10/10/13 09:21:05]    Obtained Personality Information

[10/10/13 09:21:05]    Manufacturers name :

[10/10/13 09:21:05]    Data Location :

[10/10/13 09:21:05]    Copied all Personality Information to Framework

[10/10/13 09:21:05]    Querying Personality Module Succeeded...

[10/10/13 09:21:05]    Retrieving relevant Values from Personality Module...

[10/10/13 09:21:05]    Client Brand Status:- DEFAULT

[10/10/13 09:21:05]    User Command: unattended

[10/10/13 09:21:05]    DUP Capabilities Value: 50331647 (0x2FFFFFF)

[10/10/13 09:21:05]    DUP Vendor Software Version: 17.6.0.0

[10/10/13 09:21:05]    Local System/Model Compatible with this Package? Yes

[10/10/13 09:21:05]    Local System OS Version: 6.2.0.0

[10/10/13 09:21:05]    OS Compatible with this Package? Unknown

[10/10/13 09:21:05]    Local System OS Language: Unknown

[10/10/13 09:21:05]    Language Compatible with this Package? Unknown

[10/10/13 09:21:05]    User Parameter: logfile

[10/10/13 09:21:05]    User Parameter: logfile changed to: c:\windows\temp\dup.log

[10/10/13 09:21:05]    User Parameter: force

[10/10/13 09:21:05]    Identified Behavior : unattended

[10/10/13 09:21:05]    Temporary payload log file name: C:\ProgramData\dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12\DUP8565.tmp

[10/10/13 09:21:05]    Translated Command Line : brcmsetup.exe /s  /v"LOGFILE=\"C:\ProgramData\dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12\DUP8565.tmp\""

[10/10/13 09:21:05]    Path : C:\ProgramData\dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12

[10/10/13 09:21:05]    Identified Behavior : unattended

[10/10/13 09:21:08]    Append Vendor Software Log: C:\ProgramData\dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12\DUP8565.tmp

[10/10/13 09:21:08]    

--- Start of Vendor Software Log ---



[10/10/13 09:21:08]    ASCII payload log file detected.

[10/10/13 09:21:08]     ============== Update Package Started ==============


 Date/Time Executed: Thu Oct 10 09:21:05 2013

 


 Command Parameters: "C:\ProgramData\Dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12\BrcmSetup.exe" /s  /v"LOGFILE=\"C:\ProgramData\dell\drivers\Network_Driver_PYKJH_WN_17.6.0.0_17.6.0.12\DUP8565.tmp\""


 ====================================================




 ============== Update Result ==============


 Date/Time Completed: Thu Oct 10 09:21:08 2013

 


 Exit code = 1603 (Fatal error during installation.)


 ====================================================






[10/10/13 09:21:08]    

--- End of Vendor Software Log ---



[10/10/13 09:21:08]    Vendor Software Return Code: 1603

[10/10/13 09:21:08]    Name of Exit Code: ERROR

[10/10/13 09:21:08]    Exit Code set to: 1 (0x1)

[10/10/13 09:21:08]    Result: FAILURE

[10/10/13 09:21:08]    Name of Exit Code: ERROR

[10/10/13 09:21:08]    Execution terminated at date-time 10/10/13 09:21:08

[10/10/13 09:21:08]    ######
PackageReleaseId  Nicht verfügbar
PackageState  complete
PackageStatus  5
TotalStatus  One or more Update Packages failed during execution, but the update continued running to the end.
TotalStatusMessage  Softwareupdate finished.

gz

Sergej

Hi,

have 3 another servers, where all updates were install successful, but the Broadcom NIC's can't be updated.

Broadcom NetXtreme Gigabit Ehernet #3    driver   installed: 15.6.0.10    availible: 17.6.0.0

on the other machine

Broadcom NetXtreme II GigE #35    driver   installed: 7.6.2.0    availible: 17.6.0.0

3rd machine

Broadcom NetXtreme II GigE #43    driver   installed: 7.6.2.0    availible: 17.6.0.0

also all 3 systems want to install the driver for the Broadcom I and II driver family in 17.6.0.0  (installed 17.6.0)

Sry but the tool is confusing me more and more...

Have i to handle the NIC updates in other way?

gz

Sergej