– Improved the retrieval of Weather TAF and TTF in multi thread and multi station simultaneous download.
– This release includes decode information for TTF METAR and TAF data on a worldwide scale.
As it turns out, the decoding of weather world wide is rather complex. It is surprising just how many countries have their own format and data sets. Russia with Runway snow and braking information, temperate in different units, QNH, auto machine forecasts to name a few. We hop that any inaccuracies are reported via the feedback within the app, and screen shots.
While working with a new out of the box TFS 2017, the following error was given when uploading files that were 11 MEG. Not particularly big, but hay this is Microsoft. I say this having wasted a lot of time trying to get the RTM version of TFS 2017 to work, only to find out that web site login is broken out of the box, and SP1 fixed my issues. (Back to the Balmer days!).
Anyway the configuration we are using that would appear to make a difference here is that we took on the Microsoft suggestion at setup to use HTPS and SSL. So using the self signing certificates forcing the SSL connection, we find that the out of the box setup for Team Foundation Server 2017 with SP1 installed has this error on large file upload.
While trying to run the OAuth provider setup in Microsoft Dynamics CRM, to configure among other things the Post-instillation setup to allow connectivity by devices and applications. I was banging my head on a problem following the instructions:
Follow these steps to configure the OAuth provider in Microsoft Dynamics 365.
Log on to the Microsoft Dynamics 365 server as an administrator.
In a Windows PowerShell console window, run the following script.
$ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings
$ClaimsSettings.Enabled = $true
Set-CrmSetting -Setting $ClaimsSettings
Get-CrmSetting : The term ‘Get-CrmSetting’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At line:1 char:19+ $ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings+ ~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-CrmSetting:String) , CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
Driving me nuts!
Turns out from these instructions found here: https://msdn.microsoft.com/en-us/library/dn531010.aspx
That an additional step is required:
To configure the Dynamics 365 server to enable federated claims, follow these steps.
Log on as administrator on the Dynamics 365 server that hosts the deployment service role and open a Windows PowerShell command window.
Add the Dynamics 365Windows PowerShell snap-in (Microsoft.Crm.PowerShell.dll). More information: TechNet: Administer the deployment using Windows PowerShell
Enter the following Windows PowerShell commands.
Now it works!