Leon1983 Posted July 24, 2016 Report post Posted July 24, 2016 I have just attempted to upgrade from 1511 to 1606, after the prerequisite checks passed. The error message I am receiving is "failed to apply update changes 0x87d20b15" however I believe the error "ALTER ASSEMBLY failed because the required method "ParseiOSVPPSyncRow" in type "Microsoft.SystemsManagementServer.SQLCLR.StateSys.VPPMessageParsing" was not found with the same signature in the updated assembly" is more specific to the issue. Has anyone else experienced this, also can anyone assist? Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 25, 2016 Report post Posted July 25, 2016 hi nope, but I can ask the PG to comment, can you share your cmupdate.log please ? your error is similar to this users problem fyi https://social.technet.microsoft.com/Forums/en-US/d072c5af-5c23-4977-a9c0-2219a11cde2f/configuration-manager-1602-installation-failed?forum=ConfigMgrDeployment Quote Share this post Link to post Share on other sites More sharing options...
Leon1983 Posted July 25, 2016 Report post Posted July 25, 2016 Yes I did see that post, many thanks. Please see below - if this is not enough info should I just attach the full log file? INFO: Configuring SQL Server CLR assemblies... CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly ServiceBrokerInterface from file ServiceBrokerInterface.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly MessageHandlerService from file MessageHandlerService.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly DcmObjectModel_SQLCLR from file DcmObjectModel_SQLCLR.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly CryptoUtility from file CryptoUtility.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly ModelFactory from file ModelFactory.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)INFO: SQL Server CLR assembly SMSSQLCLR from file smssqlclr.dll already exist in database, skip it. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)sql object StateSysSqlClr with hash SHA256:D3EC1B62BE7429D29850E4BA4EEFAD9BA7E6B7782ACBB2BED1318EF3AA660AED is not found. It will be created. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)*** SELECT HashMatch = COUNT(*), ClrExists = (SELECT COUNT(*) FROM sys.assemblies WHERE name = N'StateSysSqlClr') FROM DBSchema WHERE ObjectName=N'StateSysSqlClr' AND ObjectHashAlg=N'SHA256' AND ObjectHash=0xD3EC1B62BE7429D29850E4BA4EEFAD9BA7E6B7782ACBB2BED1318EF3AA660AED AND SiteNumber = dbo.fnGetSiteNumber() CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)*** [42000][6270][Microsoft] [sql Server]ALTER ASSEMBLY failed because the required method "ParseiOSVPPSyncRow" in type "Microsoft.SystemsManagementServer.SQLCLR.StateSys.VPPMessageParsing" was not found with the same signature in the updated assembly. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)ERROR: Failed to create assembly StateSysSqlClr. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)ERROR: Failed to UPDATE CLR assemblies. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)Failed to update database. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)Successfully reverted SQL function fnCurrentSiteVersion. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)Successfully reverted SQL function fnCurrentSiteVersion_INT. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C)Successfully reverted SQL function fnCurrentSiteVersion_INT_TABLE. CONFIGURATION_MANAGER_UPDATE 24/07/2016 23:37:56 15932 (0x3E3C) Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 25, 2016 Report post Posted July 25, 2016 i need the full log file please - can you email it directly to me and i'll pass it to Microsoft thanks Quote Share this post Link to post Share on other sites More sharing options...
Leon1983 Posted July 25, 2016 Report post Posted July 25, 2016 Of course, many thanks Niall. Quote Share this post Link to post Share on other sites More sharing options...
Leon1983 Posted July 25, 2016 Report post Posted July 25, 2016 As per the log file I believe the errors seem to be related to SQL and during my daily checks noted some WSUS errors in the event log id's 6700 and 6703 relating to an "Unspecified SQL error". On running the Disk usage report on the database I noticed that the data files only showing 7.44 % of free space. The data files are also not limited to a specific size. We have limited the log files due to the fact that these were constantly filling up disk space, so was wondering if there was a recommendation to do this for data also? Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 25, 2016 Report post Posted July 25, 2016 i dont believe it's anything to do with lack of disk space, however did you place a checkmark in ignore prerequisite checks ? what does your ConfigMgrPrereq.log look like ? Quote Share this post Link to post Share on other sites More sharing options...
Leon1983 Posted July 25, 2016 Report post Posted July 25, 2016 I do not knowingly do this. Also FYI I ran the prerequsities checks prior to attempting the upgrade which passed. I will email you the log file Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 27, 2016 Report post Posted July 27, 2016 the issue Leon had was resolved with Microsoft's help and is documented here 1 Quote Share this post Link to post Share on other sites More sharing options...
