CRM 2016 Organization Creation Error hangs on "Microsoft.Crm.Admin.ImportDefaultAction" - crm

CRM 2016 Organization Creation Error hangs on "Microsoft.Crm.Admin.ImportDefaultAction"
CRM Install has taken place, CRM 2016, front and back end has been updated with the latest Microsoft updates 2017.
After checking the error file from the SQL database:

Related

Does IBM Database Add-Ins for Visual Studio support VS2019?

After scouting numerous articles and stack overflow for hours it seems that the IBM Database Add-Ins are not supported for Visual Studio 2019. Do correct me if I'm wrong.
Reasons for installing the Add Ins was to create entity classes in asp.net using web forms.
IBM Database Version : DB2 LUW 10.5
Reasons for the conclusions:
Installed the same fix packs for the IBM Data Server Driver Package as well as IBM Database Add-Ins for Visual Studio (Fix Pack 11) https://www.ibm.com/support/pages/node/3501195
Log Error Message : MSI (c) (98:58) [17:45:41:129]: Windows Installer installed the product. Product Name: IBM Database Add-Ins for Visual Studio, Product Version: 10.5.1100.2866, Product Language: 1041, Manufacturer: Company Name, Installation Success or Error Status: 1603
If the add in does not support Visual Studio 2019 , what would be the best replacement for Entity Framework 6.0 in order to use with IBM Db2?
If the add in does support Visual Studio 2019 is there a workaround to the following problem?
To get paid support (from IBM) for Visual-Studio 2019 in Db2, you need to have the visual studio add in that comes with Db2 v11.5.
For Db2 V10.5, it supports up to Visual Studio 2013.
It does not mean it will not work with older Db2 versions, but when you have issues (which is very likely), you won't get much help from IBM unless you have the right versions. You might be able to devise workarounds in some cases, but why bother?
If you are paying for a licence for Db2, pay for the current version and get the relevant paid support included. If you are not paying (for example, you are using a community edition) then get the latest version anyway. There seems no genuine reason for using the (out of support) Db2 v10.5 build if you are trying to use it with Microsoft software that was developed long after Db2 v10.5 was created.
Here is the link to the page that shows Db2 v11.5 supports Visual Studio 2019.
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.swg.vs.addins.doc/html/ibmdevtsk-MigratingDB2Projects.htm

Microsoft SQL Server 2014 exception

I open my SQL Server 2014 Management Studio and try to open any table from my databases, I got this message.
When I follow the path below I don't have a folder called Microsoft\AppEnv\10.0\ActivityLog.xml.

BizTalk 2013 R2 CU 5 Installation

I am planning to install CU 5 for BizTalk 2013 R2. I cannot find any reviews online so I wanted to have your feedback if there are issues installing the CU 5. I am using BizTalk 2013 R2 and I haven't installed any CU updates thus far.
Link of CU upgrade - Cumulative Update package 5 for BizTalk Server 2013 R2
You should install all BizTalk CU's during regular maintenance.
It's a good idea to treat them like any other app update, meaning apply to DEV, then TEST, then PROD, applying all you regular test procedures along the way.
For clarity, all BizTalk Server CU's are cumulative so CU5 will include all updates and patches from 1-4 as well.
There is an issue with BizTalk 2013R2 CU5 when you install it without the required SQL admin rights (the installer doesn't notify about this the way it should according to my opinion).
At the end of the installation, the installer will tell you it failed completing some post-installer steps. In the installer log file you will find a reference to the missing SQL rights.
When you try to open the BizTalk Admin Console, you will encouter a 'Could not find stored procedure ops_ClearOperationsProgress' exception.
The only way to recover from this is doing a database restore of the management database.
I wrote a blog post about this here.

Report Builder 2016 freezes, SQL Server 2016 RC 3.3 and VS 2015 installed

Using Report Builder 2016 after creating the Data source the program freezes.
On my computer I have installed SQL Server 2016 RC 3.3 and VS Community 2015 w/ SSDT
Tried to create a blank report adding in the Data source and query, when trying to preview the report I get an error.
The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.

Dynamics AX 2009 Developer Install

I am trying to set my new laptop up with a developer installation of MS Dynamics AX 2009.
I start by installing MS SQL Server 2008 R2, this goes in fine, I create a new database in here.
I then launch the AX 2009 setup, I firstly install the Application Files, go through this, all is OK.
I then re-launch the AX 2009 setup, installing the AOS, I login using a specific username / password setup for the AOS.
I then re-launch the AX 2009 setup and install the Client and Debugger.
When I go to launch the AOS in Services the service gets 'stuck on "Starting" and after 5/10/15 minutes waiting and refreshing nothing happens?
Do I need to install the Database files in the AX 2009 setup as well?
Many thanks...
Yes you need to have an AX 2009 database. Either install it via the AX 2009 installer or deploy the contoso example database from Microsoft. Easier to install from the installer.
The first start of the AOS can take some time, but if you don't have a database, I can't imagine how it would work.
Go to (Administrative Tools>Microsoft Dynamics AX 2009 Server Configuration) and click the database tab of your instance, and what does it have? Does that database exist or is anything selected?
You should check the windows event viewer under "applications" to see issues during service startup.
/This isn't really code btw...

Resources