Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.ne
ws.teranews.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio
>|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.ne
ws.teranews.com...
> trying
> April
the[vbcol=seagreen]
> edition
> appreciated.
>|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.teran
ews.com>...[vbcol=seagreen]
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> that
> --
> --
> trying
> April
> the
> edition
> appreciated.
Showing posts with label install. Show all posts
Showing posts with label install. Show all posts
Thursday, March 29, 2012
Can not install Reporting Services, Help!
Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- Sergio
I would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio
>
|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> ----
--
> ----
--[vbcol=seagreen]
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> trying
> April
the
> edition
> appreciated.
>
|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.terane ws.com>...[vbcol=seagreen]
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> that
> --
> --
> trying
> April
> the
> edition
> appreciated.
sql
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- Sergio
I would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio
>
|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> ----
--
> ----
--[vbcol=seagreen]
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> trying
> April
the
> edition
> appreciated.
>
|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.terane ws.com>...[vbcol=seagreen]
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> that
> --
> --
> trying
> April
> the
> edition
> appreciated.
sql
Can not install Reporting Services, Help!
Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
--
-----------------------
-----------------------
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> -----------------------
--
> -----------------------
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> > Hi,
> > I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
> trying
> > to install the MS SQL Server Reporting Services that is in the MSDN of
> April
> > 2004. I also have Visual studio.net installed.
> > So when I run the CD all goes well until you specify the database for
the
> > reporting server and then I get the following error:
> > "This edition of the Report Server Database is not supported on the
> edition
> > of SQL Server 2000 you have chosen. Please choose on that matches the
> > requirements."
> > MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> > Developer edition.
> > What does this mean, any comments or feedback will be greately
> appreciated.
> > - Sergio|||I am running SQL Server developer and got the same message. However, I
continued with the installation and it works fine. That is, it works
in VS.NET 2003. I can create new "business intelligence" projects.
"SD" <npspam@.nowhere.net> wrote in message news:<ab8fe521601065edf8fa050f7602dbb6@.news.teranews.com >...
> Ha!
> I wasn't for some stupid reason I was running the personal edition. Thanks
> for your help, I would still be wasting time if I hadn't followed your
> suggestion.
> Thank you a heap.
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> > I would verify that you are running the developer addition. You can do
> that
> > by running this SELECT statement on your XP machine:
> > SELECT SERVERPROPERTY ('edition')
> > --
> > -----------------------
> --
> > -----------------------
> --
> > --
> > Need SQL Server Examples check out my website at
> > http://www.geocities.com/sqlserverexamples
> > "SD" <npspam@.nowhere.net> wrote in message
> > news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> > > Hi,
> > > > I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
> trying
> > > to install the MS SQL Server Reporting Services that is in the MSDN of
> April
> > > 2004. I also have Visual studio.net installed.
> > > > So when I run the CD all goes well until you specify the database for
> the
> > > reporting server and then I get the following error:
> > > > "This edition of the Report Server Database is not supported on the
> edition
> > > of SQL Server 2000 you have chosen. Please choose on that matches the
> > > requirements."
> > > > MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> > > Developer edition.
> > > > What does this mean, any comments or feedback will be greately
> appreciated.
> > > > - Sergio
> >|||How did you continue with the install. I have the same error, the
Developer Edition and when I get the error and click OK, it just returns
me to the same install step. Click Next again and I get the error message
again and so on...
Can not install Reporting Services, Help!
Hi,
I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm trying
to install the MS SQL Server Reporting Services that is in the MSDN of April
2004. I also have Visual studio.net installed.
So when I run the CD all goes well until you specify the database for the
reporting server and then I get the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose on that matches the
requirements."
MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
Developer edition.
What does this mean, any comments or feedback will be greately appreciated.
- SergioI would verify that you are running the developer addition. You can do that
by running this SELECT statement on your XP machine:
SELECT SERVERPROPERTY ('edition')
--
-----------------------
-----------------------
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"SD" <npspam@.nowhere.net> wrote in message
news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> Hi,
> I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
trying
> to install the MS SQL Server Reporting Services that is in the MSDN of
April
> 2004. I also have Visual studio.net installed.
> So when I run the CD all goes well until you specify the database for the
> reporting server and then I get the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose on that matches the
> requirements."
> MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> Developer edition.
> What does this mean, any comments or feedback will be greately
appreciated.
> - Sergio|||Ha!
I wasn't for some stupid reason I was running the personal edition. Thanks
for your help, I would still be wasting time if I hadn't followed your
suggestion.
Thank you a heap.
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:%23SBoVWUMEHA.3348@.TK2MSFTNGP09.phx.gbl...
> I would verify that you are running the developer addition. You can do
that
> by running this SELECT statement on your XP machine:
> SELECT SERVERPROPERTY ('edition')
> --
> -----------------------
--
> -----------------------
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "SD" <npspam@.nowhere.net> wrote in message
> news:f000323c8d8a00f8f3a9e2a81b3d483d@.news.teranew s.com...
> > Hi,
> > I'm running Windows XP and SQL Server Developer Edition (sp3) and I'm
> trying
> > to install the MS SQL Server Reporting Services that is in the MSDN of
> April
> > 2004. I also have Visual studio.net installed.
> > So when I run the CD all goes well until you specify the database for
the
> > reporting server and then I get the following error:
> > "This edition of the Report Server Database is not supported on the
> edition
> > of SQL Server 2000 you have chosen. Please choose on that matches the
> > requirements."
> > MS Requirements are SQL 2000 Standard, SQL 2000 Enterprise, and SQL 2000
> > Developer edition.
> > What does this mean, any comments or feedback will be greately
> appreciated.
> > - Sergio
Can not install MSDE 2000A
I am attempting to install the MS SQL Server Desktop Engine. I have the
MSDE2000A.exe file and it unpacks successfully. I then run the setup and get
an install fail with the following:
Install message:
Setup failed to configure the server. See the server error logs and setup
error logs.
The only server error log I can find sez the following:
2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
server Copyright (C) 1988-2002 Microsoft Corporation.
server All rights reserved.
server Server Process ID is 2716.
server Logging SQL Server messages in file 'C:\Program Files\Microsoft
SQL Server\MSSQL\LOG\ERRORLOG'.
server SQL Server is starting at priority class 'normal'(1 CPU detected).
server SQL Server configured for thread mode processing.
server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
Owner Blocks.
spid3 Warning ******************
spid3 SQL Server started in single user mode. Updates allowed to system
catalogs.
spid3 Starting up database 'master'.
server Using 'SSNETLIB.DLL' version '8.0.766'.
spid5 Starting up database 'model'.
spid3 Server name is 'BART9550'.
spid3 Skipping startup of clean database id 5
spid3 Skipping startup of clean database id 6
spid3 Starting up database 'msdb'.
spid5 Clearing tempdb database.
server SQL server listening on Shared Memory.
server SQL Server is ready for client connections
spid5 Starting up database 'tempdb'.
spid3 Recovery complete.
spid3 SQL global counter collection task is created.
spid3 Warning: override, autoexec procedures skipped.
spid3 SQL Server is terminating due to 'stop' request from Service
Control Manager.
The application event log sez:
Event Type:Warning
Event Source:MSSQLServer
Event Category:(8)
Event ID:19011
Date:2/11/2005
Time:3:22:01 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.
Also another entry sez:
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:2/11/2005
Time:3:22:00 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: 17834,
Using 'SSNETLIB.DLL' version '8.0.766'.
How do I get this install to work as I have an application that requires SQL
desktop.
Thanks...
Read the readme files that come with MSDE. You can't just run the setup.exe
with no parameters an expect to install SQL Server exactly like you would
like it configured. MSDE a developer's tool so act like a developer and do
some investigative work before trying to install it.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:555AF044-A697-401C-8D08-0121BCFAFDD4@.microsoft.com...
>I am attempting to install the MS SQL Server Desktop Engine. I have the
> MSDE2000A.exe file and it unpacks successfully. I then run the setup and
> get
> an install fail with the following:
> Install message:
> Setup failed to configure the server. See the server error logs and setup
> error logs.
> The only server error log I can find sez the following:
> 2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
> server Copyright (C) 1988-2002 Microsoft Corporation.
> server All rights reserved.
> server Server Process ID is 2716.
> server Logging SQL Server messages in file 'C:\Program Files\Microsoft
> SQL Server\MSSQL\LOG\ERRORLOG'.
> server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> server SQL Server configured for thread mode processing.
> server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> spid3 Warning ******************
> spid3 SQL Server started in single user mode. Updates allowed to
> system
> catalogs.
> spid3 Starting up database 'master'.
> server Using 'SSNETLIB.DLL' version '8.0.766'.
> spid5 Starting up database 'model'.
> spid3 Server name is 'BART9550'.
> spid3 Skipping startup of clean database id 5
> spid3 Skipping startup of clean database id 6
> spid3 Starting up database 'msdb'.
> spid5 Clearing tempdb database.
> server SQL server listening on Shared Memory.
> server SQL Server is ready for client connections
> spid5 Starting up database 'tempdb'.
> spid3 Recovery complete.
> spid3 SQL global counter collection task is created.
> spid3 Warning: override, autoexec procedures skipped.
> spid3 SQL Server is terminating due to 'stop' request from Service
> Control Manager.
> The application event log sez:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 2/11/2005
> Time: 3:22:01 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> Also another entry sez:
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 2/11/2005
> Time: 3:22:00 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> 17834,
> Using 'SSNETLIB.DLL' version '8.0.766'.
> How do I get this install to work as I have an application that requires
> SQL
> desktop.
> Thanks...
|||Hi Jim,
Thanks for the put down. Most appreciated.
I am not a developer. I am simply a computer user trying to use a program
that requires MSDE. And, I did not think that MSDE was a developer tool,
but simply a db engine that apps could plug into. But clearly you know more
than I.
And, with a little research by this end user I switched on no back out so I
could read the install log, and I supplied the setup.ini file with the
following:
BLANKSAPWD=1
SQLSecurityMode=SQL
By stopping the back out I now have SQL server running. but can not install
ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
Thanks Jim,...
Looking forward to your next put down.
BTW, I was directed to this forum by MS support as the place to receive help.
"Jim Young" wrote:
> Read the readme files that come with MSDE. You can't just run the setup.exe
> with no parameters an expect to install SQL Server exactly like you would
> like it configured. MSDE a developer's tool so act like a developer and do
> some investigative work before trying to install it.
> Jim
|||I'm sorry, my comment was most inappropriate. I'll try to help you with your
problem any way that I can.
If MSDE is running then MDAC (and the ODBC drivers) must already be
installed - SQL Server can't run without it.
I find it surprising and disappointing that the application you are trying
to install, that requires MSDE, does not make the installation of MSDE
seamless to you. What is the name of the program you are trying to install?
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:931E2080-068B-4120-BCC8-5F548C5C5B79@.microsoft.com...
> Hi Jim,
> Thanks for the put down. Most appreciated.
> I am not a developer. I am simply a computer user trying to use a program
> that requires MSDE. And, I did not think that MSDE was a developer tool,
> but simply a db engine that apps could plug into. But clearly you know
> more
> than I.
> And, with a little research by this end user I switched on no back out so
> I
> could read the install log, and I supplied the setup.ini file with the
> following:
> BLANKSAPWD=1
> SQLSecurityMode=SQL
> By stopping the back out I now have SQL server running. but can not
> install
> ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
> Thanks Jim,...
> Looking forward to your next put down.
> BTW, I was directed to this forum by MS support as the place to receive
> help.
> "Jim Young" wrote:
>
|||"Jim Young" wrote:
> I'm sorry, my comment was most inappropriate. I'll try to help you with your
> problem any way that I can.
> If MSDE is running then MDAC (and the ODBC drivers) must already be
> installed - SQL Server can't run without it.
> I find it surprising and disappointing that the application you are trying
> to install, that requires MSDE, does not make the installation of MSDE
> seamless to you. What is the name of the program you are trying to install?
Hi Jim,
Thank you. We’ll start fresh. Here’s the deal.
OS= WinXPpro.
App=ACT! 2005 (version7)
And yes, I have gone around and around with BEST software (makers of ACT!)
about the need to support the install of SQL MSDE. They claim that it is a
MS problem. However, I have used this install of XP for 2 or 3 yrs with
hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
course not all at once). FYI ACT! Is a contact manager. I have been using
v6 with a great deal of success. However, v7 is a total rewrite and uses
SQL. It is essentially version one. I don’t know that I want to trust my
data to a program that is such a problem to install, and relies on some
else’s db engine.
On to the problem:
I could only get MSDE up and running when I switched on don’t back out on
failure:
setup.exe DISABLEROLLBACK=1
I did this based on a clue that the last line in the SQL error log was:
SQL Server is terminating due to a ‘stop’ request from Service Control
Manager.
My thought was that if it can be stopped it must be running. Lo and behold
on reboot the little computer icon is in the system tray. And Task list
shows SQL server running, and sqlmangr running.
However, the drivers tab in ODBC do NOT show SQL Server. And, when I
attempt to install MDAC v2.8 it bombs out.
Part of my problem is that I don’t under stand the functional relationships
between all these elements. My thought is that SQL MSDE is the db engine,
and that MDAC drivers in the ODBC are essentally middle ware allowing the
application to access the db.
Before SQL was running, when I last attempted to install ACT! v7 the error
out was 1603 can not configure server. I have not tried to reinstall yet
wanting to get as many ducks in a row as possible.
Looking forward to your post.
Thanks
BartC
|||You're correct MSDE is the database engine, MDAC is the communication layer
between the application and the database.
The DISABLEROLLBACK option is an option for the Windows installer to not
rollback any changes to your system if the installation fails. The original
error your received, 1603, is basically a general error reporting back that
the MSDE installation failed.
It seem to me that although MSDE is apparently running, the installation is
in an inconsistent state. What I would recommend is completely unistalling
MSDE. The following link is to a KB article for manually removing MSDE from
your system.
http://support.microsoft.com/default...b;en-us;320873
On your system go to Control Panel | Add Remove Program and see if there is
an entry for removing MSDE (it may be referenced as SQL Server). If you find
it then uninstall it. If that is successful then continue with the Remove
Files and Folders part of the KB article and finish the rest of the steps on
the article, removing registry entries.
If this is all successful then you have a system that is cleaned of MSDE.
Next I would try installing MDAC 2.8 and see if you get through that
successfully. If you don't then I would not attempt to install MSDE, since I
doubt it will succeed.
Next reinstall MSDE by running setup.exe with the following command line
parameters. You could use an .ini file for the SECURITYMODE or BLANKSAPWD
options if you want. Personally, I find using the command line easier.
/Lv c:\MSDEsetup.log SECURITYMODE="SQL" BLANKSAPWD=1
This will install a default instance of MSDE to the default directories
(c:\program files\Microsoft SQL Server) with a blank sa password.
If the install fails then you should have a verbose log on the root of drive
C. Post to this group the tail end of the log where the installation start
to break down; you'll see where there is first a failure and then rollbacks
of registry entries and files.
A lot embedded database application are moving their data storage over to
MSDE. It's a very powerful and reliable environment (once you get it
installed!). The problem is that SQL Server is much more complex of an
application to install than a simple flat file database or an Access based
solution. When the installation of MSDE goes sideways, recovering from it
can be quite a lot of trouble, as you've experienced.
Good luck - I hope you are able to get MSDE finally installed.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:1D534BF8-4C6F-49D9-A7F8-CB426F7A8EE8@.microsoft.com...
> "Jim Young" wrote:
> Hi Jim,
> Thank you. We'll start fresh. Here's the deal.
> OS= WinXPpro.
> App=ACT! 2005 (version7)
> And yes, I have gone around and around with BEST software (makers of ACT!)
> about the need to support the install of SQL MSDE. They claim that it is
> a
> MS problem. However, I have used this install of XP for 2 or 3 yrs with
> hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
> course not all at once). FYI ACT! Is a contact manager. I have been
> using
> v6 with a great deal of success. However, v7 is a total rewrite and uses
> SQL. It is essentially version one. I don't know that I want to trust my
> data to a program that is such a problem to install, and relies on some
> else's db engine.
> On to the problem:
> I could only get MSDE up and running when I switched on don't back out on
> failure:
> setup.exe DISABLEROLLBACK=1
> I did this based on a clue that the last line in the SQL error log was:
> SQL Server is terminating due to a 'stop' request from Service Control
> Manager.
> My thought was that if it can be stopped it must be running. Lo and
> behold
> on reboot the little computer icon is in the system tray. And Task list
> shows SQL server running, and sqlmangr running.
> However, the drivers tab in ODBC do NOT show SQL Server. And, when I
> attempt to install MDAC v2.8 it bombs out.
> Part of my problem is that I don't under stand the functional
> relationships
> between all these elements. My thought is that SQL MSDE is the db engine,
> and that MDAC drivers in the ODBC are essentally middle ware allowing the
> application to access the db.
> Before SQL was running, when I last attempted to install ACT! v7 the error
> out was 1603 can not configure server. I have not tried to reinstall yet
> wanting to get as many ducks in a row as possible.
> Looking forward to your post.
> Thanks
> BartC
|||Hi Jim,
Well I see one error of my ways. I was installing MSDE first and then
attempting an install of MDAC 2.8.
If I understand you correctly after I remove everything I should start with
MDAC and then go on to installing MSDE.
I will try this, but it will have to wait for a day or two. The pressure of
work interfers with all the fun stuff ;-)
Thanks... I'll post results in a few days.
BartC
"Jim Young" wrote:
> snip...
> It seem to me that although MSDE is apparently running, the installation is
> in an inconsistent state. What I would recommend is completely unistalling
> MSDE. The following link is to a KB article for manually removing MSDE from
> your system.
|||It wasn't an error to install MDAC after MSDE; I just thought it would be a
good test to make sure that your system is in good order first. All windows
versions since Windows 2000 come with MDAC preinstalled, but it is best to
upgrade to 2.8 before you start the MSDE installation.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:075F0748-C889-4FA2-8E80-EE7482B059EE@.microsoft.com...
> Hi Jim,
> Well I see one error of my ways. I was installing MSDE first and then
> attempting an install of MDAC 2.8.
> If I understand you correctly after I remove everything I should start
> with
> MDAC and then go on to installing MSDE.
> I will try this, but it will have to wait for a day or two. The pressure
> of
> work interfers with all the fun stuff ;-)
> Thanks... I'll post results in a few days.
> BartC
>
>
>
> "Jim Young" wrote:
>
|||Jim,
OK, here is the latest:
re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
There was no SQL server in Add/Remove.
This in spite of the fact the icon was in the system tray, and I could call
up the control panel to start and stop the SQL server.
Soooooo... I stepped through the manual removal. And took out lots of SQL
keys that were in the registry, plus all the stuff that the KB article
suggested. Removed the temp files and the entire branch of SQL server in the
directory structure.
I also ran Registry First Aid and did a general clean up of the registry.
I then ran the MDACsetup and received the following:
MDAC 2.8 RTM is incompatible with this version of Windows. All of its
features are currently part of Windows.
There is a Details button that brought up nothing.
OK, so which is it... Incompatible with WinXP pro or already installed?
Hard to know from that error mess.
Forging ahead I ran the SQL setup with your (Jim’s) command line switches.
(See previous message.) That resulted in the same error as before... to wit:
Setup failed to configure the server. Refer to the error logs.
With the verbose log switched turned on the resultant log is 3.6 MB. I am
not going to post that (don’t think I could anyway.) There is a lot of note
1: 2360- stuff near the top, and then tons of opening and adding RegValues.
But here is the middle part. This is near the end of the install and a bit
into the rollback. It seems to vomit at (24!1C) at the config server
execution.
I am at a total loss as how to proceed.
Starting custom action CallSQLAdHlp
c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (24:B8) [06:36:45:799]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:799]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (24:B8) [06:36:46:070]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:36:46:070]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (24:B8) [06:36:46:320]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:36:46:330]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 6:37:50: InstallFinalize. Return value 3.
MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:823]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (24:B8) [06:37:50:823]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing backup files,CleanupTemplate=File: [1])
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallServices,Description=Insta lling new
services,Template=Service: [2])
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=MSSQLSERVER,Action=8,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
MSI (s) (24:B8) [06:37:51:193]: Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Registering type
libraries,Template=LibID: [1])
MSI (s) (24:B8) [06:37:51:193]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:213]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:233]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
|||This may be a long shot, but is the Server service running on your machine?
Go to Control Panel | Adminstrative Tools | Services. If it is not running
then bring up the properties for the service, set the startup to automatic
and start the service. Then try re-installing MSDE.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:B7EE12E7-D84E-4D83-96E6-70229C1F445C@.microsoft.com...
> Jim,
> OK, here is the latest:
> re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
> There was no SQL server in Add/Remove.
> This in spite of the fact the icon was in the system tray, and I could
> call
> up the control panel to start and stop the SQL server.
> Soooooo... I stepped through the manual removal. And took out lots of
> SQL
> keys that were in the registry, plus all the stuff that the KB article
> suggested. Removed the temp files and the entire branch of SQL server in
> the
> directory structure.
> I also ran Registry First Aid and did a general clean up of the registry.
> I then ran the MDACsetup and received the following:
> MDAC 2.8 RTM is incompatible with this version of Windows. All of its
> features are currently part of Windows.
> There is a Details button that brought up nothing.
> OK, so which is it... Incompatible with WinXP pro or already installed?
> Hard to know from that error mess.
> Forging ahead I ran the SQL setup with your (Jim's) command line switches.
> (See previous message.) That resulted in the same error as before... to
> wit:
> Setup failed to configure the server. Refer to the error logs.
> With the verbose log switched turned on the resultant log is 3.6 MB. I am
> not going to post that (don't think I could anyway.) There is a lot of
> note
> 1: 2360- stuff near the top, and then tons of opening and adding
> RegValues.
> But here is the middle part. This is near the end of the install and a
> bit
> into the rollback. It seems to vomit at (24!1C) at the config server
> execution.
> I am at a total loss as how to proceed.
> Starting custom action CallSQLAdHlp
> c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
> MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity succeeded
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
> MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> MSI (s) (24:B8) [06:36:46:320]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:36:46:330]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0,
> Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop
> Engine
> -- Setup failed to configure the server. Refer to the server error logs
> and
> setup error logs for more information.
> Action ended 6:37:50: InstallFinalize. Return value 3.
> MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
> MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is
> 0
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=0,Argument=1033)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
> backup files,CleanupTemplate=File: [1])
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
> SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action UnInstSQLAgentSecurity
> Starting custom action UnInstSQLAgentSecurity
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallServices,Description=Insta lling new
> services,Template=Service: [2])
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=MSSQLSERVER,Action=8,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Registering type
> libraries,Template=LibID: [1])
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:213]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:233]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
>
MSDE2000A.exe file and it unpacks successfully. I then run the setup and get
an install fail with the following:
Install message:
Setup failed to configure the server. See the server error logs and setup
error logs.
The only server error log I can find sez the following:
2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
server Copyright (C) 1988-2002 Microsoft Corporation.
server All rights reserved.
server Server Process ID is 2716.
server Logging SQL Server messages in file 'C:\Program Files\Microsoft
SQL Server\MSSQL\LOG\ERRORLOG'.
server SQL Server is starting at priority class 'normal'(1 CPU detected).
server SQL Server configured for thread mode processing.
server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
Owner Blocks.
spid3 Warning ******************
spid3 SQL Server started in single user mode. Updates allowed to system
catalogs.
spid3 Starting up database 'master'.
server Using 'SSNETLIB.DLL' version '8.0.766'.
spid5 Starting up database 'model'.
spid3 Server name is 'BART9550'.
spid3 Skipping startup of clean database id 5
spid3 Skipping startup of clean database id 6
spid3 Starting up database 'msdb'.
spid5 Clearing tempdb database.
server SQL server listening on Shared Memory.
server SQL Server is ready for client connections
spid5 Starting up database 'tempdb'.
spid3 Recovery complete.
spid3 SQL global counter collection task is created.
spid3 Warning: override, autoexec procedures skipped.
spid3 SQL Server is terminating due to 'stop' request from Service
Control Manager.
The application event log sez:
Event Type:Warning
Event Source:MSSQLServer
Event Category:(8)
Event ID:19011
Date:2/11/2005
Time:3:22:01 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.
Also another entry sez:
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:2/11/2005
Time:3:22:00 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: 17834,
Using 'SSNETLIB.DLL' version '8.0.766'.
How do I get this install to work as I have an application that requires SQL
desktop.
Thanks...
Read the readme files that come with MSDE. You can't just run the setup.exe
with no parameters an expect to install SQL Server exactly like you would
like it configured. MSDE a developer's tool so act like a developer and do
some investigative work before trying to install it.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:555AF044-A697-401C-8D08-0121BCFAFDD4@.microsoft.com...
>I am attempting to install the MS SQL Server Desktop Engine. I have the
> MSDE2000A.exe file and it unpacks successfully. I then run the setup and
> get
> an install fail with the following:
> Install message:
> Setup failed to configure the server. See the server error logs and setup
> error logs.
> The only server error log I can find sez the following:
> 2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
> server Copyright (C) 1988-2002 Microsoft Corporation.
> server All rights reserved.
> server Server Process ID is 2716.
> server Logging SQL Server messages in file 'C:\Program Files\Microsoft
> SQL Server\MSSQL\LOG\ERRORLOG'.
> server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> server SQL Server configured for thread mode processing.
> server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> spid3 Warning ******************
> spid3 SQL Server started in single user mode. Updates allowed to
> system
> catalogs.
> spid3 Starting up database 'master'.
> server Using 'SSNETLIB.DLL' version '8.0.766'.
> spid5 Starting up database 'model'.
> spid3 Server name is 'BART9550'.
> spid3 Skipping startup of clean database id 5
> spid3 Skipping startup of clean database id 6
> spid3 Starting up database 'msdb'.
> spid5 Clearing tempdb database.
> server SQL server listening on Shared Memory.
> server SQL Server is ready for client connections
> spid5 Starting up database 'tempdb'.
> spid3 Recovery complete.
> spid3 SQL global counter collection task is created.
> spid3 Warning: override, autoexec procedures skipped.
> spid3 SQL Server is terminating due to 'stop' request from Service
> Control Manager.
> The application event log sez:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 2/11/2005
> Time: 3:22:01 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> Also another entry sez:
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 2/11/2005
> Time: 3:22:00 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> 17834,
> Using 'SSNETLIB.DLL' version '8.0.766'.
> How do I get this install to work as I have an application that requires
> SQL
> desktop.
> Thanks...
|||Hi Jim,
Thanks for the put down. Most appreciated.
I am not a developer. I am simply a computer user trying to use a program
that requires MSDE. And, I did not think that MSDE was a developer tool,
but simply a db engine that apps could plug into. But clearly you know more
than I.
And, with a little research by this end user I switched on no back out so I
could read the install log, and I supplied the setup.ini file with the
following:
BLANKSAPWD=1
SQLSecurityMode=SQL
By stopping the back out I now have SQL server running. but can not install
ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
Thanks Jim,...
Looking forward to your next put down.
BTW, I was directed to this forum by MS support as the place to receive help.
"Jim Young" wrote:
> Read the readme files that come with MSDE. You can't just run the setup.exe
> with no parameters an expect to install SQL Server exactly like you would
> like it configured. MSDE a developer's tool so act like a developer and do
> some investigative work before trying to install it.
> Jim
|||I'm sorry, my comment was most inappropriate. I'll try to help you with your
problem any way that I can.
If MSDE is running then MDAC (and the ODBC drivers) must already be
installed - SQL Server can't run without it.
I find it surprising and disappointing that the application you are trying
to install, that requires MSDE, does not make the installation of MSDE
seamless to you. What is the name of the program you are trying to install?
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:931E2080-068B-4120-BCC8-5F548C5C5B79@.microsoft.com...
> Hi Jim,
> Thanks for the put down. Most appreciated.
> I am not a developer. I am simply a computer user trying to use a program
> that requires MSDE. And, I did not think that MSDE was a developer tool,
> but simply a db engine that apps could plug into. But clearly you know
> more
> than I.
> And, with a little research by this end user I switched on no back out so
> I
> could read the install log, and I supplied the setup.ini file with the
> following:
> BLANKSAPWD=1
> SQLSecurityMode=SQL
> By stopping the back out I now have SQL server running. but can not
> install
> ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
> Thanks Jim,...
> Looking forward to your next put down.
> BTW, I was directed to this forum by MS support as the place to receive
> help.
> "Jim Young" wrote:
>
|||"Jim Young" wrote:
> I'm sorry, my comment was most inappropriate. I'll try to help you with your
> problem any way that I can.
> If MSDE is running then MDAC (and the ODBC drivers) must already be
> installed - SQL Server can't run without it.
> I find it surprising and disappointing that the application you are trying
> to install, that requires MSDE, does not make the installation of MSDE
> seamless to you. What is the name of the program you are trying to install?
Hi Jim,
Thank you. We’ll start fresh. Here’s the deal.
OS= WinXPpro.
App=ACT! 2005 (version7)
And yes, I have gone around and around with BEST software (makers of ACT!)
about the need to support the install of SQL MSDE. They claim that it is a
MS problem. However, I have used this install of XP for 2 or 3 yrs with
hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
course not all at once). FYI ACT! Is a contact manager. I have been using
v6 with a great deal of success. However, v7 is a total rewrite and uses
SQL. It is essentially version one. I don’t know that I want to trust my
data to a program that is such a problem to install, and relies on some
else’s db engine.
On to the problem:
I could only get MSDE up and running when I switched on don’t back out on
failure:
setup.exe DISABLEROLLBACK=1
I did this based on a clue that the last line in the SQL error log was:
SQL Server is terminating due to a ‘stop’ request from Service Control
Manager.
My thought was that if it can be stopped it must be running. Lo and behold
on reboot the little computer icon is in the system tray. And Task list
shows SQL server running, and sqlmangr running.
However, the drivers tab in ODBC do NOT show SQL Server. And, when I
attempt to install MDAC v2.8 it bombs out.
Part of my problem is that I don’t under stand the functional relationships
between all these elements. My thought is that SQL MSDE is the db engine,
and that MDAC drivers in the ODBC are essentally middle ware allowing the
application to access the db.
Before SQL was running, when I last attempted to install ACT! v7 the error
out was 1603 can not configure server. I have not tried to reinstall yet
wanting to get as many ducks in a row as possible.
Looking forward to your post.
Thanks
BartC
|||You're correct MSDE is the database engine, MDAC is the communication layer
between the application and the database.
The DISABLEROLLBACK option is an option for the Windows installer to not
rollback any changes to your system if the installation fails. The original
error your received, 1603, is basically a general error reporting back that
the MSDE installation failed.
It seem to me that although MSDE is apparently running, the installation is
in an inconsistent state. What I would recommend is completely unistalling
MSDE. The following link is to a KB article for manually removing MSDE from
your system.
http://support.microsoft.com/default...b;en-us;320873
On your system go to Control Panel | Add Remove Program and see if there is
an entry for removing MSDE (it may be referenced as SQL Server). If you find
it then uninstall it. If that is successful then continue with the Remove
Files and Folders part of the KB article and finish the rest of the steps on
the article, removing registry entries.
If this is all successful then you have a system that is cleaned of MSDE.
Next I would try installing MDAC 2.8 and see if you get through that
successfully. If you don't then I would not attempt to install MSDE, since I
doubt it will succeed.
Next reinstall MSDE by running setup.exe with the following command line
parameters. You could use an .ini file for the SECURITYMODE or BLANKSAPWD
options if you want. Personally, I find using the command line easier.
/Lv c:\MSDEsetup.log SECURITYMODE="SQL" BLANKSAPWD=1
This will install a default instance of MSDE to the default directories
(c:\program files\Microsoft SQL Server) with a blank sa password.
If the install fails then you should have a verbose log on the root of drive
C. Post to this group the tail end of the log where the installation start
to break down; you'll see where there is first a failure and then rollbacks
of registry entries and files.
A lot embedded database application are moving their data storage over to
MSDE. It's a very powerful and reliable environment (once you get it
installed!). The problem is that SQL Server is much more complex of an
application to install than a simple flat file database or an Access based
solution. When the installation of MSDE goes sideways, recovering from it
can be quite a lot of trouble, as you've experienced.
Good luck - I hope you are able to get MSDE finally installed.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:1D534BF8-4C6F-49D9-A7F8-CB426F7A8EE8@.microsoft.com...
> "Jim Young" wrote:
> Hi Jim,
> Thank you. We'll start fresh. Here's the deal.
> OS= WinXPpro.
> App=ACT! 2005 (version7)
> And yes, I have gone around and around with BEST software (makers of ACT!)
> about the need to support the install of SQL MSDE. They claim that it is
> a
> MS problem. However, I have used this install of XP for 2 or 3 yrs with
> hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
> course not all at once). FYI ACT! Is a contact manager. I have been
> using
> v6 with a great deal of success. However, v7 is a total rewrite and uses
> SQL. It is essentially version one. I don't know that I want to trust my
> data to a program that is such a problem to install, and relies on some
> else's db engine.
> On to the problem:
> I could only get MSDE up and running when I switched on don't back out on
> failure:
> setup.exe DISABLEROLLBACK=1
> I did this based on a clue that the last line in the SQL error log was:
> SQL Server is terminating due to a 'stop' request from Service Control
> Manager.
> My thought was that if it can be stopped it must be running. Lo and
> behold
> on reboot the little computer icon is in the system tray. And Task list
> shows SQL server running, and sqlmangr running.
> However, the drivers tab in ODBC do NOT show SQL Server. And, when I
> attempt to install MDAC v2.8 it bombs out.
> Part of my problem is that I don't under stand the functional
> relationships
> between all these elements. My thought is that SQL MSDE is the db engine,
> and that MDAC drivers in the ODBC are essentally middle ware allowing the
> application to access the db.
> Before SQL was running, when I last attempted to install ACT! v7 the error
> out was 1603 can not configure server. I have not tried to reinstall yet
> wanting to get as many ducks in a row as possible.
> Looking forward to your post.
> Thanks
> BartC
|||Hi Jim,
Well I see one error of my ways. I was installing MSDE first and then
attempting an install of MDAC 2.8.
If I understand you correctly after I remove everything I should start with
MDAC and then go on to installing MSDE.
I will try this, but it will have to wait for a day or two. The pressure of
work interfers with all the fun stuff ;-)
Thanks... I'll post results in a few days.
BartC
"Jim Young" wrote:
> snip...
> It seem to me that although MSDE is apparently running, the installation is
> in an inconsistent state. What I would recommend is completely unistalling
> MSDE. The following link is to a KB article for manually removing MSDE from
> your system.
|||It wasn't an error to install MDAC after MSDE; I just thought it would be a
good test to make sure that your system is in good order first. All windows
versions since Windows 2000 come with MDAC preinstalled, but it is best to
upgrade to 2.8 before you start the MSDE installation.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:075F0748-C889-4FA2-8E80-EE7482B059EE@.microsoft.com...
> Hi Jim,
> Well I see one error of my ways. I was installing MSDE first and then
> attempting an install of MDAC 2.8.
> If I understand you correctly after I remove everything I should start
> with
> MDAC and then go on to installing MSDE.
> I will try this, but it will have to wait for a day or two. The pressure
> of
> work interfers with all the fun stuff ;-)
> Thanks... I'll post results in a few days.
> BartC
>
>
>
> "Jim Young" wrote:
>
|||Jim,
OK, here is the latest:
re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
There was no SQL server in Add/Remove.
This in spite of the fact the icon was in the system tray, and I could call
up the control panel to start and stop the SQL server.
Soooooo... I stepped through the manual removal. And took out lots of SQL
keys that were in the registry, plus all the stuff that the KB article
suggested. Removed the temp files and the entire branch of SQL server in the
directory structure.
I also ran Registry First Aid and did a general clean up of the registry.
I then ran the MDACsetup and received the following:
MDAC 2.8 RTM is incompatible with this version of Windows. All of its
features are currently part of Windows.
There is a Details button that brought up nothing.
OK, so which is it... Incompatible with WinXP pro or already installed?
Hard to know from that error mess.
Forging ahead I ran the SQL setup with your (Jim’s) command line switches.
(See previous message.) That resulted in the same error as before... to wit:
Setup failed to configure the server. Refer to the error logs.
With the verbose log switched turned on the resultant log is 3.6 MB. I am
not going to post that (don’t think I could anyway.) There is a lot of note
1: 2360- stuff near the top, and then tons of opening and adding RegValues.
But here is the middle part. This is near the end of the install and a bit
into the rollback. It seems to vomit at (24!1C) at the config server
execution.
I am at a total loss as how to proceed.
Starting custom action CallSQLAdHlp
c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (24:B8) [06:36:45:799]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:799]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (24:B8) [06:36:46:070]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:36:46:070]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (24:B8) [06:36:46:320]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:36:46:330]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 6:37:50: InstallFinalize. Return value 3.
MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:823]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (24:B8) [06:37:50:823]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing backup files,CleanupTemplate=File: [1])
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallServices,Description=Insta lling new
services,Template=Service: [2])
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=MSSQLSERVER,Action=8,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
MSI (s) (24:B8) [06:37:51:193]: Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Registering type
libraries,Template=LibID: [1])
MSI (s) (24:B8) [06:37:51:193]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:213]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:233]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
|||This may be a long shot, but is the Server service running on your machine?
Go to Control Panel | Adminstrative Tools | Services. If it is not running
then bring up the properties for the service, set the startup to automatic
and start the service. Then try re-installing MSDE.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:B7EE12E7-D84E-4D83-96E6-70229C1F445C@.microsoft.com...
> Jim,
> OK, here is the latest:
> re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
> There was no SQL server in Add/Remove.
> This in spite of the fact the icon was in the system tray, and I could
> call
> up the control panel to start and stop the SQL server.
> Soooooo... I stepped through the manual removal. And took out lots of
> SQL
> keys that were in the registry, plus all the stuff that the KB article
> suggested. Removed the temp files and the entire branch of SQL server in
> the
> directory structure.
> I also ran Registry First Aid and did a general clean up of the registry.
> I then ran the MDACsetup and received the following:
> MDAC 2.8 RTM is incompatible with this version of Windows. All of its
> features are currently part of Windows.
> There is a Details button that brought up nothing.
> OK, so which is it... Incompatible with WinXP pro or already installed?
> Hard to know from that error mess.
> Forging ahead I ran the SQL setup with your (Jim's) command line switches.
> (See previous message.) That resulted in the same error as before... to
> wit:
> Setup failed to configure the server. Refer to the error logs.
> With the verbose log switched turned on the resultant log is 3.6 MB. I am
> not going to post that (don't think I could anyway.) There is a lot of
> note
> 1: 2360- stuff near the top, and then tons of opening and adding
> RegValues.
> But here is the middle part. This is near the end of the install and a
> bit
> into the rollback. It seems to vomit at (24!1C) at the config server
> execution.
> I am at a total loss as how to proceed.
> Starting custom action CallSQLAdHlp
> c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
> MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity succeeded
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
> MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> MSI (s) (24:B8) [06:36:46:320]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:36:46:330]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0,
> Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop
> Engine
> -- Setup failed to configure the server. Refer to the server error logs
> and
> setup error logs for more information.
> Action ended 6:37:50: InstallFinalize. Return value 3.
> MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
> MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is
> 0
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=0,Argument=1033)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
> backup files,CleanupTemplate=File: [1])
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
> SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action UnInstSQLAgentSecurity
> Starting custom action UnInstSQLAgentSecurity
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallServices,Description=Insta lling new
> services,Template=Service: [2])
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=MSSQLSERVER,Action=8,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Registering type
> libraries,Template=LibID: [1])
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:213]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:233]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
>
Tuesday, March 27, 2012
can not install MSDE
Hi
I have installed .net framework 1.1 and .net web matrix from 'sams teach yourself asp.net' CD. I installed MSDE from the same CD, its not giving any error, but at the end it does not promt to restart the computer, even after restarting I can not see the MSDE icon in the system tray, also I dont see MSDE in the add/remove programs in control panel.I installed sql2kdesksp3.exe from www.asp.net/msde/, but the same thing repeats.
I have installed .net framework 1.1 and .net web matrix from 'sams teach yourself asp.net' CD. I installed MSDE from the same CD, its not giving any error, but at the end it does not promt to restart the computer, even after restarting I can not see the MSDE icon in the system tray, also I dont see MSDE in the add/remove programs in control panel.I installed sql2kdesksp3.exe from www.asp.net/msde/, but the same thing repeats.
1. Shld I install the sql2kasp3.exe(Analysis services companents) and sql2ksp3.exe(Databasre components) also?
I am new to asp,It will be helpful if somebody can tell me how to install MSDE.
ThanksHere are step-by-step instructions. Try going over them again in case the machine didn't install it properly:
http://www.asp.net/webmatrix/guidedtour/Appendices/installMsde.aspx|||Hii
I Installed MSDE via command line as given in tht site and there was no error but dint get tht MSDE icon in system tray.
I tried to install MSDE via batch file, there was no error, but when started the MSDE service, I couldnt see the "MSSQLSERVER", there is only MSSQLServiceASHelper, when clicked on it it gives the error as
"could not start the MSSQLServerADHelper service on Local Computer
eror2:The system cannot find the file specified"
Now wht shld I do??Can I download the missing file separately.I installed from the cd again and the same repeated.plzz tell me whtt I shld do now.
Thank You|||Yeah, follow the directions here to reinstall:
http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1|||Hi
I tried by installing from tht site, to install it again it takes another 8 to 10hours as I use dialup connection.Cant I download the missing file separately?|||The files you point to are Service Pack 3 files for SQL Server 2000. You need this file to patch MSDE with SP3: Sql2kdesksp3.exe
Check out the SQL Server and MSDE Service Pack 3a update page:
http://www.microsoft.com/sql/downloads/2000/SP3.asp
You may be able to order on CD, or at least download the correct file.|||Thanks a lot for answering me, I am downloading it again from the given site, if the same problem repeates then I'll buy the Cd.
Does SQL server 2000 and MSDE work the same way?
Thank you.|||Pretty much. MSDE doesn't have all the high-end features that SQL Server has, nor does it have a graphical interface designer like Query Analyzer or Enterprise Manager.
Can not install July CTP with June CTP already installed
I was thinking the installing July CTP upon June CTP is like installing a service pack, but the set up tells me the upgrade was blocked.
Any one has any idea how to install July CTP on a server with June CTP installed already?
Do I have to back up all the databases and uninstall June CTP and do a installation of July CTP from scratch and restored all the databases or is there a way of upgrading to July CTP?
Any comments and inputs are highly appreciated.
Bo
Hi Bo,
We are currently not supporting a direct upgrade between the two CTPs. You should however be able to backup your database, uninstall the June CTP, install the July CTP and then attach your database. This should be the easiest route between the two CTPs.
Thank you,
Elisa Flasko
Program Manager, Data Programmability
It worked for me, though it seems a little bit tedious.
Thanks a lot for your advice, Elisa.
sql
Can not install - workstation components on Longhorn x86 or x64
Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?
I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?
(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Actually, I postponed x64 tests.
On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.
I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.
|||Has anyone been able to get reporting services for Katmai running on Longhorn?
Thanks,
Can not install - workstation components on Longhorn x86 or x64
Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?
I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?
(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Actually, I postponed x64 tests.
On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.
I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.
|||Has anyone been able to get reporting services for Katmai running on Longhorn?
Thanks,
Can not find Microsoft.SqlServer.InstApi when trying to run a SMO trace
I install the follwing components
1.Microsoft SQL Server 2005 Management Objects Collection
2.Microsoft Core XML Services (MSXML) 6.0
3.Microsoft SQL Server Native Client
(available from http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&DisplayLang=en)
on a clean machine with no SQL Server 2005 client tools.
I get the following error.
Failed to initialize object as reader.
Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
A gacutil tells me that this assembly is not installed.
Is there are way to run SMO trace without having to install the 2005 client tools and only the Management Objects Collection and necessary components?
Sample code:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using Microsoft.SqlServer.Management.Trace;
using Microsoft.SqlServer.Management.Common;
namespace SMOTraceTestProgram
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void bStart_Click(object sender, EventArgs e)
{
TraceServer smoTraceServerReader;
ConnectionInfoBase cInfoBase = new SqlConnectionInfo();
SetupConnectionInfoBase((cInfoBase as SqlConnectionInfo));
smoTraceServerReader = new TraceServer();
try
{
smoTraceServerReader.InitializeAsReader(cInfoBase, "2005NOSPIDFilter.tdf");
smoTraceServerReader.Stop();
MessageBox.Show("Trace Started and stopped successfully");
}
catch (Exception exception)
{
StringBuilder sb = new StringBuilder();
sb.Append(exception.Message);
Exception ex = exception.InnerException;
while(ex != null)
{
sb.Append(ex.Message);
ex = ex.InnerException;
}
MessageBox.Show(sb.ToString());
}
}
private void SetupConnectionInfoBase(SqlConnectionInfo sqlConnectionInfo)
{
sqlConnectionInfo.ServerName = eSeverName.Text;
if (eUserName.Text.Length > 0)
{
sqlConnectionInfo.UserName = eUserName.Text;
sqlConnectionInfo.Password = ePassword.Text;
sqlConnectionInfo.UseIntegratedSecurity = false;
}
else
{
sqlConnectionInfo.UseIntegratedSecurity = true;
}
}
}
}
I have reproduced this issue in house and can confirm that this is a problem with the Microsoft SQL Server 2005 Management Objects Collection. We will consider this issue for inclusion in Service Pack 2.
As for workarounds, I don't have one. I tried Gac'cing the missing DLL, but there is apparently more registration required, as evidenced by the new error message I got. ("Failed to initialize object as reader.Failed to get SQL Tools directory path from InstAPI.")
|||Thanks James,
Appreciate the feedback. For the time being I will get the users of my profiling tool to install management tools from the SQL Server 2005 Install. This seems to install the necessary components for SMO Trace to work.
Look forward to a fix though, as this installs a lot more than is required.
sqlcan not download service pack 2 for xp home after computor restore
i have been trying to re install SP2 for xp home since my computor had to be restored to factory settings,but for some reason it is not being found in automatic updates,it finds 87security updates for xp home but thats it . can anyone help plz
what the tool you used to find the pending updates. use Microsoft Baseline Security Analyzer.. ...otherwise you can directly install sp2 , if select @.@.Version is not showing sp2 ..
http://www.microsoft.com/technet/security/tools/mbsahome.mspx
Madhu
Sunday, March 25, 2012
Can not create my Publisher
Hi,
I install Sql server 2000 on a server named JMI_SQL
After Installation we decide to rename the server JMI_SQL for SQL2007
I create a Distributor on the server SQLDIST2007
Once my distibutor created i try to create my Publisher on SQL2007 and I
receive this message
Error 18482 Could not connec to server SqlDIST2007 because JMI_SQL is not
defined as a remote Server
In the Wizard when I was creating my Publisher I select SQl2007 as Publisher
and the wizard is looking for JMI_SQL which the old name of the server
I try those commands in sql query analyser to get some information
select @.@.servername Show JMI_SQL
SELECT srvname, srvid
FROM sysservers
Show this
ADAMM_DB1
BESERVER_DB2
CATALOG_DB3
JMI_SQL0
repl_distributor 4
In the tables master.sysservers I try to Change manually all the JMI_SQL for
SQL2007 Sql server dont let me change it
Is there a way that I can change the JMI_SQL for SQL2007 in the sysservers
table
I would like to avoid to uninstall and reinstall Sql Server 2000
Before trying to do something I would like to have an advise from
experimented person on how to do that.
Thanks in advance and have a nice day!
Hi Gav,
Thanks a lot for the information
I appreciate very much !
Have a nice day
"Gav" wrote:
> Using Query Analyzer, execute the following:
> Use master
> go
> sp_dropserver 'JMI_SQL', droplogins
> go
> sp_addserver 'SQL2007', LOCAL
> go
> After you have done this make sure you restart the SQL service or restart
> your computer (whichever you fancy!) and that should do it
> Regards
> Gav
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:65162A3C-16DB-43C1-884D-601056BEFAF8@.microsoft.com...
>
>
sql
I install Sql server 2000 on a server named JMI_SQL
After Installation we decide to rename the server JMI_SQL for SQL2007
I create a Distributor on the server SQLDIST2007
Once my distibutor created i try to create my Publisher on SQL2007 and I
receive this message
Error 18482 Could not connec to server SqlDIST2007 because JMI_SQL is not
defined as a remote Server
In the Wizard when I was creating my Publisher I select SQl2007 as Publisher
and the wizard is looking for JMI_SQL which the old name of the server
I try those commands in sql query analyser to get some information
select @.@.servername Show JMI_SQL
SELECT srvname, srvid
FROM sysservers
Show this
ADAMM_DB1
BESERVER_DB2
CATALOG_DB3
JMI_SQL0
repl_distributor 4
In the tables master.sysservers I try to Change manually all the JMI_SQL for
SQL2007 Sql server dont let me change it
Is there a way that I can change the JMI_SQL for SQL2007 in the sysservers
table
I would like to avoid to uninstall and reinstall Sql Server 2000
Before trying to do something I would like to have an advise from
experimented person on how to do that.
Thanks in advance and have a nice day!
Hi Gav,
Thanks a lot for the information
I appreciate very much !
Have a nice day
"Gav" wrote:
> Using Query Analyzer, execute the following:
> Use master
> go
> sp_dropserver 'JMI_SQL', droplogins
> go
> sp_addserver 'SQL2007', LOCAL
> go
> After you have done this make sure you restart the SQL service or restart
> your computer (whichever you fancy!) and that should do it
> Regards
> Gav
> "GC" <GC@.discussions.microsoft.com> wrote in message
> news:65162A3C-16DB-43C1-884D-601056BEFAF8@.microsoft.com...
>
>
sql
Can not create a new instance
I have SBS2003. I am trying to install Panda Antivirus. It tries to create an
MSDE instance and fails with "setup failed to configure the server ...". I
have been through the process of deleting the previous MSDE instance
completely yet the problem still occurs. I have tried to create a manual
instance with a different name but get the same error.
Can anyone assist. I dont know where the MSDE install log file is either.
Note also that SBSmonitoring was removed and that too will not re-install
from the SBS CD.
Regards
Ian
hi Ian,
Ian wrote:
> I have SBS2003. I am trying to install Panda Antivirus. It tries to
> create an MSDE instance and fails with "setup failed to configure the
> server ...". I have been through the process of deleting the
> previous MSDE instance completely yet the problem still occurs. I
> have tried to create a manual instance with a different name but get
> the same error.
> Can anyone assist. I dont know where the MSDE install log file is
> either.
> Note also that SBSmonitoring was removed and that too will not
> re-install from the SBS CD.
>
please have a look at
http://support.microsoft.com/default...;EN-US;Q290991 for further
instructions on how manually remove a SQL Server/MSDE instance and related
clean up..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
|||Thanks.
I have looked at the steps to remove a named instance of SQL and the
instance is not in the registry. I already have an instance named
MSSQL$SHAREPOINT which works ok so I do not want to remove all instances.
What else can I try?
"Andrea Montanari" wrote:
> hi Ian,
> Ian wrote:
> please have a look at
> http://support.microsoft.com/default...;EN-US;Q290991 for further
> instructions on how manually remove a SQL Server/MSDE instance and related
> clean up..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.bizhttp://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
MSDE instance and fails with "setup failed to configure the server ...". I
have been through the process of deleting the previous MSDE instance
completely yet the problem still occurs. I have tried to create a manual
instance with a different name but get the same error.
Can anyone assist. I dont know where the MSDE install log file is either.
Note also that SBSmonitoring was removed and that too will not re-install
from the SBS CD.
Regards
Ian
hi Ian,
Ian wrote:
> I have SBS2003. I am trying to install Panda Antivirus. It tries to
> create an MSDE instance and fails with "setup failed to configure the
> server ...". I have been through the process of deleting the
> previous MSDE instance completely yet the problem still occurs. I
> have tried to create a manual instance with a different name but get
> the same error.
> Can anyone assist. I dont know where the MSDE install log file is
> either.
> Note also that SBSmonitoring was removed and that too will not
> re-install from the SBS CD.
>
please have a look at
http://support.microsoft.com/default...;EN-US;Q290991 for further
instructions on how manually remove a SQL Server/MSDE instance and related
clean up..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
|||Thanks.
I have looked at the steps to remove a named instance of SQL and the
instance is not in the registry. I already have an instance named
MSSQL$SHAREPOINT which works ok so I do not want to remove all instances.
What else can I try?
"Andrea Montanari" wrote:
> hi Ian,
> Ian wrote:
> please have a look at
> http://support.microsoft.com/default...;EN-US;Q290991 for further
> instructions on how manually remove a SQL Server/MSDE instance and related
> clean up..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.bizhttp://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
Thursday, March 22, 2012
can not connect to Report server from SQL SERVER 2005 Management studio
Hi All,
I have a brand new install of sql server 2005 on brand new WINDOWS SERVER2003 with latest versions. Every thing works fine excepting I get a 404 when I connect to report server from management studio..
I am even able to publish reports and all the
url://localhost/reportserver
url://localhost/reports
url://localhost/reportserver/reportbuilder/reportbuilder.application
all work fine on local machine and with in the network behind the fire wall.
But when I try to connect to report server using management studio on the local server or remote server, I get the following error.
"
TITLE: Microsoft SQL Server Management Studio
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
ADDITIONAL INFORMATION:
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
"
More techinal details
"===================================
Cannot connect to xxxxxxxxxxxx.
===================================
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
"
Any help would be greatly appreciated.
Bob
What are you passing in as the server name to Management Studio?
You can connect several ways
http://localhost/reportserver
servername
servername\instance
|||I passed both the servername and the servername\instance to the management studio.
My IIS and uses port 80. I can access Reportserver, report manager and report bilder thru the Internet. I just can not connect to Report server from Management studio.
I will try connecting to RS is Management studo using http://localhost/reportserver.
Regards
Bobba
|||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
||||||bobba wrote:
Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
Indeed, I am very interested in disvoering the answer. We had a developer in our organization with the same problem and could only connect by enterting http://localhost/reportserver. The DBA team is fine using servername\instance.
Is this a bug that will be resolved?
thanks in advance,
Jason Wall
|||You should be able to connect using machine\instance. This method uses WMI to get the url for SOAP calls. Will you try opening the report server config tool? Can this tool connect to the machine? Are you specifying the same instance name listed in the config tool connection dialog?|||I have the same problem.
I can connect to the reporting service by using machine\instance in report server config tool.
But I cannot connect to the reporting service through managment studio by providing machine\instance, instead, if I use http://localhost/reportserver, I can connect to the report server through management studio.
I even tried to uninstall the report service, and reinstall it again. This problem still exists.
But the same thing does not happen on my colleague's machine.
I think it is better to look into this issue...
|||I managed to solve this problem...
If you want to use machine\instance to connect Management studio.
You need to make sure in rsreportservice.config, element <UrlRoot>http://localhost/reportserver</UrlRoot> is correctly configured. (You can test this by visit this url)
I guess, the machine\instance will eventurally be translated to the <UrlRoot>. If the <UrlRoot> is not correct, then you will not be able to use machine\instance to connect report service.
|||the attempt to connect to the report server failed. check your connection information and that the report server is a compatible version(.Net 2003 version)|||I am try to solve this problem i give for this error"i have SQL 2205 with SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" as well as "http://localhost/reportserver" i am getting a error saying.
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
===================================
but if i try and connect to other reporting server on other machine using web http://servername/reportserver i m able to connect it.
but dont know whats the problem on my machine.
do i need to start any services for this...
so anybody knows how to troubleshoot this issue.
Thanks in advance...
|||
Hi,
Any solution for the above mentioned problem?
have SQL 2005 without SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" it says, "No connection could not be made because the target machine actively refused it"
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
Please post your suggestion, if you resolved it already.
Regards,
Bhuvana
|||i tried visiting this URL. it says 503, service un available error. Please give me the solution.|||Something to try:
I had the same issue, what I did to fix is goto C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services and ensure that the ASPNET user has read,read&Execute and List Folder security permissions applied to all the subdirectories also ensure that you click the 'Advance' button when applying the permissions to ensure the security settings are applied to all child objects. During my installation for some reason it did not assign the proper permissions to the ASPNET user (aspnet_wp account). It couldn't even read the config files.
good luck
sqlcan not connect to Report server from SQL SERVER 2005 Management studio
Hi All,
I have a brand new install of sql server 2005 on brand new WINDOWS SERVER2003 with latest versions. Every thing works fine excepting I get a 404 when I connect to report server from management studio..
I am even able to publish reports and all the
url://localhost/reportserver
url://localhost/reports
url://localhost/reportserver/reportbuilder/reportbuilder.application
all work fine on local machine and with in the network behind the fire wall.
But when I try to connect to report server using management studio on the local server or remote server, I get the following error.
"
TITLE: Microsoft SQL Server Management Studio
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
ADDITIONAL INFORMATION:
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
"
More techinal details
"===================================
Cannot connect to xxxxxxxxxxxx.
===================================
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
"
Any help would be greatly appreciated.
Bob
What are you passing in as the server name to Management Studio?
You can connect several ways
http://localhost/reportserver
servername
servername\instance
|||I passed both the servername and the servername\instance to the management studio.
My IIS and uses port 80. I can access Reportserver, report manager and report bilder thru the Internet. I just can not connect to Report server from Management studio.
I will try connecting to RS is Management studo using http://localhost/reportserver.
Regards
Bobba
|||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
||||||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
Indeed, I am very interested in disvoering the answer. We had a developer in our organization with the same problem and could only connect by enterting http://localhost/reportserver. The DBA team is fine using servername\instance.
Is this a bug that will be resolved?
thanks in advance,
Jason Wall
|||You should be able to connect using machine\instance. This method uses WMI to get the url for SOAP calls. Will you try opening the report server config tool? Can this tool connect to the machine? Are you specifying the same instance name listed in the config tool connection dialog?|||I have the same problem.
I can connect to the reporting service by using machine\instance in report server config tool.
But I cannot connect to the reporting service through managment studio by providing machine\instance, instead, if I use http://localhost/reportserver, I can connect to the report server through management studio.
I even tried to uninstall the report service, and reinstall it again. This problem still exists.
But the same thing does not happen on my colleague's machine.
I think it is better to look into this issue...
|||I managed to solve this problem...
If you want to use machine\instance to connect Management studio.
You need to make sure in rsreportservice.config, element <UrlRoot>http://localhost/reportserver</UrlRoot> is correctly configured. (You can test this by visit this url)
I guess, the machine\instance will eventurally be translated to the <UrlRoot>. If the <UrlRoot> is not correct, then you will not be able to use machine\instance to connect report service.
|||the attempt to connect to the report server failed. check your connection information and that the report server is a compatible version(.Net 2003 version)|||I am try to solve this problem i give for this error"i have SQL 2205 with SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" as well as "http://localhost/reportserver" i am getting a error saying.
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
===================================
but if i try and connect to other reporting server on other machine using web http://servername/reportserver i m able to connect it.
but dont know whats the problem on my machine.
do i need to start any services for this...
so anybody knows how to troubleshoot this issue.
Thanks in advance...
|||
Hi,
Any solution for the above mentioned problem?
have SQL 2005 without SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" it says, "No connection could not be made because the target machine actively refused it"
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
Please post your suggestion, if you resolved it already.
Regards,
Bhuvana
|||i tried visiting this URL. it says 503, service un available error. Please give me the solution.|||Something to try:
I had the same issue, what I did to fix is goto C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services and ensure that the ASPNET user has read,read&Execute and List Folder security permissions applied to all the subdirectories also ensure that you click the 'Advance' button when applying the permissions to ensure the security settings are applied to all child objects. During my installation for some reason it did not assign the proper permissions to the ASPNET user (aspnet_wp account). It couldn't even read the config files.
good luck
can not connect to Report server from SQL SERVER 2005 Management studio
Hi All,
I have a brand new install of sql server 2005 on brand new WINDOWS SERVER2003 with latest versions. Every thing works fine excepting I get a 404 when I connect to report server from management studio..
I am even able to publish reports and all the
url://localhost/reportserver
url://localhost/reports
url://localhost/reportserver/reportbuilder/reportbuilder.application
all work fine on local machine and with in the network behind the fire wall.
But when I try to connect to report server using management studio on the local server or remote server, I get the following error.
"
TITLE: Microsoft SQL Server Management Studio
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
ADDITIONAL INFORMATION:
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
"
More techinal details
"===================================
Cannot connect to xxxxxxxxxxxx.
===================================
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
"
Any help would be greatly appreciated.
Bob
What are you passing in as the server name to Management Studio?
You can connect several ways
http://localhost/reportserver
servername
servername\instance
|||I passed both the servername and the servername\instance to the management studio.
My IIS and uses port 80. I can access Reportserver, report manager and report bilder thru the Internet. I just can not connect to Report server from Management studio.
I will try connecting to RS is Management studo using http://localhost/reportserver.
Regards
Bobba
|||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
||||||Hi Brad Syputa,
Thank you for the suggestion. I worked. I was not able to try your suggestion immediatly as I was out of town.
Now I have this big question:
Why am I only able to connect to "report server" from "management studio" using
1. http://localhost/reportserver
and not using
2. servername
3. servername\instance.
Your help would save me a lot of time
Regards
Bobba(Bob)
Indeed, I am very interested in disvoering the answer. We had a developer in our organization with the same problem and could only connect by enterting http://localhost/reportserver. The DBA team is fine using servername\instance.
Is this a bug that will be resolved?
thanks in advance,
Jason Wall
|||You should be able to connect using machine\instance. This method uses WMI to get the url for SOAP calls. Will you try opening the report server config tool? Can this tool connect to the machine? Are you specifying the same instance name listed in the config tool connection dialog?|||I have the same problem.
I can connect to the reporting service by using machine\instance in report server config tool.
But I cannot connect to the reporting service through managment studio by providing machine\instance, instead, if I use http://localhost/reportserver, I can connect to the report server through management studio.
I even tried to uninstall the report service, and reinstall it again. This problem still exists.
But the same thing does not happen on my colleague's machine.
I think it is better to look into this issue...
|||I managed to solve this problem...
If you want to use machine\instance to connect Management studio.
You need to make sure in rsreportservice.config, element <UrlRoot>http://localhost/reportserver</UrlRoot> is correctly configured. (You can test this by visit this url)
I guess, the machine\instance will eventurally be translated to the <UrlRoot>. If the <UrlRoot> is not correct, then you will not be able to use machine\instance to connect report service.
|||the attempt to connect to the report server failed. check your connection information and that the report server is a compatible version(.Net 2003 version)|||I am try to solve this problem i give for this error"i have SQL 2205 with SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" as well as "http://localhost/reportserver" i am getting a error saying.
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
===================================
but if i try and connect to other reporting server on other machine using web http://servername/reportserver i m able to connect it.
but dont know whats the problem on my machine.
do i need to start any services for this...
so anybody knows how to troubleshoot this issue.
Thanks in advance...
|||
Hi,
Any solution for the above mentioned problem?
have SQL 2005 without SP1 installed on my machine.
and i m not bale to connect to Report Server using SQL management studio as well as from web.
i have installed reporting server and database on same machine. i tried using
"http://localhost/reportserver"
"http://localhost/reports"
"http://localhost/reportmanager"
but i am not bale to connect i am getting "Service Unavailable" page.
and when i try to connect using SQL Management Studio with "servername/instance" it says, "No connection could not be made because the target machine actively refused it"
===================================
Cannot connect to http://localhost/reportserver.
The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)
Please post your suggestion, if you resolved it already.
Regards,
Bhuvana
|||i tried visiting this URL. it says 503, service un available error. Please give me the solution.|||Something to try:
I had the same issue, what I did to fix is goto C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services and ensure that the ASPNET user has read,read&Execute and List Folder security permissions applied to all the subdirectories also ensure that you click the 'Advance' button when applying the permissions to ensure the security settings are applied to all child objects. During my installation for some reason it did not assign the proper permissions to the ASPNET user (aspnet_wp account). It couldn't even read the config files.
good luck
Subscribe to:
Posts (Atom)