kjsmith3
asked on
Setup cannot copy the file msxml3.dll Error
I use a cab file to download and install the msxml parsers onto clients machines! This has worked for me without a problem for some time, but recently I have encountered machines which given me this error.
Setup cannot copy the file msxml3.dll
Ensure that the location specified below is correct, or change it and insert '(Unknown)' in the drive you specified.
Copy from
(windows temp dir)
Again this has worked on hundreds of machines with out problem.
Help.
Setup cannot copy the file msxml3.dll
Ensure that the location specified below is correct, or change it and insert '(Unknown)' in the drive you specified.
Copy from
(windows temp dir)
Again this has worked on hundreds of machines with out problem.
Help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Zero response means no one was interested in this question's final deposition.
This provides information on how to finalize questions.
https://www.experts-exchange.com/help.jsp#hs5
I will forward a request today to our Moderator team for closure within the next 7 days. If, however, you feel you've been helped you still have the option to award points either directly to one best response or split points between experts who added insights.
I am requesting that this be DELETED - NO REFUND
Asta
This provides information on how to finalize questions.
https://www.experts-exchange.com/help.jsp#hs5
I will forward a request today to our Moderator team for closure within the next 7 days. If, however, you feel you've been helped you still have the option to award points either directly to one best response or split points between experts who added insights.
I am requesting that this be DELETED - NO REFUND
Asta
Greetings.
I was inadvertently granted points here, though not for the technical question you had asked. Was it your intention to award these points to Monspot instead and erred?
A Moderator should be checking into this question when time permits, so that if you'd like them to correct this, please comment here with your intent.
In the interim, perhaps these will be helpful links for you and add value to this item which has now moved to our PAQ:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsxml/html/joyofsax.asp
Brief synopsis from the above source link follows:
Hello World?
With Visual Basic (VB), the typical approach to experimentation with a Component Object Model (COM) component such as the MSXML3.dll file is to create a new Standard EXE project, and then go to the Project/References menu to add a reference to the MSXML3.dll Type Library (Microsoft XML, version 3.0). At this point, the Visual Basic Object Browser can be used to examine the properties, methods, and events for the interface of your choice.
One of the key features of the May 2000 MSXML Technology Preview is an implementation of SAX2 (Simple API for XML, version 2). As an introduction to SAX2, the MSDN XML Developer Center provides an article entitled SAX2 Jumpstart for XML Developers and a downloadable Microsoft® Visual C++® application. In this article, I outline an approach to programming the SAX2 interfaces from Visual Basic®. Note that this sample is unsupported and is intended to assist you in prototyping SAX/Visual Basic solutions. In addition, it should be made clear that the interfaces in this sample have no bearing on Microsoft's Visual Basic support for SAX in the future.
--------------------------
I can't help thinking that the answer was, indeed, that either the dll was corrupted or the source had been changed. Perhaps the way in which you accessed (rights issue).
Setup cannot copy the file msxml3.dll
Ensure that the location specified below is correct, or change it and insert '(Unknown)' in the drive you specified.....
I was inadvertently granted points here, though not for the technical question you had asked. Was it your intention to award these points to Monspot instead and erred?
A Moderator should be checking into this question when time permits, so that if you'd like them to correct this, please comment here with your intent.
In the interim, perhaps these will be helpful links for you and add value to this item which has now moved to our PAQ:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsxml/html/joyofsax.asp
Brief synopsis from the above source link follows:
Hello World?
With Visual Basic (VB), the typical approach to experimentation with a Component Object Model (COM) component such as the MSXML3.dll file is to create a new Standard EXE project, and then go to the Project/References menu to add a reference to the MSXML3.dll Type Library (Microsoft XML, version 3.0). At this point, the Visual Basic Object Browser can be used to examine the properties, methods, and events for the interface of your choice.
One of the key features of the May 2000 MSXML Technology Preview is an implementation of SAX2 (Simple API for XML, version 2). As an introduction to SAX2, the MSDN XML Developer Center provides an article entitled SAX2 Jumpstart for XML Developers and a downloadable Microsoft® Visual C++® application. In this article, I outline an approach to programming the SAX2 interfaces from Visual Basic®. Note that this sample is unsupported and is intended to assist you in prototyping SAX/Visual Basic solutions. In addition, it should be made clear that the interfaces in this sample have no bearing on Microsoft's Visual Basic support for SAX in the future.
--------------------------
I can't help thinking that the answer was, indeed, that either the dll was corrupted or the source had been changed. Perhaps the way in which you accessed (rights issue).
Setup cannot copy the file msxml3.dll
Ensure that the location specified below is correct, or change it and insert '(Unknown)' in the drive you specified.....
Cab file processes are memory intensive. Check the PCs RAM. Discharge any static electric on you by touching a large metal object before you play with RAM chips. Also please unplug the machine (not just shut down) before removing or inserting RAM.
Sincerely,
MoNsPoT