Category Archives: Server Tips

alphassl the requested property value is empty Exception for HRESULT 0x80094004

alphassl the requested property value is empty Exception for HRESULT 0x80094004


When completing an Alphassl certificate install on IIS using the “Complete Certificate Request” you receive the error:

There was an error while performing this operation.


The requested property value is empty. (Exception from HRESULT: 0x80094004)

Exception for HRESULT 0x80094004

Now this is a Typical Microsoft Error in that it really only has meaning to the person who created the error. For us end users stuck in this weird Microsoft world, the error message is trying to tell us that the Certificate you pointed to for the “Complete Certificate Request function in IIS

IIS Complete Certificate Request

is pointing to a .CER file that is not valid as a certificate for import.

So at this point it is time to check what certificate you placed in the .CER file that you are trying to import.


In particular with Alphassl certificates, the process of completing a new certificate request is completed by email. The end of the process involves receiving an email with instructions on how to complete the process of import.

Screenshot 2018 03 14 13 12 32

Now if you are anything like me, and you think you know what you are doing having completed this process a few times. You tend to work fast and read instructions later (like an IKEA assembly job). And on several of my certificate install jobs I have made the same error. That being that I read to point 2 above. Click the link which if I read it is obviously to the Root Certificate Install. Then proceed to copy and paste the SHA-256 Certificate into the process and save is as a .cer file, then try to complete the process with that hash. 

Screenshot 2018 03 14 13 16 13

So basically this is all wrong. The certificate Hash is actually included in the bottom of the email received from Alphassl and that hash from the bottom fo the email is the correct hash to copy and paste to your IIS server and save as a .cer file. It is then this file that you use to complete the process with your IIS “Complete Certificate Request” function. Not the above Root certificate.




There was an error while performing this operation.


The requested property value is empty. (Exception from HRESULT: 0x80094004)

Windows Server 2016 Download Maps Manager Delayed Start

Windows Server 2016 Download Maps Manager Delayed Start Red in Server Manager Dashboard

Its kind of annoying to find that after a fresh install of Windows 2016 Server you have a service that fails to behave correctly.

Download Maps Manager Delayed Start

When you click on the service, you will see something like this.

Screenshot 2017 08 02 22 40 27

Even if you attempt to force a start, it does not resolve this issue.

The good news is that this service is really not something you want anyway if you have a windows server doing actual server functions.

The Fix

The simple fix is to disable this service. The easy way to do this is to:

Open Windows Powershell

Windows 2016 Server Power Shell

Windows Powershell

Type this command:

Get-Service -Name MapsBroker | Set-Service -StartupType Disabled -Confirm:$false


Disable MapsBroker in Powershell

Problem is now fixed, and this annoying service is off and will not bother you again. 

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. 

Install Disk Cleanup on Windows.png

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.

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.

Enable TLS 1.2 on Windows 2008 R2


How to enable TLS 1.2 on Windows Server 2008 R2?


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.


    1. Start the registry editor by clicking on Start and Run. Type in “regedit” into the Run field (without quotations).


      1. 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.


           You will be editing the registry.  This could have detrimental effects on your computer if done incorrectly, so it is strongly advised to make a backup.

          1. Browse to the following registry key:


            1. Right click on the Protocols folder and select New and then Key from the drop-down menu. This will create new folder.  Rename this folder to TLS 1.2.


              1. Right click on the TLS 1.2 key and add two new keys underneath it.


                1. Rename the two new keys as:
                  • Client
                  • Server


                  1. Right click on the Client key and select New and then DWORD (32-bit) Value from the drop-down list.


                    1. Rename the DWORD to DisabledByDefault.


                      1. Right-click the name DisabledByDefault and select Modify… from the drop-down menu.


                        1. Ensure that the Value data field is set to 0 and the Base is Hexadecimal.  Click on OK.


                          1. Create another DWORD for the Client key as you did in Step 7.


                            1. Rename this second DWORD to Enabled.


                              1. Right-click the name Enabled and select Modify… from the drop-down menu.


                                1. Ensure that the Value data field is set to 1 and the Base is Hexadecimal. Click on OK.


                                  1. Repeat steps 7 to 14 for the Server key (by creating two DWORDs, DisabledByDefault and Enabled, and their values underneath the Server key).


                                  1. Reboot the server.

                                  Your server should now support TLS 1.2.


                                  Note: This article cannot be used on a Windows Server 2003 (IIS 6).  Windows Server 2003 does not support the TLS 1.2 protocol.

                                  Reverting Back

                                  If you make a mistake or something just isn’t right, you can revert back to your previous registry settings by opening the Registry Editor and importing the backup you made in step x.

                                  The trust relationship between this workstation and the primary domain failed Hyper-V Server

                                  The trust relationship between this workstation and the primary domain failed

                                  When playing around with some Hyper-V servers that have been inactive for some time, we received an error:

                                  Screenshot 2016 01 05 19 31 45

                                  The cause of this is due to the fact that Active Directory is doing a lot more than simple user name and password storage. We found that a Hyper-V system that remains off for some time, then is turned on again can suffer this. The reason for this has to do with the way that some applications use the Active Directory. Take Exchange Server, for example. Exchange Server stores messages in a mailbox database residing on a mailbox server. However, this is the only significant data that is stored locally on Exchange Server. All of the Exchange Server configuration data is stored within the Active Directory. In fact, it is possible to completely rebuild a failed Exchange Server from scratch (aside from the mailbox database) simply by making use of the configuration data that is stored in the Active Directory.

                                  The suggestion by some other blogs is to: simply reset the computer account. To do so, open the Active Directory Users and Computers console and select the Computers container. Right click on the computer that you are having trouble with. Select the Reset Account command from the shortcut menu, as shown in Figure 2. When you do, you will see a prompt asking you if you are sure that you want to reset the computer account.  Click Yes and the computer account will be reset.


                                  This is perfectly safe to do, but is not likely to resolve the issue.

                                  The Fix

                                  1. Log into the server in question using the non domain admin account.

                                  2. Open the Power Shell and run the command:

                                  $credential = Get-Credential

                                  (When prompted, you need to enter the domain administrator account and name.)

                                  3. Then run the command: 

                                  Reset-ComputerMachinePassword -Server ClosestDomainControllerNameHere

                                  (Replacing the “ClosestDomainControllerNameHere” with your domain AD domain. for example.)

                                  After running this you should be good to login.

                                  CRM 2015 Extend Auto Logout Time in IFD

                                  CRM 2015 and CRM 2016 IFD will Automatically Logout the user with a Message:

                                  Your session in Microsoft Dynamics CRM is about to expire. To continue working, you must sin in again.

                                  CRM 2015 Auto Logout

                                  By Default this setting is 60 minutes, and the message will pop up around 20 minutes before logout.

                                  Any unsaved changes will be lost as your session ends.


                                  The Fix

                                  To extend the automatic logout time in CRM 2015, we must extend the time set in ADFS 3.0 using the PowerShell command. First we need to know the name that was used to set up the Relying Party Trust in ADFS.

                                  1. Open Server Manager and from the Tools menu select ADFS Management

                                  ADFS Management

                                  2. in AD FS management, open Relying Party Trusts and find the Display name for the CRM IFD Relying Party Trust

                                  Screenshot 2015 04 03 17 30 58

                                  In this case, we have called the Relying Party Trust – “CRM IFD Relying Party” as we keep things simple when we create things. Using the exact name for the title of the trust as we created it. But really it could be anything. One distinguishing feature is that the URL identifier is going to be optioning to the URL that displays in the browser window when you are in the process of login into your IFD CRM.

                                  3. Start PowerShell

                                  Screenshot 2015 04 03 17 35 57

                                  4.  Check you have the correct name of the Relying Party Trust by typing the following command.

                                  Get-ADFSRelyingPartyTrust -Name "relying_party"

                                  Where you replace the “relying_party” with the name you identified in Step 2 above. In our case the command will be: 

                                  Get-ADFSRelyingPartyTrust -Name “CRM IFD Relying Party


                                  The result should look something like this if you get it correct.

                                  Screenshot 2015 04 03 17 40 02

                                  5. Not type the command to set the time you want to set for Auto Logout.

                                  Set-ADFSRelyingPartyTrust -Targetname “CRM IFD Relying Party“ -TokenLifetime 720

                                  (Again replacing the “CRM IFD Relying Party” with the name used on your system.)

                                  Note: The 720 is time in minutes. 12 Hours in this case. You can change the value up and down as liked.

                                  Set-ADFSRelyingPartyTrust -Targetname “CRM IFD Relying Party“ -TokenLifetime 720

                                  Screenshot 2015 04 03 17 43 47

                                  6. Close out the PowerShell and you are done.

                                  CRM 2015 IFD Adding a New Organization Additional Steps

                                  Error when attempting to login to a New Organisation in CRM 2015 IFD

                                  When attempting to login to a newly configured Organisation you may receive an error looking like this.

                                  Screenshot 2015 03 28 18 43 05 

                                               An error occurred
                                  An error occurred. Contact your administrator for more information.


                                  • Activity ID: 00000000-0000-0000-1400-0080010000ff
                                  • Error time: Sat, 28 Mar 2015 07:37:45 GMT


                                  The Cause

                                  Because IFD (Internet Facing Deployment) uses the AD FS Authentication it requires an additional step after using the CRM Deployment Manager to setup a new Organisation to then register at login with the AD FS setup.

                                  Basically it is saying that you have set up the org, but not gin figured the authentication login settings in AD FS.


                                  The Fix

                                  1. Open AD FS Mananagement

                                  Screenshot 2015 03 28 18 46 58 

                                  2. Click on AD FS / Trust Relationships / Relying Party Trusts and local your CRM IFD Relying Party Trust associated with the IFD Authentication.

                                  Screenshot 2015 03 28 18 49 52 

                                  3. Highlight it, and select Update Federation Metadata

                                   Screenshot 2015 03 28 18 50 30

                                  4. Update

                                  Screenshot 2015 03 28 19 04 29 

                                  And you are done!

                                  You should now be able to login to the CRM server without getting the error message, and with no need to reset IIS or any other services.




                                  CRM 2015 Reporting Extension Setup Error The SQL Server Reporting Services account is a local user and is not supported

                                  Error Message installing CRM 2015 Reporting Extensions

                                  When installing Microsoft Dynamics CRM Reporting Extension Setup you receive an error message: The SQL Server Reporting Services account is a local user and is not supported. This is during the System Checks.

                                  SQL 2014 CRM 2015 Reporting Extension Setup Error.png

                                  In our instance this was with MS CRM 2015 on SQL 2014 on the same server in a test environment.

                                  The Solution

                                  The fix is easy.

                                  1. Open the SQL 2014 Reporting service configuration Manager

                                  Screenshot 2015 03 28 17 56 17

                                  2. Connect to your Server.

                                  Screenshot 2015 03 28 17 57 04

                                  3. Select the Service Account

                                  Screenshot 2015 03 28 17 57 37

                                  4. Select the Local System account and apply with the appropriate security levels.

                                  Screenshot 2015 03 28 17 58 25

                                  That’s about it. Run the setup process again and you should be good to go.