Re: Error 0x8009310B bad tag value met

Sorry for the long delay, but every time I start to reply to your defense of
your colleague, I become upset that you would think that I maligned his
reputation. If you read my post carefully -- and not defensively --
hopefully you will see that there is absolutely no malignment. At least, I
meant none.

The point I tried to make was that, here was a person whom I hold with the
highest regard referring me to a group that, in this case at least, I hold
in a considerably lower regard. Microsoft throws in the WGA (highly
justifiable) and by doing so, screws up thousands of "genuine" users, and in
many cases, just leaves them to fend for themselves.

If anyone would know about this error, it should be the MVPs -- because they
are usually a step or two ahead. I imagine that some of their expertise is
provided by some kind of support from MS -- which obviously has not happened
in this case. If there were any "disappointment" (your word, not mine), it
would be with Microsoft. (My word was "disconcerting" -- not even close to
"disappointment".)

I realize you guys (MVPs) blow through hundreds of posts every day.
Hopefully you will read my post again and take the time to understand it and
to realize that I maintain the MS MVP group to be a priceless source of
infomation.

Best regards,

Hoppy
~~
Lawrence wrote on Thu, 27 Oct 2005 00:04:39 -0500:

LGM> And, before too much maligning of reputations is done, let's revisit
LGM> the exact text of that reply:

??>> Call the number on this page for assistance, Hoppy:
??>> http://support.microsoft.com/oas/def...spx?Gprid=6527
??>>
??>> Don't think the phone call is Toll Free, but Support for your issue
??>> is
??>>
??>> MowGreen [MVP 2003-2006]

LGM> Steve commented that he didn't think the phone calls were toll free
LGM> (but they are), but that the support is [free] (which it is).. as
LGM> are /all/ support calls involving issues with Windows Update. So to
LGM> suggest that anything was going to be done "at your expense" is just
LGM> a mite bit exaggerated -- wouldn't you agree?

LGM> As for your disappointment with MVPs.... we don't have any special
LGM> doorway into advance knowledge of things that are going to break on
LGM> Patch Tuesday. And, truly, the only difference between MVPs and the
LGM> rest of the people here is that the MVPs spend a bit more time
LGM> studying and researching an issue when it comes up -- actually,
LGM> truth be told, we spend a /lot/ more time studying and researching
LGM> these issues -- on behalf of those experiencing the problems and
LGM> answering the questions. None of us are so good as to be 100%
LGM> accurate, and since all of us are /volunteers/ to expect an
LGM> immediate response to anything is flat out unrealistic.

LGM> The best answer is exactly the one Steve gave you, and the one you
LGM> alluded to in your original post:
LGM> "Nobody seems to know anything about this error -- which I find
LGM> impossible to believe. I posted to this group a few weeks ago and
LGM> received 0 responses. I've also tried googling the error and MS's
LGM> KB, but there's nothing of any use out there."

LGM> It would be a good thing to consider the possibility that there
LGM> isn't anybody /here/ who knows anything about this error, and the
LGM> lack of responses and the failure of your Google search support that
LGM> consideration. Even Robert provides a very accurate assessment of
LGM> why things are this way: "Because nobody has a found a resolution
LGM> before (or if they have they haven't posted about it) and because
LGM> nobody ever gives any details or gives any indication that they want
LGM> to do a diagnosis."

LGM> So... in this particular case, if you want an authoritative source
LGM> for diagnosing an error that you can't get a response in the public
LGM> groups about, the /correct/ answer is to call PSS. Sometimes if FREE
LGM> cannot help, you have to get out the checkbook -- although, as
LGM> noted, in this case, it does not require the checkbook.

LGM> "Hoppy" wrote in message
LGM> news:%23RVSmwq2FHA.3108@tk2msftngp13.phx.gbl...
??|> Hello Robert --
??|>
??|> Thank you for responding. It would appear that you've encountered the
same
??|> lack of information on this error as I and as many others have.
??|> As mentioned in my previous post in this thread, yes, I have searched
the net
??|> for some clue on this error, but there's nothing that seems
appropriate.
??|>
??|> ...and, no, it was not I who said your "...previous post...was
unhelpful."
??|> No one ever responded to my original post on this error, and I rarely
??|> consider any responses to my posts as unhelpful. In *this* thread
??|> I received a response from an MS MVP who suggested I call MS Support
??|> at my expense -- probably only to have them tell me to re-install XP.
??|> (Excuse my cynicism; my limited experience with MS Support has been
quite positive.)
??|>
??|> But I must say that the lack of response and lack of information in
??|> newsgroups, and especially by MVPs is very disconcerting. I've always
??|> regarded MVPs as the ultimate source of reliable information.
??|> They strike me as very highly self-motivated and not by-the-book
??|> kind of people, and I greatly respect their knowledge and views.
??|> To have an MVP suggest that I call MS Support blows me away.
??|>
??|> I'll check out KB822798 tomorrow; thank you for the reference.
??|> Good luck to you as well. ...Tom
??|> ~~
??|> Robert wrote on Tue, 25 Oct 2005 21:09:19 -0400:
??|>
RA>>> "Hoppy" <General.Disarray@Unrealized.Reality.com> wrote in
LGM> message
RA>>> news:eRR6zjC2FHA.2616@tk2msftngp13.phx.gbl
RA>>> ...
??>>>> What makes this error so mysterious?
??>>>> Why doesn't anybody know what it is
??|>
RA>>> Try a search?
??|>
RA>>> (MSN search for
RA>>> (0x8009310b OR 8009310b) site:microsoft.com language:en )
RA>>> <quote> CRYPT_E_ASN1_BADTAG ASN.1 bad tag value met
0x8009310B</quote>
??|>
RA>>> Isn't that informative?
??|>
??>>>> or why it's caused?
??|>
RA>>> Because nobody has a found a resolution before
RA>>> (or if they have they haven't posted about it)
RA>>> and because nobody ever gives any details
RA>>> or gives any indication that they want to do a diagnosis.
??|>
RA>>> BTW were you the one who decided that my previous post on
RA>>> a similar symptom was unhelpful? <eg>
??|>
LGM>
http://www.microsoft.com/communities...63c&sloc=en-us
??|>
RA>>> (web interface to this newsgroup's search for 0x8009310B )
??|>
RA>>> If you want a guess for a possible resolution you could start with
RA>>> <title>KB822798 - You cannot install some updates or programs</title>
??|>
RA>>> Good luck
??|>