How did you get msxml6 in that folder? Looks like you have copied yourself.
If you redist msxml6 in your app like this please know that you or your 
customers will not be supported for future fixes etc.

If you need Msxml6, You really should be using msxml6.msi from
http://www.microsoft.com/downloads/details.aspx?familyid=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

-- 
Regards,
- Umut Alev [MSFT]

This email sent from a machine running Vista RC1.


"Sih Huseyin Ulger" <ulger@(dontspam).microsoft.com> wrote in message 
news:5E221DF8-673F-4874-8B02-676159C52021@m......
> If it is already in system32 you do not need to re-register it. Anyway, if
> you are trying to register C:\Program
> Files\MyCompanyName\SetupSMO\msxml6.dll, make sure that there is also
> msxml6r.dll in the same directory.
>
> -- 
> Sih Huseyin Ulger [MSFT]
> MSXML Dev
>
>
> "RJ" wrote:
>
>> I am writing a small VB.Net application with VS2005 that references the 
>> new
>> SQL2005 DTS.Runtime namespace. In my code I am using the 
>> Package.LoadFromXML
>> method to load into memory an SSIS package which is a resource in my
>> Application. The problem I am seeing is when I try to run the Installer 
>> .MSI
>> that is created as part of the Setup Project. There seems to be a 
>> reference
>> to the msxml6.dll which is in the Windows\System32 directory because I 
>> can
>> see it as a "detected dependncy". Anyway when my Install program runs it
>> fails at the end with the folllowing message;
>>
>> Module C:\Program Files\MyCompanyName\SetupSMO\msxml6.dll failed to
>> register, HRESULT -2147023782. Contact your support personnel,
>>
>> I'm not sure if it is actually trying to place a copy of that file into 
>> the
>> Program Files directory which I'm guessing may be the problem. I'm 
>> wondering
>> if anyone has seen this error before or if there is just something simple 
>> I
>> missed in creating the Setup Project. Any help is appreciated and I can
>> gladly supply more information if needed. Thanks.
>>
>> -RJ