locked
Cannot access WHS RRS feed

  • Question

  • Some days ago I had a power outage, which resulted in my Fujitsu Siemens SCALEO Home Server went in to a never endig reboot loop. No luck fixing it with the recovery CD, but after removing the battery from the home server motherboard and thus resetting the bios, I was able to boot it up. But appearently something has happended to the home server operating system, because the connector icon on the three clients I´ve got has all been grayed out. I tried to reinstall the WHS connector on one of the clients, and got as far as typing the password, but it is refused "wrong password" eaven though I have tried sevral times and are 100% certain it is correct. I also get refused on standard network connection to the servers shares. The message notifies me that I do not have access... The "funny" thing is that I can still connect to the server through the console and through Remote Desktop (using the Administrator account). I´m guessing some of the user account settings has gone bad from the crash, when I tried to recover or by removing the MB battery, but I have no clue on how to fix it.
    Is there someting I can do fraom Remote desktop or the console to rebuild the user access, or do I have to reinstall the operating system?
    In that case, does my curren datapool/shared files and folders stay intact? I got my entire film, music and photos collection on it and are anxious abut loosing it.
    BTW I run win7 x64 on my clients and PP3 RC on the home server.
    Friday, November 13, 2009 1:04 PM

Answers

  • Thanks for the help, Olaf.
    I actually managed to solve it :D. As I wrote, the server vent into a continually reboot-loop after the power outage. I first tried to restore it throught the SCALEO Home Server restore-mode and WHS restore software. No dice. So I pulled the BIOS battery to reset the system. This made the server boot again, but at this point I was not able to access it´s shared folders and the Home Server Connector-backup function was not functioning on the clients. But it could be reached through Remote Desktop. What turned out to be the cause - and thereby the solution, was the fact that the bios-clock was reset as a result of pulling the battery. By resetting the date and time I was able to get all the connection right again. YIHAA. My precious files are safe!
    • Proposed as answer by kariya21Moderator Friday, November 13, 2009 7:35 PM
    • Marked as answer by WITno Sunday, November 15, 2009 12:45 PM
    Friday, November 13, 2009 6:21 PM

All replies

  • A power outage can have several effects on the file structure of disks, so in worst case the data is also hit.
    A damaged Backup database may cause WHS components to crash. So deleting the backup database might be an option (depends from what you find in the event log).
    Can you still connect via Remote Desktop?
    If so, check the event log of the server for error messages and share them with us.
    Also follow the FAQ How to check all the drives in your server for errors.

    You have two methods of server reinstall (uninstall the Connector software on the 32 bit client, from which you start setup) - one is factory reset, which takes away all data, one is server recovery, which should keep your data intact, if all goes well. If you have no external backup, I would recommend to backup the data before starting the server recovery, as outlined in the FAQ How to recover data after server failure.

    Good luck
    Olaf
    Friday, November 13, 2009 2:39 PM
    Moderator
  • Thanks for the help, Olaf.
    I actually managed to solve it :D. As I wrote, the server vent into a continually reboot-loop after the power outage. I first tried to restore it throught the SCALEO Home Server restore-mode and WHS restore software. No dice. So I pulled the BIOS battery to reset the system. This made the server boot again, but at this point I was not able to access it´s shared folders and the Home Server Connector-backup function was not functioning on the clients. But it could be reached through Remote Desktop. What turned out to be the cause - and thereby the solution, was the fact that the bios-clock was reset as a result of pulling the battery. By resetting the date and time I was able to get all the connection right again. YIHAA. My precious files are safe!
    • Proposed as answer by kariya21Moderator Friday, November 13, 2009 7:35 PM
    • Marked as answer by WITno Sunday, November 15, 2009 12:45 PM
    Friday, November 13, 2009 6:21 PM
  • You are my friend!

    Found your old post and saw the similarities, although I was certain that I had reentered time/date. Which I had, but in the european sequence of day and month! (language - english, ha!)

    So looking into BIOS I see that it was all wrong. YIAA to you too. But why this has the effect of locking you out from the server only by refusing user/password (I could access folders on other PC's) could be an interesting lecture.

    Monday, June 21, 2010 6:46 PM
  • I think I got the same thing. When I got back from a trip I could not connect to server. Noticed it rebooted over and over and powerbutton was flashing. Tried recovery but it could not reach the server.

    How long did you leave the batery out? Did you do anything else? How did you enter the bios to change the time settings afterwards?

    Tuesday, July 6, 2010 8:33 PM
  • I don't know if there is a universal time for having the battey out, but for my ASUS P5k it is 10 secs and it has the effect of resetting the RTC. For setting the time that may also differ for different MB brands. Look in your MB documentation. My problem was that my BIOS expects MMDDYY, whereas in my part of the world the implied format is YYMMDD.
    Thursday, July 8, 2010 11:26 AM
  • For people having Brownouts, Blackouts, Over voltage problems your best friend would be a Battery Backup device AKA (UPS) Uninterruptible Power Supply. There is also a WHS addin Grid Junction which can be found here.

    http://www.kentdome.com/gridjunction

    j
    Thursday, July 8, 2010 5:13 PM