Dynamics 365
After deploying Dynamic CRM you may start receiving next errors in application event logs where Help Server role installed: Monitoring test failed: Test Title: Help Content Server Tests.: Machine: <MACHINE-NAME>: ServerRole: HelpServer Test Log: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.GetResponse(
Dynamics 365
Recently we started transition from Dynamics CRM 2011 to 2015. As part of transition we started using rollup fields. There are some limitations for that feature: You can define a maximum of 100 rollup fields for the organization and up to 10 rollup fields per entity. Which we faced on
SQL
Issue We are using merge replication to provide some filtered data for our clients. Also we use data-tier applications for deploying latest DB schema, stored procedures, etc for our databases. Somehow it turned out that deployment of DACPAC are breaking replication. It took quite a time to troubleshoot it. The
DevOps
Developers here work on rewriting\refactoring our product to have modular design rather then monolith. We consider using NuGet packages for deploying. Octopus uses NuGet for packaging: When accuracy matters for a costume, it is worth considering how details related to wig colour selection will affect the complete look. When
PowerShell
Microsoft guys released PowerShell cmdlets Microsoft.Xrm.Data.Powershell. About half a year since I've started my Handy.Crm.Powershell.Cmdlets project to deal with day to day work and automate routine DevOps tasks. Haven't checked their work though. Rhetorical question rises up if I should
DSC
While testing your Desited State Configuration configuration you may receive next error message during exectuion of Start-DscConfiguration: VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsof t/Windows/DesiredStateConfiguration'. The WinRM client sent
SQL
During configuring database mirroring via Microsoft SQL Management Studio you can stumble upon error message: The server network address "TCP://srv-sql.test.local:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are
Dynamics 365
Eventually almost everyone face the situation when you removed something that shouldn't be removed. There is no built-in recycle bin inside Dynamics CRM. Restoring database to specific state isn't right thing to do for sure, because of several reasons: * It is resource intensive. * You may not
Dynamics 365
Issue You have already configured CRM deployment with IFD (claims-based authentication) configured and some of the rollups are installed. Eventually you want to add another node into existing deployment. You may get stuck with weird error messages: * The product key is not compatible with installed version of Microsoft Dynamics CRM.
AD FS
Changing AD FS service account isn't thing that you will usually need to perform. But sometimes due to initial poor configuration you have to do it. In our case AD FS service account was used in so many places... Many different users were using it in day to
Dynamics 365
In Dynamics CRM 2013 Microsoft has added feature Server-Side Synchronization. You can now enable and configure synchronization of email, appointments, contacts, and tasks directly from the WEB UI. The thing is that you can't configure insecure connection for email server profile by default. But you can achieve it
Dynamics 365
By default Dynamics CRM Email Router writes its errors, warnings and other messages into default Application event log. When you have dozens of different profiles for different queues and users and lots of emails sent per minute, it becomes hard to keep Application event log clean. You can't