<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic sql.preg timeout period expired in Storage Software</title>
    <link>https://community.hpe.com/t5/storage-software/sql-preg-timeout-period-expired/m-p/4519602#M82</link>
    <description>Receiving period emails from various VSQLs. Nothing appears to be harmed so I've been ignoring them.  Should I increase a timeout seeting somewhere?  If so, where?&lt;BR /&gt;&lt;BR /&gt;message: Volume C:\SQLMounts\PRODDATA\OTGPRD\Data\sql.preg from instance OTGPRD failed with error This operation returned because the timeout period expired.&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Oct 2009 18:11:22 GMT</pubDate>
    <dc:creator>Tammy Lawson</dc:creator>
    <dc:date>2009-10-22T18:11:22Z</dc:date>
    <item>
      <title>sql.preg timeout period expired</title>
      <link>https://community.hpe.com/t5/storage-software/sql-preg-timeout-period-expired/m-p/4519602#M82</link>
      <description>Receiving period emails from various VSQLs. Nothing appears to be harmed so I've been ignoring them.  Should I increase a timeout seeting somewhere?  If so, where?&lt;BR /&gt;&lt;BR /&gt;message: Volume C:\SQLMounts\PRODDATA\OTGPRD\Data\sql.preg from instance OTGPRD failed with error This operation returned because the timeout period expired.&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Oct 2009 18:11:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/sql-preg-timeout-period-expired/m-p/4519602#M82</guid>
      <dc:creator>Tammy Lawson</dc:creator>
      <dc:date>2009-10-22T18:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: sql.preg timeout period expired</title>
      <link>https://community.hpe.com/t5/storage-software/sql-preg-timeout-period-expired/m-p/4519603#M83</link>
      <description>SQL.preg contains the registry keys that are copied from live SQL node to backup SQL node during a failover or rehost.  The message indicates either 1) a network issue or 2) a storage issue.  You can adjust the timeout value also (Right click OTGPRD in Application tab, Probe configuration.&lt;BR /&gt;&lt;BR /&gt;Probe Configuration:&lt;BR /&gt;Timeout (seconds): 45 seconds is the max we should consider.&lt;BR /&gt;&lt;BR /&gt;1) Network - &lt;BR /&gt;Make certain you have current NIC drivers, esp if using Broadcom.  &lt;BR /&gt;Verify all the network config stuff - Public has discourage admin.  Admin network has admin traffic configured.  &lt;BR /&gt;Verify Flow control, RSS and all offloads are disbled on ALL nics; &lt;BR /&gt;Public NIC should be first followed by the admin network in the Network Bindings&lt;BR /&gt;&lt;BR /&gt;Admin Network Interface Card (NIC) &lt;BR /&gt;* Disable NetBIOS over = TCP/IP&lt;BR /&gt;* Remove the checkmark for Client for Microsoft and File and Print sharing.&lt;BR /&gt;* IP properties - Advanced - DNS tab - Uncheck â  Register this connectionâ  s addresses in DNS.â   This is checked by default&lt;BR /&gt;* Do not list any DNS servers for the private NICs.&lt;BR /&gt;* Remove File and Print Sharing for Microsoft Networks &lt;BR /&gt;* Leave the DNS and WINS fields blank on the private interfaces. &lt;BR /&gt;&lt;BR /&gt;2) Storage - verify not using unsupported storport driver and current or 1 revision back miniport driver.  All storage VAR require minimum of this driver version.&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/932755" target="_blank"&gt;http://support.microsoft.com/kb/932755&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 24 Oct 2009 11:51:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/sql-preg-timeout-period-expired/m-p/4519603#M83</guid>
      <dc:creator>Dan Tyndale</dc:creator>
      <dc:date>2009-10-24T11:51:35Z</dc:date>
    </item>
  </channel>
</rss>

