install SQL on WinXP: March 2012

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.
- 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.

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

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,

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')

-----------------------
-----------------------
--

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.

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)
>

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.

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.

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 ?

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 INSERT to the second table

Hi, everyone, I write a SP and the first table can be inserted succesfully, but the second fails.
However there are not any error message to occur, just passes it. Anyone can give me a tip?
I am a begineer of SQL.


CREATE PROCEDURE sp_FinalizePurchase
 @.Inv_shipAddress as varchar(50),
 @.Inv_shipCity as VarChar(50),
 @.Inv_shipProvince as VarChar(20),
 @.Inv_shipPostalCode as Char(6),
 @.Inv_shipPhone as VarChar(10),
 @.INV_billAddress as VarChar(50),
 @.INV_billCity as VarChar(50),
 @.INV_billProvince as VarChar(20),
 @.INV_billPostalCode as Char(6),
 @.INV_billPhone as Char(10),
 @.CUS_customerID as Int,
 @.Inv_invoiceID as Int OutputAS
-- STEP 1
--Do the Insert
 INSERT tblInvoice
 (Inv_date,
 Inv_shipAddress,
 Inv_shipCity,
 Inv_shipProvince,
 Inv_shipPostalCode,
 Inv_shipPhone,
 INV_billAddress,
 INV_billCity,
 INV_billProvince,
 INV_billPostalCode,
 INV_billPhone,
 INV_status,
 CUS_customerID
 )
 VALUES
 (getdate(),
 @.Inv_shipAddress,
 @.Inv_shipCity,
 @.Inv_shipProvince,
 @.Inv_shipPostalCode,
 @.Inv_shipPhone,
 @.INV_billAddress,
 @.INV_billCity,
 @.INV_billProvince,
 @.INV_billPostalCode,
 @.INV_billPhone,
 1,
 @.CUS_customerid)
--FIND OUT WHAT THEIR NEW ID IS
 SELECT @.Inv_invoiceid = @.@.identity
-- STEP 2:
--Do the Insert
 INSERT Into tblInvoiceLine
 (INV_invoiceID,
 PRD_productID,
 ILN_description,
 ILN_quantity,
 ILN_unitprice
 )
 SELECT DISTINCT
 @.Inv_invoiceid,
 tblBasket.productID,
 tblMovie.mov_description,
 tblBasket.quantity,
 tblProduct.PRD_Price
 FROM tblBasket, tblProduct, tblMovie
 WHERE tblBasket.productID=tblProduct.PRD_ProductID

I suspect it's this:


 SELECT DISTINCT
 @.Inv_invoiceid,
 tblBasket.productID,
 tblMovie.mov_description,
 tblBasket.quantity,
 tblProduct.PRD_Price
 FROM tblBasket, tblProduct, tblMovie
 WHERE tblBasket.productID=tblProduct.PRD_ProductID

You're not giving it any join criteria.|||Thank your hints, I have added another join criteria as follows but it still does not work correctly,just skips it.

SELECT DISTINCT
@.Inv_invoiceid,
tblBasket.productID,
tblMovie.mov_description,
tblBasket.quantity,
tblProduct.PRD_Price
FROM tblBasket, tblProduct, tblMovie
WHERE tblBasket.productID=tblProduct.PRD_ProductID
AND tblProduct.MOV_movieID=tblMovie.MOV_MovieID

Any suggestions I can get from your guys?|||remove the@. sign at the second line.

hth|||Does the Select query work in Query Analyzer? If the select query works, then add the insert to the beginning of it and see if that works. If that doesn't, it's either because the select query returns no records, there is a syntax error, or some constraint has been violated. QA will give you a hint in any of those cases. Try that.

Also, a more standard syntax for joins is:


SELECT DISTINCT
@.Inv_invoiceid,
tblBasket.productID,
tblMovie.mov_description,
tblBasket.quantity,
tblProduct.PRD_Price
FROM tblBasket b
join tblProduct p
 on b.productID = p.PRD_ProductID
join tblMovie m
 on p.MOV_movieID = m.MOV_MovieID

|||First, I would like to say I have solved the problem. Thank your guys's hints.
Second, I want to share my experience with your guys.

To upstairs 2 friends:

ndinakar says should "remove the @. sign at the second line.", I have to say this is wrong. Because the parameter @.Inv_invoiceid come from the the first table and it is a variable.

As I have told, the SP runs properly in QA, but it does not insert the data into the table. Paraigh analyse the reasons, "it's either because the select query returns no records, there is a syntax error, or some constraint has been violated." what you said is partly correct. This is really a "syntax error" but QA skips it. I look into it carefully and eventually I find the reason occurs in the tblMovie.mov_description field. In tblmovie, I claim the varchar length 255, but in tblinvoiceline I claim the varchar length is 50. It passes the QA but occurs error in runtime.

I think this is syntax error but QA seems no regard it as an error and skips it. In my opinion, this is a needed improvement aspects in SQL Server.

Can not insert into table that have IDENTITY

Hi All,
I have 2 table. Table one is CREATE TABLE [coba] (
[id] [int] IDENTITY (1, 1) NOT NULL ,
[desc] [char] (10) ).
Table two is CREATE TABLE [coba2] (
[id] [int] IDENTITY (1, 1) NOT NULL ,
[desc] [char] (10) ).
In table coba i insert data such as :
insert into coba (desc) values ('a')
insert into coba (desc) values ('b')
insert into coba (desc) values ('c')
And if i try to show with select * from coba. It will show
1 a
2 b
3 c
The problem is that i want to transfer all of the record in table coba
into coba2. I used this query "insert into coba2 select * from coba".
It show error like this "An explicit value for the identity column in
table 'coba2' can only be specified when a column list is used and
IDENTITY_INSERT is ON."
So, does anyone know how to insert all records in table coba into
coba2?
Thank you very much for your help.I have tried this out and the following will work:
INSERT INTO coba2
SELECT [desc] from coba|||Name the columns for both the INSERT statement as well as the SELECT:
INSERT INTO tbl (col1, col2)
SELECT col1, col2
FROM ...
And consider whether you want to carry over the same idenity values in the t
arget table as you have
in the source table. If so, read about SET IDENTITY_INSERT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"afang" <khokimfang@.gmail.com> wrote in message
news:1146643380.200925.54580@.e56g2000cwe.googlegroups.com...
> Hi All,
> I have 2 table. Table one is CREATE TABLE [coba] (
> [id] [int] IDENTITY (1, 1) NOT NULL ,
> [desc] [char] (10) ).
> Table two is CREATE TABLE [coba2] (
> [id] [int] IDENTITY (1, 1) NOT NULL ,
> [desc] [char] (10) ).
> In table coba i insert data such as :
> insert into coba (desc) values ('a')
> insert into coba (desc) values ('b')
> insert into coba (desc) values ('c')
> And if i try to show with select * from coba. It will show
> 1 a
> 2 b
> 3 c
> The problem is that i want to transfer all of the record in table coba
> into coba2. I used this query "insert into coba2 select * from coba".
> It show error like this "An explicit value for the identity column in
> table 'coba2' can only be specified when a column list is used and
> IDENTITY_INSERT is ON."
> So, does anyone know how to insert all records in table coba into
> coba2?
> Thank you very much for your help.
>|||Thanks Tibor for your help. It works.
Rgds,
Afang

Can not insert into table that have IDENTITY

Hi All,
I have 2 table. Table one is CREATE TABLE [coba] (
[id] [int] IDENTITY (1, 1) NOT NULL ,
[desc] [char] (10) ).
Table two is CREATE TABLE [coba2] (
[id] [int] IDENTITY (1, 1) NOT NULL ,
[desc] [char] (10) ).
In table coba i insert data such as :
insert into coba (desc) values ('a')
insert into coba (desc) values ('b')
insert into coba (desc) values ('c')
And if i try to show with select * from coba. It will show
1 a
2 b
3 c
The problem is that i want to transfer all of the record in table coba
into coba2. I used this query "insert into coba2 select * from coba".
It show error like this "An explicit value for the identity column in
table 'coba2' can only be specified when a column list is used and
IDENTITY_INSERT is ON."
So, does anyone know how to insert all records in table coba into
coba2?
Thank you very much for your help.I have tried this out and the following will work:
INSERT INTO coba2
SELECT [desc] from coba|||Name the columns for both the INSERT statement as well as the SELECT:
INSERT INTO tbl (col1, col2)
SELECT col1, col2
FROM ...
And consider whether you want to carry over the same idenity values in the target table as you have
in the source table. If so, read about SET IDENTITY_INSERT.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"afang" <khokimfang@.gmail.com> wrote in message
news:1146643380.200925.54580@.e56g2000cwe.googlegroups.com...
> Hi All,
> I have 2 table. Table one is CREATE TABLE [coba] (
> [id] [int] IDENTITY (1, 1) NOT NULL ,
> [desc] [char] (10) ).
> Table two is CREATE TABLE [coba2] (
> [id] [int] IDENTITY (1, 1) NOT NULL ,
> [desc] [char] (10) ).
> In table coba i insert data such as :
> insert into coba (desc) values ('a')
> insert into coba (desc) values ('b')
> insert into coba (desc) values ('c')
> And if i try to show with select * from coba. It will show
> 1 a
> 2 b
> 3 c
> The problem is that i want to transfer all of the record in table coba
> into coba2. I used this query "insert into coba2 select * from coba".
> It show error like this "An explicit value for the identity column in
> table 'coba2' can only be specified when a column list is used and
> IDENTITY_INSERT is ON."
> So, does anyone know how to insert all records in table coba into
> coba2?
> Thank you very much for your help.
>|||Thanks Tibor for your help. It works.
Rgds,
Afangsql

Can not insert input field with length gt 128

I got this problem that really puzzled me. I used a stored procedure to
insert records into SQL. When the field of input string contained more than
128 characters, it gave me this message:
The identifier that starts with 'Today is a nice day..........Good bye'
is too long. Maximum length is 128.
But here I am not sending in an identifier name, I am sending in the actual
input which is more than 128 characters long. The input field in the data
base is defined as varchar(1000).
Any ideas?What is the size on the parameter declaration in the stored procedure? I'll
bet you a shiny new nickel it's VARCHAR(128) or CHAR(128).
"pelican" <pelican@.discussions.microsoft.com> wrote in message
news:D4B955D4-C318-4E38-BB9F-77B439561881@.microsoft.com...
>I got this problem that really puzzled me. I used a stored procedure to
> insert records into SQL. When the field of input string contained more
> than
> 128 characters, it gave me this message:
> The identifier that starts with 'Today is a nice day..........Good bye'
> is too long. Maximum length is 128.
> But here I am not sending in an identifier name, I am sending in the
> actual
> input which is more than 128 characters long. The input field in the data
> base is defined as varchar(1000).
> Any ideas?|||> What is the size on the parameter declaration in the stored procedure?
> I'll bet you a shiny new nickel it's VARCHAR(128) or CHAR(128).
Actually, it sounds like the call he is making to the database doesn't
properly encapsulate this string. It seems SQL Server has mistaken the
string for an identifier (otherwise the error would be "string or binary
data would be truncated"). This usually happens when someone uses " instead
of ' for delimiting a string, but there are other possibilities as well.
"pelican", how about showing us the actual code you are using, instead of
vaguely describing it -- then we don't have to guess. I suppose DDL for the
table you are trying to INSERT into wouldn't hurt either (see
http://www.aspfaq.com/5006).|||Good point, probably an embedded ' in the input somewhere that wasn't
properly escaped by the app. Interesting that it would pick 128 as the
cut-off size, however. I would definitely need to see the code for the SP
and the input string.
"AB - MVP" <ten.xoc@.dnartreb.noraa> wrote in message
news:u6KSE6AUFHA.2712@.TK2MSFTNGP09.phx.gbl...
> Actually, it sounds like the call he is making to the database doesn't
> properly encapsulate this string. It seems SQL Server has mistaken the
> string for an identifier (otherwise the error would be "string or binary
> data would be truncated"). This usually happens when someone uses "
> instead of ' for delimiting a string, but there are other possibilities as
> well.
> "pelican", how about showing us the actual code you are using, instead of
> vaguely describing it -- then we don't have to guess. I suppose DDL for
> the table you are trying to INSERT into wouldn't hurt either (see
> http://www.aspfaq.com/5006).
>|||> Good point, probably an embedded ' in the input somewhere that wasn't
> properly escaped by the app. Interesting that it would pick 128 as the
> cut-off size, however.
That is the maximum size for an identifier. I don't think it is an errant
', it just received this string that it thinks is supposed to be a column,
and is saying, WHOA, this column name is bigger than 128, hold on. It could
be 129 or 8000 characters... the same error will get kicked out.|||Thank you all so much! "AB - MVP" is right, once I changed the double quote
(") to single ('), it worked fine! In the stored procedure, the size on the
parameter is varchar(1000). I did not realize that the "" sign will make SQ
L
believe I was passing an identifier instead of the actually content.
You are my life saver...
"AB - MVP" wrote:

> Actually, it sounds like the call he is making to the database doesn't
> properly encapsulate this string. It seems SQL Server has mistaken the
> string for an identifier (otherwise the error would be "string or binary
> data would be truncated"). This usually happens when someone uses " inste
ad
> of ' for delimiting a string, but there are other possibilities as well.
> "pelican", how about showing us the actual code you are using, instead of
> vaguely describing it -- then we don't have to guess. I suppose DDL for th
e
> table you are trying to INSERT into wouldn't hurt either (see
> http://www.aspfaq.com/5006).
>
>|||I read about the identifier length in the help section. It said the same
thing as AB-MVP pointed out, that 128 is the maximum length per row for an
identifier. I just never dreamed that a " will do it.
Thanks a lot!|||Yeah it's called a "quoted identifier" and can be circumvented by using
"parameterized queries".
"pelican" <pelican@.discussions.microsoft.com> wrote in message
news:6F3F8CAB-1EBD-45A6-BF74-4DC272EA1804@.microsoft.com...
> Thank you all so much! "AB - MVP" is right, once I changed the double
> quote
> (") to single ('), it worked fine! In the stored procedure, the size on
> the
> parameter is varchar(1000). I did not realize that the "" sign will make
> SQL
> believe I was passing an identifier instead of the actually content.
> You are my life saver...
> "AB - MVP" wrote:
>|||Yep that's what they get for slapping a SQL statement together with +'s
instead of using parameterized queries.
"AB - MVP" <ten.xoc@.dnartreb.noraa> wrote in message
news:uGWbvCBUFHA.1896@.TK2MSFTNGP14.phx.gbl...
> That is the maximum size for an identifier. I don't think it is an errant
> ', it just received this string that it thinks is supposed to be a column,
> and is saying, WHOA, this column name is bigger than 128, hold on. It
> could be 129 or 8000 characters... the same error will get kicked out.
>

Can not initialize report server or run rsactivate

I get the following error when running the RSActivate utility:
"Unable to find Reporting Services WMI namespace = on <machinename>. Reporting Services may not be installed"
This is an urgent problem so any suggestions would be welcomed.
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=d737907db3624cb18a4c69da471c4572
*****************************************Double-check that that WMI Service is started in the Services Manager/MMC.
Edgar,
"Jared Smith via SQLMonster.com" wrote:
> I get the following error when running the RSActivate utility:
> "Unable to find Reporting Services WMI namespace => on <machinename>. Reporting Services may not be installed"
> This is an urgent problem so any suggestions would be welcomed.
> *****************************************
> * This message was posted via http://www.sqlmonster.com
> *
> * Report spam or abuse by clicking the following URL:
> * http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=d737907db3624cb18a4c69da471c4572
> *****************************************
>

Can not get sqlcmd and unable to create peer-to-peer replication.

Hi, Pros,

I am new to SQL server 2005. We have installed SQL server 2005 cluster. I tried to setup peer-to-peer replication with another standard server. Unfortunately, when I creating publication, I got error message : SQL server cound not configure "MyServer" as a Distributor [New publication Wizard] Additional information: An exception occurred whild executing a Transact_SQL statement or batch.

The Server "Myserveris already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisitingDistributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard. Changed database context to 'master'. [Microsoft SQL Server, Error: 14099]

I tried to use sqlcmd and I got another error message:

C:\>sqlcmd

HResult 0x2, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [2].

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi

shing a connection to the server. When connecting to SQL Server 2005, this failu

re may be caused by the fact that under the default settings SQL Server does not

allow remote connections..

Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Does anyone have any idea how to get the sqlcmd work?

Thank you in advance.

Hi Vicent,

You should use "sqlcmd -S %VirtualInstanceName%" (replace %VirtualInstanceName% with the virtual server name of your cluster.

For the issue of setting up distributor, have you follow the instruction in your error message?

Peng

|||

Hi, Peng,

Thanks for your kind reply. I am so glad your command works. I got another error when I tried to drop distributor from my cluster because when I setup replication the message shows the cluster has been setup as distributor.

I use sqlcmd to drop distributor and get the error message below. Do you have any idea?

C:\>sqlcmd -S myvirtualname
1> sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Thanks for your help.

|||

Hi Vincent,

The first parameter of sp_dropdistributor is not server name. Please see this page (http://msdn2.microsoft.com/en-us/library/ms173516.aspx) for the document. For example, you should say "EXEC sp_dropdistributor" or "EXEC sp_dropdistributor 1".

Peng

|||

Hi, Peng,

I tried the command EXEC, it does not work either.

C:\Documents and Settings\HCLLCLUS>sqlcmd -S myvirtualname
1> EXEC sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Do you know how to fix? Do I need to log on machine instead of virtual name? I wonder how did this distributor setup. Is there any way I can check this?

Thanks,

|||

I need to mention one more thing. I did follow the error message and tried to find Disable Publication and Distributor Wizard. It was not there. It seems the only way left for me is the command line.

Thanks.

|||

It is really my bad. I use the command to drop off distributor.

1> EXEC sp_dropdistributor
2> GO
Msg 21043, Level 16, State 1, Server virtualserver, Procedure sp_dropdistributor,
Line 50
The Distributor is not installed.
1>

It is looks like the ditributor did not installed on the server. However if I tried to configure replication via wizard, the error message shows the distributor was installed.

SQL Server could not configure ‘virtualname’ as a Distributor.

Additional information.

An exception occurred while executing a Transact-SQL statement or batch.

[Microsoft.SqlServer.ConnectionInfo]

The server ‘Virtualname’ is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the existing Distributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard. Changed database context to ‘master’. [Microsoft SQL Server Error: 14099]

|||

Could you run the following command against your cluster instance and report the result back?

SELECT srvname FROM master.dbo.sysservers WHERE srvstatus & 8 <> 0

If you get any row back, it means that your server is already defined as distributor.

Peng

|||

Hi, Peng,

I am glad to tell you. I have resolved this problem. Actually, there was a security problem when I set up replication. I went to Local Security Settings >User Rights Assignment >Lock pages in memory, I put adminstrator user in it and I was able to setup replication. Thanks for your instruction.

I have an another problem. I did not realize that it need SQL Server 2005 Enterprise edition to setup P2P replication. I had bought upraged license. However, I do not know how to upgrade SQL server 2005 standard to Enterprise edition. Does anyone know how? Thank you.

|||Run setup from the command prompt. Here are instructions on how to do this.

http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade

Can not get sqlcmd and unable to create peer-to-peer replication.

Hi, Pros,

I tried to use sqlcmd and I got another error message:

C:\>sqlcmd

HResult 0x2, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [2].

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi

shing a connection to the server. When connecting to SQL Server 2005, this failu

re may be caused by the fact that under the default settings SQL Server does not

allow remote connections..

Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Does anyone have any idea how to get the sqlcmd work?

Thank you in advance.

Hi Vicent,

You should use "sqlcmd -S %VirtualInstanceName%" (replace %VirtualInstanceName% with the virtual server name of your cluster.

For the issue of setting up distributor, have you follow the instruction in your error message?

Peng

|||

Hi, Peng,

I use sqlcmd to drop distributor and get the error message below. Do you have any idea?

C:\>sqlcmd -S myvirtualname
1> sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Thanks for your help.

|||

Hi Vincent,

Peng

|||

Hi, Peng,

I tried the command EXEC, it does not work either.

C:\Documents and Settings\HCLLCLUS>sqlcmd -S myvirtualname
1> EXEC sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Do you know how to fix? Do I need to log on machine instead of virtual name? I wonder how did this distributor setup. Is there any way I can check this?

Thanks,

|||

I need to mention one more thing. I did follow the error message and tried to find Disable Publication and Distributor Wizard. It was not there. It seems the only way left for me is the command line.

Thanks.

|||

It is really my bad. I use the command to drop off distributor.

1> EXEC sp_dropdistributor
2> GO
Msg 21043, Level 16, State 1, Server virtualserver, Procedure sp_dropdistributor,
Line 50
The Distributor is not installed.
1>

It is looks like the ditributor did not installed on the server. However if I tried to configure replication via wizard, the error message shows the distributor was installed.

SQL Server could not configure ‘virtualname’ as a Distributor.

Additional information.

An exception occurred while executing a Transact-SQL statement or batch.

[Microsoft.SqlServer.ConnectionInfo]

|||

Could you run the following command against your cluster instance and report the result back?

SELECT srvname FROM master.dbo.sysservers WHERE srvstatus & 8 <> 0

If you get any row back, it means that your server is already defined as distributor.

Peng

|||

Hi, Peng,

|||Run setup from the command prompt. Here are instructions on how to do this.

http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade

Can not get sqlcmd and unable to create peer-to-peer replication.

Hi, Pros,

I tried to use sqlcmd and I got another error message:

C:\>sqlcmd

HResult 0x2, Level 16, State 1

Named Pipes Provider: Could not open a connection to SQL Server [2].

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi

shing a connection to the server. When connecting to SQL Server 2005, this failu

re may be caused by the fact that under the default settings SQL Server does not

allow remote connections..

Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Does anyone have any idea how to get the sqlcmd work?

Thank you in advance.

Hi Vicent,

You should use "sqlcmd -S %VirtualInstanceName%" (replace %VirtualInstanceName% with the virtual server name of your cluster.

For the issue of setting up distributor, have you follow the instruction in your error message?

Peng

|||

Hi, Peng,

I use sqlcmd to drop distributor and get the error message below. Do you have any idea?

C:\>sqlcmd -S myvirtualname
1> sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Thanks for your help.

|||

Hi Vincent,

Peng

|||

Hi, Peng,

I tried the command EXEC, it does not work either.

C:\Documents and Settings\HCLLCLUS>sqlcmd -S myvirtualname
1> EXEC sp_dropdistributor 'myvirtualname'
2> GO
HResult 0x1FB2, Level 16, State 5
Error converting data type varchar to bit.
1>

Do you know how to fix? Do I need to log on machine instead of virtual name? I wonder how did this distributor setup. Is there any way I can check this?

Thanks,

|||

I need to mention one more thing. I did follow the error message and tried to find Disable Publication and Distributor Wizard. It was not there. It seems the only way left for me is the command line.

Thanks.

|||

It is really my bad. I use the command to drop off distributor.

1> EXEC sp_dropdistributor
2> GO
Msg 21043, Level 16, State 1, Server virtualserver, Procedure sp_dropdistributor,
Line 50
The Distributor is not installed.
1>

It is looks like the ditributor did not installed on the server. However if I tried to configure replication via wizard, the error message shows the distributor was installed.

SQL Server could not configure ‘virtualname’ as a Distributor.

Additional information.

An exception occurred while executing a Transact-SQL statement or batch.

[Microsoft.SqlServer.ConnectionInfo]

|||

Could you run the following command against your cluster instance and report the result back?

SELECT srvname FROM master.dbo.sysservers WHERE srvstatus & 8 <> 0

If you get any row back, it means that your server is already defined as distributor.

Peng

|||

Hi, Peng,

|||Run setup from the command prompt. Here are instructions on how to do this.

http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgradesql

Thursday, March 29, 2012

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Can not install Reporting Services, Help!

Can not install MSDE 2000A

Tuesday, March 27, 2012

can not install MSDE

Can not install July CTP with June CTP already installed

Can not install - workstation components on Longhorn x86 or x64

Can not install - workstation components on Longhorn x86 or x64

Can not INSERT to the second table

Can not insert into table that have IDENTITY

Can not insert into table that have IDENTITY

Can not insert input field with length gt 128

Can not initialize report server or run rsactivate

Can not get sqlcmd and unable to create peer-to-peer replication.

Can not get sqlcmd and unable to create peer-to-peer replication.

Can not get sqlcmd and unable to create peer-to-peer replication.

install SQL on WinXP

Blog Archive

About Me