Friday, March 30, 2012
Installing MSDE 2000 Release A on a XP Home Machine
I'd like to install MSDE 2000 Release A on a XP Home machine via the
command-prompt switches and parameters. I have two areas of ignorance:
1) At first blush, it seems to me that I'll have disparate server names. By
this I mean that when I install MSDE on my computer to conduct the
development, it will have the name "Server_Name"\"Instance_Name". My
server's called "Dell," So I'll have a MSDE instance of,
DELL\"Instance_Name" On the other hand, the target server, an XP Home
machine, is called "SherPerf." So this server instance will be named
SHERPERF\"Instance_Name"
I plan on using an Access adp front end. I don't know how to code viable
connection strings around disparate server names. I.E. in development I'm
connecting to server name #1; but, in production I'm connecting to server
name #2.
What am I missing?
2) If I want to use Windows Authentication, should I create a new user? If
so, what groups should this user be part of? Is it standard practice to
create a user account for MSDE programmatically? If so, how do I do this?
LDAP?
I realize this is a lot to ask. Thanks in advance.
--
Mark Holahan
You application should utilize a configuration file or the registry to store
the ADO connection string or the parameters for the connection string. Then
you would simply change the configuration information to point to another
server. Making a connection string for a different server is easy - just
replace one server name with another. See the Books Online for more
information about ADO or ADO.NET connection strings and how to construct
them.
Jim
"Mark Holahan" <mark.holahan@.unifiedllc.com> wrote in message
news:unoBXFtDFHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I'd like to install MSDE 2000 Release A on a XP Home machine via the
> command-prompt switches and parameters. I have two areas of ignorance:
> 1) At first blush, it seems to me that I'll have disparate server names.
> By this I mean that when I install MSDE on my computer to conduct the
> development, it will have the name "Server_Name"\"Instance_Name". My
> server's called "Dell," So I'll have a MSDE instance of,
> DELL\"Instance_Name" On the other hand, the target server, an XP Home
> machine, is called "SherPerf." So this server instance will be named
> SHERPERF\"Instance_Name"
> I plan on using an Access adp front end. I don't know how to code viable
> connection strings around disparate server names. I.E. in development I'm
> connecting to server name #1; but, in production I'm connecting to server
> name #2.
> What am I missing?
> 2) If I want to use Windows Authentication, should I create a new user? If
> so, what groups should this user be part of? Is it standard practice to
> create a user account for MSDE programmatically? If so, how do I do this?
> LDAP?
> I realize this is a lot to ask. Thanks in advance.
> --
> --
> Mark Holahan
>
|||Thanks Jim! Yes...of course. Can you tell I haven't done this before?
Do you have any comment regarding my second question?
Many thanks.
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:%23ioGNN0DFHA.3536@.TK2MSFTNGP15.phx.gbl...
> You application should utilize a configuration file or the registry to
> store the ADO connection string or the parameters for the connection
> string. Then you would simply change the configuration information to
> point to another server. Making a connection string for a different server
> is easy - just replace one server name with another. See the Books Online
> for more information about ADO or ADO.NET connection strings and how to
> construct them.
> Jim
> "Mark Holahan" <mark.holahan@.unifiedllc.com> wrote in message
> news:unoBXFtDFHA.2600@.TK2MSFTNGP09.phx.gbl...
>
|||Regarding question #2 - If your computers are not a member of a domain then
Windows authentication will be of less importance and all user will be local
to the machine they are running on. If you have the chance to use Windows
security then what groups the users are a member of is entirely up to you.
Ideally you would make the groups the logins to the server and the add the
user to the groups. That way you do not have to add each user individually
as a login to the server.
Jim
"Mark Holahan" <mark.holahan@.unifiedllc.com> wrote in message
news:eaXlKZ2DFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Thanks Jim! Yes...of course. Can you tell I haven't done this before?
> Do you have any comment regarding my second question?
> Many thanks.
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:%23ioGNN0DFHA.3536@.TK2MSFTNGP15.phx.gbl...
>
Monday, March 12, 2012
Installation problem - Cannot see home directory
I installed reporting services with SQL server 2005 on Windows Server 2003 R2. After installation which run successful without warning I want to check my installation. I open IE on the server and type:
http://localhost/reportserver$SQLEXPRESS but all I got is:
localhost/ReportServer$SQLExpress - /
2 lines
-----------
-----------
Microsoft SQL Server Reporting Services Version 9.00.2047.00
And that's all. Why I cannot see the home directory displayed ?
Appart selecting Chinese_PRC_90 for the collate I think I have just validated the default option for everything.
When I start the RS Configuration Manager, I see the Initialization button in grey and I cannot access it. Is this normal ?
I have explained why it is not working in the thread below because Express is free Microsoft have it setup you have to choose use either the Algebra end which is the Advanced or Toolkit which is the Calculus end, to use both you need the no deployment developer edition which cost a few dollars. Hope this helps.
http://forums.asp.net/thread/1482957.aspx
|||Thank you for the answer. I tried to read carefully all the links you provided but I still cannot understand. On the server (Windows server 2003) I installed only the SQL Server 2005 Express Edition with Advanced Services SP1 (SQLEXPR_ADV.EXE). I did again the installation installing only SQL server engine with shared tools and reporting services with shared tools. I did not install any client part. But it is still the same.
|||
(SQL Server 2005 Express Edition Toolkit)
And because Express is free you cannot use the Tool Kit and the Advanced together because the Tool Kit is for the Calculus end and the Advanced is for the Algebra end, Microsoft have it setup you cannot have both, to use both you need the developer edition. Hope this helps.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
I hope you understand the above, the developer edition.
http://www.provantage.com/microsoft-e32-00575~7MCSB0EX.htm
|||
Thank you for the help but this is just the information you already provided in the first link you gave.
I partially solved my problem. To access the reporting services I should use the URL:http://localhost/reports$SQLExpress.
This worked on a new installation I have done. And finally after comparing my new installation with old one I fixed my problem.
Also I used the information fromhttp://sqljunkies.com/Article/525B575A-7F61-483A-AC8F-FEC700C34674.scuk explaining how to move reporting service default directories.
Thank you.
|||I am glad you have resolved your problem but that is what I have been trying to explain to you now you are using the Tool Kit you cannot use any part of the Advanced. That is what Microsoft said you have to use both ends separately.Friday, March 9, 2012
Installation on Vista
Hi, I have a serious issue installing sql server express (advanced edition) on Windows Vista Home Premium. I'm doing the install with elevated priviledges but setup of the sql server always fails at the same point with the following error:
{Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'
I've tried many different combinations, including advanced installation options selecting sql server instance to run as local system or local server but nothing came out of that. I always select add current user to the sql server administrators group.
Any help on this issue is appreciated. Below follows the setup summary log:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Mon Feb 26 22:02:41 2007
Machine : JUPITER
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQLSupport_1.log
--
Machine : JUPITER
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQLNCLI_1.log
--
Machine : JUPITER
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SqlWriter_1.log
--
Machine : JUPITER
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
--
Machine : JUPITER
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error Number : 29515
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Feb 26 22:30:02 2007
Also had trouble with installation as well.
It's weird how they don't tell you to setup the app correctly.
There are two ways I believe to set up the app as an administrator.
The easiest for me was to goto "All Programs" in the start bar and right-click on the SQL Management application and they click "Run as Administrator"
Maybe it might launch correctly. It did for me.
Or I remember with Win XP days that you could boot and hit one of the function keys (I think F2) that would normally take you to Safe Mode but gives you the option to log onto as a system administrator as well.
Maybe that may work for Vista as well. Once you log in as system administrator you can open SQL Management and add your user windows account as a sysadmin through the app to give you correct permissions.
Hope any of that was readable and somewhat understandable.
|||
Hi, Amie.
Thank you for the tip, but the trouble is that this error occurs during the installation fase of the sql engine, so installation fails and it rolls back, which essentially means that the sql instance fails to run, so there is no server to manage. :-(
|||Hi Zzermont,
Are you installing a new instance of SQL or upgrading an existing installation? If you are upgrading an existing installation I would guess that you are trying to select SQL Authentication during the upgrade process, which is not supported. If this is a new installation, I'm not sure what's going on. I've installed SQL Express successfully on Vista a number of times.
Either way, I'm pushing this message over to the Setup forum for more directed help.
Mike
|||Hi, Mike.
It is a new installation on vista. The only thing to note is that I have Visual Studio 2005 SP1 installed (with sql server deselected at installation time).
Alek
Installation on Vista
Hi, I have a serious issue installing sql server express (advanced edition) on Windows Vista Home Premium. I'm doing the install with elevated priviledges but setup of the sql server always fails at the same point with the following error:
{Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'
I've tried many different combinations, including advanced installation options selecting sql server instance to run as local system or local server but nothing came out of that. I always select add current user to the sql server administrators group.
Any help on this issue is appreciated. Below follows the setup summary log:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Mon Feb 26 22:02:41 2007
Machine : JUPITER
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQLSupport_1.log
--
Machine : JUPITER
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQLNCLI_1.log
--
Machine : JUPITER
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SqlWriter_1.log
--
Machine : JUPITER
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
--
Machine : JUPITER
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_JUPITER_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error Number : 29515
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Feb 26 22:30:02 2007
Also had trouble with installation as well.
It's weird how they don't tell you to setup the app correctly.
There are two ways I believe to set up the app as an administrator.
The easiest for me was to goto "All Programs" in the start bar and right-click on the SQL Management application and they click "Run as Administrator"
Maybe it might launch correctly. It did for me.
Or I remember with Win XP days that you could boot and hit one of the function keys (I think F2) that would normally take you to Safe Mode but gives you the option to log onto as a system administrator as well.
Maybe that may work for Vista as well. Once you log in as system administrator you can open SQL Management and add your user windows account as a sysadmin through the app to give you correct permissions.
Hope any of that was readable and somewhat understandable.|||
Hi, Amie.
Thank you for the tip, but the trouble is that this error occurs during the installation fase of the sql engine, so installation fails and it rolls back, which essentially means that the sql instance fails to run, so there is no server to manage. :-(
|||Hi Zzermont,
Are you installing a new instance of SQL or upgrading an existing installation? If you are upgrading an existing installation I would guess that you are trying to select SQL Authentication during the upgrade process, which is not supported. If this is a new installation, I'm not sure what's going on. I've installed SQL Express successfully on Vista a number of times.
Either way, I'm pushing this message over to the Setup forum for more directed help.
Mike
|||Hi, Mike.
It is a new installation on vista. The only thing to note is that I have Visual Studio 2005 SP1 installed (with sql server deselected at installation time).
Alek
Wednesday, March 7, 2012
Installation of SQL Server 2000 and SQL Server 2005 Developer Editions on the same PC
Is it safe (or even advisable) to also install SQL Server Developer Edition
2000 on the same PC? I have two clients, one using SQL Server 2000 and
another one on 2005 so I need to do testing on both.
BillPersonally, the way I would do it, just to be safest, is to remove SQL
Server 2005 completely. Install SQL Server 2000 dev edition, 2000 SP4 and
maybe even the 2187 cumulative hotfix, then install an instance of SQL
Server 2005 and then SQL Server 2005 SP2.
To keep things absolutely straight I might install both as named instances,
e.g. yourmachine\SQL2000 and yourmachine\SQL2005.
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunne
r.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||I have both on my laptop, but installed them in the opposite order you are
wanting to do. Don't know if there would be issues doing 2005 first and
then 2000.
TheSQLGuru
President
Indicium Resources, Inc.
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunne
r.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||Thanks for the helpful advice I received from both of you. I'll follow the
steps you recommended.
Bill
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunne
r.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||I have both on my laptop also without any issues. You can always try it
first in a virtual machine program
Sincerely,
John K
Knowledgy Consulting, LLC
www.knowledgy.org
Atlanta's Business Intelligence and Knowledge Management Experts
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunne
r.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
Installation of SQL Server 2000 and SQL Server 2005 Developer Editions on the same PC
Is it safe (or even advisable) to also install SQL Server Developer Edition
2000 on the same PC? I have two clients, one using SQL Server 2000 and
another one on 2005 so I need to do testing on both.
BillPersonally, the way I would do it, just to be safest, is to remove SQL
Server 2005 completely. Install SQL Server 2000 dev edition, 2000 SP4 and
maybe even the 2187 cumulative hotfix, then install an instance of SQL
Server 2005 and then SQL Server 2005 SP2.
To keep things absolutely straight I might install both as named instances,
e.g. yourmachine\SQL2000 and yourmachine\SQL2005.
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||I have both on my laptop, but installed them in the opposite order you are
wanting to do. Don't know if there would be issues doing 2005 first and
then 2000.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||Thanks for the helpful advice I received from both of you. I'll follow the
steps you recommended.
Bill
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>|||I have both on my laptop also without any issues. You can always try it
first in a virtual machine program
--
Sincerely,
John K
Knowledgy Consulting, LLC
www.knowledgy.org
Atlanta's Business Intelligence and Knowledge Management Experts
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
Installation of SQL Server 2000 and SQL Server 2005 Developer Editions on the same PC
Is it safe (or even advisable) to also install SQL Server Developer Edition
2000 on the same PC? I have two clients, one using SQL Server 2000 and
another one on 2005 so I need to do testing on both.
Bill
Personally, the way I would do it, just to be safest, is to remove SQL
Server 2005 completely. Install SQL Server 2000 dev edition, 2000 SP4 and
maybe even the 2187 cumulative hotfix, then install an instance of SQL
Server 2005 and then SQL Server 2005 SP2.
To keep things absolutely straight I might install both as named instances,
e.g. yourmachine\SQL2000 and yourmachine\SQL2005.
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
|||I have both on my laptop, but installed them in the opposite order you are
wanting to do. Don't know if there would be issues doing 2005 first and
then 2000.
TheSQLGuru
President
Indicium Resources, Inc.
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
|||Thanks for the helpful advice I received from both of you. I'll follow the
steps you recommended.
Bill
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
|||I have both on my laptop also without any issues. You can always try it
first in a virtual machine program
Sincerely,
John K
Knowledgy Consulting, LLC
www.knowledgy.org
Atlanta's Business Intelligence and Knowledge Management Experts
"Bill Murphy" <wmdmurphy@.houston.rr.com> wrote in message
news:4651de2d$0$15152$4c368faf@.roadrunner.com...
>I currently have SQL Server 2005 Developer Edition installed on my home PC.
>Is it safe (or even advisable) to also install SQL Server Developer Edition
>2000 on the same PC? I have two clients, one using SQL Server 2000 and
>another one on 2005 so I need to do testing on both.
> Bill
>
Friday, February 24, 2012
installation fails on xp home - failed to configure server
First I attemtped to upgrade MSDE to sp4, and I got the error
"This product is not installed",
So I removed the installation of MSDE and just installed sp4 directly. But
when I do, I get the error
"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop Engine
(VLM) -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information."
The only other line in the log that metions a failure is
Setting SqlEdition property failed
The installer then backs everthing out and removes the service. The service
was already installed and running at that point.
I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
Thanks,
Brian
hi Brian,
msnews.microsoft.com wrote:
> Hi,
> First I attemtped to upgrade MSDE to sp4, and I got the error
> "This product is not installed",
> So I removed the installation of MSDE and just installed sp4
> directly. But when I do, I get the error
> "Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop
> Engine (VLM) -- Setup failed to configure the server. Refer to the
> server error logs and setup error logs for more information."
> The only other line in the log that metions a failure is
> Setting SqlEdition property failed
> The installer then backs everthing out and removes the service. The
> service was already installed and running at that point.
> I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
this usually means you did not comletely uninstall MSDE (not your fault,
just MSDE fault :D)
I succesfully cleared my registry and file system following
http://support.microsoft.com/default...b;en-us;290991 KB article
adiveces but the Windows Installer entries, that can be cleared using the
Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873 (never tried)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Got it fixed.
To get it to work I did the following:
1. Intalled a default instance. I had removed it as well. That worked.
2. re-registering sqldmo.dll. I did this because DbaMgr got an automation
error when connecting to the default instance
3. Installed the named instance I wanted. This time it worked.
Notes:
The error I was getting was
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
Things learned along the way:
1. If the install fails, then enable verbose logging with /L*v
C:\MSDELog.log. Look in the log when its finished for what failed. When you
get the error message box, LEAVE IT THERE, and go look at the log. The last
thing it did is the last line.
2. If you get the error "Unable to configure server", then look in the file
cnfgsvr.out. It will be in C:\Program files\Microsoft SQL
Server\MSSQL$<instancename>\Inatall (assuming drive c)
3. To clean manully to get the installer to resintall completely if a
partial install is left on the system:
- Run Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873
The command is MSIZAP.EXE" T {product code}. The product code can be
found in the install log (C:\MSDELog.log in the example above). The product
code for MDSE service pack 4 was
{E09B48B5-E141-427A-AB0C-D3605127224A} so I ran
MSIZAP.EXE" T {E09B48B5-E141-427A-AB0C-D3605127224A}
- Manually delete the folder C:\Program Files\Microsoft SQL Server\MSSQL
or C:\Program Files\Microsoft SQL Server\MSSQL$<instancename>. Make sure you
look at cnfgsvr.out first if you need too!
Brian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3s9k91Fn804jU1@.individual.net...
> hi Brian,
> msnews.microsoft.com wrote:
> this usually means you did not comletely uninstall MSDE (not your fault,
> just MSDE fault :D)
> I succesfully cleared my registry and file system following
> http://support.microsoft.com/default...b;en-us;290991 KB article
> adiveces but the Windows Installer entries, that can be cleared using the
> Windows Installer SDK tool Msizap.exe as per
> http://support.microsoft.com/default...b;en-us;320873 (never
> tried)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>