installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.

|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

sql

installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.

|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.

|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

installation bug found SQL Server 2005

Hi!

I had the earlier builds and this did not happen but:

just downloaded SQL Server 2005 (RTM) from msdn

When selecting to install integration services (amoungst other options), whilst installating it gives me an error saying I do not have admin privledges to install one of the .NET libraries/runtime files? I cannot remember the file name at all im afraid.

Error: 0x80131501

So I cancelled the install and just installed everything but the integration services... and it works fine now. I do not know if this is a bug but just thought I would let you knowHello.

My fix is the same as yours. Install a little less at the time. Do it in two steps.

sqlxml4.msi?

The error message is (obviously) wrong. I have seen this when the system has memory starvation.

Do you have enough ram?

Are you running inside Virtual PC/Server on a newly installed image that has not yet grown its swap space?|||Hi!

You would be insane to install it on a VPC system lol

I have more than enough RAM - 512MB, I have also put in an extra 512MB but makes no difference.

Any other solutions? This issue should be sorted out before the official ship date.|||Greetings

> You would be insane to install it on a VPC system lol

You must know something I don't.

> Any other solutions? This issue should be sorted out before the official ship date.

I tried to raise the subject in other channels with SEPT CTP, but interest is slim.
My guess is that it is a Windows Installer bug, and ideally should be solved by another team.

I guess it would help if you gave a few more details about your environment.

btw, some times litening is better than laughing,

regards
|||sometimes listening to an Employee who has been at Microsoft for a year+, and who is part of another team for 4 years, helps too and who is about to return back after he gets his university degree.

Environment is what I posted in my initial post. take another read.

what else do you want to know about environment?

i wouldnt say it is an installer bug. It may make sense but i dont believe it is.

interest should be huge and i am sure it will be as when shipping a product which does not install is a bug fallback for the product|||

Hello again
Excuse me if I offended you, I was trying to help.

Virtualization
Using virtual server has been Microsofts own choice for working with the betas. I have seen it used by three of the leading "Yukon" experts in the world (one of them hatet virtual server). I myself have run "Yukon" versions in both VPC and VS for a years time. Lol as much as you want.

Installation issue
Well, we didn't get enough momentum on it. The bits are in production now.
Your error code is COR_E_SYSTEM. It generally is declared in the exception base class and means "Exception for this error not implemented". Without an error message it is hard to read anything from it.

Environment
I must have been unclear. I ment enough information about you hardware and software to reproduce your bug. Obviously, everybody else is not having your problem, so more information about your environment is needed.

|||Sure

hardware:

P4 3GHz 800FSB
512MB DDR400 RAM
200GB 7200 RPM 8MB cache
160GB 7200RPM 2MB Cache
Intel 865GBF motherboard

network card, graphics card (256MB AGP 8x), sound card

Software running:

WS2003 Enterprise edition (with SP1)
VS.NET 2003 .NET framework 1.1
SQL Server 2000 Enterprise edition (MSDN)

Office 2003 (with sp2)

anything else?|||OK. Good for you. No caveats that I can see.
What is the virus/virus killer situation?

There is no doupt that there are people with the same hardware configuration that has successfully installed all parts of SQL Server 2005, or you wouldn't be the only one screaming.

I haven't tried it with Office SP2, which leads me towards thinking there is a (remote) chance that it could be version panic with SQLXML, Windows Installer or something. (I know there is something called side by side execution, it's just that I am not convinsed)

Have you tried re-running setup and install (just) Integration Services on top of the rest?

If it does not work, you could try deinstalling any data access components optionally installed with office or office SP2 but it's a long shot.

If you had added 512MB RAM, you could comfortably run SQL in VPC or Virtual Server.

BTW: did you (in your first install) do a cutom install and include the samples?|||

Virus killer situation is none on that computer as it is not connectable to the internet. But I did scan the system anyway using Norton Anti Virus (latest definations etc...) from another computer and there are no viruses - so we can take this out the equation.

I did re-run setup and I was able to select the integration services alone (after deselecting it the first time I installed SQL Server 2005) and it did install fine.

I have also tried to run setup and choosing all the options, including integration services and the same problem happened again.

I will try to de-install data access components and see what happens.

I also have another issue which is in the SQL Server tools forum, relating to profiler and I think that the error of that is related to data access components... hopefully If i remove the data access components and perhaps re-install it I can solve that problem and who knows, this problem too with the installation of SQL Server 2005

I will update you with the steps to be done on my end...

thanks

|||

P.S - just checked, SQL Server 2005 Enterprise edition is up for grabs, it was said it would be next week but its up now! So, I will see if i encounter a problem with that setup process

|||

OK, well I am installing SQL Server 2005 ENT edition and it still produces the error when installing integration services (selected all options except reporting services)

Error:

Failed to install and configure assemblies: C:\program files\Microsoft SQL Server\90\DTS\tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087.

Error Message: Unknown Error 0x80131501

Error description: You must have administrator credentials to perform this task. Contact your system administrator for assistance.

Now, I am installing, and logged in all the time, as administrator! So I have admin privledges no doubt.

Even after following the help link file for this error message, there is still the problem. It tells me to make sure that the DTC is started on the Network Service Account, which it is, and to restart the service and try again... did this but I still get the error.

|||I also have this installation problem installing Enterprise edition (with admin priveleges.)

Again, no problem with DTC running.

I do have SQL 2000 installed.|||

Hi all-
I'm new here, but found this when searching for the error I recieved.
I just attended the Launch event here in Chicago yesterday, and decided to install on my home system. I recieved the similar errors as discussed here (trying to install all features.

Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The default full-text language is not supported by the full-text search component.. Refer to the server error logs and Setup logs for detailed error information.

I'll try without integration services too

Hardware shouldn't be an issue:
Dual XEON 2.2
2GB Ram
XP SP2
8 GBdisk free

|||

Hi
I am using Microsoft 2005 RTM version and recieved the same error.

Failed to install and configure assemblies C:\Program Files\Microsoft SQL

Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.

Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted

CTP September version was working properly on my machine, can any one help

me

Thanks

|||

Issue resolved.

see my new thread about installation issue resolved

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1

Insidious Bug?

This looks like a bug to me, can someone verify that this is faulty behavior or tell me why it is proper?

Two stored procedures are defined, each creates a temporary table of the same name, but with different definitions. Both procedures compile successfully. If procedure Two is executed by itself, errors are produced. Once procedure One has been run, then both procedures succeed.

It seems to be an issue of improperly resolving the definition of the temporary table.

Thanks

drop procedure one

go

create procedure one

as

begin

create table #salt(

a int not null,

b int not null,

c varchar(100)

)

insert #salt values( 1, 1, 'Fred' )

insert #salt values( 1, 2, 'Barney' )

insert #salt values( 1, 3, 'Wilma' )

insert #salt values( 2, 1, 'Betty' )

insert #salt values( 2, 2, 'Pebbles' )

insert #salt values( 2, 3, 'BamBam' )

insert #salt values( 3, 1, 'Dino' )

Selecta,

b

From#salt

end

go

drop procedure two

go

create procedure two

as

begin

create table #salt(

a int not null,

b int not null

)

insert #salt

Execone

Select*

From#salt

end

go

--Exec one

go

Exec two

go

This is by design and has to do with how we compile modules/batches. When you run SP two for the first time without running one before, we will try to compile the definition of SP two. And when we hit the call to SP one we will try to compile it. At this point the temporary table #salt exists and the compilation will use that as definition. This needs to be done to allow scenarios where you can create a temporary table in one SP and reference it any SPs that you call without creating it. The error message happens now because the table definition is different and/or you already have the object created. If you run SP one first then there is no temporary table at the time of compilation and the definition inside the SP will be used. This plan is cached and it will be reused later when you call SP two so it will work fine. Part of this has to do with deferred name resolution and compilation which will kick-in here because of the use of temporary table.

The moral is that you should avoid creating temporary tables with same name and different definitions in multiple SPs that will call one another. The results can often be unpredictable if you don't know the exact call order. And if you have statements or constructs that will be deferred to run-time for resolution/compilation it becomes even more problematic.

|||

Thanks for the information. It certainly explains the problem.

However, it really seems like a bad design or at least a lazy one. There is a different meaning to two procedures creating temporary tables and two procedures sharing temp tables. Furthermore, the meaning of each case is clear to the compiler as one contains a new Create Table at the inner level. And this design is inconsistent with the rest of the implementation. Once the second Create Table is executed there are two temp tables. In other words, the compiler is forcing the table to share definitions even though they do not share the same instances.

As a practical matter, this behavior is very difficult to deal with. The very fact that inconsistent behavior is produced based on the order of execution points that out. The error message received can vary wildly based on the actual statements involved. I encountered this by calling a procedure written by someone sharing my office and it was more a wild stab that I got it fixed. Imagine calling code delivered with a purchased package. It does not seem reasonable that a developer should have to be aware of the implementation of every stored procedure they might call.

Thanks again for the explanation.