Comments on: Updating Windows Live Custom Domains Failed http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/ Connecting Your Digital World Fri, 12 Mar 2010 12:54:09 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: boggy4062 http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12212 boggy4062 Thu, 12 Nov 2009 18:29:09 +0000 http://www.wegotserved.com/?p=15193#comment-12212 Oh Terry, you is so right .... :) You are lucky, you doesn't have to learn Ebonics by Oakland school district (California).... B) Oh Terry, you is so right …. :) You are lucky, you doesn't have to learn Ebonics by Oakland school district (California)…. B)

]]> By: Updating Windows Live Custom Domains Failed | We Got Served … | ArtykułyNet http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12207 Updating Windows Live Custom Domains Failed | We Got Served … | ArtykułyNet Thu, 12 Nov 2009 11:59:55 +0000 http://www.wegotserved.com/?p=15193#comment-12207 [...] more here: Updating Windows Live Custom Domains Failed | We Got Served … Kontynuuj czytanie » || Napisał dnia: 10.11.09. || Tagi:custom, Domains, fire-before, [...] [...] more here: Updating Windows Live Custom Domains Failed | We Got Served … Kontynuuj czytanie » || Napisał dnia: 10.11.09. || Tagi:custom, Domains, fire-before, [...]

]]> By: @FalconFour http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12201 @FalconFour Wed, 11 Nov 2009 22:51:42 +0000 http://www.wegotserved.com/?p=15193#comment-12201 I gave up on going to my server console each time WHS decides a computer has a problem and "Ignoring" the issue. My status is always "Critical" now and I just don't even care. :P Hopefully - SERIOUSLY hopefully - the next version of WHS will have options to disable computer-related notifications. I really only want to know when the <i>server itself</i> is having issues. Then I might actually pay attention! I was hoping there was an add-on to correct this, but a quick <a href="http://forum.wegotserved.com/index.php?showtopic=9718" target="_blank">topic</a> said that no such add-on exists (sadly). Hopefully soon... I gave up on going to my server console each time WHS decides a computer has a problem and "Ignoring" the issue. My status is always "Critical" now and I just don't even care. :P

Hopefully – SERIOUSLY hopefully – the next version of WHS will have options to disable computer-related notifications. I really only want to know when the server itself is having issues. Then I might actually pay attention! I was hoping there was an add-on to correct this, but a quick topic said that no such add-on exists (sadly). Hopefully soon…

]]> By: Terry Walsh http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12200 Terry Walsh Wed, 11 Nov 2009 21:37:26 +0000 http://www.wegotserved.com/?p=15193#comment-12200 If it's any consolation, I now read/hear so much US media, my UK English gammar has gone to pot! If it's any consolation, I now read/hear so much US media, my UK English gammar has gone to pot!

]]> By: Chris http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12198 Chris Wed, 11 Nov 2009 20:11:53 +0000 http://www.wegotserved.com/?p=15193#comment-12198 When I try and log into my home server I get this after attempting to log in. I have rebooted the computer I am using and the home server. Server Error in '/Remote' 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> When I try and log into my home server I get this after attempting to log in. I have rebooted the computer I am using and the home server.

Server Error in '/Remote' 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>

]]> By: Jim_Clark http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12197 Jim_Clark Wed, 11 Nov 2009 20:10:08 +0000 http://www.wegotserved.com/?p=15193#comment-12197 Ya know, the more I work with them thar Brits, the more I has began to wright like 'em. ;) There, have a field day with that sentance! BTW, there is a very distinct difference in how each side of the pond deals with "have" and "has". One must realize that as a melting pot, US English has been "influenced" by so many languages, it is amazing that there are not more differences. Ya know, the more I work with them thar Brits, the more I has began to wright like 'em.
;)

There, have a field day with that sentance! BTW, there is a very distinct difference in how each side of the pond deals with "have" and "has".

One must realize that as a melting pot, US English has been "influenced" by so many languages, it is amazing that there are not more differences.

]]> By: Mjordan http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12196 Mjordan Wed, 11 Nov 2009 19:10:27 +0000 http://www.wegotserved.com/?p=15193#comment-12196 Seems to be working again here in Georgia.... Seems to be working again here in Georgia….

]]> By: David Hunter http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12194 David Hunter Wed, 11 Nov 2009 17:52:49 +0000 http://www.wegotserved.com/?p=15193#comment-12194 Yes same here for a few month's as well. Yes same here for a few month's as well.

]]> By: Sean Daniel http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12192 Sean Daniel Wed, 11 Nov 2009 16:13:24 +0000 http://www.wegotserved.com/?p=15193#comment-12192 The DNS issues for this particular case should not take 24 hours. The Time to Live (TTL) on the homeserver.com domain name are very short. I would say about 10 minutes maximum you should be back online. Thanks for your patience. The DNS issues for this particular case should not take 24 hours. The Time to Live (TTL) on the homeserver.com domain name are very short. I would say about 10 minutes maximum you should be back online.

Thanks for your patience.

]]> By: Jim_Clark http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12190 Jim_Clark Wed, 11 Nov 2009 15:10:19 +0000 http://www.wegotserved.com/?p=15193#comment-12190 The "official" word from MS: "Today the Live DNS service had a hiccup that prevented updates for records on the .homeserver.com domain name. Thus if your WAN IP address changed on your router, the home server was unable to update this record, and remote access was not available. This may have been accompanied with an alert from the home server. If your WAN address did not change during the last 24 hours, remote access was unaffected. This issue has been resolved as of 8:16pm Pacific Time." DNS issues take time to filter thru the 'net, usually within 24 hours???? The "official" word from MS:

"Today the Live DNS service had a hiccup that prevented updates for records on the .homeserver.com domain name. Thus if your WAN IP address changed on your router, the home server was unable to update this record, and remote access was not available. This may have been accompanied with an alert from the home server. If your WAN address did not change during the last 24 hours, remote access was unaffected.

This issue has been resolved as of 8:16pm Pacific Time."

DNS issues take time to filter thru the 'net, usually within 24 hours????

]]> By: Christian http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12189 Christian Wed, 11 Nov 2009 15:01:56 +0000 http://www.wegotserved.com/?p=15193#comment-12189 My error got cleared again on 11-Nov-2009 15.55 GMT+1. I've now had 16 warnings and 16 cleared messages. The first warning came 10-Nov-2009 03:04 GMT+1. My error got cleared again on 11-Nov-2009 15.55 GMT+1. I've now had 16 warnings and 16 cleared messages. The first warning came 10-Nov-2009 03:04 GMT+1.

]]> By: Christian http://www.wegotserved.com/2009/11/10/updating-windows-live-custom-domains-failed/comment-page-1/#comment-12187 Christian Wed, 11 Nov 2009 14:46:56 +0000 http://www.wegotserved.com/?p=15193#comment-12187 I'm still getting this error "Windows Home Server was unable to update Windows Live Custom Domains with your current IP address. Your Web site may not be available on the Internet." 11-Nov-2009 15:42 GMT+1. But it has been less error messages today than yesterday. But it's not solved. I'm still getting this error "Windows Home Server was unable to update Windows Live Custom Domains with your current IP address. Your Web site may not be available on the Internet." 11-Nov-2009 15:42 GMT+1. But it has been less error messages today than yesterday. But it's not solved.

]]>