Skip to content

Blog

Website Developer Sydney

How Install Disk Cleanup Tools Windows 2012 or Windows 2016

Install Disk Cleanup Tools Windows 2012 or Windows 2016 Server. Installing the function to clean your disk, requires that you install the Desktop Experience module from the Windows Feature list.  1. Open a PowerShell with Administrator rights. 2. Exercute: Import-Module ServerManager Install-WindowsFeature Desktop-Experience That’s it. A Reboot of the Computer is required.

Exchange Server MAPI Speed

How to Fix Outlook Slow and Unresponsive with MAPI over HTTP to Exchange 2016

Outlook Slow and Unresponsive wiht MAPI over HTTP to Exchange 2016 Server In our case the versions in question were found to be: Outlook 2013 connecting to Exchange 2016 with MAPI over HTTP enabled. Reported Problems The user reported that outlook was slow to open email, and unresponsive with searching in outlook. The CTRL right click on the Outlook connection icon (bottom right) showed the connection was made with HTTP The Problem It is reported that MAPI over HTTP which is a newer connection method of laterExchange servers and potential better and more reliable for devices connecting has some unreliabilities in some instances with earlier version of Outlook. Our testing shows that later outlook versions and the Mac versions of outlook have no troubles at all. The Solution IN Exchange 2016 it is possible to disable MAPI for a users mailbox. The issue this may have is that they could… Read More »How to Fix Outlook Slow and Unresponsive with MAPI over HTTP to Exchange 2016

Windows PowerShell Module you receive NotSpecified: (:) [Import-Module], FileLoadException

Windows PowerShell Module you receive NotSpecified: (:) [Import-Module], FileLoadException This is a typical error for Modules that have been downloaded from the internet and are not given permission to run on the computer. The solution Really Easy.  Open PowerShell Navigate to the directory in the error message that contains the Module you intend to run. Running a command like: cd C:\Users\administrator\Documents\WindowsPowerShell\Modules\ACMESharp\ Then Run the Command:  Get-ChildItem . | Unblock-File This will set the module files to be able to be used by PowerShell That’s it. Now the module should run fine.

Team Foundation Server 2017 HTTP code 413: Request Entity Too Large

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

Website Developer Sydney

Get-CrmSetting : The term 'Get-CrmSetting' is not recognized as the name of a cmdlet

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"

Microsoft CRM global search fails causing in-line search SQL error

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

Website Developer Sydney

InteractiveWebs Email (smartermail) With Mac Mail Exchange Connection

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.

Microsoft.Crm.CrmException: Database having version 7.0.1.129 is not supported for upgraded Microsoft.Crm.CrmException: Database having version 7.0.1.129 is not supported for upgraded.

When upgrading from CRM 2013 to CRM 2015 you get an error: Microsoft.Crm.CrmException: Database having version 7.0.1.129 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

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

Microsoft CRM 2016 on-PREMISE

How to Set Up Microsoft CRM 2016 IFD on Windows 2012 R2 Server

How to Set Up Microsoft CRM 2016 IFD on Windows 2012 R2 Server We already have a popular post for the configuration of IFD setup with CRM 2015, CRM 2013, CRM 2011. Now we are updating this post to support CRM 2016. Microsoft have a compatibility listing for CRM 2016 here: https://support.microsoft.com/en-us/kb/3124955 The Development Setup  Once again we are running this configuration as a test environment for development. As such we will be running, we are running the server on a Hyper V server. A single VM machine, that is running a fully patched version of: Windows 2012 R2 SP2 64 Bit – (MSDN File: en_windows_server_2012_r2_x64_dvd_2707946)  SQL 2014 R2 64 Bit – SQL Server 2014 Standard Edition x64 – (MSDN File: en_sql_server_2014_standard_edition_x64_dvd_3932034) – Patched to SP2 Microsoft Dynamics CRM Server 2016 – en_microsoft_dynamics_crm_server_2016_x86_x64_dvd_7171743 NOTE: The Domain we have used for setup with this dev server is: iwebscrm16.com You can substitute your domain in place throughout… Read More »How to Set Up Microsoft CRM 2016 IFD on Windows 2012 R2 Server