Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Suddenly can not access to Homeserver via Internet RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The access was fine.  I haven't tried it for a couple of week.  A few days ago, I tried to access to the Homeserver via Internet, I got script error.  I thought it was a temporarily situation that server was not available.  However, I tried a few times today, the same error occurred.  Can someone shed some lights for me?  I haven't really changed the network or router setting; other than removing one PC from the Homeserver...The error message is:

     

    Server Error in '/Home' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

    Monday, May 19, 2008 11:26 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you installed anything on your home server recently? WebGuide? Web Folders? Anything else with a web interface?
    Tuesday, May 20, 2008 3:29 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Regarding updates: you can run Windows Update manually on Windows Home Server. Best practice is to allow the server to download and install critical updates itself, and only to manually install something other than a high priority update if you have a specific need for it. That means, for the most part, that you should never install any optional update including TS client 6.1, .Net Framework 3.0 (unless, as I said, you have a sepecific need for it), etc.
    Tuesday, May 20, 2008 12:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Also, related to .Net 3 and Windows Foundation Class, is this Knowledgebase article for Server 2003. It might give you a few pointers.

     

     

    Colin

    Thursday, May 29, 2008 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    After a help from my friend, who has a program can re-size the logical C drive, I could remove the .NET Framework 3.0 using the add/remove tool and I can access via web, can do remote access and also access the Home server console again.  Thank you for everyone's help.  I'll mark the issue being resolved.

     

    Thursday, June 5, 2008 3:50 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you installed anything on your home server recently? WebGuide? Web Folders? Anything else with a web interface?
    Tuesday, May 20, 2008 3:29 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I don't think so, but I'll double check tomorrow when I have access to the homeserver (and have a bit time).  I had problem a couple of weeks ago in connecting Homeserver to the LAN (hence to the Internet)...I opened IE and Firefox several times in the process to validate the Internet connection was OK...That was all I can remember thing I did related to IE...

     

    Thx!  JW

     

    Tuesday, May 20, 2008 6:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had exactly same errors. On googling about I did not found any really helpful informations, except on one Google-Link, I didn't remember exactly, from a forum or something like that, in which they assume as I understand, that this errors was a result when you do manually microsoft-/windows-update and take really ALL of the offered user specific updates, even not only the rescue updates. I did play back an Acronis-Image from my WHS, which I made direct after the installation few months ago - and all works fine!

     

    After this, for to verify and to isolate a little more this errors, I played back this Acronis-Image in an Virtual PC 2008-VM, so that I can often do snapshooting, undos etc.

     

    I can reproduce the error. When I do nothing more as to start my WHS-VM with all default settings, no add-ins or something like that, all works fine again; then I do a full manual user-specific windows update, at first there will be around 40-50 updates for server 2003 and a few for WHS. Reboot, launch windows update again, and anew there were found a few updates, I believe, as I remembered, mostly in association with the .Net-Frameworks 2.0 and 3.0 and something like that, and I did these windows updatings after every reboot as often as there were offered updates.

     

    The only offered updates, which I do not use, was the client-side extensions for server 2003 (in relation to the blowned-up GPOs from server 2008) and the updated RDP-client for server 2003.

     

    And voilà: there were this error, as described above; additionally you found hundreds of error-entries in event-log about heavily .Net Framework 2.0 crashes, about app-pool-errors in the WHS-IIS and even more ...on every try to connect to the webservice over http or https to WHS.

     

    So when I had much, much, much time ...somewhere in the future ;-)) ...I try to isolate the reason for this errors a bit more precisely... because you had to install ONE update, reboot, try the remote-connect website of WHS, next update ...and so on!

     

    cheers

    WoW

     

    Tuesday, May 20, 2008 9:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Regarding updates: you can run Windows Update manually on Windows Home Server. Best practice is to allow the server to download and install critical updates itself, and only to manually install something other than a high priority update if you have a specific need for it. That means, for the most part, that you should never install any optional update including TS client 6.1, .Net Framework 3.0 (unless, as I said, you have a sepecific need for it), etc.
    Tuesday, May 20, 2008 12:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Ken and WowlsNow...I'll check the updates tonight.  I believe I manually downloaded all updates, including optionals...I'll report back whether this is the cause...

     

    Thx!  JW

     

    Tuesday, May 20, 2008 10:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Surely if this is the case (where manual downloads can cause issues) then they should not have been included as such in the product but placed somewhere else with a warning.

     

    I have… having manually downloaded .NET 3 no access at all to my own intranet having switched of the server last night and switched it back on again tonight.

     

    Wednesday, May 21, 2008 12:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Since the only management interface to Windows Home Server is designed to be the Console, there was no need to remove access to optional updates. All the Console will let you check for and install is high priority updates. Many enthusiasts are more accustomed to using traditional PC and server management tools, and a lot of the issues that they have are a result of doing so inappropriately. The tools are there because Microsoft wanted to provide full support for custom development on Windows Home Server, and because they're part of Windows Server 2003, but you aren't supposed to be using them on a daily basis.
    Wednesday, May 21, 2008 3:04 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have tried 4 times to remote .NET framework 3.0 through add/remove programs in the control panel.  However, it failed 4 times.  Don't know why.  Any suggestions how to remove it?

    Wednesday, May 21, 2008 4:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I found an error log and it says the "installation failed because it can't find Windows Communication Foundation"...I do not have any idea what is that and when I installed it and why it is needed to remove .NET Framework 3.0...If anyone can help (the goal is to remove .Net Framework 3.0), it will be highly appreciated.

    Wednesday, May 21, 2008 4:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    On my test machine as a VM in Virtual PC 2007, for to isolate the main reasons of these errors, I did the following:

     

    - the restored image of WHS which I made direct after first full functional install became nearly all at this time offered updates including the optional ones via MICROSOFT Update (not via Windows Update, cause I want to know, if eventually Microsoft Update shows more or other updates as Windows Update - which I think, was not); including .Net Framework 1.x, 2.0-Service Packs. -patches etc.; excluding only the initial full .Net Framework 3.0, newest RDP client, GPO CSEs, IE7 and Silverlight.

     

    - after reboot: all seemed to be work fine

     

    - took IE7 as an optional Microsoft Update

     

    - after reboot: all seemed to be work fine

     

    - took again all offered updates including the optional ones for IE7 etc; .Net Framwork 3.0, RDP client etc. (look above) was still excluded updates

     

    - after reboot: all seemed to be work fine

     

    - take the first time full .Net Framwork 3.0 via Microsoft Update

     

    - after reboot: all seemed to be work fine

     

    - take then all the offered updates for .Net Framwork 3.0 and, surprise, surprise, suddenly there were again offered updates for .Net Framwork 2.0, especially the language pack for .Net Framwork 2.0-SP1!! (WHS, .Net Frameworks etc. are german releases)??

     

    - after reboot: there were 2 times this well known errors like in the very first post here above

     

    - after a new reboot, there were sometimes these remote connect errors ...and sometimes not!

     

    - as I saw, that there was an error with both offered language packs as Microsoft Update tries to install it, I do first try to install manually the language pack for .Net Framwork 3.0 ...and the installer gui said, that at first there must be installed the .Net Framwork 2.0 language pack (which was already installed I think in step 3 of all updates steps via microsoft update!); I then tried the manual installation of the .Net Framwork 2.0 language pack - this installer gui said, that there was already installed a .Net Framwork 2.0 language pack... so i uninstalled .Net Framwork 2.0 language pack via the "add/remove programs"-area in control panel, did again install manual the .Net Framwork 2.0 language pack, rebooted, tried to install manually the .Net Framwork 3.0 language pack, which ended successfully(!!) this time...

     

     - after reboot: all worked fine, I then tried again Microsoft Update which found then no new updates, excluding, the known RDP client, GPO CSEs, Silverlight etc.

     

    - today, I did the whole yesterdays evening/night, I start again the WHS-VM, remote connect etc. worked already fine and Microsoft Update and, after do the well known sc stop wuauserv, delete complete "%windir%\SoftwareDistribution", sc start wuauserv, I switched back to Windows Update, both updating strategies, Microsoft and Windows Update found no new updates except the known RDP client update etc.

     

    - after reboot: all seems to be work fine...

     

    A word to the posts about "could it be a great failure to accept optional updates via Windows or Microsoft Update in WHS!?":

    There is the build in HFNetChk in each expanded update.exe in every update, and many, many more strategies for to let know the user, which starts the manual Microsoft / Windows Update, if a offered update is to be offered or not, is to be right or not, could be resolve some of the known persistent WHS bugs or could even make new ones!

     

    We all know, especially in the described .Net Framwork problems, for example in a few month  Microsoft said, .Net Framework 3.0, 3.5 is a MUST in WHS for this and this Service Pack, Power Pack, Patch, Hotfix, Add-In and, and, and...

     

    We all could good imagine upcoming update "messages" like "update failed, because .Net Framework 3.5 was not found!" etc. pp...

     

    When there were offered optional updates especially for a small single software like WHS, it could be really not the very best to take them all, but when they were used, then they should tested, approved etc. Otherwise strike them from the WHS update table! It should be very easy (see HFNetChk procedures etc.).

     

    And why do so many WHS users search and look after updates, WHS hotfixes etc.!? Because it's in some circumstances (common circumstances!), in too many areas still a too buggy product, especially for a system, which could be so often "the last rescue" for to hold important data integer, for backups etc. A product from the disaster recovery, backup area must have a 150% quality!! At the moment, WHS is this not! And that's, in my opinion, the need for so many WHS users, to search after each possibility, that their WHS becomes finally stable and for all more trusted, because there are my so important data, backups and so on. If it would be a "normal" (and brand new!) operating system for example, we all could and would be more tolerant! But iIn disaster recovery spheres we all could not allow even small failures, bugs etc.

     

    Cheers

    WowIsNow

    Wednesday, May 21, 2008 8:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There are two programs making impact to the error - .NET Framework 3.0 and MSXML...I can't remove either one of them using add/remove utility.  Is there a way to restore to the previous known good state?  I can't find restore in WHS...Sorry, I'm not familiar with WHS...

    Thursday, May 22, 2008 5:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    wowisnow: I said this before, but there is no need to install any update listed on Microsoft Update as optional or low priority. If Windows Home Server needs an update to a component for proper operation, that update will be marked as high priority and downloaded automatically. Optional hot fixes are for components that you won't use, because they aren't exposed by Windows Home Server to the end user or used internally by the product.

    If you install third party software which relies on .Net Framework 3.0 (2.0 is built in to Windows Home Server and is all that WHS itself needs) then you're responsible for the installation. High priority updates for that version of the framework will then download automatically as well.
    Thursday, May 22, 2008 12:06 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I tried many time to remove .NET Framework 3.0 using add/remove program in the control, but failed.  The tool just can't remove the program.  Is there other way to do it without re-install WHS...

    Friday, May 23, 2008 3:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You might try Aaron Stebner's cleanup utility at http://blogs.msdn.com/astebner/archive/2005/04/08/406671.aspx.

    Friday, May 23, 2008 7:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I downloaded the zip file and tried it a few times in the last couple of days.  Unfortunately, it did not help the situation and I still can't remove the .Net Framework 3.0 and the web access is still blocked by the same script error...

     

    Any other hints???

     

    Thursday, May 29, 2008 3:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Also, related to .Net 3 and Windows Foundation Class, is this Knowledgebase article for Server 2003. It might give you a few pointers.

     

     

    Colin

    Thursday, May 29, 2008 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you, ColinWH.  The link is helpful.  I applied the tool, but failed to have it running due to no space left at C drive.  I believe that I made a mistake and only allocated 20G for C drive for system files.  Some errors happened recently might be related to the space issue in C drive.

     

    I have plenty of D drive (logical drive) and others.  I wonder whether I can dynamically allocate some space from D drive to C?  I checked the KD, but no luck in finding any article to help the situation.  If anyone knows, please help; otherwise I may face a re-allocate the HD and re-install of WHS...

     

    It will be helpful even if I can set up so the temp files will use the D drive, and so as other system files...If there are articles, please point me...I'll see whether by utilizing other logical drive, I can get by and solve current problem...

     

    Friday, May 30, 2008 8:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    After a help from my friend, who has a program can re-size the logical C drive, I could remove the .NET Framework 3.0 using the add/remove tool and I can access via web, can do remote access and also access the Home server console again.  Thank you for everyone's help.  I'll mark the issue being resolved.

     

    Thursday, June 5, 2008 3:50 AM