Hello! I had problems similar to yours in one of the companies I advise. After three incredible months of research, testing a number of possible solutions, could definitely solve my problem by following these steps: 1 -) Go to the Windows registry (Start> Run> Regedit); 2 -) Navigate to the key HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ lanmanworkstation \ parameters; 3 -) Right-click the blank area, create a new DWORD value with the name of SessTimeout (make sure this DWORD value already exists on all servers I have discussed, none exist); 4 -) Set the value to decimal and enter the number 600 (0x258 hex will be generated), this is the time in seconds that will be considered before the timeout waiting for network availability All servers I have analyzed, I solved the problem of backups in units involving remotes networks connections that way. Hope you can help! Sorry for my english, I'm still doing classes to improve their quality. Regards, Luis Gustavo Bugallo Brazil - São Paulo - SP Quem mata o tempo, assassina oportunidades...

Hello Luis, Thanks for the clue I will try this on all the Source Servers anything to do on the Storage Device also?. Your English is perfect don't worry I am French and so having the same trouble as you we are Technician not Linguist :) Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

hello, I am getting several errors on a SQL Backup and I am looking for SCOM ideas (or others if not a good way to do it!!) to trace this issue... SCOM is already sending an alert on the job failure but now I am looking fopr more informations about the type of failure Alert: IS Package Failed Resolution state: Closed Source: MsDtsServer Path: RBPCONPROD.ad Last modified by: AD\xxxxxxx Last modified time: 7/18/2011 10:05:10 AM Alert description: Package "user_db" failed. Date 7/7/2011 7:46:14 PM Log SQL Server (Current - 7/21/2011 2:21:00 AM) Source spid60 Message Error: 18210, Severity: 16, State: 1. Date 7/1/2011 7:36:21 PM Log SQL Server (Current - 7/21/2011 2:21:00 AM) Source spid60 Message Error: 18210, Severity: 16, State: 1. Date 6/28/2011 7:38:00 PM Log SQL Server (Current - 7/21/2011 2:21:00 AM) Source spid60 Message Error: 18210, Severity: 16, State: 1. Date 6/12/2011 7:41:02 PM Log SQL Server (Archive #2 - 6/18/2011 11:20:00 PM) Source spid60 Message Error: 18210, Severity: 16, State: 1. Date 6/12/2011 7:41:02 PM Log SQL Server (Archive #2 - 6/18/2011 11:20:00 PM) Source spid60 Message BackupMedium::ReportIoError: write failure on backup device '\\XXXXX\P123_Backup\PCONPROD\user_db\payercm_backup_201106121931.bak'. Operating system error 64(The specified network name is no longer available.) Apparently there is an issue for this file which is 60 Gb from a server to the storage EMC. As it is happening several times a month (at least 6 times for the last 30 days) i need to investigate it now...Is it feasible with SCOM? Performance Views and dashboards? on NIC, Drives? Any ideas are welcome, Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Just make sure that safety standards for reading / writing of the directory where you are performing backup recording, is properly configured and adjusted to the user used in the backup routine. The timeout waiting for write response (I / O) on who ends up happening is writing / reading the directory (ie the server that is recording this device on the network). If you need anything else let me know, Regards, Luis Gustavo Bugallo Brazil - Sao Paulo - SPQuem mata o tempo, assassina oportunidades...