Weather gadget not working- Cannot connect to service

Why would I do that, and cause myself trouble?

You are supposed to learn that removing the read-only attribute won't cause any trouble.

On the Feb. 15th, I wrote this in another thread:

"And exactly a Week ago I had to RE-save my config-xml file, and today I had to do the same again, so it seems it'll be a Weekly manouver from now on to RE-save the config.xml"

Then on Feb. 19th, I wrote this in the same msg:

"This morning I simply changed the Date on the config.xml, to 2017, and then set the Attribute READ ONLY on the file, and it's still working ..."

And on Feb. 12th, you wrote on this threa d:

"Don't ask me what this really is about" ,

and you still act like you don't know, and not want to know.

Back then there was something that caused the Weather Gadget to stop working every 3-4 days, but since i changed the Year to 2017 on the config.xml and set the Attribute to Read-Only, I haven't had to touch that file, and the Weather Gadgets (I'm using two at the same time, for two different places) are working just fine.

Stop talking about "something". I and others have made clear that this is a timeout phenomenon and not the mysterious background file manipulations imagined by you. Everybody including you has realized that all timestamp modification has to be donemanually, so what's the point in assuming secret automatisms the file would have to be protected against? On February 19, in an angry move to finally gain control over the darn file, you have arbitrarily decided to take two steps at once, instead of only changing the timestamp and seeing if this alone would work. It just turns out that your second step, making the file read-only, is unnecessary and against the logic of this issue, but you just won't unterstand this and instead rather stick to repeatedly adding an irrelevant recommendation to a relevant one.

This issue does not arise from something going on with the file, but  from nothinggoing on with it. "Nothing going on" poses zero threat, and I've explained this more than once.

So my way works, and my "mantra" stands:

ALL one has to do, is to change the Date = Year, to like 2017, on the config.xml, and then set the config.xml to be Read-Only.

The path in my system are:

C:\Users*Your_Own_Windows_User_Name*\AppData\Local\Microsoft\Windows Live\Services\Cache

And when there, just:

Change the Year on the config.xml to 2017

and then set it as a Read-Only file, and that WILL

make the Weather Gadget work again.

Change the year on the config.xml to

whatever future date you like, and that WILL

make the weather gadget work again.

There is nothing further to do.

@Mitch: Your details on the remaining configW7.xml are really interesting. I'd say until September 21, that gadget should be fine except for the location search issue which has to have another cause, because to this gadget the configW7-deficit simply doesn't exist yet. Also, the search issue has had another time of appearence, as you can see here:

http://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/weather-gadget-not-working-cannot-connect-to/6707d8b4-1a37-4412-a609-5677c9b99a7a?page=34

It is of course true that you'll have to do a workaround only if configW7.xml is missing, but unfortunately in the meantime this has occured on lots of user accounts and has become the default case, sure to be found on a fresh installation and therefore a config.xml not even being newly created there. I also have never said it's not necessary to set the date modified to the future, but Anders won't let go of instructing something unessential surplus with the sole function of making people ask "why"?

Regards, VZ

VZ,

Yes, it seems to be such a simple problem/MS Bug that they could fix, but its hard to get it to the proper address? Maybe even impossible as they are so large! LoL

I submitted a Bug Report to MS today about the problem to msdn.microsoft.com (many sites/urls here), but not sure they are the best place to submit them and get an answer (I was trying to submit it to a Developers Forum that covers gadgets)? I'd like to know the best site and URL for submitting a Problem like this if you know?  If I get a good answer, I'll Post it!

Regards MitchZZ

Why would I do that, and cause myself trouble?

You are supposed to learn that removing the read-only attribute won't cause any trouble.

On the Feb. 15th, I wrote this in another thread:

"And exactly a Week ago I had to RE-save my config-xml file, and today I had to do the same again, so it seems it'll be a Weekly manouver from now on to RE-save the config.xml"

Then on Feb. 19th, I wrote this in the same msg:

"This morning I simply changed the Date on the config.xml, to 2017, and then set the Attribute READ ONLY on the file, and it's still working ..."

And on Feb. 12th, you wrote on this threa d:

"Don't ask me what this really is about" ,

and you still act like you don't know, and not want to know.

Back then there was something that caused the Weather Gadget to stop working every 3-4 days, but since i changed the Year to 2017 on the config.xml and set the Attribute to Read-Only, I haven't had to touch that file, and the Weather Gadgets (I'm using two at the same time, for two different places) are working just fine.

Stop talking about "something". I and others have made clear that this is a timeout phenomenon and not the mysterious background file manipulations imagined by you. Everybody including you has realized that all timestamp modification has to be donemanually, so what's the point in assuming secret automatisms the file would have to be protected against? On February 19, in an angry move to finally gain control over the darn file, you have arbitrarily decided to take two steps at once, instead of only changing the timestamp and seeing if this alone would work. It just turns out that your second step, making the file read-only, is unnecessary and against the logic of this issue, but you just won't unterstand this and instead rather stick to repeatedly adding an irrelevant recommendation to a relevant one.

This issue does not arise from something going on with the file, but  from nothinggoing on with it. "Nothing going on" poses zero threat, and I've explained this more than once.

So my way works, and my "mantra" stands:

ALL one has to do, is to change the Date = Year, to like 2017, on the config.xml, and then set the config.xml to be Read-Only.

The path in my system are:

C:\Users*Your_Own_Windows_User_Name*\AppData\Local\Microsoft\Windows Live\Services\Cache

And when there, just:

Change the Year on the config.xml to 2017

and then set it as a Read-Only file, and that WILL

make the Weather Gadget work again.

Change the year on the config.xml to

whatever future date you like, and that WILL

make the weather gadget work again.

There is nothing further to do.

@Mitch: Your details on the remaining configW7.xml are really interesting. I'd say until September 21, that gadget should be fine except for the location search issue which has to have another cause, because to this gadget the configW7-deficit simply doesn't exist yet. Also, the search issue has had another time of appearence, as you can see here:

http://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/weather-gadget-not-working-cannot-connect-to/6707d8b4-1a37-4412-a609-5677c9b99a7a?page=34

It is of course true that you'll have to do a workaround only if configW7.xml is missing, but unfortunately in the meantime this has occured on lots of user accounts and has become the default case, sure to be found on a fresh installation and therefore a config.xml not even being newly created there. I also have never said it's not necessary to set the date modified to the future, but Anders won't let go of instructing something unessential surplus with the sole function of making people ask "why"?

Regards, VZ

Before you continue getting in my and other people's way with your read-only mantra, remove the attribute from your file for a week, if it's not asking too much, and acknowledge reality.

Why would I do that, and cause myself trouble?

On the Feb. 15th, I wrote this in another thread:

"And exactly a Week ago I had to RE-save my config-xml file, and today I had to do the same again, so it seems it'll be a Weekly manouver from now on to RE-save the config.xml"

Then on Feb. 19th, I wrote this in the same msg:

"This morning I simply changed the Date on the config.xml, to 2017, and then set the Attribute READ ONLY on the file, and it's still working ..."

Back then there was something that caused the Weather Gadget to stop working every 3-4 days, but since i changed the Year to 2017 on the config.xml and set the Attribute to Read-Only, I haven't had to touch that file, and the Weather Gadgets (I'm using two at the same time, for two different places) are working just fine.

So my way works, and my "mantra" stands:

ALL one has to do, is to change the Date = Year, to like 2017, on the config.xml, and then set the config.xml to be Read-Only.

The path in my system are:

C:\Users*Your_Own_Windows_User_Name*\AppData\Local\Microsoft\Windows Live\Services\Cache

And when there, just:

Change the Year on the config.xml to 2017

and then set it as a Read-Only file, and that WILL

make the Weather Gadget work again.

Anders,

If you have the configW7.xml file in your Temp Internet file folder for IE,  you don't need your fix as it continues to work fine, except you now have to search using a zip code to get a new City!?? If your System IE Temp Internet Files does not have this file, then your fix may work or be a good workaround? 

The real problem (that MS needs to fix immediately) is that MS has removed support of the online copy of the configW7.xml file, which I assume would allow you to still search for new City locations using the City name in your search,  as the online file would keep your temp file updated?  Wake up MS and acknowledge this problem/Bug you created and restore the online file immediately so that Win 7 Users have full use of this great Weather Gadget!!!!!!  There is no excuse for removing this support!!!!!