View Full Version : The description for Event ID 65535 from source VSS Keep-aliv
sgilmer
10-29-2010, 01:42 PM
Has any one seen this error, I am getting this error on my ds-client (windows 7 64bit). I am seeing it when backing up a 2008 server and a 2003 server. I get about 10gb backed up and then i start to see The description for Event ID 65535 from source VSS Keep-alive cannot be found in the asigra logs. when i check the windows log i get this error:
The description for Event ID 65535 from source VSS Keep-alive cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The specified network name is no longer available.
terrydavis
10-29-2010, 02:14 PM
What's the output of 'vssadmin list writers' on the source server?
sgilmer
10-29-2010, 02:38 PM
DISKSHADOW> list writers status
Listing writer status information ...
* WRITER "System Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {e8132975-6f93-4464-a53e-1050253ae220}
- Writer instance ID: {44529e49-d8ed-496f-b566-81e21f780db7}
* WRITER "ASR Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
- Writer instance ID: {2f22cd21-fbca-4458-a3c7-0741f286af0a}
* WRITER "Shadow Copy Optimization Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
- Writer instance ID: {b4431843-32aa-44dd-beb4-7ab87a47579d}
* WRITER "Registry Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {afbab4a2-367d-4d15-a586-71dbb18f8485}
- Writer instance ID: {f9e05f74-7a8a-4287-99c5-98ef0ebb19ba}
* WRITER "FRS Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {d76f5a28-3092-4589-ba48-2958fb88ce29}
- Writer instance ID: {d49c489b-9aa1-42d9-80fa-b770e8f74903}
* WRITER "IIS Config Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
- Writer instance ID: {4e828d49-a8a1-4765-923a-0d49d31d0f79}
* WRITER "IIS Metabase Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
- Writer instance ID: {7e7c8066-7ee0-4a23-9bca-04e8dde8194a}
* WRITER "COM+ REGDB Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {542da469-d3e1-473c-9f4f-7847f01fc64f}
- Writer instance ID: {46e7f9e4-e106-4420-a064-1d7fdd42e4ef}
* WRITER "NTDS"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
- Writer instance ID: {08ecbbcd-390d-4248-a362-af7f7369d504}
* WRITER "BITS Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {4969d978-be47-48b0-b100-f328f07ac1e0}
- Writer instance ID: {8ee13d84-cfcd-4cb4-8f69-7fe2614bcbf2}
* WRITER "WMI Writer"
- Status: 1 (VSS_WS_STABLE)
- Writer failure code: 0x00000000 (S_OK)
- Writer ID: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
- Writer instance ID: {cda14aa8-e20b-4295-91a0-0e1faef6b71a}
Number of writers listed: 11
sgilmer
10-29-2010, 02:39 PM
i dont have vsadmin on this server but i do have diskshadow
terrydavis
10-29-2010, 02:58 PM
Try running this on the source server:
1. Start | Run
2. cmd
3. cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
sgilmer
11-02-2010, 11:03 AM
I tried this on the ds-client and 2008 server. I think it is the same thing you asked me to do but for 2008
net stop "System Event Notification Service"
net stop "Background Intelligent Transfer Service"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ATL.DLL
regsvr32 /s comsvcs.DLL
regsvr32 /s credui.DLL
regsvr32 /s CRYPTNET.DLL
regsvr32 /s CRYPTUI.DLL
regsvr32 /s dhcpqec.DLL
regsvr32 /s dssenh.DLL
regsvr32 /s eapqec.DLL
regsvr32 /s esscli.DLL
regsvr32 /s FastProx.DLL
regsvr32 /s FirewallAPI.DLL
regsvr32 /s kmsvc.DLL
regsvr32 /s lsmproxy.DLL
regsvr32 /s MSCTF.DLL
regsvr32 /s msi.DLL
regsvr32 /s msxml3.DLL
regsvr32 /s ncprov.DLL
regsvr32 /s ole32.DLL
regsvr32 /s OLEACC.DLL
regsvr32 /s OLEAUT32.DLL
regsvr32 /s PROPSYS.DLL
regsvr32 /s QAgent.DLL
regsvr32 /s qagentrt.DLL
regsvr32 /s QUtil.DLL
regsvr32 /s raschap.DLL
regsvr32 /s RASQEC.DLL
regsvr32 /s rastls.DLL
regsvr32 /s repdrvfs.DLL
regsvr32 /s RPCRT4.DLL
regsvr32 /s rsaenh.DLL
regsvr32 /s SHELL32.DLL
regsvr32 /s shsvcs.DLL
regsvr32 /s /i swprv.DLL
regsvr32 /s tschannel.DLL
regsvr32 /s USERENV.DLL
regsvr32 /s vss_ps.DLL
regsvr32 /s wbemcons.DLL
regsvr32 /s wbemcore.DLL
regsvr32 /s wbemess.DLL
regsvr32 /s wbemsvc.DLL
regsvr32 /s WINHTTP.DLL
regsvr32 /s WINTRUST.DLL
regsvr32 /s wmiprvsd.DLL
regsvr32 /s wmisvc.DLL
regsvr32 /s wmiutils.DLL
regsvr32 /s wuaueng.DLL
sfc /SCANFILE=%windir%\system32\catsrv.DLL
sfc /SCANFILE=%windir%\system32\catsrvut.DLL
sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL
net start "COM+ Event System"
sgilmer
11-02-2010, 11:04 AM
the commands above did not help at all, I get about 8gb backed up and then I start to receive the error.
sgilmer
11-09-2010, 01:19 PM
just wanted to know if any has seen this yet
terrydavis
11-09-2010, 01:28 PM
Do you have another process or backup program using VSS? Any anti-virus?
jjohnsen
11-15-2010, 09:58 AM
Hi
I have the same problem so i am just putting an ear to this thread :)
sgilmer
11-15-2010, 11:29 AM
By default a 2008 default domain GPO is set to only allow a 10hr connection to any service in that domain after that time has been reached the service will be disconnected. This is where you go to change that setting. This is the fix Asigra suggested and I am testing now. This is a little frustrating since I have spent about 10rh’s trouble shooting with Microsoft.
default Domain Policy/Computer settings/Policies/Security Settings/Acount Policies/Kerberos Policy
maximum lifetime for service ticket by default is 600 min (10hr)
maximum lifetime for user ticket by default is 10 hours
change it accordingly
terrydavis
11-16-2010, 03:20 PM
Whoa, this is the tip of the year. They must have just found this because I have wrestled with this before with Asigra.
sgilmer
11-16-2010, 03:37 PM
yes and it works, are problem is now fixed. this fix allies to 2003 domains and 2008 domains
terrydavis
11-16-2010, 05:27 PM
This problem hasn't been around forever though. I also have customers that have sets that run forever due to bandwidth issues. Did they indicate if it is only related to 2008 R2 sources or is it dsclient host OS related?
sgilmer
11-17-2010, 01:14 PM
I have clients with small pipes as well that have jobs which take a long time to finish as well that never have this issue. I am sure that this setting is in their default GPO and i would expect it to affect them but it does not. If you do see the issue then it could be this, it did fix two problems at clients sites and they wear running 2008 and 2003 domains.
sgilmer
11-17-2010, 01:16 PM
they did not say if the problem was related to the ds-client or just the OS.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.