<?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 SMSQL timeout mount errors on Win2003R2x64SP2 in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SMSQL-timeout-mount-errors-on-Win2003R2x64SP2/m-p/16674#M3911</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a daily process that takes a snapshot of multiple databases on server A and then mounts those flexclones on Server B. The snapshot process on server A kicks off at a designated time and once it completes it starts the process on server B. The process on server B detaches the current databases, disconnects those drives, deletes the old flexclones, grabs the new snapshot, creates flexclones, mounts the new flexclones &amp;amp; drives up to the server and then re-attaches the databases. The process on server B is handled by a perl script that utilizes the SnapDrive/NetApp API. This all should work great but we end up having issues with server B almost weekly and to the point where we have to reboot it. The perl script and API calls become unresponsive and can't mount up the flexclones. We end up with errors like this....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ServerB: Checking input parameters&lt;/P&gt;&lt;P&gt;ServerB : Checking access control&lt;/P&gt;&lt;P&gt;ServerB : Checking policies&lt;/P&gt;&lt;P&gt;ServerB : Turning on space reservation&lt;/P&gt;&lt;P&gt;ServerB : Connecting to the LUN&lt;/P&gt;&lt;P&gt;Unable to connect to the LUN&lt;/P&gt;&lt;P&gt;Error: A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system.&lt;/P&gt;&lt;P&gt;Can't spawn "sdcli disk connect -m ServerB -p 172.xx.xx.xx:/vol/nb1serverbdb/lun01 -d W:\ -IG ServerB ServerB -dtype dedicated"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server B seems to become more and more unresponsive as we try the process/script to the point where it hangs on even trying to execute the script. At that point we reboot the server and everything runs perfectly. I am confused why Server B is becoming unresponsive and what could be causing it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me give some details about the OS and software we are running. Both server A and B are running same software.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Windows Server 2003 R2 64-Bit SP2&lt;/LI&gt;&lt;LI&gt;SQL Server 2005 SP2&lt;/LI&gt;&lt;LI&gt;SnapDrive 6.2.0.4519 &lt;/LI&gt;&lt;LI&gt;NetApp Windows Host Utilities 5.2.3297.2229&lt;/LI&gt;&lt;LI&gt;Snap Manager for SQL Server 5.0&lt;/LI&gt;&lt;LI&gt;Data ONTAP DSM for Windows MPIO 3.3.3298.1305&lt;/LI&gt;&lt;LI&gt;NetApp 7.3.3P2&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anyone else experiencing these same issues and/or have any ides what could be causing our problems?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:09:20 GMT</pubDate>
    <dc:creator>simonengelbert</dc:creator>
    <dc:date>2025-06-05T07:09:20Z</dc:date>
    <item>
      <title>SMSQL timeout mount errors on Win2003R2x64SP2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMSQL-timeout-mount-errors-on-Win2003R2x64SP2/m-p/16674#M3911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a daily process that takes a snapshot of multiple databases on server A and then mounts those flexclones on Server B. The snapshot process on server A kicks off at a designated time and once it completes it starts the process on server B. The process on server B detaches the current databases, disconnects those drives, deletes the old flexclones, grabs the new snapshot, creates flexclones, mounts the new flexclones &amp;amp; drives up to the server and then re-attaches the databases. The process on server B is handled by a perl script that utilizes the SnapDrive/NetApp API. This all should work great but we end up having issues with server B almost weekly and to the point where we have to reboot it. The perl script and API calls become unresponsive and can't mount up the flexclones. We end up with errors like this....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ServerB: Checking input parameters&lt;/P&gt;&lt;P&gt;ServerB : Checking access control&lt;/P&gt;&lt;P&gt;ServerB : Checking policies&lt;/P&gt;&lt;P&gt;ServerB : Turning on space reservation&lt;/P&gt;&lt;P&gt;ServerB : Connecting to the LUN&lt;/P&gt;&lt;P&gt;Unable to connect to the LUN&lt;/P&gt;&lt;P&gt;Error: A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system.&lt;/P&gt;&lt;P&gt;Can't spawn "sdcli disk connect -m ServerB -p 172.xx.xx.xx:/vol/nb1serverbdb/lun01 -d W:\ -IG ServerB ServerB -dtype dedicated"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server B seems to become more and more unresponsive as we try the process/script to the point where it hangs on even trying to execute the script. At that point we reboot the server and everything runs perfectly. I am confused why Server B is becoming unresponsive and what could be causing it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me give some details about the OS and software we are running. Both server A and B are running same software.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Windows Server 2003 R2 64-Bit SP2&lt;/LI&gt;&lt;LI&gt;SQL Server 2005 SP2&lt;/LI&gt;&lt;LI&gt;SnapDrive 6.2.0.4519 &lt;/LI&gt;&lt;LI&gt;NetApp Windows Host Utilities 5.2.3297.2229&lt;/LI&gt;&lt;LI&gt;Snap Manager for SQL Server 5.0&lt;/LI&gt;&lt;LI&gt;Data ONTAP DSM for Windows MPIO 3.3.3298.1305&lt;/LI&gt;&lt;LI&gt;NetApp 7.3.3P2&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anyone else experiencing these same issues and/or have any ides what could be causing our problems?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:09:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMSQL-timeout-mount-errors-on-Win2003R2x64SP2/m-p/16674#M3911</guid>
      <dc:creator>simonengelbert</dc:creator>
      <dc:date>2025-06-05T07:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: SMSQL timeout mount errors on Win2003R2x64SP2</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMSQL-timeout-mount-errors-on-Win2003R2x64SP2/m-p/16678#M3912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;UPDATE: We upgraded SnapDrive on the Windows 2003 server to 6.3.0.4601 and that has helped tremendously. We are still having issues but the need to reboot the server is rare now&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Nov 2010 20:07:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMSQL-timeout-mount-errors-on-Win2003R2x64SP2/m-p/16678#M3912</guid>
      <dc:creator>simonengelbert</dc:creator>
      <dc:date>2010-11-18T20:07:17Z</dc:date>
    </item>
  </channel>
</rss>

