Error installing SQL Server 2005 Upgrade Advisor

I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:

"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."

The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.

Any suggestions?

You need to be running Windows Installer 3.1. You can find it here:

http://support.microsoft.com/?id=893803

|||

I'm also having problems installing the Upgrade Advisor on a W2K server running SQL Server 2000. .net Framework 2.0 is installed as is Windows Installer 3.1.

I'm getting the follwing error message: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755."

Any ideas what might be the problem here ?

|||

You need to install Windows 2003 SP1, .NET frameworks 2.0 before installing Upgrade Advisor

You can refer http://msdn2.microsoft.com/en-us/library/ms144256.aspx

If you are still seeing install errors, you gather verbose log and post it in this newsgroup. To create verbose log:

Ex: msiexec /i SQLUASetup.msi /l*v e:\temp\verbose.log

Thanks

Sethu Srinivasan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Error installing SQL Server 2005 Upgrade Advisor

I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:

"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."

The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.

Any suggestions?

You need to be running Windows Installer 3.1. You can find it here:

http://support.microsoft.com/?id=893803

|||

I'm also having problems installing the Upgrade Advisor on a W2K server running SQL Server 2000. .net Framework 2.0 is installed as is Windows Installer 3.1.

I'm getting the follwing error message: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755."

Any ideas what might be the problem here ?

|||

You need to install Windows 2003 SP1, .NET frameworks 2.0 before installing Upgrade Advisor

You can refer http://msdn2.microsoft.com/en-us/library/ms144256.aspx

If you are still seeing install errors, you gather verbose log and post it in this newsgroup. To create verbose log:

Ex: msiexec /i SQLUASetup.msi /l*v e:\temp\verbose.log

Thanks

Sethu Srinivasan

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Error Installing RS with exising DB

I am getting the following error while attempting to install RS on a Small
Business Server 2000 box that already contains the ReportServer DB from a
previous setup where the Web portion of RS resided on another box.
The error is:
"A database with the specified name (ReportServer) already exists and is not
a valid report server database. You must either remote the existing database
or select a new database name."
What may be wrong?
Tx
AndyRS won't allow you to install onto a DB that already exists locally. If the
RS that used this database is not needed anymore, then just delete it (and
the temp database associated with it), then you can install. Or you can just
select a new name for the database when running setup.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy Schmidt" <andys@.minunteclinic.com> wrote in message
news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
>I am getting the following error while attempting to install RS on a Small
> Business Server 2000 box that already contains the ReportServer DB from a
> previous setup where the Web portion of RS resided on another box.
> The error is:
> "A database with the specified name (ReportServer) already exists and is
> not
> a valid report server database. You must either remote the existing
> database
> or select a new database name."
> What may be wrong?
> Tx
> Andy
>|||Daniel,
I don't want to re-create all of the folder structure, permissions, etc. If
I create a new db is there a way to import from the old db's tables?
Tx
Andy
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:#6$JXoAAFHA.204@.TK2MSFTNGP10.phx.gbl...
> RS won't allow you to install onto a DB that already exists locally. If
the
> RS that used this database is not needed anymore, then just delete it (and
> the temp database associated with it), then you can install. Or you can
just
> select a new name for the database when running setup.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Andy Schmidt" <andys@.minunteclinic.com> wrote in message
> news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
> >I am getting the following error while attempting to install RS on a
Small
> > Business Server 2000 box that already contains the ReportServer DB from
a
> > previous setup where the Web portion of RS resided on another box.
> >
> > The error is:
> >
> > "A database with the specified name (ReportServer) already exists and is
> > not
> > a valid report server database. You must either remote the existing
> > database
> > or select a new database name."
> >
> > What may be wrong?
> >
> > Tx
> > Andy
> >
> >
>|||You can use rsconfig to point to the old database after you install to a new
database. Just make sure that both db schemas are the same. That is if the
original DB is SP1 make sure to upgrade the new one to SP1 before using
rsconfig. You will most likely then have issues with reading encrypted
data. If you saved off your symmetric key from the old installation, after
using rsconfig you can import the key using rskeymgmt. If you did not save
the old symmetric key, after running rsconfig, run rskeymgmt -d. This will
delete all encrypted data from RS. That means you will need to enter all
your report/data source credential again.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy Schmidt" <andys@.minunteclinic.com> wrote in message
news:Ohy1KViAFHA.2316@.TK2MSFTNGP15.phx.gbl...
> Daniel,
> I don't want to re-create all of the folder structure, permissions, etc.
> If
> I create a new db is there a way to import from the old db's tables?
> Tx
> Andy
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:#6$JXoAAFHA.204@.TK2MSFTNGP10.phx.gbl...
>> RS won't allow you to install onto a DB that already exists locally. If
> the
>> RS that used this database is not needed anymore, then just delete it
>> (and
>> the temp database associated with it), then you can install. Or you can
> just
>> select a new name for the database when running setup.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Andy Schmidt" <andys@.minunteclinic.com> wrote in message
>> news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
>> >I am getting the following error while attempting to install RS on a
> Small
>> > Business Server 2000 box that already contains the ReportServer DB from
> a
>> > previous setup where the Web portion of RS resided on another box.
>> >
>> > The error is:
>> >
>> > "A database with the specified name (ReportServer) already exists and
>> > is
>> > not
>> > a valid report server database. You must either remote the existing
>> > database
>> > or select a new database name."
>> >
>> > What may be wrong?
>> >
>> > Tx
>> > Andy
>> >
>> >
>>
>sql

Error in the Metadata Manager

I'm attempting to deploy a new solution on AS 2005 developer edition. Apparently, a previous, unrelated solution deployment has a problem, and this prevents me from deploying mine. I've cleaned up the data directory, tried all sorts of options, but still I get the same thing. Here's the error:

Error 1 XML parsing failed at line 2, column 0: A document must contain exactly one root element. . Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\E:\SQL 2005\MSSQL.2\OLAP\Data\Analysis Services Project1.0.db\cluster Population By Zip ~MC.0.cub\~CaseDetail ~MG.0.det.xml'. Errors in the metadata manager. The dimension with ID of 'Population By Zip', Name of 'Population By Zip' referenced by the 'cluster Population By Zip ~MC' cube, does not exist. Errors in the metadata manager. An error occurred when loading the cluster Population By Zip ~MC cube, from the file, '\\?\E:\SQL 2005\MSSQL.2\OLAP\Data\Analysis Services Project1.0.db\cluster Population By Zip ~MC.0.cub.xml'.

any ideas?

thanks, Chris

Chris,

Did you ever get to the bottom of this? I'm having a similar problem.

-Jamie

|||

OK, fixed it thanks to this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125660&SiteID=1

Error in the Metadata Manager

I'm attempting to deploy a new solution on AS 2005 developer edition. Apparently, a previous, unrelated solution deployment has a problem, and this prevents me from deploying mine. I've cleaned up the data directory, tried all sorts of options, but still I get the same thing. Here's the error:

Error 1 XML parsing failed at line 2, column 0: A document must contain exactly one root element. . Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\E:\SQL 2005\MSSQL.2\OLAP\Data\Analysis Services Project1.0.db\cluster Population By Zip ~MC.0.cub\~CaseDetail ~MG.0.det.xml'. Errors in the metadata manager. The dimension with ID of 'Population By Zip', Name of 'Population By Zip' referenced by the 'cluster Population By Zip ~MC' cube, does not exist. Errors in the metadata manager. An error occurred when loading the cluster Population By Zip ~MC cube, from the file, '\\?\E:\SQL 2005\MSSQL.2\OLAP\Data\Analysis Services Project1.0.db\cluster Population By Zip ~MC.0.cub.xml'.

any ideas?

thanks, Chris

Chris,

Did you ever get to the bottom of this? I'm having a similar problem.

-Jamie

|||

OK, fixed it thanks to this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125660&SiteID=1

Error in sql log when restarting SQL server

Whenever we restart sql server the following error appears:
2005-12-20 12:34:22.28 server Attempting to initialize Distributed
Transaction Coordinator.
2005-12-20 12:34:22.31 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
When I check the MSDTC service in the SQL service manager to see if is
running - the service says it is running. Do I still have anything to worry
about?
We are running SL server 2000 sp3a.
thanks
MeenalHi
Checking other posts it seems that this is a warning telling you that MSDTC
has not started at the time and most people seem to ignore it. You could mak
e
the SQL Service dependent on MSDTC although this is not a usual condition an
d
will slow down the bootup process.
John
"Meenal Dhody" wrote:

> Whenever we restart sql server the following error appears:
> 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-12-20 12:34:22.31 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> When I check the MSDTC service in the SQL service manager to see if is
> running - the service says it is running. Do I still have anything to wor
ry
> about?
> We are running SL server 2000 sp3a.
> thanks
> Meenal
>
>|||Many thanks
Meenal
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ECF7845A-79A0-4D8E-91EC-0D367454B336@.microsoft.com...
> Hi
> Checking other posts it seems that this is a warning telling you that
MSDTC
> has not started at the time and most people seem to ignore it. You could
make
> the SQL Service dependent on MSDTC although this is not a usual condition
and[vbcol=seagreen]
> will slow down the bootup process.
> John
> "Meenal Dhody" wrote:
>
worry[vbcol=seagreen]|||Meenal Dhody Wrote:
> Many thanks
> Meenal
> "John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote
THis won't cause any issue because SQL server starts earlier than DTC.
This happens due to chain process, that DTC depends on RPC and it takes
long time.
If you able to access SQL server once it is released for use then ok.
Else you can add depend on in the registry of regedt32 for sql server
Cheers,
muthu
Muthu
---
Muthu's Profile: http://www.dbtalk.net/m370
View this thread: http://www.dbtalk.net/t302909

Error in sql log when restarting SQL server

Whenever we restart sql server the following error appears:
2005-12-20 12:34:22.28 server Attempting to initialize Distributed
Transaction Coordinator.
2005-12-20 12:34:22.31 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
When I check the MSDTC service in the SQL service manager to see if is
running - the service says it is running. Do I still have anything to worry
about?
We are running SL server 2000 sp3a.
thanks
MeenalHi
Checking other posts it seems that this is a warning telling you that MSDTC
has not started at the time and most people seem to ignore it. You could make
the SQL Service dependent on MSDTC although this is not a usual condition and
will slow down the bootup process.
John
"Meenal Dhody" wrote:
> Whenever we restart sql server the following error appears:
> 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-12-20 12:34:22.31 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> When I check the MSDTC service in the SQL service manager to see if is
> running - the service says it is running. Do I still have anything to worry
> about?
> We are running SL server 2000 sp3a.
> thanks
> Meenal
>
>|||Many thanks
Meenal
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ECF7845A-79A0-4D8E-91EC-0D367454B336@.microsoft.com...
> Hi
> Checking other posts it seems that this is a warning telling you that
MSDTC
> has not started at the time and most people seem to ignore it. You could
make
> the SQL Service dependent on MSDTC although this is not a usual condition
and
> will slow down the bootup process.
> John
> "Meenal Dhody" wrote:
> > Whenever we restart sql server the following error appears:
> >
> > 2005-12-20 12:34:22.28 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2005-12-20 12:34:22.31 server Failed to obtain
> > TransactionDispenserInterface: Result Code = 0x8004d01b
> >
> > When I check the MSDTC service in the SQL service manager to see if is
> > running - the service says it is running. Do I still have anything to
worry
> > about?
> > We are running SL server 2000 sp3a.
> >
> > thanks
> > Meenal
> >
> >
> >|||Meenal Dhody Wrote:
> Many thanks
> Meenal
> "John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote
THis won't cause any issue because SQL server starts earlier than DTC
This happens due to chain process, that DTC depends on RPC and it take
long time.
If you able to access SQL server once it is released for use then ok
Else you can add depend on in the registry of regedt32 for sql server
Cheers,
muth
--
Muth
----
Muthu's Profile: http://www.dbtalk.net/m37
View this thread: http://www.dbtalk.net/t30290