Business Client Catalog

November 20, 2013, 3:23 am

≫ Next: OpenManage Software Support Matrix 6 - invalid PDF

≪ Previous: Spotlight on Windows Freeware

Hi,

The list of supported laptops in the Business Client Catalog does not include Vostro models, but these are sold in Premier as business laptops. Why are they not included in the Catalog?

We have quite a few of these in our business and without the catalog I'll have to manually patch them via WIndows update.

Thanks

Gary

↧

OpenManage Software Support Matrix 6 - invalid PDF

January 24, 2014, 1:27 am

≫ Next: DSM SA Data Manager service keeps crashing - Dell OpenManage v7.3

≪ Previous: Business Client Catalog

Hello,

I think PDF included on the above website with support matrix for open manage is INVALID.

http://www.dell.com/support/Manuals/us/en/19/Product/dell-opnmang-sw-v6.1

Please check table 3.1, it does not fit on the page!

Could you please provide me information whether RHEL 3 is supported?

---

↧

DSM SA Data Manager service keeps crashing - Dell OpenManage v7.3

August 25, 2013, 3:47 am

≫ Next: RACADM Version 6.5.0 command to backup DRAC Configuration

≪ Previous: OpenManage Software Support Matrix 6 - invalid PDF

HI Everyone,

We suddenly started to have the DSM SA Data manager service stopping and starting unexpectedly on one of the Dell Servers running Windows Server 2012. We have installed Dell Openmanage v7.2 on a Dell poweredge R910 server. When the issue occured i wasn't able to see any hardware information in the Dell openmanage administrator web console . I tried updating the Dell open manage from v7.2 to v7.3 and the hardware information started displaying as before. No alerts or warning are seen, onlly green ticks but the issue still seems to be persistent. as the service is still crashing randomly.

Below is the information from the application logs when the issue occurred. I would appreciate if anyone from Dell community could shed some light regarding this issue as this is a bit concerning for us.

Log Name: Application
Source: Application Error
Date: 25/08/2013 06:58:19
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MKHVXX
Description:
Faulting application name: dsm_sa_datamgr64.exe, version: 7.3.0.350, time stamp: 0x51b23742
Faulting module name: dcadpt64.dll, version: 7.3.0.350, time stamp: 0x51b238e1
Exception code: 0xc0000005
Fault offset: 0x000000000000e2c5
Faulting process id: 0x2a40
Faulting application start time: 0x01cea15519540cde
Faulting application path: C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe
Faulting module path: C:\Program Files\Dell\SysMgt\omsa\bin\dcadpt64.dll
Report Id: 573678f6-0d4b-11e3-93f5-8ffa18280fa2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-25T05:58:19.000000000Z" />
<EventRecordID>9381</EventRecordID>
<Channel>Application</Channel>
<Computer>MKHVXXk</Computer>
<Security />
</System>
<EventData>
<Data>dsm_sa_datamgr64.exe</Data>
<Data>7.3.0.350</Data>
<Data>51b23742</Data>
<Data>dcadpt64.dll</Data>
<Data>7.3.0.350</Data>
<Data>51b238e1</Data>
<Data>c0000005</Data>
<Data>000000000000e2c5</Data>
<Data>2a40</Data>
<Data>01cea15519540cde</Data>
<Data>C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe</Data>
<Data>C:\Program Files\Dell\SysMgt\omsa\bin\dcadpt64.dll</Data>
<Data>573678f6-0d4b-11e3-93f5-8ffa18280fa2</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

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

Log Name: Application
Source: Application Error
Date: 25/08/2013 03:48:13
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MKHVXX
Description:
Faulting application name: dsm_sa_datamgr64.exe, version: 7.3.0.350, time stamp: 0x51b23742
Faulting module name: dcadpt64.dll, version: 7.3.0.350, time stamp: 0x51b238e1
Exception code: 0xc0000005
Fault offset: 0x000000000000a084
Faulting process id: 0x3dac
Faulting application start time: 0x01cea13446ee0b21
Faulting application path: C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe
Faulting module path: C:\Program Files\Dell\SysMgt\omsa\bin\dcadpt64.dll
Report Id: c842cdc9-0d30-11e3-93f5-8ffa18280fa2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-25T02:48:13.000000000Z" />
<EventRecordID>9369</EventRecordID>
<Channel>Application</Channel>
<Computer>MKHVXX</Computer>
<Security />
</System>
<EventData>
<Data>dsm_sa_datamgr64.exe</Data>
<Data>7.3.0.350</Data>
<Data>51b23742</Data>
<Data>dcadpt64.dll</Data>
<Data>7.3.0.350</Data>
<Data>51b238e1</Data>
<Data>c0000005</Data>
<Data>000000000000a084</Data>
<Data>3dac</Data>
<Data>01cea13446ee0b21</Data>
<Data>C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe</Data>
<Data>C:\Program Files\Dell\SysMgt\omsa\bin\dcadpt64.dll</Data>
<Data>c842cdc9-0d30-11e3-93f5-8ffa18280fa2</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

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

Log Name: Application
Source: Application Error
Date: 25/08/2013 11:12:01
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MKHVXX
Description:
Faulting application name: wmiprvse.exe, version: 6.2.9200.16384, time stamp: 0x5010ad15
Faulting module name: OLEAUT32.dll, version: 6.2.9200.16384, time stamp: 0x50108a1d
Exception code: 0xc0000005
Fault offset: 0x0000000000001245
Faulting process id: 0x2c8c
Faulting application start time: 0x01cea17b89e7d5ca
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\OLEAUT32.dll
Report Id: c7c8c204-0d6e-11e3-93f5-8ffa18280fa2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-25T10:12:01.000000000Z" />
<EventRecordID>9392</EventRecordID>
<Channel>Application</Channel>
<Computer>MKHVXX</Computer>
<Security />
</System>
<EventData>
<Data>wmiprvse.exe</Data>
<Data>6.2.9200.16384</Data>
<Data>5010ad15</Data>
<Data>OLEAUT32.dll</Data>
<Data>6.2.9200.16384</Data>
<Data>50108a1d</Data>
<Data>c0000005</Data>
<Data>0000000000001245</Data>
<Data>2c8c</Data>
<Data>01cea17b89e7d5ca</Data>
<Data>C:\Windows\system32\wbem\wmiprvse.exe</Data>
<Data>C:\Windows\system32\OLEAUT32.dll</Data>
<Data>c7c8c204-0d6e-11e3-93f5-8ffa18280fa2</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

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

this log was only seen one time but the one's mentioned above were occuring frequently as seen in application logs.

Log Name: Application

Source: Application Error
Date: 25/08/2013 11:12:00
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MKHVXX
Description:
Faulting application name: racadm.exe, version: 7.3.0.350, time stamp: 0x51b238fe
Faulting module name: dchipm64.dll, version: 7.3.0.350, time stamp: 0x51b237e2
Exception code: 0xc0000005
Fault offset: 0x000000000001d9e7
Faulting process id: 0x830
Faulting application start time: 0x01cea17b89a2ca21
Faulting application path: C:\Program Files\Dell\SysMgt\idrac\racadm.exe
Faulting module path: C:\Windows\SYSTEM32\dchipm64.dll
Report Id: c76be743-0d6e-11e3-93f5-8ffa18280fa2
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-25T10:12:00.000000000Z" />
<EventRecordID>9387</EventRecordID>
<Channel>Application</Channel>
<Computer>MKHVXX</Computer>
<Security />
</System>
<EventData>
<Data>racadm.exe</Data>
<Data>7.3.0.350</Data>
<Data>51b238fe</Data>
<Data>dchipm64.dll</Data>
<Data>7.3.0.350</Data>
<Data>51b237e2</Data>
<Data>c0000005</Data>
<Data>000000000001d9e7</Data>
<Data>830</Data>
<Data>01cea17b89a2ca21</Data>
<Data>C:\Program Files\Dell\SysMgt\idrac\racadm.exe</Data>
<Data>C:\Windows\SYSTEM32\dchipm64.dll</Data>
<Data>c76be743-0d6e-11e3-93f5-8ffa18280fa2</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Thanks,

Logesh

↧

RACADM Version 6.5.0 command to backup DRAC Configuration

January 29, 2014, 12:44 pm

≫ Next: OMSA on ESXi 5.5 free license, working but not recognized from Openmanage essentials

≪ Previous: DSM SA Data Manager service keeps crashing - Dell OpenManage v7.3

Hello All,

I am trying to Backup the DRAC Configuration using RACADM Version 6.5.0 using command as below:

“racadm get –t xml –f <path/filename.xml>”

got error msg ERROR: Invalid subcommand specified. Can someone suggest me what command should support RACADM 6.5.0 to backup DRAC Configuration. Thank you.

↧

OMSA on ESXi 5.5 free license, working but not recognized from Openmanage essentials

February 1, 2014, 8:41 pm

≫ Next: QLOGIC update not working via SUU for m710HDs

≪ Previous: RACADM Version 6.5.0 command to backup DRAC Configuration

Hi, here some details:

Running ESXi 5.5 free license with OMSA 7.3.0
I can login to OMSA using this procedure:
- connect to OMSA installed on a Windows system
- without log in, click on "manage remote node"
- enter ESXi credentials, with flag on "ignore certificate warnings"

Now: I am trying to get it into Openmanage essentials. Consider that in ESXi free there is no option to enable SNMP.
After the discovery I have it's IP in the Unknown section. I can't get it recognized properly.

Any advice?

What about WS-Man discovery feature? I tried that but it's still not recognized...

↧

QLOGIC update not working via SUU for m710HDs

September 25, 2012, 6:18 pm

≫ Next: CCTK Log File

≪ Previous: OMSA on ESXi 5.5 free license, working but not recognized from Openmanage essentials

Hi,

In trying to update two servers using the latest SUU, an error is occurring I have not seen before. All updates seem to be suceeding except the QLogic update, version 3.00.08

It returns an error of "Update of some components might have failed....." The log file then referred to is underneath (Sorry for the long paste.....). Other parts of the SUU update are fine.

Other m710hd's are updating fine using exactly the same suu repository.

A reboot or 3 does not help.

Thx,

John Bradshaw

Log file below:

Wed Sep 26 07:32:39 EST 2012 M710HD_BIOS_914F0_WN32_6.0.3.EXE - reboot required to complete update
Wed Sep 26 07:32:39 EST 2012 Drivers-for-OS-Deployment_Application_968MD_WN32_7.1.0.9_A00.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 Network_Driver_TJPWC_WN32_3.00.08_A00.EXE - update unsuccessful, see support log
Wed Sep 26 07:32:39 EST 2012 package log: [09/26/12 07:04:25]   Update Package Execution Started
[09/26/12 07:04:26]   Original command line: C:\dell\suu\124133890\Network_Driver_TJPWC_WN32_3.00.08_A00.EXE /s /l=C:\Windows\TEMP\DUP.log
[09/26/12 07:04:26]   DUP Framework EXE Version: 3.0.92.1
[09/26/12 07:04:26]   DUP Release: TJPWCA00-00
[09/26/12 07:04:26]   Intializing framework...
[09/26/12 07:04:26]   Server Infastructure Detected...Proceeding with PM Module...
[09/26/12 07:04:26]   Querying if HAPI is Installated...
[09/26/12 07:04:26]   HAPI already Installated...
[09/26/12 07:04:26]   Querying Personality Module for data via ..GetPersonalityInfo()
[09/26/12 07:04:26]   Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[09/26/12 07:04:26]   Obtained Personality Information
[09/26/12 07:04:26]   Manufacturers name :
[09/26/12 07:04:26]   Data Location :
[09/26/12 07:04:26]   Copied all Personality Information to Framework
[09/26/12 07:04:26]   Querying Personality Module Succeeded...
[09/26/12 07:04:26]   Retrieving relevant Values from Personality Module...
[09/26/12 07:04:26]   Client Brand Status:- DEFAULT
[09/26/12 07:04:26]   User Command: unattended
[09/26/12 07:04:26]   DUP Capabilities Value: 14680063 (0xDFFFFF)
[09/26/12 07:04:26]   DUP Vendor Software Version: 3.00.08
[09/26/12 07:04:26]   Local System/Model Compatible with this Package? Yes
[09/26/12 07:04:26]   Local System OS Version: 6.1.1.0
[09/26/12 07:04:26]   OS Compatible with this Package? Yes
[09/26/12 07:04:26]   Local System OS Language: EN
[09/26/12 07:04:26]   Language Compatible with this Package? Yes
[09/26/12 07:04:26]   User Parameter: logfile
[09/26/12 07:04:26]   User Parameter: logfile changed to: c:\windows\temp\dup.log
[09/26/12 07:04:27]   Identified Behavior : unattended
[09/26/12 07:04:27]   Temporary payload log file name: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6303.tmp
[09/26/12 07:04:27]   Translated Command Line : QLogicSetup.exe /s /z"/vtdriver /logfile=\"C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6303.tmp\""
[09/26/12 07:04:27]   Path : C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00
[09/26/12 07:04:27]   Identified Behavior : unattended
[09/26/12 07:05:44]   Append Vendor Software Log: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6303.tmp
[09/26/12 07:05:44]
--- Start of Vendor Software Log ---

[09/26/12 07:05:44]
--- End of Vendor Software Log ---

[09/26/12 07:05:44]   Vendor Software Return Code: 1603
[09/26/12 07:05:44]   Name of Exit Code: ERROR
[09/26/12 07:05:44]   Exit Code set to: 1 (0x1)
[09/26/12 07:05:44]   Result: FAILURE
[09/26/12 07:05:44]   Name of Exit Code: ERROR
[09/26/12 07:05:44]   Execution terminated at date-time 09/26/12 07:05:44
[09/26/12 07:05:44]   ######
Wed Sep 26 07:32:39 EST 2012 SAS-Drive_Firmware_NFMCR_WN32_CS07_A04.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 Lifecycle-Controller_Application_6V5JC_WN32_1.5.5.27_A00.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 ESM_Firmware_GKM8R_WN32_3.40_A00.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 Network_Driver_H8HTP_WN32_17.2.0_A00.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 Network_Driver_8D5KK_WN32_13.5.0_A00.EXE - update successful
Wed Sep 26 07:32:39 EST 2012 Network_Firmware_Y9W1K_WN32_13.5.6_A00.EXE - reboot required to complete update
Wed Sep 26 07:32:39 EST 2012 Network_Firmware_0RP00_WN_7.2.14_A00.EXE - reboot required to complete update
Wed Sep 26 08:05:11 EST 2012 Network_Driver_8D5KK_WN32_13.5.0_A00.EXE - update successful
Wed Sep 26 08:05:11 EST 2012 Network_Driver_TJPWC_WN32_3.00.08_A00.EXE - update unsuccessful, see support log
Wed Sep 26 08:05:11 EST 2012 package log: [09/26/12 08:04:08]   Update Package Execution Started
[09/26/12 08:04:08]   Original command line: C:\dell\suu\1641566\Network_Driver_TJPWC_WN32_3.00.08_A00.EXE /s /l=C:\Windows\TEMP\DUP.log
[09/26/12 08:04:08]   DUP Framework EXE Version: 3.0.92.1
[09/26/12 08:04:08]   DUP Release: TJPWCA00-00
[09/26/12 08:04:08]   Intializing framework...
[09/26/12 08:04:08]   Server Infastructure Detected...Proceeding with PM Module...
[09/26/12 08:04:08]   Querying if HAPI is Installated...
[09/26/12 08:04:08]   HAPI already Installated...
[09/26/12 08:04:08]   Querying Personality Module for data via ..GetPersonalityInfo()
[09/26/12 08:04:08]   Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[09/26/12 08:04:08]   Obtained Personality Information
[09/26/12 08:04:08]   Manufacturers name :
[09/26/12 08:04:08]   Data Location :
[09/26/12 08:04:08]   Copied all Personality Information to Framework
[09/26/12 08:04:08]   Querying Personality Module Succeeded...
[09/26/12 08:04:08]   Retrieving relevant Values from Personality Module...
[09/26/12 08:04:08]   Client Brand Status:- DEFAULT
[09/26/12 08:04:08]   User Command: unattended
[09/26/12 08:04:08]   DUP Capabilities Value: 14680063 (0xDFFFFF)
[09/26/12 08:04:08]   DUP Vendor Software Version: 3.00.08
[09/26/12 08:04:08]   Local System/Model Compatible with this Package? Yes
[09/26/12 08:04:08]   Local System OS Version: 6.1.1.0
[09/26/12 08:04:08]   OS Compatible with this Package? Yes
[09/26/12 08:04:08]   Local System OS Language: EN
[09/26/12 08:04:08]   Language Compatible with this Package? Yes
[09/26/12 08:04:08]   User Parameter: logfile
[09/26/12 08:04:08]   User Parameter: logfile changed to: c:\windows\temp\dup.log
[09/26/12 08:04:09]   Identified Behavior : unattended
[09/26/12 08:04:09]   Temporary payload log file name: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPC35E.tmp
[09/26/12 08:04:09]   Translated Command Line : QLogicSetup.exe /s /z"/vtdriver /logfile=\"C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPC35E.tmp\""
[09/26/12 08:04:09]   Path : C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00
[09/26/12 08:04:09]   Identified Behavior : unattended
[09/26/12 08:05:11]   Append Vendor Software Log: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPC35E.tmp
[09/26/12 08:05:11]
--- Start of Vendor Software Log ---

[09/26/12 08:05:11]
--- End of Vendor Software Log ---

[09/26/12 08:05:11]   Vendor Software Return Code: 1603
[09/26/12 08:05:11]   Name of Exit Code: ERROR
[09/26/12 08:05:11]   Exit Code set to: 1 (0x1)
[09/26/12 08:05:11]   Result: FAILURE
[09/26/12 08:05:11]   Name of Exit Code: ERROR
[09/26/12 08:05:11]   Execution terminated at date-time 09/26/12 08:05:11
[09/26/12 08:05:11]   ######
Wed Sep 26 08:32:25 EST 2012 Network_Driver_TJPWC_WN32_3.00.08_A00.EXE - update unsuccessful, see support log
Wed Sep 26 08:32:25 EST 2012 package log: [09/26/12 08:31:22]   Update Package Execution Started
[09/26/12 08:31:22]   Original command line: C:\dell\suu\84458088\Network_Driver_TJPWC_WN32_3.00.08_A00.EXE /s /l=C:\Windows\TEMP\DUP.log
[09/26/12 08:31:22]   DUP Framework EXE Version: 3.0.92.1
[09/26/12 08:31:22]   DUP Release: TJPWCA00-00
[09/26/12 08:31:22]   Intializing framework...
[09/26/12 08:31:22]   Server Infastructure Detected...Proceeding with PM Module...
[09/26/12 08:31:22]   Querying if HAPI is Installated...
[09/26/12 08:31:22]   HAPI already Installated...
[09/26/12 08:31:22]   Querying Personality Module for data via ..GetPersonalityInfo()
[09/26/12 08:31:22]   Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[09/26/12 08:31:22]   Obtained Personality Information
[09/26/12 08:31:22]   Manufacturers name :
[09/26/12 08:31:22]   Data Location :
[09/26/12 08:31:22]   Copied all Personality Information to Framework
[09/26/12 08:31:22]   Querying Personality Module Succeeded...
[09/26/12 08:31:22]   Retrieving relevant Values from Personality Module...
[09/26/12 08:31:22]   Client Brand Status:- DEFAULT
[09/26/12 08:31:22]   User Command: unattended
[09/26/12 08:31:22]   DUP Capabilities Value: 14680063 (0xDFFFFF)
[09/26/12 08:31:22]   DUP Vendor Software Version: 3.00.08
[09/26/12 08:31:22]   Local System/Model Compatible with this Package? Yes
[09/26/12 08:31:22]   Local System OS Version: 6.1.1.0
[09/26/12 08:31:22]   OS Compatible with this Package? Yes
[09/26/12 08:31:22]   Local System OS Language: EN
[09/26/12 08:31:22]   Language Compatible with this Package? Yes
[09/26/12 08:31:22]   User Parameter: logfile
[09/26/12 08:31:22]   User Parameter: logfile changed to: c:\windows\temp\dup.log
[09/26/12 08:31:23]   Identified Behavior : unattended
[09/26/12 08:31:23]   Temporary payload log file name: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6363.tmp
[09/26/12 08:31:23]   Translated Command Line : QLogicSetup.exe /s /z"/vtdriver /logfile=\"C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6363.tmp\""
[09/26/12 08:31:23]   Path : C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00
[09/26/12 08:31:23]   Identified Behavior : unattended
[09/26/12 08:32:25]   Append Vendor Software Log: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUP6363.tmp
[09/26/12 08:32:25]
--- Start of Vendor Software Log ---

[09/26/12 08:32:25]
--- End of Vendor Software Log ---

[09/26/12 08:32:25]   Vendor Software Return Code: 1603
[09/26/12 08:32:25]   Name of Exit Code: ERROR
[09/26/12 08:32:25]   Exit Code set to: 1 (0x1)
[09/26/12 08:32:25]   Result: FAILURE
[09/26/12 08:32:25]   Name of Exit Code: ERROR
[09/26/12 08:32:25]   Execution terminated at date-time 09/26/12 08:32:25
[09/26/12 08:32:25]   ######
Wed Sep 26 08:33:03 EST 2012 Network_Driver_8D5KK_WN32_13.5.0_A00.EXE - update successful
Wed Sep 26 08:38:08 EST 2012 Network_Driver_TJPWC_WN32_3.00.08_A00.EXE - update unsuccessful, see support log
Wed Sep 26 08:38:08 EST 2012 package log: [09/26/12 08:37:06]   Update Package Execution Started
[09/26/12 08:37:06]   Original command line: C:\dell\suu\92764010\Network_Driver_TJPWC_WN32_3.00.08_A00.EXE /s /l=C:\Windows\TEMP\DUP.log
[09/26/12 08:37:06]   DUP Framework EXE Version: 3.0.92.1
[09/26/12 08:37:06]   DUP Release: TJPWCA00-00
[09/26/12 08:37:06]   Intializing framework...
[09/26/12 08:37:06]   Server Infastructure Detected...Proceeding with PM Module...
[09/26/12 08:37:06]   Querying if HAPI is Installated...
[09/26/12 08:37:06]   HAPI already Installated...
[09/26/12 08:37:06]   Querying Personality Module for data via ..GetPersonalityInfo()
[09/26/12 08:37:06]   Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[09/26/12 08:37:06]   Obtained Personality Information
[09/26/12 08:37:06]   Manufacturers name :
[09/26/12 08:37:06]   Data Location :
[09/26/12 08:37:06]   Copied all Personality Information to Framework
[09/26/12 08:37:06]   Querying Personality Module Succeeded...
[09/26/12 08:37:06]   Retrieving relevant Values from Personality Module...
[09/26/12 08:37:06]   Client Brand Status:- DEFAULT
[09/26/12 08:37:06]   User Command: unattended
[09/26/12 08:37:06]   DUP Capabilities Value: 14680063 (0xDFFFFF)
[09/26/12 08:37:06]   DUP Vendor Software Version: 3.00.08
[09/26/12 08:37:06]   Local System/Model Compatible with this Package? Yes
[09/26/12 08:37:06]   Local System OS Version: 6.1.1.0
[09/26/12 08:37:06]   OS Compatible with this Package? Yes
[09/26/12 08:37:06]   Local System OS Language: EN
[09/26/12 08:37:06]   Language Compatible with this Package? Yes
[09/26/12 08:37:06]   User Parameter: logfile
[09/26/12 08:37:06]   User Parameter: logfile changed to: c:\windows\temp\dup.log
[09/26/12 08:37:07]   Identified Behavior : unattended
[09/26/12 08:37:07]   Temporary payload log file name: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPA514.tmp
[09/26/12 08:37:07]   Translated Command Line : QLogicSetup.exe /s /z"/vtdriver /logfile=\"C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPA514.tmp\""
[09/26/12 08:37:07]   Path : C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00
[09/26/12 08:37:07]   Identified Behavior : unattended
[09/26/12 08:38:07]   Append Vendor Software Log: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPA514.tmp
[09/26/12 08:38:07]
--- Start of Vendor Software Log ---

[09/26/12 08:38:07]
--- End of Vendor Software Log ---

[09/26/12 08:38:07]   Vendor Software Return Code: 1603
[09/26/12 08:38:07]   Name of Exit Code: ERROR
[09/26/12 08:38:07]   Exit Code set to: 1 (0x1)
[09/26/12 08:38:07]   Result: FAILURE
[09/26/12 08:38:07]   Name of Exit Code: ERROR
[09/26/12 08:38:07]   Execution terminated at date-time 09/26/12 08:38:07
[09/26/12 08:38:07]   ######
Wed Sep 26 10:45:19 EST 2012 Network_Driver_8D5KK_WN32_13.5.0_A00.EXE - update successful
Wed Sep 26 10:45:19 EST 2012 Network_Driver_TJPWC_WN32_3.00.08_A00.EXE - update unsuccessful, see support log
Wed Sep 26 10:45:19 EST 2012 package log: [09/26/12 10:44:18]   Update Package Execution Started
[09/26/12 10:44:18]   Original command line: C:\dell\suu\183484254\Network_Driver_TJPWC_WN32_3.00.08_A00.EXE /s /l=C:\Windows\TEMP\DUP.log
[09/26/12 10:44:18]   DUP Framework EXE Version: 3.0.92.1
[09/26/12 10:44:18]   DUP Release: TJPWCA00-00
[09/26/12 10:44:18]   Intializing framework...
[09/26/12 10:44:18]   Server Infastructure Detected...Proceeding with PM Module...
[09/26/12 10:44:18]   Querying if HAPI is Installated...
[09/26/12 10:44:18]   HAPI already Installated...
[09/26/12 10:44:18]   Querying Personality Module for data via ..GetPersonalityInfo()
[09/26/12 10:44:18]   Entered GetPersonalityInfo,Waiting for results...from PMDataCollector.lib->getPMInfo()
[09/26/12 10:44:18]   Obtained Personality Information
[09/26/12 10:44:18]   Manufacturers name :
[09/26/12 10:44:18]   Data Location :
[09/26/12 10:44:18]   Copied all Personality Information to Framework
[09/26/12 10:44:18]   Querying Personality Module Succeeded...
[09/26/12 10:44:18]   Retrieving relevant Values from Personality Module...
[09/26/12 10:44:18]   Client Brand Status:- DEFAULT
[09/26/12 10:44:18]   User Command: unattended
[09/26/12 10:44:18]   DUP Capabilities Value: 14680063 (0xDFFFFF)
[09/26/12 10:44:18]   DUP Vendor Software Version: 3.00.08
[09/26/12 10:44:18]   Local System/Model Compatible with this Package? Yes
[09/26/12 10:44:18]   Local System OS Version: 6.1.1.0
[09/26/12 10:44:18]   OS Compatible with this Package? Yes
[09/26/12 10:44:18]   Local System OS Language: EN
[09/26/12 10:44:18]   Language Compatible with this Package? Yes
[09/26/12 10:44:18]   User Parameter: logfile
[09/26/12 10:44:18]   User Parameter: logfile changed to: c:\windows\temp\dup.log
[09/26/12 10:44:19]   Identified Behavior : unattended
[09/26/12 10:44:19]   Temporary payload log file name: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPD6AF.tmp
[09/26/12 10:44:19]   Translated Command Line : QLogicSetup.exe /s /z"/vtdriver /logfile=\"C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPD6AF.tmp\""
[09/26/12 10:44:19]   Path : C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00
[09/26/12 10:44:19]   Identified Behavior : unattended
[09/26/12 10:45:19]   Append Vendor Software Log: C:\Users\MyUserID\AppData\Local\dell\drivers\Network_Driver_TJPWC_WN32_3.00.08_A00\DUPD6AF.tmp
[09/26/12 10:45:19]
--- Start of Vendor Software Log ---

[09/26/12 10:45:19]
--- End of Vendor Software Log ---

[09/26/12 10:45:19]   Vendor Software Return Code: 1603
[09/26/12 10:45:19]   Name of Exit Code: ERROR
[09/26/12 10:45:19]   Exit Code set to: 1 (0x1)
[09/26/12 10:45:19]   Result: FAILURE
[09/26/12 10:45:19]   Name of Exit Code: ERROR
[09/26/12 10:45:19]   Execution terminated at date-time 09/26/12 10:45:19
[09/26/12 10:45:19]   ######

↧

CCTK Log File

February 4, 2014, 9:55 am

≫ Next: Openmanage Essentials Installed but appears to do nothing

≪ Previous: QLOGIC update not working via SUU for m710HDs

I am pushing the exported exe from CCTK as a package via Kaspersky. I am using local workstation credentials to authenticate the install. Kaspersky is reporting that the exe completed the process successfully, but I want to verify this by looking at the log that the exe creates. I cannot find it, however.

I have looked in the user directory of the credentials that I used but no trace of it was found.

Any other places it logs when run this way?

↧

Openmanage Essentials Installed but appears to do nothing

February 4, 2014, 8:09 pm

≫ Next: OMSA on Windows Server 2008 R2

≪ Previous: CCTK Log File

G'Day All,

I have installed OME 1.2 and the patch onto a Windows 2008R2 server, after pre-requisites were installed the OME software installed with no apparent issues, but there appears to be no "activity" from OME. I cant discover anything, I have added 6 servers by FQDN, all are DELL R620 servers, all with SNMP installed and I can do an SNMPwalk from my PC.

I would expect to see something in the dashboard but OME appears to be just sitting there doing nothing to get back any kind of information from the servers. What am I missing here??????

Sid

↧

OMSA on Windows Server 2008 R2

February 5, 2014, 5:41 am

≫ Next: OMSA Patch 7.3.0.1

≪ Previous: Openmanage Essentials Installed but appears to do nothing

I can't figure out why I can't install the patch update 7.0.3.1 on a few of my above referenced servers, I don't get an error, it tries to install the patch then rolls back.

↧

OMSA Patch 7.3.0.1

February 6, 2014, 1:58 am

≫ Next: DSET for R810 running Citrix XenServer 6.1

≪ Previous: OMSA on Windows Server 2008 R2

I have tried to install the patch on 2 servers (Win 2012 R2 on a R520 and Win 2012 R1 on a T410) and on both it fails saying the file Data1.cab is corrupt (had to enable logging though) and crashes the installed OMSA. I have tried to add it to the normal OMSA 7.3 installation with TRANSFORM= but it also fails. I haven't found any Data1.cab...

↧

DSET for R810 running Citrix XenServer 6.1

February 7, 2014, 6:31 pm

≫ Next: How to install and configure iDRAC Service Module?

≪ Previous: OMSA Patch 7.3.0.1

Where can I download the correct version of DSET for an R810 running Citrix XenServer 6.1?

↧

How to install and configure iDRAC Service Module?

February 12, 2014, 3:33 am

≫ Next: Proxy server

≪ Previous: DSET for R810 running Citrix XenServer 6.1

The Integrated Dell Remote Access Controller(iDRAC) Service Module is a lightweight optional software application that can be installed on Dell 12G Server or later. The iDRAC Service Module complements iDRAC interfaces – Graphical User Interface (GUI), RACADM CLI and Web Service Management (WSMAN) with additional monitoring data. You can configure the features on the supported operating system depending on the features to be installed and the unique integration needs in a work environment.

The iDRAC Service Module architecture uses IP socket communication and provides additional Server Management data (OS/device driver) to iDRAC and presents one-to-many consoles with access to Systems Management data through OS standard interfaces.

For more information, see the following video tutorials.

Installing iDRAC Service Module on Microsoft Windows OS

(Please visit the site to view this video)

Configuring iDRAC Service Module

(Please visit the site to view this video)

↧

Proxy server

February 12, 2014, 10:16 pm

≫ Next: Video driver

≪ Previous: How to install and configure iDRAC Service Module?

How do I get my Venue 11 Pro to not default to proxy server? I don't use one but it always tries to start that way. I turn it off but the next time I start up it is back on.

↧

Video driver

February 12, 2014, 10:18 pm

≫ Next: Attension dell 1537 bios computrace status

≪ Previous: Proxy server

Three times within a week my new Venue 11 Pro has said that the video driver stopped working. What is the problem? Solution?

↧

Attension dell 1537 bios computrace status

February 13, 2014, 5:16 am

≫ Next: OMSA 7.3 broken in RHEL / CentOS6.4

≪ Previous: Video driver

Hi I activated the computrace status part at bios and ı tried to fix it but i couldnt. and my computers antivirus program percieved that application like a normal virus .Many appliactions are not working .No one could help us about that subject in Turkey . the product is mine and ı have bills too. Can you help for closing the computrace at bios ? thank you very much Please help i'm from turkey

↧

OMSA 7.3 broken in RHEL / CentOS6.4

September 11, 2013, 8:47 am

≫ Next: iDRAC 6 Openssh vulnerabilities

≪ Previous: Attension dell 1537 bios computrace status

Hello,

Looks like a change in RHEL 6.3 -> 6.4 breaks some Dell OMSA functionality.

https://www.redhat.com/archives/rhelv6-list/2013-February/msg00033.html

I've just confirmed the issue on a PE1950 - the service dsm_sa_datamgrd refuses to start meaning you don't get any inventory or health info.

[root@myhost etc]# service dataeng status
dsm_sa_datamgrd is stopped
dsm_sa_eventmgrd (pid 27528) is running
dsm_sa_snmpd (pid 27585) is running

Are there any workarounds or plans to fix this on the Dell side of things?

Thanks

Nick

↧

iDRAC 6 Openssh vulnerabilities

February 13, 2014, 11:22 am

≫ Next: key board mouse

≪ Previous: OMSA 7.3 broken in RHEL / CentOS6.4

We were testing out dell's iDRAC software on an older gen server with idrac 6 embedded. I scanned this device with nessus, and it looks like even with the most recent firmware available (1.96) Dell appears to be using openssh 5.2 while the most current is 6.5. I realize that dell has deprecated iDRAC 6 and moved to 7, but are there any plans to update the firmware to address this vulnerability in iDRAC 6?

↧

key board mouse

February 16, 2014, 5:16 pm

≫ Next: DSM SA Data Manager won't start after updating firmware and driver on H700 Controller

≪ Previous: iDRAC 6 Openssh vulnerabilities

How do I cancel my key board mouse with windows 7!!!

↧

DSM SA Data Manager won't start after updating firmware and driver on H700 Controller

January 7, 2014, 7:13 am

≫ Next: Update idrac6 from v1.20.01 to latest firmware

≪ Previous: key board mouse

I have been updating firmware on a bunch of our T710 and R710 servers recently for the H700 Controller. I have been noticing now that the DSM SA Data Manager service is no longer starting when the server reboots and when I manually try to start the service, I am getting the following:

Windows could not start the DSM SA Data Manager service on Local Computer. Error 1067: The process terminated unexpectedly.

When I look at the Windows Event log, I am seeing the following three entries being entered:

Log Name: Application

Source: Application Error

Date: 1/7/2014 8:53:45 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: 00079LPTV01.dcsg.com

Description:

Faulting application name: dsm_sa_datamgr32.exe, version: 5.9.5.696, time stamp: 0x4d39fc39

Faulting module name: dchbas32.dll, version: 7.2.0.3999, time stamp: 0x50602be4

Exception code: 0xc0000005

Fault offset: 0x0001df58

Faulting process id: 0x1a70

Faulting application start time: 0x01cf0bafd732cbf1

Faulting application path: C:\Program Files (x86)\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr32.exe

Faulting module path: C:\Windows\system32\dchbas32.dll

Report Id: 1f793da1-77a3-11e3-b0de-d067e5f99ca8

Event Xml:

<Channel>Application</Channel>

</System>

<Data>dsm_sa_datamgr32.exe</Data>

<Data>dchbas32.dll</Data>

<Data>C:\Program Files (x86)\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr32.exe</Data>

<Data>C:\Windows\system32\dchbas32.dll</Data>

</EventData>

</Event>

Entry 2:

Log Name: Application

Source: Windows Error Reporting

Date: 1/7/2014 8:53:45 AM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: 00079LPTV01.dcsg.com

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: dsm_sa_datamgr32.exe

P2: 5.9.5.696

P3: 4d39fc39

P4: dchbas32.dll

P5: 7.2.0.3999

P6: 50602be4

P7: c0000005

P8: 0001df58

P9:

P10:

Attached files:

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr32_61b1465496169981f95e8d5a11936a42a56d6074_159d8c28

Analysis symbol:

Rechecking for solution: 0

Report Id: 1f793da1-77a3-11e3-b0de-d067e5f99ca8

Report Status: 4

Event Xml:

<Channel>Application</Channel>

</System>

<Data>

</Data>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>dsm_sa_datamgr32.exe</Data>

<Data>dchbas32.dll</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr32_61b1465496169981f95e8d5a11936a42a56d6074_159d8c28</Data>

<Data>

</Data>

</EventData>

</Event>

Entry 3:

Log Name: Application

Source: Windows Error Reporting

Date: 1/7/2014 8:53:45 AM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: 00079LPTV01.dcsg.com

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: dsm_sa_datamgr32.exe

P2: 5.9.5.696

P3: 4d39fc39

P4: dchbas32.dll

P5: 7.2.0.3999

P6: 50602be4

P7: c0000005

P8: 0001df58

P9:

P10:

Attached files:

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr32_61b1465496169981f95e8d5a11936a42a56d6074_159d8c28

Analysis symbol:

Rechecking for solution: 0

Report Id: 1f793da1-77a3-11e3-b0de-d067e5f99ca8

Report Status: 0

Event Xml:

<Channel>Application</Channel>

</System>

<Data>

</Data>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>dsm_sa_datamgr32.exe</Data>

<Data>dchbas32.dll</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr32_61b1465496169981f95e8d5a11936a42a56d6074_159d8c28</Data>

<Data>

</Data>

</EventData>

</Event>

Most of the systems are running OMSA 6.5 with a few scattered to 6.3 and 6.2.

Any help in getting this service to restart would be appreciated. Thanks in advance!

↧

Update idrac6 from v1.20.01 to latest firmware

February 17, 2014, 8:16 pm

≫ Next: 64-bit Windows SUU availability

≪ Previous: DSM SA Data Manager won't start after updating firmware and driver on H700 Controller

I cannot for the life of me get this idrac6 updated.

The posts I've read so far say to:

1) iDRAC updates via iDRAC web GUI

2) iDRAC updates via command line using RACADM

1) This option is to get the .IMG file update package, extract the file then perform an update either through the DRAC web GUI (assuming your iDRAC is connected to the network and addressable). To do that you type in the IP address of your DRAC card in any web browser, log in with the username / password (if you haven’t changed anything u:root p:calvin) then click on the iDRAC Settings > Update tab. Point the GUI towards the firmware image, and you should be good to go.

2) Using a tool called RACADM (Remote Access Controller Administrator) you can update the firmware via a command line. The comand to update firmware is racadm fwupdate -p -u -d <path>

1, my GUI doesn't have a update tab, it must be a version 1.2 thing.

2, I've installed racadm and run the following command:

C:\Program Files (x86)\Dell\SysMgt\rac5>racadm.exe -r 10.1.40.14 -u root -p calvin fwupdate -p -u -d C:\delldracz
where 10.1.10.14 is the IP of the drac port, and C:\delldracz is the folder where the firmimg.d6 image is stored

This starts off ok, says it uploading the firmware, then after about 5-10 minutes i get the error "ERROR: Unable to transfer image file to the RAC."

If i try to run racreset or racreset hard, I get: "ERROR: A firmware update is currently in progress. Unable to reset the RAC at this time."

Powering off the machine and pulling the powercord for 30 seconds fixes this issue, have tried to update to v1.5 first, still same error.

Its a T610, with ESXI 5.0 installed.

Any help would be appreciated.

_bk201.