Can't mount backups on PP1 since patches applied
- I came across this issue by chance a couple days back and it currently has me stumped. I've filed a bug on Connect with some more details. Hopefully someone has some more suggestions for me.
It seems that I'm not able to open any of my backups to retrieve files even though the backups appear to be good. The symptom is that the backup mount process gets to 3% and then fails saying that the backup service may not be running. This occurs on all of the client systems I've tried (I tried it on four of our six PC's). It occurs with all of the backups I've tried (I've tried several backups from different PC's on each of the four PC's tested). I can run the WHS console from any of our PC's (except one now, more on that below) and the WHS Connector is working as well. The issue seems to be limited to communication with the backup service.
I went through the WHS logs but the only errors I'm seeing are in the WHS Console logs (Error: Client [guid] not found by BackupHelpers.FindClient and Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException:[guid]). Unfortunately it's been long enough since this started that I've lost a few days worth of logs. My oldest ones are dated August 16th. Everything else looks clean. The WHS Event logs just stop registering backups after the 13th with no errors.
The only correlation to this time period I've been able to find was that I applied several OS patches August 14th but didn't reboot until the 20th. The patches applied look pretty harmless so I'm not sure if they had direct impact on anything.
kb953839 - ActiveX - http://support.microsoft.com/kb/953839/en-us
kb951066 - Outlook Express - http://support.microsoft.com/kb/951066/en-us
kb951072-v2 - Time Zone update - http://support.microsoft.com/kb/951072/en-us
kb950974 - remote code execution - http://support.microsoft.com/kb/950974/en-us
kb952954 - Windows image color management - http://support.microsoft.com/kb/952954/en-us
I checked the backup database, no errors found. Ran the repair feature in PP1, no errors found. I've rebooted the server and clients at least twice since I discovered the errors. I then chose a victim and uninstalled the WHS connector software. After uninstalling and rebooting the connector software won't fully reinstall. The initial install goes fine but then the 2nd part where backups are configured breaks and the same error comes up - the backup service may not be running (it is).
I found in a couple other threads references to issues with add-ins so I went ahead and uninstalled the add-ins I was using but that didn't help either.
I'm starting to run out of ideas and I really do need some of the data in the backups restored so if anyone else has any suggestions, let me know. I may attempt a restore to a virtual PC just for kicks.
답변
- Ok, I figured out what is failing. I feel a little silly that it took me so long to figure it out since it's a pretty basic troubleshooting step. I also have no idea why it is failing other than the obvious misconfiguration.
For whatever reason, the windows firewall has started blocking TCP port 8912. The backup service communication is not happening over the RDP port so while RDP is working fine (you can use Remote Desktop and the WHS console) but any time the WHS client tries to connect to the backup service it fails after a timeout.
From the client this is easy to see. As soon as I attempt to open a backup netstat shows a port connection to 8912 on the server as SYN_SENT but that never transitions to ESTABLISHED. Before breaking out the sniffer I decided to just disable the firewall on WHS. Magically I was able to open backups. :)
I have NOT messed with the Windows Firewall on WHS other than to add a couple additional exceptions necessary for 3rd party apps running on the server. So the big question is, what caused the change and removed the exception for WHS backup communication?
Can someone share with me what they have as far as default exceptions for the Windows Firewall on WHS? The only WHS related exception I have is "Windows Home Server Transport Service" (TCP 1138) at this point. Oh, and lots of Windows Media Connect exceptions that I can delete since I'm not using Media Connect.
I'm wondering if I should just add whsbackup.exe to the exceptions list and not worry about how this broke...
- 답변으로 표시됨tfieldho 2008년 9월 5일 금요일 오후 6:25
- Hi,
Nice to hear you found the problem.
The firewall rules are:
Service or Protocol
Ports
Scope
HTTP
TCP 55000
Subnet
HTTPS
TCP 56000
Subnet
Windows Home Server Computer Backup
TCP 8912
Subnet
Windows Home Server Transport Service
TCP 1138
Subnet
This is taken from the 'Troubleshooting WHS Connector' available here.
Colin
If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.- 답변으로 표시됨Lara Jones중재자2008년 9월 5일 금요일 오후 5:07
- tfieldho said:
Ok, I figured out what is failing. I feel a little silly that it took me so long to figure it out since it's a pretty basic troubleshooting step. I also have no idea why it is failing other than the obvious misconfiguration.
For whatever reason, the windows firewall has started blocking TCP port 8912. The backup service communication is not happening over the RDP port so while RDP is working fine (you can use Remote Desktop and the WHS console) but any time the WHS client tries to connect to the backup service it fails after a timeout.
From the client this is easy to see. As soon as I attempt to open a backup netstat shows a port connection to 8912 on the server as SYN_SENT but that never transitions to ESTABLISHED. Before breaking out the sniffer I decided to just disable the firewall on WHS. Magically I was able to open backups. :)
I have NOT messed with the Windows Firewall on WHS other than to add a couple additional exceptions necessary for 3rd party apps running on the server. So the big question is, what caused the change and removed the exception for WHS backup communication?
Can someone share with me what they have as far as default exceptions for the Windows Firewall on WHS? The only WHS related exception I have is "Windows Home Server Transport Service" (TCP 1138) at this point. Oh, and lots of Windows Media Connect exceptions that I can delete since I'm not using Media Connect.
I'm wondering if I should just add whsbackup.exe to the exceptions list and not worry about how this broke...
Here are the links to the technical briefs. They home networking brief contains the chart Colin posted above.
Windows Home Server Technical Brief for Home Computer Backup and Restore
Windows Home Server Technical Brief for Home Networking
Windows Home Server - Remote Access
Windows Home Server Technical Brief for Media Sharing
Thanks
Lara Jones [MSFT] Windows Home Server Team- 답변으로 표시됨tfieldho 2008년 9월 5일 금요일 오후 6:27
모든 응답
Please try starting a manual backup from one or more clients, when it fails please have a look at the eventlogs on the client and server and the most recent log in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs.
brubber wrote: Please try starting a manual backup from one or more clients, when it fails please have a look at the eventlogs on the client and server and the most recent log in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs.
Here's the client logs:
WHSTrayApp.082808_2940.log[8/28/2008 11:00:34 AM b80] Health healthy icon is 0x8012D
[8/28/2008 11:00:34 AM b80] Health at risk icon is 0x60131
[8/28/2008 11:00:34 AM b80] Health critical icon is 0xD012F
[8/28/2008 11:00:34 AM b80] Backup blue icon is 0x10133
[8/28/2008 11:00:34 AM b80] Password sync icon is 0x10135
[8/28/2008 11:00:34 AM b80] Transport offline icon is 0x10137
[8/28/2008 11:00:34 AM b80] Transport upgrade icon is 0x10139
[8/28/2008 11:00:34 AM b80] Silent upgrade icon is 0x1013B
[8/28/2008 11:00:34 AM b80] Silent upgrade icon is 0x1013D
[8/28/2008 11:00:35 AM b80] WARN : SingleIconTrayApplication::UpdateTrayData active operation=HealthTrayOperation(0x1DED20), activeOperationChanged=1
[8/28/2008 11:00:35 AM b80] WARN : SingleIconTrayApplication::UpdateTrayData changing icon from (0x0) to (0x8012D)
[8/28/2008 11:00:35 AM b80] ERROR: Trying to update an app that is not added to the tray
[8/28/2008 11:00:35 AM b80] ERROR: hr=0x80070057 (at func: SingleIconTrayApplication::UpdateTrayData, d:\wssg_src\whs_pp1\qhs\src\client\trayapp\singleicontrayapplication.cpp (1068)) Tray::Instance().UpdateApplication(*this) 0
[8/28/2008 11:00:35 AM b80] Icon for app 0x1DEEF4 is now 0x8012D
[8/28/2008 11:01:08 AM b80] WARN: BackupTrayOperation::UpdateMenu - disabling backup now, state=0console.082808_1008.log[8/28/2008 11:01:12 AM a28] WARN : !result failed (last error = 2) (at func: SecretStore::LoadBlob, d:\wssg_src\whs_pp1\qhs\src\client\common\inc\secretstore.h (197))
[8/28/2008 11:01:18 AM a28] WARN : !result failed (last error = 2) (at func: SecretStore::DiscardSecret, d:\wssg_src\whs_pp1\qhs\src\client\common\inc\secretstore.h (124))
[8/28/2008 11:01:19 AM a28] m_PartnerManager.CoCreateInstance.
[8/28/2008 11:01:19 AM a28] Calling m_PartnerManager.GetServerInfo.
[8/28/2008 11:01:19 AM a28] m_PartnerManager.GetServerInfo returns 0x0.
[8/28/2008 11:01:19 AM a28] Calling m_PartnerManager.GetServerDetails.
[8/28/2008 11:01:30 AM a28] m_PartnerManager.GetServerDetails returns 0x0.
[8/28/2008 11:01:30 AM a28] WARN : CreateAndConnectRdp - admin name is SERVER\Administrator.
[8/28/2008 11:01:30 AM a28] Connecting to SERVER at path C:\Program Files\Windows Home Server\
[8/28/2008 11:01:38 AM a28] Got data from virtual channel: P .- Home Server console log
[1]080828.110033.9916: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110033.9916: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110043.9917: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110043.9917: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110103.9920: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110103.9920: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110137.0237: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110137.0237: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110207.6959: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110207.6959: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110317.9781: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110317.9781: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
[1]080828.110541.5268: Error: Client 8180e705-5da3-4fdc-9751-4d39087b7646 not found by BackupHelpers.FindClient
[1]080828.110541.5268: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 8180e705-5da3-4fdc-9751-4d39087b7646
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
I've tried starting a manual backup from the WHS console running on the client and also from the WHS system. There's no error reported - it doesn't appear to even try to start a backup after asking for the backup name.
I had to dig a little to find the log on the Vista client since junction points don't seem to work very well with the explorer. Grabbing the full path and pasting it into the explorer path was the easiest way to get around that but I learned a bit about junction points in the meantime. Didn't know about the /al switch. But I digress.
I'm on vacation and am heading for a rental property for a few days. I doubt there will be Internet access but if there is, I'll check in. Worst case, I'll be back online September 2nd. Hi Tom,
Let us know when you're back, we'll try and deal with the issue then (If WHS team hasn't solved it already for you).
Have a nice holiday!
- thanks
brubber wrote: Let us know when you're back, we'll try and deal with the issue then (If WHS team hasn't solved it already for you).
Have a nice holiday!
I'm back; welcomed home by red and yellow warnings in the Home Server Console since WHS has finally determined that my systems haven't been backed up for more than two weeks (shocking!).
I honestly haven't given this much thought while out of the house but now that I'm back I'm thinking I will try a restore to a vm to see if that fails as well.
Update: no luck. The restore cd appears to be connecting to the server (password hint is correct) but authentication doesn't occur (can type anything I want for the password and still get the same error) "An unknown network error has occurred during the PC Restore." Sigh.I guess the positive side of this is there aren't dozens of others having this issue as well. :|
- This evening I tried changing the duplex settings on one of my systems and resetting the network adapter in WHS. The WHS machine is on a gigabit switch. The systems I've been testing from are 100 megabit and were auto-negotiating to full duplex.
Changing to half-duplex didn't change the behavior. Can't get past the initial password prompt when attempting to connect via the restore CD and can't get past 3% mounting a backup volume.
:(
- Could you please submit a bug on Connect? Please include logs collected by the toolkit from your server and one or more affected clients (though the issue is probably not going to be related to the clients in this case).
I'm not on the WHS team, I just post a lot. :) - Bug has been filed.
https://connect.microsoft.com/WindowsHomeServer/feedback/ViewFeedback.aspx?FeedbackID=363342- 편집됨tfieldho 2008년 9월 4일 목요일 오후 4:22made url a link
- Great, thanks! I had missed that up above.What happens when you try booting one of your client PCs with the Restore CD? Does the Restore CD find your server automatically? Do you have to manually enter your server's name or IP address to view backups? Can you just not get it to connect to your server at all?
I'm not on the WHS team, I just post a lot. :) - Ken Warren said:
Great, thanks! I had missed that up above.
What happens when you try booting one of your client PCs with the Restore CD? Does the Restore CD find your server automatically? Do you have to manually enter your server's name or IP address to view backups? Can you just not get it to connect to your server at all?
I'm not on the WHS team, I just post a lot. :)
Hey Ken, The Restore CD finds the server automatically. No name or IP address required. I know it's connecting to the server because I receive the correct password hint back. Authentication appears to be broken since it doesn't matter what I type into the password field. I can fill it with random characters or the correct password and either way the behavior is identical and the same error is returned.
Not sure why MS is ticking off a percentage loaded (up to 3%) when the password hasn't even been validated yet. :O - Ok, I figured out what is failing. I feel a little silly that it took me so long to figure it out since it's a pretty basic troubleshooting step. I also have no idea why it is failing other than the obvious misconfiguration.
For whatever reason, the windows firewall has started blocking TCP port 8912. The backup service communication is not happening over the RDP port so while RDP is working fine (you can use Remote Desktop and the WHS console) but any time the WHS client tries to connect to the backup service it fails after a timeout.
From the client this is easy to see. As soon as I attempt to open a backup netstat shows a port connection to 8912 on the server as SYN_SENT but that never transitions to ESTABLISHED. Before breaking out the sniffer I decided to just disable the firewall on WHS. Magically I was able to open backups. :)
I have NOT messed with the Windows Firewall on WHS other than to add a couple additional exceptions necessary for 3rd party apps running on the server. So the big question is, what caused the change and removed the exception for WHS backup communication?
Can someone share with me what they have as far as default exceptions for the Windows Firewall on WHS? The only WHS related exception I have is "Windows Home Server Transport Service" (TCP 1138) at this point. Oh, and lots of Windows Media Connect exceptions that I can delete since I'm not using Media Connect.
I'm wondering if I should just add whsbackup.exe to the exceptions list and not worry about how this broke...
- 답변으로 표시됨tfieldho 2008년 9월 5일 금요일 오후 6:25
- Hi,
Nice to hear you found the problem.
The firewall rules are:
Service or Protocol
Ports
Scope
HTTP
TCP 55000
Subnet
HTTPS
TCP 56000
Subnet
Windows Home Server Computer Backup
TCP 8912
Subnet
Windows Home Server Transport Service
TCP 1138
Subnet
This is taken from the 'Troubleshooting WHS Connector' available here.
Colin
If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.- 답변으로 표시됨Lara Jones중재자2008년 9월 5일 금요일 오후 5:07
- tfieldho said:
Ok, I figured out what is failing. I feel a little silly that it took me so long to figure it out since it's a pretty basic troubleshooting step. I also have no idea why it is failing other than the obvious misconfiguration.
For whatever reason, the windows firewall has started blocking TCP port 8912. The backup service communication is not happening over the RDP port so while RDP is working fine (you can use Remote Desktop and the WHS console) but any time the WHS client tries to connect to the backup service it fails after a timeout.
From the client this is easy to see. As soon as I attempt to open a backup netstat shows a port connection to 8912 on the server as SYN_SENT but that never transitions to ESTABLISHED. Before breaking out the sniffer I decided to just disable the firewall on WHS. Magically I was able to open backups. :)
I have NOT messed with the Windows Firewall on WHS other than to add a couple additional exceptions necessary for 3rd party apps running on the server. So the big question is, what caused the change and removed the exception for WHS backup communication?
Can someone share with me what they have as far as default exceptions for the Windows Firewall on WHS? The only WHS related exception I have is "Windows Home Server Transport Service" (TCP 1138) at this point. Oh, and lots of Windows Media Connect exceptions that I can delete since I'm not using Media Connect.
I'm wondering if I should just add whsbackup.exe to the exceptions list and not worry about how this broke...
Here are the links to the technical briefs. They home networking brief contains the chart Colin posted above.
Windows Home Server Technical Brief for Home Computer Backup and Restore
Windows Home Server Technical Brief for Home Networking
Windows Home Server - Remote Access
Windows Home Server Technical Brief for Media Sharing
Thanks
Lara Jones [MSFT] Windows Home Server Team- 답변으로 표시됨tfieldho 2008년 9월 5일 금요일 오후 6:27
- Thanks Lara and Colin.
