Viewing 7 posts - 1 through 7 (of 7 total)
I made the change only on the target backup server and it seems to work without having to make the change on the SQL server. I could just be getting...
November 11, 2009 at 9:38 pm
I agree 100% with you and I do this every time. However, some people don't have this option and thus I have a job.
November 11, 2009 at 4:40 pm
Confirmed I made the change to both machines the backup target and the SQL server. I am going to attempt testing this in a non production system with just the...
November 11, 2009 at 4:14 pm
Microsoft recommended editing the registry on both the SQL server and the backup location. If you find you do not have to edit this on one or the other please...
September 9, 2009 at 9:39 pm
I have called Microsoft on this issue and found that the following does work
open regedit
navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
Create a New DWORD value with the name: SessTimeout
set the value: 360 keep it...
August 28, 2009 at 2:53 pm
I have called Microsoft on this issue and found that the following does work
open regedit
navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
Create a New DWORD value with the name SessTimeout
the value to 360 keep...
August 28, 2009 at 2:49 pm
I am having the exact same issue. This is from an SQL 2008 Web Edition fully patched as of today running on Windows 2003 Ent. 64 bit backing up to...
August 27, 2009 at 10:53 am
Viewing 7 posts - 1 through 7 (of 7 total)