locked
SQL Error 241 SCCM 1610 RRS feed

  • Question

  • Good day! After updating to version SCCM 1610, daily logs (statsys.log), about the same time, an error occurs:

    Inbox notification triggered, pause for 10 seconds....	SMS_STATE_SYSTEM	15.12.2016 14:51:17	1436 (0x059C)
    Found new state messages to process, starting processing thread	SMS_STATE_SYSTEM	15.12.2016 14:51:27	1436 (0x059C)
    Thread "State Message Processing Thread #0" id:16736 started	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    total chucks loaded (1)	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 241 at record 1 for TopicType 7302: "Ошибка преобразования даты или времени из символьной строки.", Line 0 in procedure ""	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    CMessageProcessor - Non-fatal error while processing N____CMU4penm2zy.SMX	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=MSCS-SCCM.BUDZDOROV.RU SITE=BZ1 PID=10220 TID=16736 GMTDATE=Чт дек 15 11:51:27.345 2016 ISTR0="N____CMU4penm2zy.SMX" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    Thread "State Message Processing Thread #0" id:16736 was unable to process file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\N____CMU4penm2zy.SMX", moving to corrupt directory.	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    INFO: File \\?\C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\N____CMU4penm2zy.SMX does not exist. No zapping needed.	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    total chucks loaded (0)	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    Thread "State Message Processing Thread #0" id:16736 terminated normally	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)
    CThreadMgr::ThreadTerminating - All threads have stopped running	SMS_STATE_SYSTEM	15.12.2016 14:51:27	16736 (0x4160)

    Based on the file smx, this problem is not in the client and server at the primary site.
    As you can see, this is a problem conversion date. Is it possible to somehow fix it? And as critical?

    On the server Russian regional settings applied

    Sunday, December 18, 2016 10:53 AM

All replies

  • > "As you can see, this is a problem conversion date"

    There is no evidence for that in the above snippet at all. The above snippet simply says that the file doesn't exist.

    Was this a one time occurrence or does it continue to happen?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Sunday, December 18, 2016 7:45 PM
  • It happens every day, after the upgrade to version 1610 in the same time.

    Error in Russian. Here is the translation

    SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 241 at record 1 for TopicType 7302 ". Error converting from a character string or date time", Line 0 in procedure "" SMS_STATE_SYSTEM 15.12.2016 14:51:27 16736 ( 0x4160)

    Sunday, December 18, 2016 8:21 PM
  • And I want to add. On another server in another organization, after the upgrade to version 1610, also appears the same error. Exactly the same as I have. Perhaps this is a problem SCCM 1610 in Russian and problems of regional settings.

    If you want, I can download the SMX file when processing is an error

    • Edited by aled105 Sunday, December 18, 2016 8:54 PM
    Sunday, December 18, 2016 8:47 PM
  • Was this an early wave of 1610 -- installed before December 1?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, December 19, 2016 3:43 PM
  • No, it was last updated Dec. 10
    Monday, December 19, 2016 9:30 PM
  • Hi,

        Was your issue resolved?

        If there is no progress, I would suggest you contact Microsoft Customer Services and Support to get an efficient solution:

    http://support.microsoft.com/contactus/?ln=en-au

    Best Regards,

    Ray


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 27, 2016 7:22 AM
  • I can confirm you that I see the same issue with another localized version (french) with 1610


    Jean-Sébastien DUCHÊNE - www.windowstouch.fr - Microsoft Valuable Professional (MVP) Enterprise Mobility - Microsoft Student Partner (MSP) 2008/2010, MCSE : Enterprise Devices and Apps, MCSE : Private Cloud, MCTS Configuration Manager/MDOP

    Thursday, January 5, 2017 11:44 AM
  • I'm also seeing the same thing. But I'm not running a localized version, just the English one. Although I do have regional settings set to Icelandic so I don't go nuts with the US date format.

    The full message logged is the following:

    SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 241 at record 1 for TopicType 7302: "Conversion failed when converting date and/or time from character string.", Line 0 in procedure ""

    I'm running the 1610 build that was released after December 1st. The Package GUID is AF633310-E419-44B3-9E0E-AB93D57087CF.

    Saturday, January 14, 2017 10:43 PM
  • I too am seeing this.

    I upgraded 3 separate environments from 2012 R2 (to 1606 then 1610) and they all do it. Our Region is EN-NZ.

    I only upgraded them 2 weeks ago using the latest 1606 media (SW_DVD5_Sys_Ctr_ConfigMgrClt_ML_1606_MultiLang_-2_ConfMgr_SCEP_MLF_X21-32003.ISO), then of course to 1610 through the Service Connection Point...

    Wednesday, February 1, 2017 10:49 PM
  • Same issue after upgrading to 1610....
    Monday, February 20, 2017 6:25 PM
  • I can confirm you that I see the same issue with another localized version (french) with 1610


    Jean-Sébastien DUCHÊNE - www.windowstouch.fr - Microsoft Valuable Professional (MVP) Enterprise Mobility - Microsoft Student Partner (MSP) 2008/2010, MCSE : Enterprise Devices and Apps, MCSE : Private Cloud, MCTS Configuration Manager/MDOP

    Same issue. This has been fixed in SCCM 2012 R2 SP1 CU3, but appears again in 1610.

    http://microsofttouch.fr/default/b/js/posts/sccm-2012-sp2-r2-sp1-le-cumulative-update-3-de-configuration-manager-2012-sp2-r2-sp1-est-disponible

    Tuesday, April 4, 2017 8:24 AM
  • We have the same issue, since upgrading to 1610. Hotfixes are installed: KB4010155 and KB4016483.

    Is there a solution for this?

    Wednesday, April 5, 2017 2:47 PM
  • We have the same issue since upgrading to 1610. We opened a case with Microsoft and they found something to fix, which they did in 1702. However in our Case this did not solve the Problem. After talking to Microsoft again, they found additional situations which can lead to this error, which they are currently checking and plan to fix in 1706. So you should test the 1702, to see if it fixes your Problem. However if you are unlucky as we are, you probably just have to wait for 1706.

    • Proposed as answer by Jiri Hybl Tuesday, May 16, 2017 10:38 AM
    Friday, April 21, 2017 10:17 AM
  • I can confirm it's happening with 1702 and the latest hotfix. Australian Locale.
    Friday, June 16, 2017 5:34 AM
  • I can confirm it's happening with 1702 and the latest hotfix too. NZ Locale.
    Sunday, June 25, 2017 9:19 PM
  • This happens every day but about 20-30 seconds later each day.

    13/06/2017  03:07 PM             2,336 N____CMUfjzo0onz.SMX
    14/06/2017  03:08 PM             2,334 N____CMU4w1pdicr.SMX
    15/06/2017  03:08 PM             2,334 N____CMUegh12ine.SMX
    16/06/2017  03:09 PM             2,334 N____CMU3mj0jvhw.SMX
    17/06/2017  03:09 PM             2,334 N____CMUfosoafcy.SMX
    18/06/2017  03:10 PM             2,334 N____CMU05vosl3m.SMX
    19/06/2017  03:11 PM             2,334 N____CMUmr0eookn.SMX
    20/06/2017  03:11 PM             2,334 N____CMUxismxkaz.SMX
    21/06/2017  03:11 PM             2,334 N____CMUrjsfe1yz.SMX
    22/06/2017  03:12 PM             2,334 N____CMUiabdtyz0.SMX
    23/06/2017  03:12 PM             2,334 N____CMUvm2xjzll.SMX
    24/06/2017  03:13 PM             2,334 N____CMU5y0b1ztk.SMX
    25/06/2017  03:14 PM             2,336 N____CMU0m2qkobh.SMX
    26/06/2017  03:14 PM             2,336 N____CMUjh1xbjqv.SMX
    27/06/2017  03:15 PM             2,336 N____CMUughvkhug.SMX
    28/06/2017  03:15 PM             2,336 N____CMUo44oh0dx.SMX
    29/06/2017  03:16 PM             2,336 N____CMUphane3qu.SMX
    30/06/2017  03:17 PM             2,336 N____CMUptbnjxsf.SMX
    13/07/2017  08:53 AM             2,334 N____CMUuxfmjft2.SMX
    14/07/2017  08:54 AM             2,334 N____CMUvg5hv2ud.SMX
    15/07/2017  08:54 AM             2,334 N____CMUemms3154.SMX
    16/07/2017  08:55 AM             2,334 N____CMUyblnpdxl.SMX
    17/07/2017  08:56 AM             2,334 N____CMUlgyisfdo.SMX
    18/07/2017  08:56 AM             2,334 N____CMU1gdvwtco.SMX
    19/07/2017  08:56 AM             2,334 N____CMUat53fhey.SMX
    20/07/2017  08:57 AM             2,334 N____CMUjhk4kbet.SMX
    21/07/2017  08:57 AM             2,334 N____CMUhirt3mw5.SMX
    22/07/2017  08:58 AM             2,334 N____CMU3ytggqcw.SMX
    23/07/2017  08:59 AM             2,334 N____CMUnzqqe332.SMX
    24/07/2017  09:00 AM             2,334 N____CMUdzssfb0q.SMX
    25/07/2017  09:00 AM             2,336 N____CMUvueym0zz.SMX
    26/07/2017  09:01 AM             2,336 N____CMUndw4crtk.SMX

    SCCM 1702 CAS PSS of the English version with latest patch levels:

      Site = 5.00.8498.1000

      Console = 5.00.8498.1711

      Clients (~90% upgraded) = 5.00.8498.1711

    There are no other errors in the actively used hierarchy.

    Exact message text =

    SQL MESSAGE: spProcessStateReport - Error: Message processing encountered a SQL error 241 at record 1 for TopicType 7302: "Conversion failed when converting date and/or time from character string.", Line 0 in procedure ""

    The double quotes at the end of the message suggest someone made a typo in the code and the %%param is null where a procedure name should exist.

    Tuesday, July 25, 2017 11:16 PM
  • Tried with SCCM 1706 as Matt_89 suggested?
    Monday, July 31, 2017 8:08 PM
  • I have updated 3 environments to 1706 with about a week apart from each one, and I can confirn this error and the corrupt (.SMX) statesys.box files stopped occurring. I'm happy this is finally resolved.

    Steve

    • Proposed as answer by Kiwifulla2 Monday, September 18, 2017 10:38 PM
    Monday, September 18, 2017 10:38 PM