RE: Unable to get this to work
From: thejamie (thejamie_at_discussions.microsoft.com)
Date: 03/04/05
- Next message: thejamie: "RE: Unable to get this to work"
- Previous message: thejamie: "Yet another kick in the head"
- In reply to: thejamie: "Unable to get this to work"
- Next in thread: thejamie: "RE: Unable to get this to work"
- Reply: thejamie: "RE: Unable to get this to work"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Mar 2005 08:53:05 -0800
Since I'm on this rant, let me say what I believe to be wrong with the
instructions
The instructions are clear, you go to the binary table, click the mdac_typ
data column, browse for the newer mdac_type.exe and replace the stream.
However, the instructsion stop at that point indication that at this point
all is okeydokey. However, in my experience, this new MDAC.MSM always fails
to do anything at all.
I don't understand the mechanics of building a merge module, but I can look
at the module signature:
MDACTYPMSM.9820376E_C13A_4831_A61C_D2BB3494402C
and the version:
2.70.7713.2
And tell immediately that this isn't gonna fly if I am installing the 2.8
MDAC. I am positive that the module signature for the 2.8 mdac must be
different or it wouldn't work. So where is the sense of checking a signature
for 2.70 when you need to install 2.71 or 2.8?
Moveover, if you proceed to examine the ModuleComponents table there is yet
more indication that this is not a valid MSM:
MDACTYPMSM.9820376E_C13A_4831_A61C_D2BB3494402C
Note again, that this number is exactly the same as the module signature
which we already know is incorrect. So in the instruction for updating the
merge module at least two important factors have been overlooked.
Now look at the Component table:
MDACTYPMSM.9820376E_C13A_4831_A61C_D2BB3494402C
Again note here the same older signature for MDAC 2.70. Once again, I don't
see how this can fly unless the proper component reference is provide for the
new stream.
Note as well that the Directory table also includes this same incorrect
reference.
If this module is to fly, I believe it must contain the corrected
references. So my option here is to figure out how and where that GUID
reference is created, what it means and how can I replace it in ORCA so that
the revised MDAC will actually do what it is supposed to do.
If someone has any idea where this information comes from or knows of a site
that explains how this works, I would really appreciate it. I have tried
and failed with so many distributions lately and it keeps coming back to me
finding out that somehow, the version of MDAC on my development machine is
rolling back (HOW IS THIS EVEN POSSIBLE?), my gut here tells me the
instruction for this "simple" (NOTE THE QUOTES) fix to upgrade the MDAC.MSM
is definitely leaving out a rather large piece of this puzzle.
I have no choice but to figure this out. If no one knows the answer, I
will post results if and when I ever find them.
Frustrated beyond belief....
"thejamie" wrote:
> http://support.microsoft.com/?kbid=320788
> Site tells how to make your own. I follow directions and it doesn't seem to
> work. I continue to get incredibly horrific results such as MDAC uninstalled
> on my development machine after a test install... then a build without
> knowing it was uninstalled... this is a nightmare. I don't understand why MS
> can't release either
> a: directions that work
> b: their own merge module for MDAC that is version based.
>
> "thejamie" wrote:
>
> > I just had a horrible experience where the wrong mdac.msm went out with a
> > previous version sewed up inside. I need either 2.71 or 2.8. Can't find em.
> > Anyone know where they went?
> > Where is the mdac.msm?
> > --
> > Regards,
> > Jamie
- Next message: thejamie: "RE: Unable to get this to work"
- Previous message: thejamie: "Yet another kick in the head"
- In reply to: thejamie: "Unable to get this to work"
- Next in thread: thejamie: "RE: Unable to get this to work"
- Reply: thejamie: "RE: Unable to get this to work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
