How view CBS.log

 
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> General Discussions RSS
Next:  Blind Carbon Copies  
Author Message
Walter Donavan
External


Since: Jan 26, 2009
Posts: 4



PostPosted: Mon Jan 26, 2009 10:38 pm    Post subject: How view CBS.log
Archived from groups: microsoft>public>windows>vista>general (more info?)

Vista Basic. Dell Vostro 220.

It tells me I do not have access. I am the administrator and only user.

* Background: I ran sfc /scannow because my system, brand new, often refuses
to run pgms or carry out commands (doing nothing when told). Sometimes it
says a file is missing. Sometimes it just ignores the command.

* sfc /scannow told me I had some corrupted files and to examine CBS.log.
But Vista won't let me examine it. I managed to TYPE it in Command Mode, but
it went by so quickly I couldn't see it. It is also very big.

* I am an inch away from using the Dell utility that restores the computer
to its original state--but of course I'd lose all my installations and
tweaking.

What can I do?

Thanks for your help.

Walter
Back to top
zachd [MSFT]
External


Since: Feb 23, 2007
Posts: 730



PostPosted: Tue Jan 27, 2009 5:38 am    Post subject: Re: How view CBS.log [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Run "cmd.exe" *as an administrator*. In that window, type "notepad
%systemroot%\logs\cbs\cbs.log". Or copy cbs.log to elsewhere and then open
it...

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Walter Donavan" wrote in message

> Vista Basic. Dell Vostro 220.
>
> It tells me I do not have access. I am the administrator and only user.
>
> * Background: I ran sfc /scannow because my system, brand new, often
> refuses to run pgms or carry out commands (doing nothing when told).
> Sometimes it says a file is missing. Sometimes it just ignores the
> command.
>
> * sfc /scannow told me I had some corrupted files and to examine CBS.log.
> But Vista won't let me examine it. I managed to TYPE it in Command Mode,
> but it went by so quickly I couldn't see it. It is also very big.
>
> * I am an inch away from using the Dell utility that restores the computer
> to its original state--but of course I'd lose all my installations and
> tweaking.
>
> What can I do?
>
> Thanks for your help.
>
> Walter
Back to top
Walter Donavan
External


Since: Jan 26, 2009
Posts: 4



PostPosted: Tue Jan 27, 2009 1:07 pm    Post subject: Re: How view CBS.log [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Thank you zachd.

The latter did not work for me, but I will try the former, which I
understand.

I have saved your response in my Tech Notes section of Documents.
Back to top
Walter Donavan
External


Since: Jan 26, 2009
Posts: 4



PostPosted: Tue Jan 27, 2009 11:35 pm    Post subject: Re: How view CBS.log [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

zachd,

Using your technique, I was able to open CBS.log, but I couldn't interpret
it. It is also huge (2+MB .txt file).

Any suggestions as to how to intepret it? (E.g. how to search for errors,
what to do when I find them?)
Back to top
zachd [MSFT]
External


Since: Feb 23, 2007
Posts: 730



PostPosted: Tue Jan 27, 2009 11:35 pm    Post subject: Re: How view CBS.log [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

What you could do is copy the existing file, rename the old one to
cbs.old.log in that elevated cmd.exe prompt, run sfc /scannow and see what's
new there. Or copy the existing one to cbs.old.log , run sfc /scannow and
windiff the two after that completes.

I don't know if there's any great interpretation mechanisms other than going
through the file. But your errors would be towards the bottom. Possibly
search for "error"?

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Walter Donavan" wrote in message

> zachd,
>
> Using your technique, I was able to open CBS.log, but I couldn't interpret
> it. It is also huge (2+MB .txt file).
>
> Any suggestions as to how to intepret it? (E.g. how to search for errors,
> what to do when I find them?)
Back to top
Darrell Gorter[MSFT]
External


Since: Jun 24, 2006
Posts: 438



PostPosted: Wed Jan 28, 2009 3:10 am    Post subject: Re: How view CBS.log [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hello,
Use this article to get the relevant SFC information out of the cbs.log file
928228 How to analyze the log file entries that the Microsoft Windows
Resource Checker (SFC.exe) program generates in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;928228



Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >Reply-To: "zachd [MSFT]"
| >From: "zachd [MSFT]"
| >References:


| >In-Reply-To:
| >Subject: Re: How view CBS.log
| >Date: Tue, 27 Jan 2009 17:19:10 -0800
| >Lines: 25
| >Message-ID:
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > format=flowed;
| > charset="iso-8859-1";
| > reply-type=response
| >Content-Transfer-Encoding: 7bit
| >X-Priority: 3
| >X-MSMail-Priority: Normal
| >X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
| >X-MS-CommunityGroup-PostID: {7FFCFAC5-39CC-4ADE-AC3B-FEF740497720}
| >X-MS-CommunityGroup-ThreadID: FB9A01CA-CD2B-41D1-A412-12B28321AA67
| >X-MS-CommunityGroup-ParentID: 09116E6C-B6C9-4689-8661-1339AD56A19C
| >Newsgroups: microsoft.public.windows.vista.general
| >Path: TK2MSFTNGHUB02.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.general:381111
| >NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| >X-Tomcat-NG: microsoft.public.windows.vista.general
| >
| >
| >What you could do is copy the existing file, rename the old one to
| >cbs.old.log in that elevated cmd.exe prompt, run sfc /scannow and see
what's
| >new there. Or copy the existing one to cbs.old.log , run sfc /scannow
and
| >windiff the two after that completes.
| >
| >I don't know if there's any great interpretation mechanisms other than
going
| >through the file. But your errors would be towards the bottom.
Possibly
| >search for "error"?
| >
| >--
| >Speaking for myself only.
| >See http://zachd.com/pss/pss.html for some helpful WMP info.
| >This posting is provided "AS IS" with no warranties, and confers no
rights.
| >--
| >"Walter Donavan" wrote in message
| >
| >> zachd,
| >>
| >> Using your technique, I was able to open CBS.log, but I couldn't
interpret
| >> it. It is also huge (2+MB .txt file).
| >>
| >> Any suggestions as to how to intepret it? (E.g. how to search for
errors,
| >> what to do when I find them?)
| >
| >
Back to top
Display posts from previous:   
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> General Discussions All times are: Eastern Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Warning: fopen(): open_basedir restriction in effect. File(/home/adsense_reject.txt) is not within the allowed path(s): (/home/helploc:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/helploc/public_html/Giga/GigaFunctions.php on line 1144

Warning: fopen(/home/adsense_reject.txt): failed to open stream: Operation not permitted in /home/helploc/public_html/Giga/GigaFunctions.php on line 1144

Warning: fwrite() expects parameter 1 to be resource, boolean given in /home/helploc/public_html/Giga/GigaFunctions.php on line 1145

Warning: fclose() expects parameter 1 to be resource, boolean given in /home/helploc/public_html/Giga/GigaFunctions.php on line 1146