Microsoft.Crm.Setup.Shared.AnalyzerBase+CollectAction failed - email

I'm not able to install Microsoft Dynamics CRM EMail Router 2015 on my machine. I had an earlier version but however needed to re-install this.
I get an error as: "Action Microsoft.Crm.Setup.Shared.AnalyzerBase+CollectAction failed"
How can I resolve this? Please help. Thanks.

I would ensure you are following the steps in the Upgrade CRM 2013 Email Router to CRM 2015 Email Router documentation.
If you plan to upgrade both the Email Router and Microsoft Dynamics CRM, perform the upgrade tasks in the following order:
1. Stop the Microsoft Dynamics CRM Email Router service. To do this, on the Start menu, type services.msc, and then press ENTER; or click Run, type services.msc, and then press ENTER. Right-click the Microsoft Dynamics CRM Email Router service, and then click Stop.
2. Upgrade Microsoft Dynamics CRM Server 2013 to Microsoft Dynamics CRM Server 2015.
3. Install the Microsoft Dynamics CRM 2015 Email Router:
If you already have the Microsoft Dynamics CRM 2013 Email Router installed, upgrade to the Microsoft Dynamics CRM 2015 Email Router, as described below.
If you don’t have the Microsoft Dynamics CRM 2013 Email Router installed, install the Microsoft Dynamics CRM 2015 Email Router, as described in Install Email Router and Rule Deployment Wizard.
4. You might need to restart the Microsoft Dynamics CRM Email Router service after the upgrade to the Microsoft Dynamics CRM 2015 Email Router finishes. To do this, in the services list, right-click Microsoft Dynamics CRM Email Router, and then click Start.
The other thing I'd review if you haven't already is that you are meeting the Microsoft Dynamics CRM Email Router software requirements
If you have done those steps already, I'd probably reboot the workstation/server and restart the install to ensure that there is not anything left in the temp files that could be conflicting with it (making sure to stop the CRM Email Router Service first if you are upgrading). I would also review the Windows Application event logs for any errors related to the CRM Email Router Service and/or installation for additional details, although typically the installer is pretty good about being clear with regards to what is not working or is not expected.
One other item I'll call out is that you need to be running as a Domain user with local administrator privileges in order to install or to upgrade the Microsoft Dynamics CRM 2015 Email Router.

Related

Oracle IAM/WNA protocol fallback to form-based logon page fails when Microsoft Online Services Sign-In Assistant is installed

First post here. Facing a problem where on Windows 10 an Oracle Identity Access Management (IAM) Windows Native Authentication (WNA) protocol fallback to a form-based logon page always fails whenever the Microsoft Online Services Sign-In Assistant (SIA) is installed. Whenever we remove the SIA, the WNA fallback to a form-based logon page always succeeds. This error is reproducible 100% of the time. We have not tested on Windows 8 or Windows 7. I've researched it, and there is not much out there to read about the SIA; it does not look to be configurable on the client end. Really want to avoid changing up code on the IAM WNA side.
Anyone out there seen this before? This is a large enterprise network, using all Windows 10 computers, which has both Oracle IAM running for some applications as well as Microsoft Windows 2008 R2 Active Directory, to which all the Windows 10 computers are joined. We are also standardized with Office 2016 with all back-end servers supporting Office apps such as Outlook, Lync, etc. in the cloud (Office 365).
Please let me know if I need to show the Oracle IAM/WNA SSO fallback code.
The Microsoft Online Services Sign-In Assistant is not configurable. But, if all your computers are running Office 2016 you do not need it anyway and it can be safely uninstalled, which as you said will make the fallback to form-based logon page work. If you were running Office 2013 you would need it however. Office 2016 apps such as Outlook and Lync can go direct with ADFS whereas previous versions could not do this. I don't have a URL reference for you, this is based on my experience.

CRM 2016 On premise - Can not connect to CRM with Plugin Registration In IFD Mode

I have Microsoft Dynamics CRM 2016 On Premise and IFD Enabled On it.
In this situation I can not connect plugin Registration to CRM. Even I can not connect with XRMtoolbox.
My problem is what is Home Realm URL?
Unable to Login to Dynamics CRM
An Error occurred while processing the login request.
Try removing all your 3rd party plugins except the plugging registration tool.
Also there is a plugin registration tool from Microsoft in the CRM SDK download that you can use as well.
Do yourself a favor and download the CRM 2011 SDK. In the bin folder is the plug-in registration tool. The new version released in 2013+ is complete garbage with bugs that Microsoft Support is not interested in fixing.
That said, I don't think you can "Use Default Credentials" with IFD. For the server you should just put organizationName.domainname.tld. For user name use your UPN or domain\username. Don't use both the domain and user name fields unless you're using integrated authentication.
The Problem is In adfs Endpoints. After you Install IFD on CRM You want a Important Endpoint That Named "Mex".
For Solve The Problem First go to ADFS Management and go to endpoints and Click on adfs/services/trust/Mex and click on Enable and Enable on proxy for this Endpoint. after that reset the iis and adfs service.
Then You can Browse that enpoint with https://service.contoso.com/adfs/services/trust/mex.
if you See the Metadata Xml Document Now You Can Connect With Any Tool Like Portal, Plugin Registration, Xrmtoolbox, etc.
but If you Don't see this metadata use this Command in Power shell to Change The Adfs Port.
Set-ADFSProperties –nettcpport: 809
i Choose 809 for My Port And You Can choose any port you want Except 443 or 80 or 90, Then like before Restart The IIS and Restart ADFS Service and then you Can see metadata And You Can Connect With Any Application to CRM 2016 On Premise IFD Mode.
At The End Of this Answer You can See My Metadata Page And My Connected Plugin Registration Tool Pictures.
If You Have Any Question You Can Ask it From Me.

Microsoft CRM 2011 IFD vs Windows Auth

Can someone explain to me why one would use IFD (Internet Facing Deployment) to access Microsoft CRM vs. just using Windows Authentication? They seem equivalent to me in their features. Not sure of the benefits of IFD over Windows auth however.
Thanks!
Take a look at this previous answer for some discussion on this topic: Exposed onsite vs IFD deployments for MS Dynamics CRM
I would say from my standpoint the biggest issue with using Windows Auth over the internet for CRM is the issue of Outlook integration. The second point I would make is that Windows Auth can present issues to people accessing CRM from a non-domain computer when outside the domain - i.e., their home computer. Not always but I have seen issues pop-up (not very often) that are avoided in a forms based configuration.
As a reminder in 2011 the IFD feature has been changed signficantly so that you must use Active Directory Federation Service which is claims-based. I recommend reading over http://blogs.msdn.com/b/crm/archive/2011/01/13/configuring-ifd-with-microsoft-dynamics-crm-2011.aspx and watching the video at http://www.youtube.com/watch?v=ZD5qaa-G99E.
You can certainly go with Windows Auth but if you are willing to put in the extra work go with the Internet Facing setups for a more robust and better supported install.
I want to add to privious answer.
Integrating Outlook client from outside the domain can be done by reseting windows credential in the control panel from time to time.
another complication is SharePoint integration which can't be used outside the domain with SSO.
If you do use IFD, I recommand on this blog:
http://dynamics.co.il/configuring-crm-2011-ifd

Microsoft Dynamics CRM 4.0: Are Powershell cmdlets available?

I am entirely new to Microsoft Dynamics CRM 4.0 and have been tasked to create some automation around MS-Crm administration.
To this end, I wish to use powershell. I have found that there are cmdlets that allow you to work with CRM (see MSDN). But what I cant seem to find out is whether these cmdlets are only available in Dynamics 2011 or are they available in Dynamics 4.0 also?
I tried running "Add-PSSnapin Microsoft.Crm.PowerShell" on the server - but get an error message that the snapin is not available. So, not sure as to what is going on.
For Dynamics CRM 4 there are no PowerShell cmdlets available. However, the cmdlets which are existing for Dynamics CRM 2011 are mostly a convenient way to automate the deployment service or to access the organization settings.
Most of these is also available in Dynamics CRM 4.
Take a look at the Deployment SDK for Dynamics CRM 4.
Keep in mind that some of the cmdlets for Dynamics CRM 2011 use new features of its Deployment Service, as for example the Import-CrmOrganization cmdlet. This is not possible with the Dynamics CRM 4 Deployment Service.
There are no official PowerShell cmdlets for CRM 4, but the Deployment web service is available for 4.0. You could code against that, or create your own cmdlets that run against it.
Do you installed the Deployment Tools role ?
Have a look to this post for more informations.

How to programmatically import a CRM Organization?

Is there any way via powershell or some api that I can't seem to find in the CRM 4.0 SDK, that would allow us to automate the refresh from our production CRM 4.0 environment to a Staging CRM server? Obviously the db backup / restore we can script but I cannot find a way to kick off a CRM Import Organization without using the MMC snap-in.
there is a Deployment SDK for Dynamics CRM 4 available. However the interesting part for you is not part of the public api.
The documentation mentions the ImportOrganizationRequest which should be used by the Deployment Manager. Unfortunately, it is marked for internal use. However, there should be no changes to this API as Dynamics CRM 2011 is just around the corner and therefore I would give it a try.
You could use this post in the msdn forums as a starting point.
btw: Dynamics CRM 2011 comes with a set of PowerShell CmdLets which makes the adminstration much more scriptable. Especially Import-CrmOrganization would be the CmdLet which you could use. See my blog post for further information.