• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
Sign in to follow this  
Followers 0
rudolfo2

After Update It Stopped Working

16 posts in this topic

Before yesterday I've upgraded to latest version,the settings were taken from old install but nothing happened.When it's time to suspend just stays on.Today I've manually suspend the server, I hope it will wake up at programmed time,if not I'll be back.Otherwise it's a great piece of software.Regards to all.

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Before yesterday I've upgraded to latest version,the settings were taken from old install but nothing happened.When it's time to suspend just stays on.Today I've manually suspend the server, I hope it will wake up at programmed time,if not I'll be back.Otherwise it's a great piece of software.Regards to all.

everything work's OK now.

Share this post


Link to post
Share on other sites

And what have you done to resolve it?

Share this post


Link to post
Share on other sites

And what have you done to resolve it?

I was happy to soon;after manually put to sleep the server did woke up at programmed time but it's not gone to suspend as it should.Now it's running, but it shouldn't.

Share this post


Link to post
Share on other sites

From what version have you upgraded? What settings are you using?

Please use Remote Desktop to connect to your server and zip all file found in C:\Documents and Settings\All Users\Application Data\LightsOut.

Send the archive by PM.

Share this post


Link to post
Share on other sites

From what version have you upgraded? What settings are you using?

Please use Remote Desktop to connect to your server and zip all file found in C:\Documents and Settings\All Users\Application Data\LightsOut.

Send the archive by PM.

You're asking too much from me, I have created zip but have no idea how to get it from server to my PC.

Share this post


Link to post
Share on other sites

You can copy the zip file into a share like \\Server\Software on the server.

Then open the same share on your PC and attach the zip file to a private message (PM).

Share this post


Link to post
Share on other sites

Thanks for the logs. Can you please tell me what's your problem?

From the logs I can see that you have enabled WHS client monitoring. The client RUDI-PC was always active the last days. You set up a forced calendar action which suspends the server. That's all working.

Share this post


Link to post
Share on other sites

Thanks for the logs. Can you please tell me what's your problem?

From the logs I can see that you have enabled WHS client monitoring. The client RUDI-PC was always active the last days. You set up a forced calendar action which suspends the server. That's all working.

The problem I have is that only resume is working but not suspend.Tonight I've deleted calendar and set up new one and I'll see if it works today.

Share this post


Link to post
Share on other sites
The problem I have is that only resume is working but not suspend.

Are you sure? The log file says:

2010-02-07 00:00:02:015 [ 23] DEBUG Is suspend supported : True

2010-02-07 00:00:02:015 [ 23] DEBUG Is hibernation supported : False

Suspend is working. Have you enabled hibernation under power options?

Please see here for for more information: http://www.axonet.de/whs/webhelp/en/00034.htm

Share this post


Link to post
Share on other sites

Are you sure? The log file says:

2010-02-07 00:00:02:015 [ 23] DEBUG Is suspend supported : True

2010-02-07 00:00:02:015 [ 23] DEBUG Is hibernation supported : False

Suspend is working. Have you enabled hibernation under power options?

Please see here for for more information: http://www.axonet.de/whs/webhelp/en/00034.htm

It will not suspend anymore.The settings are the same as in previous version,it make no sense.Will try hibernation today.

Share this post


Link to post
Share on other sites
It will not suspend anymore.

I don't understand that sentence. From the log file I can see clearly that suspend is supported and working.

Version 1.0 includes a check for supported operations and notifies the users when standby or hibernation are not supported.

In version 0.8.x you've been able to select suspend although it was not internally working.

Please see here for troubleshooting suspend/hibernation: http://www.axonet.de/whs/webhelp/en/00034.htm

The second difference between 0.8 and 1.0 is handling of calendar actions: http://www.axonet.de/whs/webhelp/en/00021.htm

Share this post


Link to post
Share on other sites

I don't understand that sentence. From the log file I can see clearly that suspend is supported and working.

Version 1.0 includes a check for supported operations and notifies the users when standby or hibernation are not supported.

In version 0.8.x you've been able to select suspend although it was not internally working.

Please see here for troubleshooting suspend/hibernation: http://www.axonet.de/whs/webhelp/en/00034.htm

The second difference between 0.8 and 1.0 is handling of calendar actions: http://www.axonet.de/whs/webhelp/en/00021.htm

My first install was one version before 1.01.1038 and was working fine with the same settings which I'm using now.Is it possible that uninstall isn't 100 %;because install of the latest version picked up settings from old install. Maybe the registry should be cleaned after uninstall or something else is screwing

the proper running.Regards.

I have disabled PC monitoring and it's working now.Regards.

Share this post


Link to post
Share on other sites
Is it possible that uninstall isn't 100 %;because install of the latest version picked up settings from old install

That's by design. You should not loose your settings when you update to a newer version.

Share this post


Link to post
Share on other sites

here is the log of my server mine not shutting down. I'm sure this will look odd, because I was playing with it trying to get it to work all morning. I kept trying to schedule a Forced Hibernate.

LightsOut.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I am running WSE2012 R2 and I only ever see red, yellow or green. I have never seen blue even when backing up. I can't explain what could be happening here, but maybe some feedback from other users may help us pin it down. What OS are your client PC's? Mine are all Win 10. Not sure if that may have a bearing.   
    • I made the leap from WHSv1 to WSE2012R2.  I like the new system but one thing seems to be missing.  In WHS v1, the tray icon would change colors to indicate various things blue - backing up now green - everything is healthy yellow - warnings detected (e.g. haven't backed up in a while) red - critical issues (e.g. recent backup failed) In WSE 2012 R2, however, I only get the blue and green indicators, even when there are critical errors on my home network.  For example, a server hard drive had failed for several weeks, but the connector icon in my system tray remained green.  I only discovered the issue when I happened to login to the dashboard for something else. Does anyone know if this feature has been removed in the latest WSE versions?  Or have I just mis-configured something?
    • I am building a new home server: I really want to use StableBit DrivePool and Scanner - am used to them and like the relative ease of use. Hardware = PC running Windows 7 Pro has SSD for OS and 5 additional 2TB HDDs + SansDigital Towerraid (model TR5M6G) connected by eSATA controller (pCie) with 5 2TB HDDs of varying age (2 brand new WD Red and the remaining 3 a combo of Hiatachi and Seagate of varying age - all test out fine for now). Towerraid is currently configured as JBOD, so I can't really see individual drives, and neither does StableBit drive pool - so I get a pool consisting 5 1.82 TB drives (the ones on the PC) and 1 giant 9.1TB drive. I have about 10 TB of data ready to go into this new build.  Will be adding more over time.  Not sure when but certain I'll have HDDs go bad on me, of course. My question(s): 1)  Is there a RAID configuration that will let StableBit do its thing watching individual drives and letting me identify sick drives that need to be removed/replaced?                           2)  If I decide to give up the RAID and just let DrivePool handle duplication, how do I configure the SansDig?                           3)  Am I just getting it all wrong from the get-go? Would appreciate any advice - thanks   
    • I have almost 10 TB in the storage pool so I was not surprised when my first server backup took a very long time (22 hrs.).  Lately the incremental server backups have been fast (15 - 18 min.)  Two days ago the server apparently initiated a full backup that failed twice but completed successfully this morning after about 23 hours.  An hour later the regular daily backup is back to a normal incremental backup times (18 min.) So why did the previous backup take so long, as long as a full backup would take? Does the server occasionally make a fresh start with a full backup to reduce the time a full incremental recovery takes?  (fewer increments, less processing time) I don't see a setting in the server backup options for specifying a number of increments between full backups, for example.    
    • I just posted a similar question elsewhere.  By Shadow Copies are you referring to the Windows 10 File History backups that periodically use shadow copy to backup open files? I too discovered that a huge amount of backup space was consumed by File History backups, no doubt because I was moving some large Blu-Ray files around.  That I fixed by moving the temporary and final file folders to the server, where they are backed up as part of the daily server backup.  That too, of course, uses Shadow Copies but that is another story. Has anyone done the math?  What is the equivalence .. or lack thereof ... between the traditional WS2012r2 (WHS v1 et al.) daily incremental backup :: and a Win7 System Image backup + File History backups? Restore time comparison? Which do you feel is best?
  • Popular Contributors