<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[MSSQL -> DCObject::isReadyForPolling: cannot obtain lock for data collection obj]]></title><description><![CDATA[<p dir="auto">I have thousands of these messages showing in the log file:</p>
<p dir="auto">DCObject::isReadyForPolling: cannot obtain lock for data collection object xxxxxx</p>
<p dir="auto">Is there something i can change to allow for more locks? or does it wait and retry the the lock on the object?</p>
<p dir="auto">(mssql 2014, windows server 2012 r2)<br />
thx<br />
__<em>_</em>___</p>
<p dir="auto">Sorry.... Netxms Version 2.1.1</p>
]]></description><link>https://forum.netxms.org/topic/5264/mssql-dcobject-isreadyforpolling-cannot-obtain-lock-for-data-collection-obj</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 17:54:47 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5264.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 28 Sep 2017 20:08:29 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to MSSQL -> DCObject::isReadyForPolling: cannot obtain lock for data collection obj on Wed, 04 Oct 2017 20:50:04 GMT]]></title><description><![CDATA[<p dir="auto"> It is internal diagnostic messages meaning that data collection scheduler was not able to work with DCI because it was locked by other part of the system. Most often it happens when DCI is locked because of database update. Other possible reason could be long running transformation scripts.<br />
If you don't experience issues with data collection and don't get "thread not responding" alarms then you can ignore those messages.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/23150</link><guid isPermaLink="true">https://forum.netxms.org/post/23150</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 04 Oct 2017 20:50:04 GMT</pubDate></item></channel></rss>