MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

sql

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSX/TSX question between SQL 2000 and 2005

Hi,
I have a SQL Server 2005 as a master server, I want to make a SQL Server
2000 default instance a target server, but it failed and the error message i
s
'The master server version 9.00.2047 is not compatible with the target serve
r
version 8.00.818'. Can we have a SQL 2000 server as a target server when we
have a SQL 2005 as a master server? If so, how?
Thanks for your help.So far i have not seen any documentation on mingling 2k and 2k5 MSX and
TSX services. I believe you would have to have both instances running
on the MSX server and have 2 complete MSX db's running.
Hong Wang wrote:
> Hi,
> I have a SQL Server 2005 as a master server, I want to make a SQL Server
> 2000 default instance a target server, but it failed and the error message
is
> 'The master server version 9.00.2047 is not compatible with the target ser
ver
> version 8.00.818'. Can we have a SQL 2000 server as a target server when w
e
> have a SQL 2005 as a master server? If so, how?
> Thanks for your help.

MSX/TSX question between SQL 2000 and 2005

Hi,
I have a SQL Server 2005 as a master server, I want to make a SQL Server
2000 default instance a target server, but it failed and the error message is
'The master server version 9.00.2047 is not compatible with the target server
version 8.00.818'. Can we have a SQL 2000 server as a target server when we
have a SQL 2005 as a master server? If so, how?
Thanks for your help.So far i have not seen any documentation on mingling 2k and 2k5 MSX and
TSX services. I believe you would have to have both instances running
on the MSX server and have 2 complete MSX db's running.
Hong Wang wrote:
> Hi,
> I have a SQL Server 2005 as a master server, I want to make a SQL Server
> 2000 default instance a target server, but it failed and the error message is
> 'The master server version 9.00.2047 is not compatible with the target server
> version 8.00.818'. Can we have a SQL 2000 server as a target server when we
> have a SQL 2005 as a master server? If so, how?
> Thanks for your help.

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.
That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.
|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.
|||Cool, thank you both.
"Geoff N. Hiten" wrote:

> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
>
>
|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||Cool, thank you both.
"Geoff N. Hiten" wrote:

> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and servi
ce
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
>
>|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||Cool, thank you both.
"Geoff N. Hiten" wrote:
> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> > Hi,
> > I just did a fresh install of SQL 2005, default instance, to a new server.
> > I
> > specified the root of D:\ as the target for the install, however I ended
> > up
> > with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> > MSSQL.1 the norm in 2k5?
> >
> > Thanks in advance.
>
>|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL