• 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
Christine

Failed remote access ISS Admin Service won't start

4 posts in this topic

Hi All,

Before I do a complete reinstall or throw my WHS off the roof I thought I would throw my situation out to other members and see if anyone has any ideas on how to repair this issue. A week or so ago one of my external hard drives failed. Before the drive failed completely I think it was somehow creating havoc with entire system. The backup service would randomly stop running, I lost remote access, and had file conflicts coming out of my ears. All the while the console was indicating that the drive was healthy. I ran chkdsk /f /r on all the drives and for some reason that is beyond my newbie mind this particular drive failed completely. Because my system is home brew and build with duct tape and gorilla glue, I decided to go with a larger drive 1.37 tb and add a sata card. This all seemed to work fine, but I still can't get remote access to work. The ISS Admin Service will not start and I don't have a clue why. The console is giving me the port forwarding has failed error. Note that is was working fine before the drive failed. I have since manually configured the router to forward ports 800, 443 and 4125. Still no joy. I have a backup of the server on a external drive and I'm wondering if I should try to reinstall from the backup or do a complete reinstall . When I restored from the backup before the drive failed it seemed to cause additional problems, but I was never sure of their origin. I think this has something to do with the ISS Admin Service failing to start, but I'm still kind of a newbie and can't figure this out. Thanks in advance for any help.

Christine

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Well, I would recommend a fresh installation. It's your best bet. as for why the IIS Admin service isn't starting... I've no idea why, and would need log files to figure that out specifically, but my guess is that there may be a corrupted file somewhere.

Without IIS Admin service running, the webserver will not start. If it doesn't start, port forwarding will fail because it checks if the site can be connected to.

Share this post


Link to post
Share on other sites
Well, I would recommend a fresh installation. It's your best bet. as for why the IIS Admin service isn't starting... I've no idea why, and would need log files to figure that out specifically, but my guess is that there may be a corrupted file somewhere.

Without IIS Admin service running, the webserver will not start. If it doesn't start, port forwarding will fail because it checks if the site can be connected to.

Hi Drashna,

That's exactly what I did. Although the system wouldn't let me do a reinstall and I had to do a fresh install. It turns out that not one, but two of my drives where bad. Of course the other failed drive was the system drive. Not much damage was done as I had everything backed up on external drives (twice, just in case). I am looking at the bright side...now I have a nice clean machine again. If there is a lesson to be learned here it is that I was using very old drives and had too many of them. So perhaps is better to use larger drives and fewer of them. For sure not ones that are 7 or 8 years old. It is a miracle they lasted as long as they did.

Thanks again,

Christine

Share this post


Link to post
Share on other sites

Ouch. Yeah, that would cause the IIS Admin service to not start! :)

I have a thing against old drives. They die. End of story. Old parts are even worse. THat and one of the biggest issues with WHS that I have seen is old drives.

As for new drives, I like to wait about six months after initial release of a drive before consider buying new ones though. Seagate's "recent" issue reinforces that fact.

And on the plus side, a nice fresh installation can be very refreshing. (though after about 60, they kinda get annoying :P)

Glad to hear you got everything sorted out though.

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



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