https://isconfigmgrdead.com/tags/sql/Recent content in Sql on Is ConfigMgr Dead?https://isconfigmgrdead.com/images/og-card.jpghttps://isconfigmgrdead.com/images/og-card.jpgHugoen-usThu, 10 Sep 2026 09:00:00 -0400https://isconfigmgrdead.com/posts/odbcdriver-20260910/Thu, 10 Sep 2026 09:00:00 -0400https://isconfigmgrdead.com/posts/odbcdriver-20260910/<p>Here&rsquo;s a fun one. When an update to the <strong>Microsoft ODBC Driver 18 for SQL Server (18.7.1.1)</strong> lands on a site server, Configuration Manager can lose its connection to the site database.</p> <p><strong>What it looks like</strong></p> <ul> <li><code>sitecomp.exe</code> crashes (exception <code>c0000005</code>), with COM+ errors (Event ID 4786) referencing <code>msodbcsql18.dll</code> in the Application log.</li> <li><code>SMSEXEC.log</code> fills with repeated failures to connect to SQL, and <code>hman.log</code> threads go quiet.</li> </ul> <p><strong>Why it happens</strong></p> <p>According to a Microsoft response in the thread, ConfigMgr ships its own older Visual C++ runtime in its install folder, and the new ODBC driver doesn&rsquo;t get along with it. Updating the system-wide VC++ redistributable alone may not fix it.</p>