July 11, 2015 at 6:37 am
Getting "The specified network name is no longer available" during SQL Backups dumping to Network share.
- problem started occurring on July 3, 2015
- our Ola Hallengren backup solution deployed to over 150 SQL Servers.. was running fine for almost 2 years
- Occurring in multiple SQL Server environments: W/Server 2012 Ent, W/Server 2008 Ent, SQL 2012 Ent, SQL 2008 R2 Ent
- We're utilizing latest Ola Hallengren backup solution (Jan 2015 release)
- Dumping to network share (jobs running under SQL Agent account w/ local admin & sysadmin on server and full rights to Network Share
July 11, 2015 at 6:40 am
ISSUE: when running Ola Hallengren BACKUPs - Jobs fail with: 64(The specified network name is no longer available.)
--> Regarding the SQL Server backup failures, I followed these steps on a few SQL Servers and the BACKUPs worked. (thanks to the dirkhondong.wordpress.com solution we found searching this issue!!!)
Resolution: Create a DWORD (32 bit) --> named ‘Sesstimeout’ and set it’s Decimal value to 360 in:
HKLM\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
To add (or modify) the registry key Sesstimeout:
- Start/Run
- Open: Regedit (Note: Regedit32 is not found)
- Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
- Check for existence of key: Sesstimeout
- If key is not available, right mouse click and select "New" then "DWORD (32 bit) Value"
- Name it: Sesstimeout
- Double click Sesstimeout
- Click BASE / DECIMAL and give it “Value data”: 360 (you can increase this value if necessary, 360 worked for us)
- NO reboot required!!
- the above registry solution worked for us! Even on 64-bi machines, we ADDED the "DWORD (32 bit) Value"
good luck
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply