With the 1600 we found you need to first apply the latest ROMPAQ upgrade then install the server using SMARTSTART 5.40, Without the ROMPAQ it won't install the foundation AGents.
Web link for Proliant Support drivers...
We had a similar problem, due to the Heatsink thermal paste not being in contact all across the processor.
Lift off the heatsink and ensure the paste is spread all accross, reseat pinsink and twist heatsink to spread paste before locking down clamp.
Make sure you have the latest ROMpaq Install and then use
SmartStart 6+
We've had similar problems in the past and upgrading BIOS & ROMpaqs and then setup with latest SmartStart resolves most of the problems.
rename the SDAT4273 file as SETUP.EXE and add to your login scripts.
Path\SETUP.EXE /SILENT
/SILENT stops the splash screen and the users having to respond.
Below 333 Mhz processor only 512Mb memory was supported on the Proliant 3000 / 5500 system boards.
May need to configure as Single processor reverse HAL to single processor, disabling system config option.
Re-install Processor, enable system config and the upgrade HAL.
Do you have internal Hard disks or an external array.
Some of the Power supplies won't start up unless there is sufficient load (minimum 1HDD) if not then a dummy load card had to be fitted.
If you upgrade the latest bios the server will sit at an F1 prompt unless the processor with the highest STEP value is in the primary Slot position.
We have recently upgraded a number of server bios, Management agents and MS SP3 and this has resolved the problem in each case.
We had a similar problem, caused by not all servers having the correct access. NT4, WIN2K + Different Domains.
In the end we configured the Download server as an FTP host and pointed all the clients to pick up from the directory using ftp anonymous login.
SDAT**** File on download server...
Run the Unistall Mcafee.
Then run REGEDT32 and delete all references to
HKLM\Software\Mcafee (v4.03)
and
HKLM\Software\Network Associates\TVD (4.5.+)
Also delete McAfee Dirs from C:\Program files
Then run Install, thinks its a fresh copy apply patch NNTSP1
If this is an Install over...
I have seen this when the NIC is set to AUTO rather then 100/Full etc, when the backups get going the NIC and the Switch seem to start re-negotiating settings and time outs occur.
On the client check the nsr/res/servers file to make sure the NetWorker server name is listed in shortname and fqdn formats.
If you have multiple IP connections on the Networker Server they all have to be given a name and included in the clients Servers file.
Using NWADMIN Select Options, Configure Ports and enter Client name.
Help then explains about defining the Service & Communication ports adn ranges available
We had somthing similar and this was resolved by adding the
following SYSTEM ENVIRONMENT VARIABLE to OS and NSRNOTES.BAT
NOTES_EXECDIRECTORY=C:\NOTES (Directory where nnotes.dll)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.