SMS SQL Error

Author
ssears
New Member
  • Total Posts : 7
  • Scores: 0
  • Reward points: 0
  • Joined: 2005/02/15 11:33:25
  • Location: Lakewood CO
  • Status: offline
2005/02/15 12:30:46 (permalink)
0

SMS SQL Error

Not sure if this should go here or under SQL but.....
I' m running SMS 2003 sp1 with a SQL 2000 database. I' ve started receiving the following error via sms_discovery_data_manager:

Microsoft SQL Server reported SQL message 8152, severity 16: [22001][8152][Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated.
I checked my SQL logs and there are no errors. Any ideas?
#1

11 Replies Related Threads

    curban
    Expert Member
    • Total Posts : 612
    • Scores: 35
    • Reward points: 14550
    • Joined: 2002/08/19 11:04:09
    • Location: Kenosha, WI
    • Status: offline
    RE: SMS SQL Error 2005/02/15 13:06:23 (permalink)
    0
    Have you performed a Site Reset yet?

    Chris
    MCT, MCSE, and Former-MVP
    ITIL v3.0 Foundation Certified
    MBA
    #2
    ssears
    New Member
    • Total Posts : 7
    • Scores: 0
    • Reward points: 0
    • Joined: 2005/02/15 11:33:25
    • Location: Lakewood CO
    • Status: offline
    RE: RE: SMS SQL Error 2005/02/15 13:18:50 (permalink)
    0
    Why would I want to do a site reset? My security hasn' t change (advanced security). This is my central site and it hasn' t had any changes make to it other than 2 addresses added.
    #3
    mserafine
    Expert Member
    • Total Posts : 1449
    • Scores: 163
    • Reward points: 6280
    • Joined: 2003/04/07 11:57:43
    • Status: offline
    RE: SMS SQL Error 2005/02/15 17:09:51 (permalink)
    0
    Data is trying to be inserted into a field that has maximum character length, and it sounds like the data exceeds this limit.

    Possibly there' s a resource with a rather long name or other property that SMS has discovered and is now trying to add to the database.

    Are there any bad DDR' s that you can look through, which might indicate this?

    Mark Serafine | Senior PFE - Manageability (ConfigMgr) | Microsoft Corporation
    #4
    ssears
    New Member
    • Total Posts : 7
    • Scores: 0
    • Reward points: 0
    • Joined: 2005/02/15 11:33:25
    • Location: Lakewood CO
    • Status: offline
    RE: RE: SMS SQL Error 2005/02/15 17:17:01 (permalink)
    0
    The DDR.box folder is empty but I do have messages saying: SMS Discovery Data Manager failed to process the discovery data record (DDR) " " , because it cannot update the data source.
    #5
    mserafine
    Expert Member
    • Total Posts : 1449
    • Scores: 163
    • Reward points: 6280
    • Joined: 2003/04/07 11:57:43
    • Status: offline
    RE: SMS SQL Error 2005/02/15 17:33:26 (permalink)
    0
    Is the " BAD_DDRS" directory under the DDM.box also empty?

    Mark Serafine | Senior PFE - Manageability (ConfigMgr) | Microsoft Corporation
    #6
    ssears
    New Member
    • Total Posts : 7
    • Scores: 0
    • Reward points: 0
    • Joined: 2005/02/15 11:33:25
    • Location: Lakewood CO
    • Status: offline
    RE: RE: SMS SQL Error 2005/02/15 17:35:33 (permalink)
    0
    Yes
    #7
    mserafine
    Expert Member
    • Total Posts : 1449
    • Scores: 163
    • Reward points: 6280
    • Joined: 2003/04/07 11:57:43
    • Status: offline
    RE: SMS SQL Error 2005/02/16 09:53:47 (permalink)
    0
    What does the DDM.log say? Does it contain any more detail about the error?

    Mark Serafine | Senior PFE - Manageability (ConfigMgr) | Microsoft Corporation
    #8
    ssears
    New Member
    • Total Posts : 7
    • Scores: 0
    • Reward points: 0
    • Joined: 2005/02/15 11:33:25
    • Location: Lakewood CO
    • Status: offline
    RE: RE: SMS SQL Error 2005/02/16 10:30:07 (permalink)
    0
    Following is a portion of the DDM.log:
    ==>Name = <WSNAMEXXX> $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.341 2005 Mountain Standard Time><thread=6004 (0x1774)>
    *** insert into System_SMS_Assign_ARR (ItemKey, SMS_Assigned_Sites0) values (7421, " SMS:BCD" )~ $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.341 2005 Mountain Standard Time><thread=6004 (0x1774)>
    *** [22001][8152][Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.341 2005 Mountain Standard Time><thread=6004 (0x1774)>
    *** insert into System_SMS_Assign_ARR (ItemKey, SMS_Assigned_Sites0) values (7421, " SMS:BCD" )~ $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.357 2005 Mountain Standard Time><thread=6004 (0x1774)>
    *** [01000][3621][Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.357 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverySource_SQL::UpdateItem - could not execute sql- insert into System_SMS_Assign_ARR (ItemKey, SMS_Assigned_Sites0) values (7421, " SMS:BCD" )~ $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.373 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverDataManager::ProcessDDRs_PS - Unable to update data source $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.373 2005 Mountain Standard Time><thread=6004 (0x1774)>
    STATMSG: ID=2636 SEV=E LEV=M SOURCE=" SMS Server" COMP=" SMS_DISCOVERY_DATA_MANAGER" SYS=IBCDENSMSC01 SITE=BCA PID=2192 TID=6004 GMTDATE=Wed Feb 16 08:34:09.373 2005 ISTR0=" " ISTR1=" " ISTR2=" " ISTR3=" " ISTR4=" " ISTR5=" " ISTR6=" " ISTR7=" " ISTR8=" " ISTR9=" " NUMATTRS=0 $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.373 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverDataManager::ProcessDDRs_PS - SQL problem detected. Will retry later. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.388 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverDataManager::Process - Failed to manage files in inbox. Will retry in at least 60 seconds $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:34:09.388 2005 Mountain Standard Time><thread=6004 (0x1774)>
    Refreshing site settings..... $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:08.014 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverDataManager::GetSiteStatus - Registering SQL types, Server = IBCDENSMSC01, Database = SMS_BCA, User = $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:08.061 2005 Mountain Standard Time><thread=6004 (0x1774)>
    Preparing to sync deletes... $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:08.061 2005 Mountain Standard Time><thread=6004 (0x1774)>
    No system deletions to replicate. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:08.076 2005 Mountain Standard Time><thread=6004 (0x1774)>
    Processing file w06519k5.DDR $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:11.311 2005 Mountain Standard Time><thread=6004 (0x1774)>
    Processing <System> #7421... $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:11.311 2005 Mountain Standard Time><thread=6004 (0x1774)>
    CDiscoverySource::VerifyClientPublicKeys - Trusted report does not contain public key information. Trust will be honored. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Feb 16 01:35:11.326 2005 Mountain Standard Time><thread=6004 (0x1774)>
    #9
    brogers
    Expert Member
    • Total Posts : 8292
    • Scores: 292
    • Reward points: 0
    • Joined: 2001/06/05 11:19:00
    • Location: Jacksonville, Florida
    • Status: offline
    RE: SMS SQL Error 2005/02/16 14:51:14 (permalink)
    0
    Is your sql server running?

    Out of disk space?

    Any errors within SQL server enterprise manager? can you even open it?


    Brian Rogers
    MVP, MCSE
    Senior Consultant, Collective Technologies
    rogersb@colltech.com

    -- Dude, Seriously!
    #10
    ssears
    New Member
    • Total Posts : 7
    • Scores: 0
    • Reward points: 0
    • Joined: 2005/02/15 11:33:25
    • Location: Lakewood CO
    • Status: offline
    RE: RE: SMS SQL Error 2005/02/16 15:04:36 (permalink)
    0
    The SQL server is up, I have 653GIG available and there are no errors withing the SQL server
    However I may have found the problem. In the DDM.log only one workstation is listed. I checked it in SMS and SQL and it has the site code listed as SMS:BCD. Since we all know the site code can only be 3 characters I think this listing maybe the problem since all the sql folks I' ve been in contact with say the error is because the colum isn' t big enough for the entry. I' m going to delete the workstation from SMS and see if that clears the error. I' ll let you know what happens

    Stan
    #11
    brogers
    Expert Member
    • Total Posts : 8292
    • Scores: 292
    • Reward points: 0
    • Joined: 2001/06/05 11:19:00
    • Location: Jacksonville, Florida
    • Status: offline
    RE: SMS SQL Error 2005/02/16 17:32:56 (permalink)
    0
    Ya lost me on that last reply...but let me know how it works out! :)

    Brian Rogers
    MVP, MCSE
    Senior Consultant, Collective Technologies
    rogersb@colltech.com

    -- Dude, Seriously!
    #12
    Jump to:
    © 2018 APG vNext Commercial Version 5.5