Sometimes when you try to delete a managed Solution, there is an error message about the dependancies of the solution being in use.
When you download the log file, you see some typical Microsoft Crap that really does nothing to help you.
The only thing it does is to tell you that you can’t delete the component because it is being used in this case by two other components.
Now the hard part is finding the components that are using it.
1. Work out the Solution Name. Navigate to CRM / Settings / Solutions - and read the exact Name of the Solution to be deleted. In this case it was “ZendeskCRM2011Connector“
2. Login to your CRM Server and open the SQL database that matches the Organisation name being used in CRM.
3. Execute an SQL query against that database that reads.
selectSolutionIdfromSolutionwhereUniqueName=’Name of your Solution‘
(Replacing the Name of Your Solution) with the exact name of your solution, So in our case:
And it executes to give:
This gives you the GUID of the managed solution in the results area. In our example it is the: 3AC85885-F78B-47A3-BAB5-F8DE569B4EDD number at the bottom.
4. Now navigate to the following URL:
https://YOUR CRM URL/tools/dependency/dependencyviewdialog.aspx?objectid=GUID&objecttype=7100&operationtype=dependenciesforuninstall
Replacing the “YOUR CRM URL” with the URL to your own CRM system. and replace the GUID with the GUID retrieved from step 3 above. Thus the URL may look like this:
It will show a page that looks like this:
Which you can use to help you work out what to edit to remove the dependencies and delete the solution.
Thanks Microsoft for making something so easy so hard!
Install the Following Components
The following method is use to install the Windows Search Service on Windows 2012 R2. The search feature is launched form the Server Manger (which will start by default as login as an administrator).
Click Add Roles and Features
Next (without selecting anything)
With the Features, select Windows Search Service – Next
Run through the process again
Next (without selecting anything)
This time select the Web Server (IIS)
When prompted select Add Features
When installing the SQL server, the required features are almost the default features with the following two ticks.
1. Database Engine Service
2. Full-Text and Semantic Extractions for Search
CRM will work much better with IIS Dynamic Compression. The install this you follow the normal Roles and Features install, and find the section for:
Web Server Role (IIS)
Second option: Under Server Manager click Add roles and features
This ensures that you can enable dynamic compression after install to ensure that performance is best.
Your session in Microsoft Dynamics CRM is about to expire. To continue working, you must sin in again.
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.
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
2. in AD FS management, open Relying Party Trusts and find the Display name for the CRM IFD Relying Party Trust
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
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.
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. 8 Hours in this case. You can change the value up and down as liked.
6. Close out the PowerShell and you are done.
‘Agent XPs’ component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘Agent XPs’ by using sp_configure. For more information about enabling ‘Agent XPs’ see “Surface Area Configuration” in SQL Server Books Online. (Object Explorer)
Details of the error are:
Cannot show requested dialog.
Unable to execute requested command.
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolMenuItemHelper.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc) at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
‘Agent XPs’ component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘Agent XPs’ by using sp_configure. For more information about enabling ‘Agent XPs’, see “Surface Area Configuration” in SQL Server Books Online. (Microsoft.SqlServer.Management.MaintenancePlanWizard)
at Microsoft.SqlServer.Management.MaintenancePlanWizard.MaintenancePlanWizardForm.LoadData() at Microsoft.SqlServer.Management.MaintenancePlanWizard.MaintenancePlanWizardForm..ctor(XmlDocument doc, IServiceProvider serviceProvider)
This is caused because the “SQL Server Agent” is not running.
By default, this service is set to start manually. This is normal after a fresh install.
1. Open SQL Server Configuration Manager
2. Start the service for SQL Server Agent.
3. Right click the service and select Properties
4. Click the Service tab and change the start mode to Automatic