Jump to content


Recommended Posts

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?

 

 

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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 ?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.