Weather Forecast SharePoint Web Part

http://weather.yahooapis.com

Thus your Sharepoint Server needs permission to access an external URL. Usually it is sufficient to get this permission when the web part DLL is deployed to the GAC but in your case there seems to be some restriction.
What is the trust level in your web.config file ?
It usually is set to “medium” as follows:

<trust level="WSS_Medium" originUrl="" />

Could it be that in your case you have set a trust level of “WSS_Minimum” ?

You should be able to see the "SafeControls" section quite at the top of the file. See below the top of a typical Sharepoint web.config file:

this would be perfect if the location was dynamic based on the user logged into sharepoint. could a current user filter webpart be use to pass a value (the zip code from the user's profile) to your weather webpart?

I guess the Sharepoint user profile does not include a ZIP field by default.
Juerg

Darren, the Yahoo service actually works fine. You also have to supply a location parameter in the URL as follows:

http://weather.yahooapis.com/forecastrss?p=94089

(Weather forecast for Sunnyvale CA)

Darren,
can you check the „defaultProxy“ setting in your web.config file ? By default it looks like:

<system.net>
  <defaultProxy>
    <proxy autoDetect="true" />
  </defaultProxy>
</system.net>

You might have to add your specific proxy information as follows:

<system.net>
   <defaultProxy>
     <proxy usesystemdefault=”false” proxyaddress=”http://xxx:yyyy/” bypassonlocal=”true” />
   </defaultProxy>
</system.net>

where “xxx” is your proxy server IP (ISA) and “yyyy” is the port of the proxy.

Ruben,
the web part is most probably not allowed to access the Yahoo weather service at http://weather.yahooapis.com/
This is most certainly due to your Proxy settings.
Can you check the „defaultProxy“ setting in your web.config file ?
By default it looks like:

<SYSTEM.NET>
<DEFAULTPROXY>
  <PROXY autoDetect="true" />
</DEFAULTPROXY>
</SYSTEM.NET>

You might have to add your specific proxy information as follows:

<SYSTEM.NET>
<DEFAULTPROXY>
  <PROXY bypassonlocal="true" proxyaddress=http://xxx:yyyy/" usesystemdefault="false" />
</DEFAULTPROXY></SYSTEM.NET>

where “xxx” is your proxy server IP (ISA) and “yyyy” is the port of the proxy.

Agent Smith,
 can you change the „trust level” line in your web.config file from
<trust level="WSS_Medium" originUrl="" />
to
<trust level="WSS_Medium" originUrl=".*" />

eg. insert the “.*” characters into the originUrl attribute. This should enable Web Service calls to any destination.
If this does not help, can you also change the “defaultProxy” setting in your web.config as follows:

<defaultProxy useDefaultCredentials="true">
    <proxy usesystemdefault="false" proxyaddress="http://xxx:yyyy" bypassonlocal="true" />
</defaultProxy>

where “xxx” is your proxy server IP (ISA) and “yyyy” is the port of the proxy.

• - temporarily turn off the web part’s “Show Humidity/Wind” option
• - or uncheck the “Wind Speed: use km/h” option (the error occurs when the web part attempts to translate mph into km/h)
• - or re-download the most recent version (we have now fixed this problem)

Andrew,
your Sharepoint web front end server needs to be able to reach out to http://weather.msn.com to get the weather data. Can you check (and if necessary) change the „trust level” line in your Sharepoint application’s web.config file from

<trust level="WSS_Medium" originUrl="" />

to

<trust level="WSS_Medium" originUrl=".*" />

(assuming that you are using the "WSS_Medium" trust level) eg. insert the “.*” characters into the originUrl attribute. This should enable Web Service calls to any destination.

1. your locale ID (as eg. "es-AR" for Spanish/Argentina")
2. the Spanish word for "Wind"
3. the Spanish word for "Humidity"

Matt,
please note that MSN will not recognize all these location codes, so you will need to look up the corresponding MSN location codes by going to
http://local.msn.com/weather.aspx and use the “Find a location” link to look up the location and then looking up the MSN location ID in the browser’s address bar.

Example for Edinburgh, GBR:
http://local.msn.com/worldweather.aspx?q=edinburgh-gbr&eid=9862

The Weather web part also accepts these MSN location ID’s (which you need to prefix with an “!” character).

• Senneville, QC, Canada=!9427188
• St. Constant, Quebec, Canada=CAXX0301
• Pudong, Shanghai, China=!30484
• L'Arbresle, Rhone, Rhone-Alpes, France=!19567
• Erkrath, Germany=!10369
• Köln, Germany=!7600
• Sulzfeld, Germany=!8233167
• Eppingen, Baden-Württemberg, Germany=!8233167
• Calco, Lecco, Italy=!3660
• Edinburgh, Scotland, United Kingdom =!9862

1. No, but you can enter the below CSS into the web part’s „Options“ setting to control the weather symbols size:
   
   css=.AEWeatherIconSmall {width:24px}
   
2. No, but you could try either the “verticalWide” or the “verticalNarrow” web part “Layout” setting.

1. extract the WSP file and place it in the root of the C: drive on the Sharepoint web front end server.
2. then use the following Sharepoint PowerShell cmdlet:
   
   Update-SPSolution –Identity AEWeatherWebpart.wsp –LiteralPath c:\AEWeatherWebpart.wsp –GACDeployment

1. Download the current version from this web page
2. extract the WSP file and place it in the root of the C: drive on the Sharepoint web front end server.
3. then use the following Sharepoint PowerShell cmdlet:
   
   Update-SPSolution –Identity AEWeatherWebpart.wsp –LiteralPath c:\AEWeatherWebpart.wsp –GACDeployment