Jump to content


JBudd

Cannot create device collections after upgrading from SCCM 2012 to current branch

Recommended Posts

Hello all,

I recently upgraded my SCCM 2012 R2 SP1 server to the current branch. I started with 1511 and then ran the updates to get it to 1606. I wanted to create a device collection with all of the clients that needed to be upgraded. I fired up the creation wizzard and set my query up, when I click the finish button I get an error saying:

 

"Error: The SMS Provider reported an error.

General
Collection Name: test
Comment:
When I look at the SMSProv.log I see the following errors:
*** [42000][6522][Microsoft]
[sql Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "fnConvertHexStringToBinary": ~~System.FormatException: Input string was not in a correct format.~~System.FormatException: ~~   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)~~   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)~~   at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)~~   at Microsoft.SystemsManagementServer.SQLCLR.SMSUtil.ConvertHexStringToBinary(SqlString sdmBinaryString)~~. : sp_SMSGetNextID
*~*~[42000][6522][Microsoft][sql Server Native Client 11.0][sql Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "fnConvertHexStringToBinary": ~~System.FormatException: Input string was not in a correct format.~~System.FormatException: ~~ at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)~~ at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)~~ at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)~~ at Microsoft.SystemsManagementServer.SQLCLR.SMSUtil.ConvertHexStringToBinary(SqlString sdmBinaryString)~~. : sp_SMSGetNextID ThreadID : 27252 , DbError: 6522 , Sev: 16~*~*
*~*~e:\cm1606_rtm\sms\siteserver\sdk_provider\smsprov\sspcollection.cpp(934) : Unable to update collection due to SQL error.~ SQL Error: [42000][6522][Microsoft][sql Server Native Client 11.0][sql Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "fnConvertHexStringToBinary": ~~System.FormatException: Input string was not in a correct format.~~System.FormatException: ~~ at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)~~ at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)~~ at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)~~ at Microsoft.SystemsManagementServer.SQLCLR.SMSUtil.ConvertHexStringToBinary(SqlString sdmBinaryString)~~. : sp_SMSGetNextID~*~*
*~*~Unable to update collection due to SQL error. [42000][6522][Microsoft][sql Server Native Client 11.0][sql Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "fnConvertHexStringToBinary": ~~System.FormatException: Input string was not in a correct format.~~System.FormatException: ~~ at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)~~ at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)~~ at System.Byte.Parse(String s, NumberStyles style, NumberFormatInfo info)~~ at Microsoft.SystemsManagementServer.SQLCLR.SMSUtil.ConvertHexStringToBinary(SqlString sdmBinaryString)~~. : sp_SMSGetNextID~*~*
Nothing has changed on the server other than the upgrade.
I have attatched the log.

SMSProv.log

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.