SMS_INVENTORY_DATA_LOADER - ][SQL Server Native Client 11.0][SQL Server]String or binary data would be truncated. : pOFFICE_PRODUCTINFO_DATA

Paczkowski, Łukasz 1 Reputation point
2020-10-14T14:02:17.32+00:00

Hi,
I found that SMS_INVENTORY_DATA_LOADER component started logging Errors

[Microsoft][SQL Server Native Client 11.0][SQL Server]String or binary data would be truncated. : pOFFICE_PRODUCTINFO_DATA

I found the problematic MIF file, looking at inventoried data of class "MICROSOFT|OFFICE_PRODUCTINFO|1.0" and comparing it to the columns in OFFICE_PRODUCTINFO_DATA table, I see that in my case value of attribute “Channel” doesn’t fit to the “Channel00” column because stored string is "Semi-Annual Enterprise Channel (Preview)" what gives 40 chars and column is limited to 30 … what should I do in this case? I cannot stop collecting this data because this is default class and cannot “uncheck” it in SCCM Client Settings/HW inventory classes, also I don’t think modification of column properties is allowed.

32327-image.png
32384-image.png
regards

Microsoft Configuration Manager Application
Microsoft Configuration Manager Application
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Application: A computer program designed to carry out a specific task other than one relating to the operation of the computer itself, typically to be used by end users.
440 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Sherry Kissinger 3,791 Reputation points
    2020-10-15T17:31:18.717+00:00

    I would open a case with Microsoft. They can guide you to the supported method to address this issue. I suspect it might be increatse the column width; but I don't know if that column width (if you were to change it) would be "reset" or cause an upgrade issue with a future upgrade of CM.

    I personally wouldn't modify the column with of a built-in table like that without engaging Microsoft ECM support.

    2 people found this answer helpful.
    0 comments No comments

  2. Tom Phillips 17,711 Reputation points
    2020-10-14T19:22:57.613+00:00

    I suggest you change your tag to msc-operations-manager-general for System Center support.

    This is not really a SQL Server problem, but an application problem.


  3. AmeliaGu-MSFT 13,956 Reputation points Microsoft Vendor
    2020-10-15T02:44:35.217+00:00

    Hi @Paczkowski, Łukasz ,

    Could you please try to increase the table data type length?
    For issue about SCCM, you can add mem-cm-general tag so that people there will help you more effectively.
    Best Regards,
    Amelia


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. Paul Jezek 1 Reputation point
    2020-10-19T22:19:38.007+00:00

    Today I opened a microsoft-case...
    Answer: This is a known bug, and it is fixed with SCCM 2006
    I can confirm this, because I updated today (from SCCM 2002)

    The case owner also mentioned that it is not supported to simply change the nvarchar(30) and highly recommended to upgrade to SCCM 2006 instead.
    As sad as it is, there is no hotfix or other (supported) workaround for this issue with SCCM 2002.

    Hope you can upgrade as soon as possible.