Error message concerning msxml3r.dll during installation of Microsoft software
Michael Portner
I don't know whether this is the right thread for my problem but perhaps
anyone can help me.
I just installed the electronic exam preparation software (Microsoft Press
Readiness Review Suite) from the original Microsoft Training CD that
comes with the book "Managing and Maintaining a Microsoft Windows
Server(TM) 2003 Environment" (70-290).During installation the this first
error comes up:
"The Windows Installer service cannot update the system file
C:\WINDOWS\system32\msxml3r.dll because the file is protected
by Windows."
The installation continues after confirming the error message with OK.
Unfortunately there are further errors when I try to start the
application.While starting the application the error in this next error
is shown:
Window title: "Application Error"
Window text:
"Error Number: 1000
Error Source: frmMain.MDIForm_Load
MDIForm:Load
[MsLocalWare] [429] ActiveX component can't create object"
When I choose "StartNew Test" from the "Test" menu the third error
appears:
Window title: "Microsoft Press Readiness Review Suite"
Window Text:
"Run-time error '91':
Object variable or With block variable not set"
Closing this error causes the whole application to quit.
I searched for information about the error in the internet but couldn't
find any suitable hints. The Microsoft Knowledgebase contains
articles concerning ActiveX errors but not exactly with this application.
I tried to use the software with "Windows XP SP3" as well as with
"Vista Ultimate SP1" - in both cases the sameerrors appear. Both
operating systems are the German version.
I think the basic error is the first one concerning the file msxml3r.dll.
I've already tried to install several versions of Microsofts MSXML Parser
and even updated the msxml3r.dll seperately by turning off system file
protection.
What shall I do to solve the problem?
Thank you for your efforts!
Best regards,
Michael
Joe Fawcett
The 'r' DLL is just a resources file with things like error messages that
are localised.
--
Joe Fawcett (MVP - XML)
http://joe.fawcett.name
"Michael Portner" <pis...@freenet.de> wrote in message
news:7917brF...@mid.uni-berlin.de...
Michael Portner
Joe Fawcett wrote:
> Can you try installing MSXML2 version 3 after the other install?
> The 'r' DLL is just a resources file with things like error messages that
> are localised.
Hi,
what do you mean with "MSXML2 version 3". I just find a download
for MSXML 3.0 SP7.
Could you provide me a download link please?
--
Regards,
Michael
Joe Fawcett
http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582&displaylang=en
--
Joe Fawcett (MVP - XML)
"Michael Portner" <pis...@freenet.de> wrote in message
news:792k23F...@mid.uni-berlin.de...
Michael Portner
Joe Fawcett wrote:
> SP7 looks like the latest one, probably the link you have but:
> http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582&displaylang=en
Hi,
thanks for the link. Unfortunately the errors still occur.
Any other hints?
Regards,
Michael
Robert Aldwinckle
"Michael Portner" <pis...@freenet.de> wrote in message news:796mklF...@mid.uni-berlin.de...
> thanks for the link. Unfortunately the errors still occur.
> Any other hints?
Which errors? The ones that show another app is using the modules
trying to be updated? Why not find out which apps those are and
stop them? If you have downloaded the install package using that
in a safe mode boot might be enough. Otherwise you could use
Process Explorer and its Find tool (e.g. press Ctrl-f) to see where
the blockage is. Another thing you could do is Run... ProcMon
(aka Process Monitor) to supplement whatever diagnostics you are
already getting (and discover others you may be overlooking. <w>)
Good luck
Robert Aldwinckle
---
Michael Portner
"Robert Aldwinckle" wrote
>
> Which errors? The ones that show another app is using the modules
> trying to be updated? Why not find out which apps those are and
> stop them? If you have downloaded the install package using that
> in a safe mode boot might be enough. Otherwise you could use
> Process Explorer and its Find tool (e.g. press Ctrl-f) to see where
> the blockage is. Another thing you could do is Run... ProcMon
> (aka Process Monitor) to supplement whatever diagnostics you are
> already getting (and discover others you may be overlooking. <w>)
The errors are still the same ones I described in detail in my first
posting.
During installation the windows file protection prevents the msxml3r.dll
from being updated. I don't know whether this is the basic error, but
it is the first one that appears.
I'll try to install and run the application in safe mode.
Thanks,
Michael
Michael Portner
"Robert Aldwinckle" wrote:
> If you have downloaded the install package using that
> in a safe mode boot might be enough.
I booted in safe mode, but the application still crashes with
the same errors. I can't install the software again because
in safe mode the Windows Installer Service is not available.
But I tried to install the application in Windows Server 2003.
Unfortunately the error concerning msxml3r.dll during installation
occured again, but the application is running without errors.
That means: I can't use the software with "Windows XP SP3"
as well as with "Vista Ultimate SP1" but with "Windows
Server 2003".
I don't understand this but I can live with this situation.
Thank you all for your help!
Regards,
Michael
Robert Aldwinckle
"Michael Portner" <pis...@freenet.de> wrote in message news:79bn9vF...@mid.uni-berlin.de...
>
> "Robert Aldwinckle" wrote:
>
>> If you have downloaded the install package using that
>> in a safe mode boot might be enough.
>
> I booted in safe mode, but the application still crashes with
> the same errors.
Then at least your diagnosis will be easier. ; )
> I can't install the software again because
> in safe mode the Windows Installer Service is not available.
I wasn't sure what the packaging of the update was.
Too bad. A really annoying thing then is that you are explicitly
prevented from starting the service in that mode!
>
> But I tried to install the application in Windows Server 2003.
> Unfortunately the error concerning msxml3r.dll during installation
> occured again, but the application is running without errors.
Sure. All you should need to do is reboot.
The blocked module gets copied into a temporay location
then listed in PendingFileRenameOperations, then later
renamed properly during a boot when nothing should be
interfering with that operation.
>
> That means: I can't use the software with "Windows XP SP3"
> as well as with "Vista Ultimate SP1" but with "Windows
> Server 2003".
>
> I don't understand this but I can live with this situation.
It wouldn't be that difficult to figure out what the messages really imply.
>
> Thank you all for your help!
>
> Regards,
> Michael
Good luck
Robert
---
Michael Portner
"Robert Aldwinckle" <rob...@techemail.com> wrote:
>> But I tried to install the application in Windows Server 2003.
>> Unfortunately the error concerning msxml3r.dll during installation
>> occured again, but the application is running without errors.
>
>
> Sure. All you should need to do is reboot.
> The blocked module gets copied into a temporay location
> then listed in PendingFileRenameOperations, then later
> renamed properly during a boot when nothing should be
> interfering with that operation.
I'm aware of the PendingFileRenameOperations mechanism. Actually
even after a reboot the DLL is still the same version, size and has the
same change date. So I wonder whether there was a replacement
of the file at all.
>>
>> That means: I can't use the software with "Windows XP SP3"
>> as well as with "Vista Ultimate SP1" but with "Windows
>> Server 2003".
>>
>> I don't understand this but I can live with this situation.
>
>
> It wouldn't be that difficult to figure out what the messages really
> imply.
Except the Operating System I used nothing has changed.
XP and Vista: installing the application, reboot, errors concerning
frmMain.MDIForm_Load / ActiveX and Run-time error '91' appear.
Windows Server 2003: installing the application, reboot and no
errors appear.
Regards,
Michael
Robert Aldwinckle
"Michael Portner" <pis...@freenet.de> wrote in message news:79brlcF...@mid.uni-berlin.de...
>
> "Robert Aldwinckle" <rob...@techemail.com> wrote:
>
>>> But I tried to install the application in Windows Server 2003.
>>> Unfortunately the error concerning msxml3r.dll during installation
>>> occured again, but the application is running without errors.
>>
>>
>> Sure. All you should need to do is reboot.
>> The blocked module gets copied into a temporay location
>> then listed in PendingFileRenameOperations, then later
>> renamed properly during a boot when nothing should be
>> interfering with that operation.
>
> I'm aware of the PendingFileRenameOperations mechanism. Actually
> even after a reboot the DLL is still the same version, size and has the
> same change date. So I wonder whether there was a replacement
> of the file at all.
So, what you could do is *before* the boot use RegEdit to find that
value and see the name of the module which should be renamed.
Oh. There are two copies, one in System32 and one in dllcache.
Are they both being replaced at the same time?
>
>>>
>>> That means: I can't use the software with "Windows XP SP3"
>>> as well as with "Vista Ultimate SP1" but with "Windows
>>> Server 2003".
>>>
>>> I don't understand this but I can live with this situation.
>>
>>
>> It wouldn't be that difficult to figure out what the messages really imply.
>
> Except the Operating System I used nothing has changed.
>
> XP and Vista: installing the application, reboot, errors concerning
> frmMain.MDIForm_Load / ActiveX and Run-time error '91' appear.
> Windows Server 2003: installing the application, reboot and no
> errors appear.
Having two cases to trace would make the analysis of both traces
much simpler. All you would need to consider would be significant
differences, without necessarily understanding what any of it actually
meant. ; )
But first I would try using ProcExp to find out what proceses are
using that module and which ones I could do without. Again, having
two cases would mean that you could compare lists and then focus
only on the differences between them.
Good luck
Robert
---