BackupExec HP-Proliant-DL380G6-P410i

It seems to be an old problem, but I did not succeed in spite of all the
hints I found:
Starting the Symantec-BackupExec-Agent causes the system to do a
cold-reset (after one or 2 minutes).
Hardware:
HP-Proliant DL 380 G6
System ROM: P62 08/16/2010
SmartArray P410i Controller on System-Board: FirmwareVersion 3.50
OS:
NetWare6.5SP8
CompaqSupportPack 8.20
HPQCISS.HAM v 1.16b
Thanks for help
Oskar

Hello *,
thanks a lot!
The firmware, the proliant support packs (the required parts of them)
and the HPQCISS-driver has been up to date already.
The solution was the "HP Insight Management Storage Agents for NetWare
Version 8.21 (probably in combination of all updates before) ...
The Backup works with a excellent performance ~2.5GB/min
Thanks!
Oskar
Am 21.06.2011 21:47, schrieb wiegandb:
> Hello,
>
> in addition to what Anders Gustafsson said this may also help:
> "http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId =3884082&prodTypeId=15351&prodSeriesId=3884082&obj ectID=c02577266"
>
> saying that you need to update the driver HPQCISS.HAM v 1.16b (already
> done) and HP Insight Management Storage Agents for NetWare Version 8.21
> (or later) from
> "http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=1 5351&prodSeriesId=3884082&prodNameId=3884083&swEnv OID=1064&swLang=8&mode=2&taskId=135&swItem=MTX-291bf28cb02f4b028e6c83d193"
>
>
> Regards and good luck
>
> Burkhard Wiegand
>
> Netware Admin
> Debeka-Versicherungen
> D-56068 Koblenz

Similar Messages

OVM 3.3 on HP ProLiant DL 380 G7

Morning folks,
I'm considering using OVM 3.3 to virtualize multiple PCs which I currently use for RAC, Cloud Control, etc. into a single physical server. The server I'm considering is an HP ProLiant DL380 G7. According to Oracle's HCL, the DL380 G7 is good to go for OVM 3.3 and even OL 7. I have 3 questions:
1. The DL380 G7 contains a P410i RAID controller. I've seen elsewhere on the internet people reporting problems with earlier versions of OVM not seeing LUNs presented using this controller, even though that controller was in a different model ProLiant. Does anyone have direct experience of the DL380 G7 working fine with OVM 3.3 with the P410i controller?
2. For RAC, I still intend to use a separate PC running Openfiler for the shared storage. This works like a charm when I use bare metal Linux installs on my PC RAC nodes, but I've never used it when the RAC nodes have been virtualized using OVM. Does anyone know if this works? All Openfiler does is present iSCSI targets to Linux, so I can't see why a VM Linux node would not work when a bare metal Linux mode does.
3. Any other issues with the DL380 G7 I should be aware of?
Thanks in advance for any help, tricks or tips you can provide.
All the best!

A workaround found - remote install using LightsOut.

OVS 2.2.1 install on HP ProLiant BL465c G7 Blade

I'm installing OVS on a HP ProLiant DL465c G7 Blade. The installation bombs at the beginning because it doesn't recognize the storage adapter. It prompts me for a driver disk but I need advise on how to do this. The server uses a HP SmartArray P410i Controller. [Would this be the correct driver to use|http://bit.ly/hjAgGZ] (64bit Redhat 5)?
Can I use a USB Thumb drive to install this driver when booting/installing OVS from CDROM? Should I modify the installation source? Any help/advice/prayers would be appreciated!
Edited by: 816964 on Apr 15, 2011 2:38 PM

Nevermind, I figured it out. In case any other noobs (like me) need help in the future - here's what I did:
I created an ext2 formatted 1GB USB stick (single Linux partition).
     1. I downloaded the driver RPM's from HP's website (Use RHEL5 x64 i386 drivers)
     2. I copied the drivers to the USB stick (root directory)
     3. Inserted the USB stick in the server (server powered off)
     4. Booted to the OVS 2.2.1 installation CDROM
     5. The installation automatically loaded the drivers from the USB stick
I should have tried this before posting. I hang my head in shame.
Edited by: 816964 on Apr 18, 2011 1:22 PM

ProLiant DL360 G6 + MSA60 and 411 Array

Hello! I have strange issue with my old ProLiant DL360 G6 and HPStorage MSA60 I have two DL360 G6 servers (one in production and one in my office) and two MSA60 Storage, witch connect to DL. In my production enviroment Battery on Array 411 is failed. I take battery and cache module from my office DL360 and plug it into production server. Everything fine and working like charm. Now i have DL360 G6 with no battery and no cache for 411. I unplug cache and battery from P410i array and plug it to 411 (MSA60 is connect to this array) Server start, but i doesn see my MSA60 and get this message: Controller: Smart Array P411 in Slot 1 is connected to a SAS expander which is not supported due to a missing cache module, out of date firmware, or unsupported configuration. Access to the storage may be disabled. If access to the storage is available, making any configuration change will lead to potential data loss on those logical drives. So, my question is: Does battery and cache from P410i can be using with 411 array controller or not? Or i did something wrong?...

Hi:
You may also want to post your question on the HP Business Support Forum -- DL Servers section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264

Solaris 10 x86 installation problem on ProLiant DL380..

I'm trying to put Sol10 b72 on a dual-proc ProLiant DL380 here, with the Compaq 5i array controller.
I have the Solaris 9 drivers from HP; they seem to work just fine for the installation.
The problem comes at the end of the first disc.
Sidebar:
For one thing (and this drove me NUTS until I got lucky and caught it during a reboot), at the end of the install, on the console, it asks for the driver diskettes..again.
The problem is, it doesn't say this ANYWHERE else, only on the console..and if you're doing the installation in the X desktop, you just never know it. It doesn't write this to the xconsole window. I tried installing a good 5-6 times before, instead of hitting the power button out of frustration after the install just hung again, I actually opened up a terminal and typed 'reboot'..and caught the "Please insert the diskette and press Enter" as it killed X. If anyone at Sun is reading this..you may want to fix this, before someone gets very frustrated that their installations never seem to finish...
End Sidebar.
So...I'm doing the console text install (otherwise you'll never see the message to insert the driver diskettes for the Broadcom NIC and the Compaq array), and sure enough, at the end of the install, it asks for the diskette. I pop in the diskette it's specifically asking for (the Compaq array diskette in this instance), and hit enter. It chugs for a second and then says it can't find the driver on the diskette.
Which is incorrect, because if it haden't found it on the diskette during the device configuration assistant phase during bootup, it wouldn't have even been able to install Solaris.
So..what's up? Anyone have any ideas why Solaris finds it one time but can't find it later? Is this a bug or problem in the installation script?
Thanks,
Greg

problem 1 is that it's looking for ../../s0.. Which I
managed to
fake out by creating the dir in the same mount
point.
Problem 2 is that it can't find .tmp_proto, which I
must
concur with. I can't find that on any of the b72 cd
images.
So, the setup_install_server fails.This seems to be the problem when you try to setup an install
server on a Solaris SPARC system for Solaris x86 clients, using
the Solaris 9 or Solaris 10/Express CD media.
There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
and it's supposed to be mounted on the "s0" mount point,
otherwise setup_install_server won't work. On a Solaris x86 box,
vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
mount point for the platform independant ISO9660 part of the CD
media, /cdrom/cdrom0/s0 is the UFS root filesystem.
Problem is that Solaris SPARC:
- does not understand Solaris x86 disk labels
- does not allow mounting x86 UFS filesystems
(and vice versa).
AFAIK, Solaris 9 DVD media does not have this problem. I
guess the same will be true when Solaris 10 DVD media is
available in a few months. On the DVD media there's enough
free space to include an extra copy of the files in the ISO9660
filesystem.

Problem booting Solaris 10 on ProLiant server after installation.

Hi all!
I have a brand new HP ProLiant DL360 G5 server. It contains 6 internal
hard drives. RAID 5 is configured on these drives using built-in HP
Smart Array P400i controller. I've just installed Solaris 10 8/07 on this
server. Solaris requires a driver for P400i controller. I'm using Driver
Update CD created from HP provided ISO image. Solaris 10 is
officially supported OS for DL360 G5 server.
Installation proceeds as expected:
1) At the begining of Solaris installation, Driver Update is used to
load HP driver for raid controller. During installation, disk is
recognized as c1d0t0 (the only disk in system); one partition is
created on this disk.
2) Disk is devided to 6 slices:
c1d0t0s0 - swap, 4GB
c1d0t0s1 - /, cca 32GB
c1d0t0s[3,4,5,6] - /zones/[a,b,c,d] - each cca 160GB
3) At the end of installation, CPQary3 driver is installed to target
system without any errors reported. No errors are reported during
installation at all.
After reboot, GRUB is started. It shows boot menu containing two
options:
- Solaris 'normal' boot
- failsafe boot
PROBLEM: Selecting 'normal' boot leads to immediate system restart.
According to documentation, this case occurs when PCQary3
driver is not installed.
I'm able to boot using 'failsafe' option in grub. After entering single
user, I load PCQary3 driver to runtime using 'install-du' command.
I'm also able to find instaled Solaris using 'install-recovery' and mount
its root volume to /a directory. Necessary driver IS installed inside
/a/kernel/drv/ directory. Options 'bootpath' in /a/boot/solaris/bootenv.rc
file is set up correctly pointing to device associated with /dev/dsk/c1d0t0s1
device. Also GRUB is able to recognize UFS filesystem for boot partition.
I've already tried (without success):
1) Use RAID 1+0 instead of RAID5
2) Create only 3,5GB partition instead of 700GB large one.
3) Place / on c1d0t0s0 instead of c1d0t0s1.
4) Re-create boot archive using 'bootadm update-archive -R /a'
So, everything seems to be installed correctly, but system cannot boot.
Do you have any ideas how to fix this problem?
Jozef

Sounds like an issue I just had with a brand new X4150, installation and failsafe worked fine, but normal booting led to immediate reboot of the server. This was due to an incompatibility of solaris and intel's newest generation xeon chips.
You can still boot 'normal' solaris in 32-bit mode:
hit 'e' at the grub menu, 'e' again to edit the 'normal' boot entry and add 'kernel/unix' after multiboot. This should boot up solaris in 32-bit mode. From there, download and install the latest patch set (125370-06 and 127112-05 are fixing this issue). After that you should be fine.
Bjoern

Installation Problem: Solaris 8 on a HP ProLiant DL360G3

When i try to install Solaris 8 02/02 on a ProLiant DL360G3 (3GHz, 2GB RAM, 18GB-SCSI) with a Broadcom NetExtreme Gigabit-NIC 5703 , the following error message appears when Solaris is trying to boot for the first time from cd:
Boot panic: traptyp e, error 0 at 1357d9
cr0: 80000011, cr2: 8, cr3: 17d000
eax: 0, ebx: 17ff78, ecx: 24e8d8, edx: ffffffff
esi: 0, edi: 800, ebp: 1fc78, esp: 1fc60
cs: 10, eip: 1357d9, ds: 63700008, es: 70640008
Entering boot debugger:
[1357d9]
Maybe a driver problem?? I have tried all drivers i found (from HP or Broadcom�s Website), but it doesn�t solve the problem.

Hold down the STOP key and also press the A key to get the Sparc 20 to come to the ok prompt. At the ok prompt type boot cdrom
press enter and away you go. Solaris will 'at a later time' ask you if you want to format the drive.
One Note: Sometimes the Sparc can be a pain to get to the ok prompt. Watch your keyboard lights ie: Num lock, Caps lock etc. right after they get tested and flash, press stop and A. Sometimes you have to hold down the stop and press the A key by itself. Hope this helps.
Carl

Install Solaris10 on HP ProLiant ML370 G6, "No Disk" error

Hello,
I want to install Solaris10 on HP ProLiant ML370 G6 servers which are on the Hardware Compatible List( HCL). However, I always encounter "No disk" issue and installation fails. The disks are HP SAS disks.
I searched online and knew that CPQAry3 driver must to be installed first. I did but the "No disk" error still happens later.
I am wondering what else I should do?
Tom

Hi Tom,
You have to apply the ROMPaq Firmware Upgrade before.
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=emea_africa&prodNameId=3884311&prodTypeId=15351&prodSeriesId=3884310&swLang=13&taskId=135&swEnvOID=2023
Marco

HP Proliante 320 g8 and Windows 7 64 bit

I know that HP Proliante 320 g8 and HP Proliante 320 g8 v2 do not supported Windows 7, but our company already has bought these computers and license Windows 7. I can install Windows 7, but I do not have drivers. More precisely Windows wants drivers only on chipset and usb. Is it possible find this? May be i can install drivers for others Proliants?
p.s. sorry for my english

Hi:
You may also want to copy and paste your question to the HP Business Support Forum--Proliant Servers section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264#.Ul7yrdco7Gg

Nstalling Windows Home Server 2011 on a ProLiant ML350e Gen 8 Server (Nothing appearing in Operating System Selection During Install)

We just purchased Windows Home Server software that required a new server to be purchased. We went with the ProLiant350e Gen8 Server. IUpon starting up the new ProLiant server I booted from CD-Rom and got to the Windows Install program. I clicked "Install
A New Server" However, as soon as this page loads it gives me an error that says "Load Driver" "A required CD/DVD Drive Device Driver is Missing. If you have a floppy disk, CD, DVD, or USB flash drive, please insert it now." It gives
me the option to browse or click okay. Browse only brings up the (x:) Boot drive and VID. It doesn't find the driver in VID Than if I click okay it gives me a message that says "No Device Drivers were found. Make sure that the Installation media contains
the correct drivers and then click ok" I have tried to use smart provisioning but this fails as it cannot recognise the media from the DVD drive.
Thanks in advance,

You should use HP smart start DVD to install the Windows Home Server. If you are booting directly from the Windows DVD it would some times not detect the drivers because of the hardware compatibility issue. You should contact the the vendor and seek help
from him.
http://www.arabitpro.com

Service Pack for Proliant installing successfully but returning failure in OSD task sequence

Building bare metal servers with SCCM 2012 SP1 CU2 OSD and running into an issue with HPs where they attempt to install the Service Pack for Proliant 2013.02.0. I am using a package with a program. Here is the program command line:
Hpsum.exe /use_latest /allow_non_bundle_components /current_credential /silent
The application installs successfully but there is a distinct delay and then errors thrown that fails the TS. Setting 'continue on error' is a work around but not what I want to have in the production environment. How can I get around this issue?
This is the same exact package and program that ran perfectly fine in SCCM 2007, but we are seeing this as a new issue since the migration to SCCM 2012.
I'd like to solve this issue as well as get rid of the "Waiting for job status notification....InstallSoftware"
Any suggestions?
SMSTS.LOG
Invoking Execution Manager to install software InstallSoftware
12/3/2013 9:59:49 AM 1568 (0x0620)
Installing software for PackageID='WCD002D2' ProgramID='Silent install' AdvertID='WC120008' has started, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Waiting for installation job to complete.. InstallSoftware
12/3/2013 9:59:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:20 AM 1568 (0x0620)
Launching command shell. OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Windows station: WinSta0 OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Desk"Apple-tab-span" style="white-space:pre;"> OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
executing command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
executed command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:50 AM 1568 (0x0620)
CompleteExecution received InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
CompleteExecution processed InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
Received job completion notification from Execution Manager
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation completed with exit code 0x80070001
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation failed with error (0x80070001)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'=''
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
GetExecRequestMgrInterface successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Releasing job request, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Releasing of Job Request successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
CompleteJob successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
reference count 1 for the source D:\_SMSTaskSequence\Packages\WCD002D2 before releasing
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Released the resolved source D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
pInstall->Install(sPackageID, sProgramName), HRESULT=80070001 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Install Software failed, hr=0x80070001 InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Process completed with exit code 2147942401
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the action: HP Server Pack for ProLiant 2013.02.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
MP server http://MP_server.company.com. Ports 80,443. CRL=false.
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Setting authenticator TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set authenticator in transport TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Sending StatusMessage TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting message signatures. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting the authenticator. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
CLibSMSMessageWinHttpTransport::Send: URL: MP_server.company.com:80 CCM_POST /ccm_system/request
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Request was succesful. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionRetCode=-2147024895
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Clear local default environment TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Let the parent group (System Management Install) decides whether to continue execution
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
The execution of the group (System Management Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the last action: HP Server Pack for ProLiant 2013.02. Execution of task sequence failed.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)

Hello Guys!
HP ProLiant Support Pack / Service Pack uses different Exit Codes, due to that this software support other operating systems than Windows. Therefore HP has standardized to use other Exit Codes, which Windows Detect as failures.
HPSum Exit Codes:
ExitCode 1 = "Installation Successful"
ExitCode 2 = "Installation Successful, but a reboot is required"
ExitCode 3 = "Installation was canceled, or no components were updated"
EcitCode 9009 = "Installation did not complete. Check the path and make sure that the Installation exists at the specified location"
HP recommends to use following Batch File to workaround this issue for SCCM:
=======================START_BatchFile=============================
:Init
@Echo Off
Cls
:Main
Echo HP Proliant Service Pack Setup
Echo Source : %~dp0
Echo ===============================================================================
Echo Installing the HP Proliant Service Pack Setup
Echo Command: "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
"%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
:CheckForErrors
Echo HP Proliant Service Pack Stauts:
If "%errorlevel%"=="0" (
     Echo *******************************************************************************
Echo                            INSTALLATION FAILED!
Echo *******************************************************************************
exit 1
If "%errorlevel%"=="1" (
     Echo Installation Successful!
     exit 0
If "%errorlevel%"=="2" (
     Echo Installation Successful, but a reboot is required.
     exit 3010
If "%errorlevel%"=="3" (
     Echo Installation was canceled, or no components were updated
     exit 0
If "%errorlevel%"=="9009" (
     Echo Installation did not complete. Check the path and make sure that the
Echo Installation exists at the specified location:
Echo Path: %~dp0
Exit 1
:End
Echo An unknown status code was returned from the PSP.
Echo This status code is [%errorlevel%]. This will be treated as a success,
Echo but please check the installation to make sure it completedly properly!
Exit 0
=======================STOP_BatchFile=============================
God Luck!
Best Regards Anders Horgen

Win 8.1 install on HP ProLiant ML10 server

If i want to install win 8.1 proff on HP ProLiant ML10 server ( xeon 3.1 ghz processor ) so it can work or not ???????
Please help .....

Hi,
For ProLiant ML10, we can get following information in this link:
http://www.windowsservercatalog.com/item.aspx?idItem=3d94ac2f-058b-25af-7225-f6119e3c25f9&bCatID=1282
Regarding to install Windows 8.1, please refer to
System requirement of Windows 8.1, and then check if HP ProLiant ML10 server meets all system requirement of Windows 8.1.
In addition, I suggest that you can post the question in
Windows 8.1 forum, or contact with your hardware vendor to confirm this issue.
Hope this helps.
Best regards,
Justin Gu

HTTP.SYS fails to load after ProLiant NIC driver update on Server 2008 R2

Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command
prompt...) DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because
it has no enabled devices associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then
restore the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...

Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command prompt...)
DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because it has no enabled devices
associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then restore
the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...

Oracle Enterprise Server 8i 8.1.7 and HP Proliant ML350 G3

I would like if it has any clarification regarding the compatibility problem between Oracle Enterprise Server 8i 8.1.7 and HP Proliant ML350 G3 Server. I cann't proceed with the installation of Oracle Enterprise Server 8i 8.1.7 on that machine whilst the process just stop at first logo. When I'm using Oracle Enterprise Server 9i 9.1 version, the installation process can proceed successfully. But, my customer (own Oracle Enterprise Server 8i 8.1.7) requires to install Oracle 8i 8.1.7 not Oracle 9i 9.1 version.
So, please someone help me to rectify that problem !!!!!

Can it be installed? It probably can be (assuming we're talking XP Professional).
Is it certified? On the main OTN page, under "Get Support" is the certification & availability matrix. Following that down, you'll find that the Oracle client was certified on 8.1.7, subject to the application of a number of patchsets, but that the Oracle database was not. Windows 2000 was the latest flavor of Windows that was certified with the 8.1.7 database.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com

How to install windows server 2008r2 on proliant microserver with 8gb storage?

I've just purchased two HP Proliant N40 Microservers and am trying to install Windows 2008 Server R2 on them. They come with a single hard drive of just 250GB capacity so on one server I have used the two supplied drives to create a RAID1 array of 250GB and Windows installed fine.
On the second I have installed four WB Green 2TB drives and have configured them as RAID10 for the best performance and resilience. So I have a single disk showing to Windows of 4GB after the RAID array is built.
But Windows gets so far before failing saying it can't proceed (and giving no clue as to why). Googling the issue it seems that there is an issue with installing Windows on a drive with > 2TB. HP themselves talk about the use of RAID drivers for Windows here: http://h20584.www2.hp.com/hpgt/guides/select?lang=en&cc=us&prodTypeId=15351&prodSeriesId=4248009&lan... but the link is useless because the link it gives for downloading the driveres just displays a "Not authorised" screen.
I just want a simple way to install Windows 2008 using a secure, performant reliable set of discs. RAID10 gives me that but Windows won't install. It seems my only option is to format two RAID1 arrays to overcome this silly limitation.
Am I right? Or is there a way to configure the four disks as a RAID10 array that Windows can be installed on?
Thanks for any advice,
Ian

Update, install continues when drives are set to IDE...so it fails using RAID (1 or 10).

BackupExec HP-Proliant-DL380G6-P410i

Similar Messages

Maybe you are looking for