Network Attached Storage (NAS) - Enterprise
1821541 Members
2343 Online
109633 Solutions
New Discussion юеВ

Error after updating SP2

 

Error after updating SP2

Dear Sir/Madam

We have a problem about the OS, my process is below:
1. Our File server (HP Proliant with Windows Storage Server) usually restart and Windows requires us update Service Pack
2. So we reinstall OS and update Service Pack:
- Install HP release 5.6
- Update SP1
- then update SP2

But we can not create "new Directory quota", File server now anounce error: "Invalid procedure call or argument5. Could you help us fix this problem. Thank you.

Sincerely,
TonyTran
2 REPLIES 2
Michael Richter
Trusted Contributor

Re: Error after updating SP2

Tony,

i hope u didn't install SP1 and/or SP2 direct from M$ !? If it is so, u might run into several troubles.

At least u have to install the Service Release 6.2 which provides Win2k3 R2 Sp1 ( before u have to upgrade to Service Release 5.6 )

SP2 for HP Storage Appliance can be downloaded from HP.com


Microsoft Windows Server 2003 Service Pack 2 (KB914961)
version 1.0.0.0 (16 Mar 07)
http://h18023.www1.hp.com/support/files/server/us/download/26767.html

rg, mike
Keith_112
Valued Contributor

Re: Error after updating SP2

Hi Tony,
Let me clarify the rebuild process from your step 2. By the way, it would help to know what ProLiant Storage Server product you have. I assume you are using the Quick Restore DVD to restore your system to its factory default state. Next, instead of running SR 5.6, if your product is not using Windows Storage Server 2003 R2, then run the HP ProLiant Storage Server Installer Kit for W2K3 SP2.

http://h18023.www1.hp.com/support/files/server/us/download/26769.html
(Note: This product has recently been released.)

The SP2 Installer Kit prepares your storage server to install W2K3 SP2. The kit will also assit you to install W2K3 SP2, but you will need to get SP2 separately from Microsoft. W2K3 SP2 is a cumulative release, meaning you do not need to install SP1 followed by SP2. No guarantees yet this will solve the directory quota issue, but it gets you to a good start point to address the issue in case it still occurs.