We’re starting to see more and more of what I’m going to call the “cloud effect” in operating systems.
Annoying but ignorable errors that make it hard to figure out what’s really going on.
If I don’t reboot my SBS 2008 production server once a month – I will get this annoying error message in my backups
Speaking of errors that everywhere you turn are told to ignore this that the system is running fine is this one that pops up on my server if I haven’t rebooted in 30 days.
| DATE / TIME | 5/30/2011 11:00:22 PM |
| Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported limit. hr = 0x80042409. Operation: PostSnapshot Event Context: Maximum supported sessions: 64 Completed sessions: 8 Active sessions: 64 Aborted sessions: 0 Writer failed sessions: 0 New snaphot set: {782dd431-d4b0-49b6-9d4f-a36834f86338} Old snapshot set: {4147229b-b95d-49d6-b187-b11b3db586a7} Old operation: 1014 Old state: 1 Old failure: 0 Execution Context: Writer Writer Class Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2} Writer Name: MSSearch Service Writer Writer Instance ID: {45a13773-f9c5-491a-8bdb-8e0470fa3420} |
Doesn’t occur on Server 2008 R2 mind you. And if you dig around you are told to ignore:
Error message when you perform a Volume Shadow Copy Service restore operation: “0x80042409”:
http://support.microsoft.com/kb/978773/en-us
That’s nice folks but it makes it hard to see if you are really having issues or not. You kinda can’t ignore what you are told to ignore.
To all of those folks that think that other stuff we’re told to ignore in SBS 2011 is a little bit annoying to be told to ignore all of these in SBS 2011 – http://support.microsoft.com/kb/2483007 keep the faith. We have an open bug and am hoping to come to a better resolution – so stay tuned. You have to be careful not to adjust too much as one of the “workaround” to get the VSS error in SBS 2011 to shut up – by removing the SharePoint in the VSS registry section – turns out it has a nasty side effect – it removes the SharePoint from the application backup section so it’s not as easy to restore.
Be careful when you start mucking around in there that you make inadvertently cause a side effect you weren’t thinking of.
Why do I call this the ‘cloud effect’ btw? It’s because once all of this stuff is in the cloud then someone else is ignoring this and it’s their problem to deal with.
“It’s because once all of this stuff is in the cloud then someone else is ignoring this and it’s their problem to deal with.”
That’s the real scary part. Is anyone on the other end even looking at the event log ? If they are, are they knowledable enough to know what they are seeing ?