Skip to main content

Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign

Post a Comment

Update Rollup 1 for CRM 2013 fails (DBUpdateAction)

The following scenario with one of my customers:
CRM 4.0 version was upgraded to CRM 2011 via in-place upgrade then we upgraded it to CRM 2013 also via in-place upgrade.

This error occured once I tried to install the CRM 2013 Update Rollup 1:

16:00:00|   Info| Found the older table DBUpdateInstallInfo_V5, updating new table and deleting
16:00:00|   Info| Updating table with older rows: DBUpdateInstallInfo
16:00:00|   Info| InstallerException: Invalid column name 'MajorVersion'.
Invalid column name 'MinorVersion'.
Invalid column name 'BuildNumber'.
Invalid column name 'DBUpdateActionId'.
Invalid column name 'CrmDatabase'.
16:00:00|  Error| System.Exception: Action Microsoft.Crm.Setup.Common.Update.DBRemoveAction failed. ---> System.Data.SqlClient.SqlException: Invalid column name 'MajorVersion'.
Invalid column name 'MinorVersion'.
Invalid column name 'BuildNumber'.
Invalid column name 'DBUpdateActionId'.
Invalid column name 'CrmDatabase'.

15:48:41|   Info| InputResult: Retry
15:48:41|   Info| CrmAction execution time; DBUpdateAction; 00:00:05.9995720
15:48:42|   Info| Found the older table DBUpdateInstallInfo_V5, updating new table and deleting
15:48:42|   Info| Inserting into DBUpdateInstallInfo: Version = 6.0.1.61, DBUpdateActionId = 1475935d-b5b2-4c8f-aba3-e6ac19c99f12, CrmDatabase = ConfigOnPremise
15:48:42|   Info| InstallerException: Invalid column name 'MajorVersion'.
Invalid column name 'MinorVersion'.
Invalid column name 'BuildNumber'.
Invalid column name 'DBUpdateActionId'.
Invalid column name 'CrmDatabase'.
Invalid column name 'DBUpdateActionId'.
Invalid column name 'MajorVersion'.
Invalid column name 'MinorVersion'.
Invalid column name 'BuildNumber'.
Invalid column name 'DBUpdateActionId'.
Invalid column name 'CrmDatabase'.

OK, this made me think some old (tables) must disturb the process:

I found this script in the WWW from :
SELECT SCHEMA_NAME(schema_id) + '.' + t.name AS 'Table Name'
FROM sys.tables t
     INNER JOIN sys.columns c
        ON c.object_id = t.object_id
WHERE c.name like '%ColumnName%'
ORDER BY 'Table Name'
 
OK, this enabled me to find some of the fields mentioned in the log, secondly the CRM Install Log above also mentions the table DBUpdateInstallInfo and DBUpdateInstallInfo_V5.
 
So after the first try of installing UR1 failed I did the following steps:

1. Created backup of my MSCRM_CONFIG database
2. Renamed dbo.dbupdateinstallinfo to dbo.dbupdateinstallinfo-old
3. Renamed dbo.dbupdateinstallinfo_V5 to dbo.dbupdateinstallinfo_V5-old
 
OK, this time the Update Rollup 1 went through as smooth as it should be.
 
Finally I got curious what the CRM 2013 UR1 routine did to my MSCRM_CONFIG database.
Actually it recreated the database dbo.DBUpdateInstallInfo with the following fields:
  • MajorVersion
  • MinorVersion
  • BuildNumber
  • Revision
  • DBUpdateActionId
  • CrmDatabase
This made me understand the original error messages with "Invalid column ....".
The installation routine was missing these columns in the original existing tables.
 
Anyway everything is fixed and CRM 2013 is up and running with UR1. AWESOME! 
 

 
Labels:

Comments

  1. AnonymousMarch 29, 2014 at 9:38 PM

    Thanks for this. As of UR2 it still isn't fixed.

    ReplyDelete

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete
16 comments
Read more

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu
1 comment
Read more

CRM 2013: Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead.

Lately I was fighting with an issue that on some CRM instances the default email templates view in the Templates section of CRM 2013 did not show up and only showed me this error message: Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead. After searching for a long time I found the simple bug. Throught migration from 4.0 to CRM 2013 over CRM 2011 and changing customizations it seemed that CRM got messed up or was not able to handle the changes very well. The issue here was to go to the views section of the Email Templates entity and to make sure there is only ONE default public view. If there are two you will get strange system behavior. I fixed this problem through updating the isdefault property of the second unwanted default view in the SavedQueryBase data table. The id of this view  you can retrieve by openen the view and by copying it out from the URL. Én voi
1 comment
Read more