|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
Bob Felton
Guest
|
 Posted: Wed Aug 22, 2007 1:59 am Post subject: MSKB 891957, VSS Update for Windows Server 2003 |
 |
|
Does anyone know if the update contained in MSKB 891957 was
incorporated into SP2 for Windows Server 2003 R2? I am receiving
Event ID 12289 from VSS just as a scheduled NTBackup kicks off. MSKB
891957 was pointed to from EventID.net as a solution for Event ID
12289. However, I already have SP2 installed and am still logging the
events. Thanks.
--
Bob Felton |
|
| Back to top |
|
 |
|
|
System Administrator
Guest
|
| Posted: Fri Aug 31, 2007 12:28 am Post subject: Re: MSKB 891957, VSS Update for Windows Server 2003 |
|
|
I just tried a manual test backup while logged in as user Backup.
Again, no VSS errors were logged.
--
Bob
On Thu, 30 Aug 2007 22:45:30 GMT, sysadmin@sprottewatson.nospam.com
(System Administrator) wrote:
| Quote: | Further to my previous, Coraleigh. FWIW, the scheduled backups are
fired off using user "Backup" credentials. This user is a member of
the Backup Operators group.
--
Bob
On Thu, 30 Aug 2007 21:55:34 GMT, sysadmin@sprottewatson.nospam.com
(System Administrator) wrote:
OK, Coraleigh, I have some answers for you:
1. The full message for Event ID 12289 being logged is:
Volume Shadow Copy Service error. Unexpected error OpenService
(shSCManager, 'VSS',SERVICE_QUERY_STATUS). hr=0x80070005.
2. There are several other events being logged related to the
scheduled backup. All of which are informational (backup progress
related) only. The 12289 event is the only error event being logged
and it comes immediately after an informational event indicating the
scheduled backup operation had started. There are two informational
events after the 12289 event indicating a shadow copy freeze start and
stop. The next five informational events show NTBackup start,
completion, operation successful, verify start and completion.
3. No errors are logged when backing up a single file using the
NTBackup user interface. The VSS events are all coming from the daily
(M-F) scheduled NTBackup backups.
4. I do not recall and can't determine if the issue started after a
particular Windows Update procedure as I empty the event log file
weekly. I do not recall them appearing immediately after system
installation, which included SP2. However, the backup tests conducted
after system installation were all made from the user interface. I do
not recall if any VSS events were logged once I began using scheduled
backups.
5. No errors were indicated when I ran "vssadmin list writers".
6. When I ran "sfc /scannow", several prompts to insert the install
CD were issued. For each prompt, I chose "Cancel" and after ten or so
prompts, I cancelled the entire procedure. Since the install CD was
being prompted for, wouldn't allowing each prompt to complete
overwrite a file that may have been updated by either the SP2 update
or a Windows Update?
7. I did not attempt to use Process Monitor as NTBackup via the user
interface did not generate a VSS event in Event Viewer.
FWIW, I have not explicitly configured anything related to VSS.
NTBackup seems to use it as a matter of course, using whatever default
configuration exists for it.
Hope this information helps in determining the problem. Thanks,
Coraleigh.
--
Bob
On Mon, 27 Aug 2007 23:07:55 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
Ok I have a bunch of questions and troubleshooting tools for you... :-)
What is your full event id 12289 error message?
Do you have any other related event ids in your log?
Do you get the error even with backing up a simple single file on the
originating server? -is it a specific type of backup which produces this
error?
When this problem started occuring were there any new updates or software
installed, or new configuration?
Do any errors show up if you run a vssadmin /listwriters?
http://technet2.microsoft.com/windowsserver/en/library/89d2e411-6977-4808-9ad5-476c9eaecaa51033.mspx?mfr=true
You could run a sfc /scannow http://support.microsoft.com/kb/310747 which
examines all of your protected system files and verifies their versions
against what you are supposed to have. It may be that there is an incorrect
version system file outside of the vss ones we looked at.
You could also try using Microsoft's Process Monitor
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx
This will help to show what files are being launched when you start a
backup. And it might give us abit more info.
When you go to use it make sure that all other programs are closed, as it
will be easier to see our data this way, and then press the clear button at
the top and then launch your mmc, then press the capture button again which
will halt the process explorer allowing you to view the info. For viewing
the file names it might be easier to have only the "Show file system
activity" button at the top pressed.
Coraleigh Miller
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:1d87d35vp18b0li3kir9bf0gg4jr9jbsdk@4ax.com...
Thanks for that research, Coraleigh. I looked at KB913648. It
indicates all the associated files (x86) are at version 5.2.3790.2669
with a date stamp of 28 Mar 06. The files on my server are at version
5.2.3790.3959 with a date stamp of 4 Apr 06, except for a few that
have 17 Apr 07, which I believe is the date I built up the server.
So, it would appear that I have newer files than indicated in KB913648
yet I am still receiving the VSS event. Anything else I can look at
or do in an attempt to resolve? Thanks.
On Wed, 22 Aug 2007 14:44:51 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
This update (also included in SP2) is actually newer and replaced the
891957
doc so you might want to check against the file dates from here instead..
http://support.microsoft.com/kb/913648/
Coraleigh
"Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message
news:uNYQWJH5HHA.3684@TK2MSFTNGP02.phx.gbl...
Hmm..well i suppose you could check the updated files listed in the
891957
doc to see if the ones on your server are the same ver and date as the
891957 files, i would think that if a few of them were older then the
891957 for some reason didnt apply correctly, or the files got
overwritten
by some other app (not sure how possible this is). Were there any errors
in your SP2 install log?
Coraleigh
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:ppcnc3dr096hgtu1mp9leui37huo65jh4i@4ax.com...
No, Coraleigh, not yet. The 4/14/2006 response on EventID.net was for
the same exact event I'm receiving and it is the one that mentioned KB
891957.
On Tue, 21 Aug 2007 20:09:06 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
The 891957 is listed as being included in 2003 SP2.
http://support.microsoft.com/kb/914962
Did you try the other suggestions at eventid.net?
Coraleigh Miller
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:k2smc3h54265iku4bcgdr3lfhfj1r409nj@4ax.com...
Does anyone know if the update contained in MSKB 891957 was
incorporated into SP2 for Windows Server 2003 R2? I am receiving
Event ID 12289 from VSS just as a scheduled NTBackup kicks off. MSKB
891957 was pointed to from EventID.net as a solution for Event ID
12289. However, I already have SP2 installed and am still logging
the
events. Thanks.
--
Bob Felton
--
Bob Felton
--
Bob Felton
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA
|
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA |
|
| Back to top |
|
|
System Administrator
Guest
|
| Posted: Fri Aug 31, 2007 12:28 am Post subject: Re: MSKB 891957, VSS Update for Windows Server 2003 |
|
|
Further to my previous, Coraleigh. FWIW, the scheduled backups are
fired off using user "Backup" credentials. This user is a member of
the Backup Operators group.
--
Bob
On Thu, 30 Aug 2007 21:55:34 GMT, sysadmin@sprottewatson.nospam.com
(System Administrator) wrote:
| Quote: | OK, Coraleigh, I have some answers for you:
1. The full message for Event ID 12289 being logged is:
Volume Shadow Copy Service error. Unexpected error OpenService
(shSCManager, 'VSS',SERVICE_QUERY_STATUS). hr=0x80070005.
2. There are several other events being logged related to the
scheduled backup. All of which are informational (backup progress
related) only. The 12289 event is the only error event being logged
and it comes immediately after an informational event indicating the
scheduled backup operation had started. There are two informational
events after the 12289 event indicating a shadow copy freeze start and
stop. The next five informational events show NTBackup start,
completion, operation successful, verify start and completion.
3. No errors are logged when backing up a single file using the
NTBackup user interface. The VSS events are all coming from the daily
(M-F) scheduled NTBackup backups.
4. I do not recall and can't determine if the issue started after a
particular Windows Update procedure as I empty the event log file
weekly. I do not recall them appearing immediately after system
installation, which included SP2. However, the backup tests conducted
after system installation were all made from the user interface. I do
not recall if any VSS events were logged once I began using scheduled
backups.
5. No errors were indicated when I ran "vssadmin list writers".
6. When I ran "sfc /scannow", several prompts to insert the install
CD were issued. For each prompt, I chose "Cancel" and after ten or so
prompts, I cancelled the entire procedure. Since the install CD was
being prompted for, wouldn't allowing each prompt to complete
overwrite a file that may have been updated by either the SP2 update
or a Windows Update?
7. I did not attempt to use Process Monitor as NTBackup via the user
interface did not generate a VSS event in Event Viewer.
FWIW, I have not explicitly configured anything related to VSS.
NTBackup seems to use it as a matter of course, using whatever default
configuration exists for it.
Hope this information helps in determining the problem. Thanks,
Coraleigh.
--
Bob
On Mon, 27 Aug 2007 23:07:55 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
Ok I have a bunch of questions and troubleshooting tools for you... :-)
What is your full event id 12289 error message?
Do you have any other related event ids in your log?
Do you get the error even with backing up a simple single file on the
originating server? -is it a specific type of backup which produces this
error?
When this problem started occuring were there any new updates or software
installed, or new configuration?
Do any errors show up if you run a vssadmin /listwriters?
http://technet2.microsoft.com/windowsserver/en/library/89d2e411-6977-4808-9ad5-476c9eaecaa51033.mspx?mfr=true
You could run a sfc /scannow http://support.microsoft.com/kb/310747 which
examines all of your protected system files and verifies their versions
against what you are supposed to have. It may be that there is an incorrect
version system file outside of the vss ones we looked at.
You could also try using Microsoft's Process Monitor
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx
This will help to show what files are being launched when you start a
backup. And it might give us abit more info.
When you go to use it make sure that all other programs are closed, as it
will be easier to see our data this way, and then press the clear button at
the top and then launch your mmc, then press the capture button again which
will halt the process explorer allowing you to view the info. For viewing
the file names it might be easier to have only the "Show file system
activity" button at the top pressed.
Coraleigh Miller
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:1d87d35vp18b0li3kir9bf0gg4jr9jbsdk@4ax.com...
Thanks for that research, Coraleigh. I looked at KB913648. It
indicates all the associated files (x86) are at version 5.2.3790.2669
with a date stamp of 28 Mar 06. The files on my server are at version
5.2.3790.3959 with a date stamp of 4 Apr 06, except for a few that
have 17 Apr 07, which I believe is the date I built up the server.
So, it would appear that I have newer files than indicated in KB913648
yet I am still receiving the VSS event. Anything else I can look at
or do in an attempt to resolve? Thanks.
On Wed, 22 Aug 2007 14:44:51 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
This update (also included in SP2) is actually newer and replaced the
891957
doc so you might want to check against the file dates from here instead..
http://support.microsoft.com/kb/913648/
Coraleigh
"Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message
news:uNYQWJH5HHA.3684@TK2MSFTNGP02.phx.gbl...
Hmm..well i suppose you could check the updated files listed in the
891957
doc to see if the ones on your server are the same ver and date as the
891957 files, i would think that if a few of them were older then the
891957 for some reason didnt apply correctly, or the files got
overwritten
by some other app (not sure how possible this is). Were there any errors
in your SP2 install log?
Coraleigh
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:ppcnc3dr096hgtu1mp9leui37huo65jh4i@4ax.com...
No, Coraleigh, not yet. The 4/14/2006 response on EventID.net was for
the same exact event I'm receiving and it is the one that mentioned KB
891957.
On Tue, 21 Aug 2007 20:09:06 -0700, "Coraleigh Miller"
CoraleighMiller@yahoo.com> wrote:
Hi Bob,
The 891957 is listed as being included in 2003 SP2.
http://support.microsoft.com/kb/914962
Did you try the other suggestions at eventid.net?
Coraleigh Miller
"Bob Felton" <bob123.removethis@fieldtown.net> wrote in message
news:k2smc3h54265iku4bcgdr3lfhfj1r409nj@4ax.com...
Does anyone know if the update contained in MSKB 891957 was
incorporated into SP2 for Windows Server 2003 R2? I am receiving
Event ID 12289 from VSS just as a scheduled NTBackup kicks off. MSKB
891957 was pointed to from EventID.net as a solution for Event ID
12289. However, I already have SP2 installed and am still logging
the
events. Thanks.
--
Bob Felton
--
Bob Felton
--
Bob Felton
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA
|
--
System Administrator
Sprotte + Watson Architecture and Planning
Vista, CA |
|
| Back to top |
|
|
|
|
