I posted a message about the backups with a Windows Home Server PP1 have stopped working after installing N360 v3. I had version 2 of 360 and had no problems. Does anyone else have this problem with the Windows Home Connector not being able to complete a backup. I tried opening the correct ports which did not work. I uninstalled N360 and evything starts working again once again proving the problem is N360 v3. I can't be the only one out here in the world using Windows Home Server am I? If anyone can shed some light on this problem it would be greatly appreciated. Any help would be greatly appreciated.
I am also having this problem. Three machines on 360 V3. Backups have failed. One machine with 360 V2, back-up OK. and one machine with Windows Firewall, Symantec Antivirus. Back-up OK.
I ended up having to restore the WHS due to complaints by the WHS that theere were back-up inconsistenies. All back-ups have been lost now and a major re-work to get all the settings right again on the server.
I look forwards to a quick solution to this problem.
Not sure the difference between Norton 360 and what I have, but I also have this problem. Just purchased and installed Norton IS 2009, Norton SystemWorks 12, and Norton Ghost 14. Soon after this (1 day), I noticed that the WHS Backups were no longer working. I'm running Vista 64 Ultimate on the client machine. I've totally uninstalled and re-installed the connector software (losing all previous backups) and still can't get it to work. Besides the Event Log error shown below, the only other thing I see in the error log is the following informational message (there are many of these info messages).
relates toe symsnap "the system failed to flush data to the transaction log. Corruption may occur"
An Update: I forgot to mention that I beta tested Norton 360 v3. At the time of Beta testing, everything worked fine (backups, Norton etcetera.) I had another issue with 360 on this machine and ended up together withe Symantec Support in disabling a service. After that all was well. To be fair, the back-up problem seems to have come in conjunction with a larger than usual Windows update. The two Windows Ultimate machines failed at the same time, the Windows Home Premium "semi-failed". When I say semi I was able to back it up after doing the Windows Home Server Re-Install and Back-up recovery tool. On the machine that was a Beta machine, I ran sfc scannow and it worked after that.
My little TX2010 with Windows Ultimate is still broken. The backup fails at ca 10%. So.. I'm using Norton 360 to do the backups but to be honest I prefer to have the HomeServer do it.
Probably not avery helpful post but I've spent 20 days trying to fix the problem.
I too am having this exact same problem. I have been lurking monitoring this thread for quite some time now and see there have been no updates by Norton.
In another thread, a problem was reported where programs failed to launch after the N360 V3 upgrade.
Having tried this and unable to reproduce, I did some other searching on the web. The only thing I could find that would maybe indicate the same problem is the following link:
We must have been struck by the same lightning although I found the info in some other posts four days ago.
On the last machine that wasn't backing up I ran chkdsk from the Vista Menu. I ran as an administrator, but it did nothing. I then went to an elevated dos prompt and ran chkdsk /f/r and it in fact found and repiared some lost stuff. Then I re-ran sfc /scannow for good measure. Then... finally... the back-up worked. It is now working fine. Good that the problem is fixed, it has taken me a long time and the lost back-ups is a very unhappy situation.
Still don't know what the root cause was, it would be nice if somebody tries to put the pzzle together.
I ran chdsk /f/r on 3 all three machines. They all finished with clean volume. Tried to run backup and none of the machines would get past 0%. It still seems that something has ahold of a file and/or drive when home server tries to get to the volume.
Home server logs:
Created at 4/15/2009 8:19:49 PM ***** Started at 4/15/2009 8:19:49 PM *** ***** Started at 4/15/2009 8:19:49 PM *** [1]090415.201949.2834: Status: Start [1]090415.201950.1828: Status: Connect to server WHS, session 200ce251-32cb-4ecd-9a00-6da7f76c8532, protocol 20 [1]090415.201950.5519: Status: Volume 1b93d342-e4f7-11dc-a3e5-806e6f6e6963 = C: [1]090415.201953.6963: Status: Acquire volume shadows [1]090415.202003.4603: Status: Volume 1 of 1 is C: size 80023716864 used 28967502848 [1]090415.202003.6028: Status: Exception: ClientException [1]090415.202003.6038: Status: : COMException [1]090415.202003.6038: Status: : Incorrect function. (Exception from HRESULT: 0x80070001) [1]090415.202003.6038: Status: : at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.HomeServer.Common.Client.Win32.ThrowLastError() at Microsoft.HomeServer.Backup.NTFS.VolumeBuffer.EndRead() at Microsoft.HomeServer.Backup.NTFS.Volume.ReadCluster(Int64 cluster) at Microsoft.HomeServer.Backup.NTFS.Volume..ctor(VolumeInfo volumeInfo, String name, Boolean writable, Int32 bytesPerCluster) at Microsoft.HomeServer.Backup.NTFS.Volume..ctor(VolumeInfo volumeInfo, String name) at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch() at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run() at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch() at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run() [1]090415.202003.6351: Status: Bytes sent=927, bytes received=19, 0 reconnects [3]090415.202003.9876: Error: ReconnectableStream: Read catch IOException Unable to read data from the transport connection: A blocking operation was interrupted by a call to WSACancelBlockingCall., generation 1, reconnect
I also saw this and tried it before but was willing to try it again. Any ideas????
Hmm, if you think it's a file that is being held on to you may try "procmon.exe" from Microsoft internals to see what files the Home Server backup program is trying to open. It may give you a clue as to what the problem is.
You may also try and turn off "Norton Product Tamper Protection" under miscellaneous settings to see if Home Server backup program is trying to touch any of the Symantec registry keys or files. If so those files may return failure as the product is trying to make sure it is not tampered with.
We have tried to reproduce this in house and have been unable to, this is why I have been asking the questions. Pretty difficult to fix something that we can't reproduce. :-(
So this problem is not easy to verify, however it would appear several people are having this issue, there must be something different with our setups.
As for reading it on a number of sites, the 2 sites you show are 1 site pointing back to this one, and the other is this thread.
Bruce, what can you tell me about your system, perhaps with the 2 systems we can find some commonality that we are not seeing in-house here.
I will try that if needed. This is odd. I can see the backup starting and then when "C:idle" then it fails. I have duplicated it on the 3 machines. 1 is Vista x64 and the other 2 are Vista 32-bit Home Premium. What I can;t figure out is what is the change be v2 and v3 that might have stopped it. Is there any logs that I can attach or send that might help...from home server or symantec logs?
I just unchecked tamper protection and it started working ...now rechecked it and tried again and it failed. AHHH! What does tamper protection stop or access that home server may be trying to access and then norton is blocking it. Logs somewhere we can look at?