Update 9.2.01 Improved – Improved the retrieval of Weather TAF and TTF in multi thread and multi station simultaneous download. Added – This release includes decode information for TTF METAR and TAF data on a worldwide scale. Notes 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.
Team Foundation Server 2017 HTTP code 413: Request Entity Too Large 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. The… Read More »Team Foundation Server 2017 HTTP code 413: Request Entity Too Large
Problem 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: Configure the OAuth provider 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. Windows PowerShell $ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings $ClaimsSettings.Enabled = $true Set-CrmSetting -Setting $ClaimsSettings Found on this page: https://msdn.microsoft.com/en-us/library/hh699726.aspx#BKMK_WS2012R2 I was getting in the Power Shell: PS C:\Users\administrator.FSERVER4> $ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings 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… Read More »Get-CrmSetting : The term 'Get-CrmSetting' is not recognized as the name of a cmdlet
Microsoft CRM IFD The SSL certificate does not contain all UPN suffix values that exist in the enterprise – Cannot Login
Cannot Login to a Previously working Microsoft CRM IFD A previously working IFD deployment of CRM 2016 (but could be CRM 2015 or CRM 2013). About 1 year after you set the system up, you start receiving: An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization’s Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support. When researching this error, we suspected what it was, and related to an article we covered here: http://www.interactivewebs.com/blog/index.php/crm-2013/microsoft-crm-2013-or-2015-event-id-1309-adfs-ifd-resolution/ However we never found and EVENT ID 1309 or anything close to that in our logs. The closest error we found (and we are not even certain that it was pointing as a result fo this problem) was the error: EVENT ID 415 The SSL certificate does not contain all UPN suffix values that exist in the enterprise. Users with UPN suffix values not… Read More »Microsoft CRM IFD The SSL certificate does not contain all UPN suffix values that exist in the enterprise – Cannot Login
Outlook Mac Office 365 Sorry, we're having server problems, so we can't add Office 365 SharePoint right now. Please try again later"
Outlook Mac Office 365 Sorry, we’re having server problems, so we can’t add Office 365 SharePoint right now. Please try again later” For no particular reason you end up with an error message: Outlook Mac Office 365 Sorry, we’re having server problems, so we can’t add Office 365 SharePoint right now. Please try again later” This starts to ask you for two or three factor authentication on your email accounts that are based on Office 365 product. My issues started December 2016 To Resolve this error: 1. Make sure you have quitted Outlook and other Office apps. Go to KeyChain Access 2. Search “Exchange” under Login –> All Items and delete everything 3. Search “Office” and delete everything 4. Search “ADAL” and delete everything 5. Launch Outlook 6. You will get the activation prompt. If the account is already added, you will see the password prompt for app and ADAL again. Please do… Read More »Outlook Mac Office 365 Sorry, we're having server problems, so we can't add Office 365 SharePoint right now. Please try again later"
CRM in-line search fails with SQL error After upgrading Microsoft CRM from earlier versions we found that the global search function when enabled failed to return any results, and once the index for the global search had run over a 24-hour period, the in-line search function for any entity would cause a crash and SQL error message to be displayed on page. The problem In our particular instance this CRM environment had been upgraded from much earlier versions of CRM and included an attempt to solve some upgrade issues by dropping indexes. Initially our thoughts were that the dropping of the indexes were responsible for the problems. However it appears retrospectively that was a fragmentation of indexes that cause the issue. I cannot be exactly sure why the maintenance procedure that is run on the SQL Server did not rebuild and reorganise the indexes sufficiently that the global social function.… Read More »Microsoft CRM global search fails causing in-line search SQL error
Changing your password in ZenDesk may affect your Microsoft CRM integration if you are to upgrade or change the password that you utilise in your ZenDesk system for the account that has been set to synchronise data with the Microsoft CRM platform, you will notice that the synchronisation may not function correctly or may only perform a one-way synchronisation. You will remember from the instructions that you likely followed in your initial configuration: http://www.interactivewebs.com/blog/index.php/zendesk/zendesk-to-crm-2015-integration/ that part of these configuration settings is to set up your password and username in the SETTINGS / ZD Personal Settings – area of your Microsoft CRM system. Below is an extract from the vendor’s configuration portal found here Step 2: Setting up new security roles The Zendesk integration introduces two new security roles to Microsoft Dynamics CRM that must be assigned before you can proceed to the next step: Zendesk – Read configuration settings – grants… Read More »ZenDesk to Microsoft CRM integration password change
Mac Mail using Exchange Connection to SmarterMail InteractiveWebs To Set up your mac mail with and Exchange Connection using Mac Mail you will need to follow these instructions carefully. On your Mac, open System Preferences. Click Internet accounts. Click Exchange. Complete the display name, full email address and password fields. Click Sign In. Ensure that you’re email address is et for your User Name, and Type the internal and external URL to read: https://mail.yourdomainname.com/ews/exchange.asmx (Note that after October 2020 we suggest that you use your own domain name in place of the mail.interactivewebs.com) Click Sign In. An account summary screen will display. You can select or unselect any features that you do not wish to sync. Click Done. Click Add Account.
To Hide a DNN Page from the Menu Note: This page will still be available to those who know the URL of that page (if for example you had put the page in a news letter). Select Edit / Page Settings Page Details / Unselect the Include in Menu Option Update Page The Page will no longer appear in the menu system. It can still be hit with the permissions that have previously been set. Alternatively – To Change Permissions on the page to hide and stop access: http://www.interactivewebs.com/blog/index.php/general-tips/dnn-change-permissions-on-a-page-to-stop-users-being-able-to-access-the-page/
To Stop users (Either members or visitors) from being able to access a page on the DNN Site. Select Edit / Page Settings Select the Permissions Tab Uptick the All users View Settings. With no view pages permissions set. No users other than the Default Administrator settings will be able to visit the page. Update Page Note This hides the page from users in the menu too. Alternatively you can just hide the page from the menu, but still allow people how know where the page exists to still access it by following this post:http://www.interactivewebs.com/blog/index.php/general-tips/dnn-hide-a-page-from-the-menu/
Problem How to enable TLS 1.2 on Windows Server 2008 R2? Note: We have an update to this post that has a new and better solution. We now suggest you read: How to Enable TLS 1.2 in Windows Server 2008 or Windows Server 2016 Resolution QuoVadis recommends enabling and using the TLS 1.2 protocol on your server. TLS 1.2 has improvements over previous versions of the TLS and SSL protocol which will improve your level of security. By default, Windows Server 2008 R2 does not have this feature enabled. This KB article will describe the process to enable this. Start the registry editor by clicking on Start and Run. Type in “regedit” into the Run field (without quotations). Highlight Computer at the top of the registry tree. Backup the registry first by clicking on File and then on Export. Select a file location to save the registry file. Note: You will be editing the registry. This could have detrimental effects on… Read More »How to Enable TLS 1.2 on Windows 2008 R2
Microsoft.Crm.CrmException: Database having version 188.8.131.52 is not supported for upgraded Microsoft.Crm.CrmException: Database having version 184.108.40.206 is not supported for upgraded.
When upgrading from CRM 2013 to CRM 2015 you get an error: Microsoft.Crm.CrmException: Database having version 220.127.116.11 is not supported for upgraded. Cause: This is usually because there is already a database that exists with the same ID. You will need to delete that Organisation in CRM deployment manager before upgrading the new organisation from the same name.
CRM 2016 Import Upgrade from CRM 2015 Failure: Timeout expired On attempting to upgrade a Microsoft CRM Dynamics 2015 Database to CRM 2016 (without service pack) you receive a Failure: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. This happens at the System Check stage. There are a bunch of suggestions online from earlier releases of CRM like 4.0 etc suggesting that you may need to change the timeout settings on the settings with some DWord changes in the registry. In this case it is not the cause. Cause Microsoft has again released an initial version of their software with some significant bugs. The biggest of these being that you cannot import your CRM 2015 database to upgrade to CRM 2016 if it has a Full Text Catalogue. Something that is likely if you have been using the improved searching functions of… Read More »CRM 2016 Import Upgrade from CRM 2015 Failure: Timeout expired