OUR NETWORK:TiVo Community Explore3DTV TechLore MyDigitalEntertainer See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 445199.0
October 14, 2008 10:25 PM

Categories: Patches and Upgrades

Rating (0 votes)
Rate This!

Member Avatar

WHSgary

Member
Joined: 10/14/2008

The HP help desk told me that the reason I was getting invalid voltage indicators was that I was not running the current version.  How can I force and upgrade?

Discussion:    Add a Comment | Comments 1-8 of 8 | Latest Comment

October 15, 2008 9:17 AM

Something is not right there. First, I doubt that the WHS software would be the cause of any HP voltage reading problems. Second, the current WHS versions are 6.0.1800.0 for all except the Drive Extender which (as of today) is at 6.0.1800.8. (You can see these in Settings-->Resources.) If you are not at least at that level, you should be. To update open the "General" section of the settings and click on "Update Now...". (I recommend you have the Windows Update set to "on" to get automatic WHS updates.)

Now, there is HP software in the MSS as well. You can check the version of that by going to the MSS remote desktop and then into My Computer. Go to the HP MediaSmart Server module, select it (single click) and open the "support information" link. The current version is, I believe, 1.3.6.21622. To update this LOG OFF the RDP session and open the console. Select the MediaSmart Server tab and, in the upper left, under the "HP MediaSmart Server Updates" section, click on "check for updates". You will be updated to the current version. (If not, restart the server and try again.) Again, I recommend you configure automatic updates for the HP software as well.

Which brings up the real problem you are having, the voltage readings. I've got to say I have never heard of the software versions, HP or MS WHS, causign problems with the voltage readings. I ass-u-me you have restarted the unit and still see the same errors (if not, please do so). If the updates solve your problem please post back here and let us know. If they do not, please post back here and let us know that, too. And then I would suggest a new thread to address the voltage problem(s). I don't recall seeing many posts about voltage problems but if they continue I would search on "volt" here and on http://www.mediasmartserver.net/forums to see what problems others have been having. I suspect you are due for a swap of your frame under warranty.

...JohnBick

October 15, 2008 7:35 PM

Thanks John, I'll try again to force the update to a current version, I do have auto-update set to "on". The HP helpdesk guy told me the voltages were not dangerously out of tolerance and suppected corruption in the OS files.

Sure appreciate you detailed idea's on helping force the update.

October 21, 2008 8:57 PM

I have not been successfull in getting an upgrade/update to install. I've tried all the suggestions above.

Gary

October 21, 2008 10:19 PM

If you cannot get it to update any other way I would RELOAD the server. You will loose all updates, settings and Add-Ins (which will have to be re-done) but a RELOAD will keep your data intact. Instructions are in the manuals. (DO NOT do the FACTORY RESET as that option WILL destroy all your data.)

Once the Reload is completed let the server sit at least overnight -- longer if you still hear disk activity -- as it takes considerable time to rebuild all the databases from the data drives. Be patient...

...JohnBick

October 23, 2008 8:22 PM

I'll go ahead with the "reload" next week. Thanks for your response JohnBick

February 6, 2009 11:28 AM

any luck with this?

I am also "stuck" on 1.1

Auto update is set to 'on' but it never does any updating (since November 2008)

Clicking on 'check for update' brings up the 'checking....' dialog box whcih never does anything.

Can't I just download the latest patch and apply it manually?

February 7, 2009 11:34 AM

I finally got the update by manually downloading from one of the posts and then manually updating within Remote Desktop. - a little dangerous unless you know windows server, but it worked fine and I never had to do a darn "reload".

February 9, 2009 11:55 AM

thanks - did it that way and that seemed to unlock my issue. I had an older update that I could then use to "check for updates" to bring me fully up to the new version.

All seems to be working as expected now.

Discussion:    Add a Comment | Back to Top | Comments 1-8 of 8 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

close this window
close this window