"TC207" wrote in message
...
Hey there!
Sorry, for not getting the hint sooner but so far I have no other context to
my error...
My system is Vista Ultimate 32bit (mentioned in my first post) and set up to
install updates automatically, whenever they trickle in...

All I have is the WindowsUpdate.log stating that the last updates happened
on Feb. 15th and since then I get the same error whenever Windows Updates
trys to connect to a server... The same .log file is the only one I can find
on my system relating to this error.


That was quite a while ago. Have you done any other updates since then?
If the files the problem update changed are common (such as WindowsUpdate.log)
you wouldn't see them just by searching on that date. E.g. that sort of search
gets best results when tried as soon as possible after the update is attempted.


However, if the search on Vista is still as anemic as the XP Search Companion
I guess that might explain why you wouldn't find anything either. So if you can't
find any documents on your whole system drive which don't contain either
8007370D OR 14093 perhaps you can at least still use findstr (in a cmd
window)? E.g. switch to a cmd window and enter:

cd /d %windir%
and
findstr /s /m /i "8007370D 14093" *


That may take a while and you would probably get best results by doing it
under an Administrator account (e.g. start your cmd window using right-click
Run As... Administrator). Also, note that I am taking a chance that the only
relevant information you might find which contains these codes would be under
your System directory. If it could occur anywhere else you might have to
expand your search accordingly.



You refer to CBS, I have no idea what that is but am very willing to learn
if you can point me in the right direction...


Try a search? There are numerous KB articles for Vista which refer to CBS.log
(found as soon as a I do a search for CBS site:microsoft.com)
It appears to be an even more general (but more detailed) log for your OS
than WindowsUpdate.log.


(ignore the title)
http://support.microsoft.com/kb/940410

(Live Search for
"cbs.log" site:support.microsoft.com
)

quote
Package Manager may return error code 87. This error code indicates that
Package Manager has received incorrect parameters. Package Manager may
also return error code 3010. This error code indicates that you should restart
the computer for the changes to take effect.

You may also want to view the log file. The log file is located in the
%windir%\Logs\Cbs\Cbs.log
folder.
/quote

Note: it says "folder" there but I suspect it really means "file".

Note that ideally for your case you would have preferred to find an article
which said something about 14093 instead of 3010. But this at least
gives you the path to the CBS.log for your own purposes.

Also, let's widen the search away from the KB but still at Microsoft:

(ignore the title)
http://www.microsoft.com/communities...7ade5df81e&p=1

(Live Search for
cbs.log (MSFT OR MVP) site:microsoft.com
)

quote
I *think* that means a system file can not be found by Component Based
Servicing [CBS]. One can view the cbs.log in WINDOWS\logs\CBS
and, *hopefully*, find out which system file is the culprit.
Be aware that this log can be very large.
/quote

So now we know what CBS stands for.
What documentation is available for it?
Hopefully wherever CBS logs are discussed in general
it will be likely that its acronym will be expanded in full...


http://technet2.microsoft.com/window....mspx?mfr=true

(Live Search for
"component based servicing" site:microsoft.com
)

There is a disappointing lack of detail here
but look over at the menu tree which this expanded.
Underneath it there are some references to some
Update Installations... Events. So this could be a clue
to look in your Event Viewer and see if you have any entries
associated with your problem update--specifically, I imagine, 4385.
Perhaps you can find more clues that way? Etc.


Good luck

Robert
---



Thanks! Roger

"Robert Aldwinckle" wrote:


"TC207" wrote in message

....

(repeating with emphasis)

As usual, an error code without its context is fairly useless.
Find the context of the code (in any of its forms)

EMPHASIS

in any diagnostics that the update created for better understanding of what it probably means.


Hi!

Here's a cut of the WindowsUpdate.log from today...


Is this the only file you were able to find which was changed during the update
which contained either the string 8007370D or 14093?

Hint: the message just before the first instance of the hex version of the code
refers to CBS... ; }

Also, remember that I don't have your OS so I have no idea what the logs
are supposed to look like or what other diagnostic files would have been
created, even for a normal case. That's why I started the cross-post,
to see if anybody else who has your OS is willing to compare their results
with yours.


Good luck

Robert
---


Full .log file is available but I think it's way too big to post here.

Looking forward to your input on this..
Roger


(extensive trimming)

....
2008-02-21 17:16:49:188 1068 334 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381"
2008-02-21 17:17:31:334 1068 334 Setup WARNING: Cbs StartSession, error =
0x8007370D
2008-02-21 17:17:31:334 1068 334 Setup FATAL: Applicability evaluation for
setup package
"WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381" failed,
error = 0x8007370D
2008-02-21 17:17:31:334 1068 334 Setup FATAL: SelfUpdate check failed, err =
0x8007370D
2008-02-21 17:17:31:334 1068 334 Agent * WARNING: Skipping scan,
self-update check returned 0x8007370D
2008-02-21 17:17:31:393 1068 334 Agent * WARNING: Exit code = 0x8007370D
2008-02-21 17:17:31:393 1068 334 Agent *********
2008-02-21 17:17:31:393 1068 334 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-02-21 17:17:31:393 1068 334 Agent *************
2008-02-21 17:17:31:393 1068 334 Agent WARNING: WU client failed Searching
for update with error 0x8007370d
2008-02-21 17:17:31:394 1068 1360 AU ## RESUMED ## AU: Search for
updates [CallId = {554B3150-2DFA-4FC0-9F4F-DDCBBAD2C309}]
2008-02-21 17:17:31:394 1068 1360 AU # WARNING: Search callback failed,
result = 0x8007370D
2008-02-21 17:17:31:394 1068 1360 AU # WARNING: Failed to find updates
with error code 8007370D
2008-02-21 17:17:31:394 1068 1360 AU #########
2008-02-21 17:17:31:394 1068 1360 AU ## END ## AU: Search for updates
[CallId = {554B3150-2DFA-4FC0-9F4F-DDCBBAD2C309}]
2008-02-21 17:17:31:394 1068 1360 AU #############
2008-02-21 17:17:31:396 1068 1360 AU AU setting next detection timeout to
2008-02-21 21:17:31
2008-02-21 17:17:31:397 1068 1360 AU Setting AU scheduled install time to
2008-02-21 18:00:00
2008-02-21 17:17:36:334 1068 334 Report REPORT EVENT:
{CB410F18-D72E-4F38-8E0A-71736B33CA8B} 2008-02-21
17:17:31:334+0100 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8007370d SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x8007370d.
************************************************** ***********

"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"TC207" wrote in message
...
Hi!
My WindowsUpdate on Vista Ultimate 32bit stopped functioning with the error
message "Windows could not search for new updates", giving error code
8007370D.

Of course that's nowhere available...

cmd_output OS="XPsp2"
F:\set /a c= 0x370D
14093
F:\net helpmsg %c%
14093 is not a valid Windows network message number.
/cmd_output


What does net helpmsg 14093 show you on Vista? ; )

Try a search?...

http://msdn2.microsoft.com/en-us/library/ms681384.aspx
(Live Search for
14093 vista codes site:microsoft.com
)
quote
ERROR_SXS_IDENTITY_PARSE_ERROR 14093 0x370D
The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes,
missing attribute name or missing attribute value.
/quote


As usual, an error code without its context is fairly useless.
Find the context of the code (in any of its forms) in any diagnostics
that the update created for better understanding of what it probably means.


Any idea in here by any chance?
Thanks! TC207


Good luck

Robert Aldwinckle
---

Hiya all!

Just for your info - I had to bite the bullet and re-install Vista completely.
Though, now Windows Update does work again... ;-)
Thanks for all your help & hints!
Roger

"Robert Aldwinckle" wrote:

"TC207" wrote in message
...
Hey there!
Sorry, for not getting the hint sooner but so far I have no other context to
my error...
My system is Vista Ultimate 32bit (mentioned in my first post) and set up to
install updates automatically, whenever they trickle in...

All I have is the WindowsUpdate.log stating that the last updates happened
on Feb. 15th and since then I get the same error whenever Windows Updates
trys to connect to a server... The same .log file is the only one I can find
on my system relating to this error.


That was quite a while ago. Have you done any other updates since then?
If the files the problem update changed are common (such as WindowsUpdate.log)
you wouldn't see them just by searching on that date. E.g. that sort of search
gets best results when tried as soon as possible after the update is attempted.


However, if the search on Vista is still as anemic as the XP Search Companion
I guess that might explain why you wouldn't find anything either. So if you can't
find any documents on your whole system drive which don't contain either
8007370D OR 14093 perhaps you can at least still use findstr (in a cmd
window)? E.g. switch to a cmd window and enter:

cd /d %windir%
and
findstr /s /m /i "8007370D 14093" *


That may take a while and you would probably get best results by doing it
under an Administrator account (e.g. start your cmd window using right-click
Run As... Administrator). Also, note that I am taking a chance that the only
relevant information you might find which contains these codes would be under
your System directory. If it could occur anywhere else you might have to
expand your search accordingly.



You refer to CBS, I have no idea what that is but am very willing to learn
if you can point me in the right direction...


Try a search? There are numerous KB articles for Vista which refer to CBS.log
(found as soon as a I do a search for CBS site:microsoft.com)
It appears to be an even more general (but more detailed) log for your OS
than WindowsUpdate.log.


(ignore the title)
http://support.microsoft.com/kb/940410

(Live Search for
"cbs.log" site:support.microsoft.com
)

quote
Package Manager may return error code 87. This error code indicates that
Package Manager has received incorrect parameters. Package Manager may
also return error code 3010. This error code indicates that you should restart
the computer for the changes to take effect.

You may also want to view the log file. The log file is located in the
%windir%\Logs\Cbs\Cbs.log
folder.
/quote

Note: it says "folder" there but I suspect it really means "file".

Note that ideally for your case you would have preferred to find an article
which said something about 14093 instead of 3010. But this at least
gives you the path to the CBS.log for your own purposes.

Also, let's widen the search away from the KB but still at Microsoft:

(ignore the title)
http://www.microsoft.com/communities...7ade5df81e&p=1

(Live Search for
cbs.log (MSFT OR MVP) site:microsoft.com
)

quote
I *think* that means a system file can not be found by Component Based
Servicing [CBS]. One can view the cbs.log in WINDOWS\logs\CBS
and, *hopefully*, find out which system file is the culprit.
Be aware that this log can be very large.
/quote

So now we know what CBS stands for.
What documentation is available for it?
Hopefully wherever CBS logs are discussed in general
it will be likely that its acronym will be expanded in full...


http://technet2.microsoft.com/window....mspx?mfr=true

(Live Search for
"component based servicing" site:microsoft.com
)

There is a disappointing lack of detail here
but look over at the menu tree which this expanded.
Underneath it there are some references to some
Update Installations... Events. So this could be a clue
to look in your Event Viewer and see if you have any entries
associated with your problem update--specifically, I imagine, 4385.
Perhaps you can find more clues that way? Etc.


Good luck

Robert
---



Thanks! Roger

"Robert Aldwinckle" wrote:


"TC207" wrote in message

....

(repeating with emphasis)

As usual, an error code without its context is fairly useless.
Find the context of the code (in any of its forms)

EMPHASIS

in any diagnostics that the update created for better understanding of what it probably means.


Hi!

Here's a cut of the WindowsUpdate.log from today...


Is this the only file you were able to find which was changed during the update
which contained either the string 8007370D or 14093?

Hint: the message just before the first instance of the hex version of the code
refers to CBS... ; }

Also, remember that I don't have your OS so I have no idea what the logs
are supposed to look like or what other diagnostic files would have been
created, even for a normal case. That's why I started the cross-post,
to see if anybody else who has your OS is willing to compare their results
with yours.


Good luck

Robert
---


Full .log file is available but I think it's way too big to post here.

Looking forward to your input on this..
Roger


(extensive trimming)

....
2008-02-21 17:16:49:188 1068 334 Setup Evaluating applicability of setup
package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381"
2008-02-21 17:17:31:334 1068 334 Setup WARNING: Cbs StartSession, error =
0x8007370D
2008-02-21 17:17:31:334 1068 334 Setup FATAL: Applicability evaluation for
setup package
"WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381" failed,
error = 0x8007370D
2008-02-21 17:17:31:334 1068 334 Setup FATAL: SelfUpdate check failed, err =
0x8007370D
2008-02-21 17:17:31:334 1068 334 Agent * WARNING: Skipping scan,
self-update check returned 0x8007370D
2008-02-21 17:17:31:393 1068 334 Agent * WARNING: Exit code = 0x8007370D
2008-02-21 17:17:31:393 1068 334 Agent *********
2008-02-21 17:17:31:393 1068 334 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-02-21 17:17:31:393 1068 334 Agent *************
2008-02-21 17:17:31:393 1068 334 Agent WARNING: WU client failed Searching
for update with error 0x8007370d
2008-02-21 17:17:31:394 1068 1360 AU ## RESUMED ## AU: Search for
updates [CallId = {554B3150-2DFA-4FC0-9F4F-DDCBBAD2C309}]
2008-02-21 17:17:31:394 1068 1360 AU # WARNING: Search callback failed,
result = 0x8007370D
2008-02-21 17:17:31:394 1068 1360 AU # WARNING: Failed to find updates
with error code 8007370D
2008-02-21 17:17:31:394 1068 1360 AU #########
2008-02-21 17:17:31:394 1068 1360 AU ## END ## AU: Search for updates
[CallId = {554B3150-2DFA-4FC0-9F4F-DDCBBAD2C309}]
2008-02-21 17:17:31:394 1068 1360 AU #############
2008-02-21 17:17:31:396 1068 1360 AU AU setting next detection timeout to
2008-02-21 21:17:31
2008-02-21 17:17:31:397 1068 1360 AU Setting AU scheduled install time to
2008-02-21 18:00:00
2008-02-21 17:17:36:334 1068 334 Report REPORT EVENT:
{CB410F18-D72E-4F38-8E0A-71736B33CA8B} 2008-02-21
17:17:31:334+0100 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8007370d SelfUpdate Failure Software
Synchronization Windows Update Client failed to detect with error 0x8007370d.
************************************************** ***********

"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"TC207" wrote in message
...
Hi!
My WindowsUpdate on Vista Ultimate 32bit stopped functioning with the error
message "Windows could not search for new updates", giving error code
8007370D.

Of course that's nowhere available...

cmd_output OS="XPsp2"
F:\set /a c= 0x370D
14093
F:\net helpmsg %c%
14093 is not a valid Windows network message number.
/cmd_output


What does net helpmsg 14093 show you on Vista? ; )

Try a search?...

http://msdn2.microsoft.com/en-us/library/ms681384.aspx
(Live Search for
14093 vista codes site:microsoft.com
)
quote
ERROR_SXS_IDENTITY_PARSE_ERROR 14093 0x370D
The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes,
missing attribute name or missing attribute value.
/quote


As usual, an error code without its context is fairly useless.
Find the context of the code (in any of its forms) in any diagnostics
that the update created for better understanding of what it probably means.


Any idea in here by any chance?
Thanks! TC207


Good luck

Robert Aldwinckle
---