Can not install MSDE 2000A
BartC
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...
Jim Young
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" <Ba...@discussions.microsoft.com> wrote in message
news:555AF044-A697-401C...@microsoft.com...
BartC
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
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" <Ba...@discussions.microsoft.com> wrote in message
news:931E2080-068B-4120...@microsoft.com...
BartC
> 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
Jim Young
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.aspx?scid=kb;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" <Ba...@discussions.microsoft.com> wrote in message
news:1D534BF8-4C6F-49D9...@microsoft.com...
BartC
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...
Jim Young
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" <Ba...@discussions.microsoft.com> wrote in message
news:075F0748-C889-4FA2...@microsoft.com...
BartC
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_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:799]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,Source=BinaryData,Target=UnInstSQLAgentSecurity,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,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_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:46:070]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Source=BinaryData,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_ABC9_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,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=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,RollbackDescription=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_ABC9_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,Version=134218489,Assignment=1,ObsoleteArg=0,,,PackageCode={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_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,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_4C0B_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=Installing 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\system32\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)
Jim Young
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" <Ba...@discussions.microsoft.com> wrote in message
news:B7EE12E7-D84E-4D83...@microsoft.com...
BartC
Well I have two answers for you...
1- There is a “Server” service running and set to Automatic. So I suppose
it is running.
2- Lo and Behold there is also MSSQLServerADHelper Service running. Since
the last MSDE 2000A install attempt did a backout, I am surprised to see this
little puppy still up. KB308853 sez that there is a bug in SP1 of SQL Server
2000, in that an uninstall does not remove this guy. I think they are
talking about the real SQL rather than the Desktop Engine. But... hey I
guess I should try yet another manual UNinstall, and be sure to shoot this
ADHelper guy and start all over.
Let me know what you think. Awaiting your reply before doing anything.
Bart
Jim Young
assuming that it is running. The MSSQLServerADHelper service assists in
integrating SQL Server with Active Directory. I kind of doubt that it is
preventing the installation. But, removing it would not hurt, since it has
no relevance to your current installation.
On more thing to look for: After installings, see if you can find a file
named ERRORLOG (no extension) under the directory where SQL Server is
installed. It should be in a directory named Log. This is the log file that
is always created when SQL Server starts. Also look for a file named
SQLAgent.OUT. If you find these files post their contents so I (and others)
can have a look at them. They may reveal more secrets as to why your
installation is failing.
Jim
"BartC" <Ba...@discussions.microsoft.com> wrote in message
news:4EE9E8F4-7027-4873...@microsoft.com...
BartC
Re: Server Service status is running and it is set to automatic
Can not find any file called: SQLAgent.OUT May have been deleted with the
rollback.
Also, any clue from the other log I posted?
And here is the ERRORLOG:
2005-02-19 06:36:47.28 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)
2005-02-19 06:36:47.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2005-02-19 06:36:47.28 server All rights reserved.
2005-02-19 06:36:47.28 server Server Process ID is 3788.
2005-02-19 06:36:47.28 server Logging SQL Server messages in file
'c:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2005-02-19 06:36:47.30 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-02-19 06:36:47.57 server SQL Server configured for thread mode
processing.
2005-02-19 06:36:47.58 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-02-19 06:36:47.67 spid3 Warning ******************
2005-02-19 06:36:47.67 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2005-02-19 06:36:47.68 spid3 Starting up database 'master'.
2005-02-19 06:36:48.29 server Using 'SSNETLIB.DLL' version '8.0.766'.
2005-02-19 06:36:48.29 spid5 Starting up database 'model'.
2005-02-19 06:36:48.40 spid3 Server name is 'BART9550'.
2005-02-19 06:36:48.40 spid3 Skipping startup of clean database id 5
2005-02-19 06:36:48.50 spid3 Skipping startup of clean database id 6
2005-02-19 06:36:48.50 spid3 Starting up database 'msdb'.
2005-02-19 06:36:49.25 server SQL server listening on Shared Memory.
2005-02-19 06:36:49.25 server SQL Server is ready for client connections
2005-02-19 06:36:49.42 spid5 Clearing tempdb database.
2005-02-19 06:36:51.27 spid5 Starting up database 'tempdb'.
2005-02-19 06:36:51.50 spid3 Recovery complete.
2005-02-19 06:36:51.50 spid3 SQL global counter collection task is
created.
2005-02-19 06:36:51.55 spid3 Warning: override, autoexec procedures
skipped.
2005-02-19 06:36:59.07 spid3 SQL Server is terminating due to 'stop'
BartC
Also, I could try to do a manual clean up, then do an install with rollback
turned off. That might give us that SQLAgent.OUT file you wanted. The last
time I did this is seemed that SQL was running. The icon was in the system
tray, and I could bring up the console to start and stop it. But there was
no connecting to it. The driver did not show up in the drivers tab of ODBC.
Bart...
BartC
I did find this file: CNVGSFV.OUT and its contents:
Perhaps the second from last line is our clue. It seems to have tried 3
times to connect and died.
Data source name not found and no default driver specified
If true, how do I declare a data source, and specify a driver
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=BART9550;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=BART9550;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=BART9550;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
SQL Server configuration failed.
###############################################################################
Jim Young
CNVGSFV.OUT is showing that it is trying to use the SQL Server driver to
connect to your instance of SQL Server named BART9550, but is failing.
I believe the problem is that the ODBC and OLEDB drivers for SQL Server are
not installed or not installed correctly on your system. Microsoft has an
MDAC Component Checker that you can download at
http://msdn.microsoft.com/data/mdac/default.aspx
With this tool you can analyze what drivers are installed and detect any
version or file conflicts.
If Component Checker shows that there are problems with your MDAC install or
the SQL Server drivers still don't appear as an installed driver then I
would recommend that you contact MS product support to get MDAC re-installed
properly (since you previously stated that running the MDAC 2.8 install does
nothing). MDAC is so tightly integrated with the OS that I would feel more
comfortable having MS guide you through a reinstall process (if that is the
problem).
Jim
"BartC" <Ba...@discussions.microsoft.com> wrote in message
news:7B844CA4-0526-4C89...@microsoft.com...
BartC
Well, I don't know what to make of all this, except that maybe I don't want
either SQL or the app that needs it. This technology is just to fragile for
real work.
At any rate. The BART9550 is the name of the computer I am trying to
install on. Would this be correct or is it looking at the wrong thing.
re: the componet checker. I run it checking specifically for 2.8 on XP w/
SP2.
It shows all files match but it also shows four registry values missing:
Three in COM:
HKEY_CLASSES_ROOTCLSID
and one in Registry Details
HKEY_LOCAL_MACHINESOFTWARE\Classes\MSDASQL.1
none of these show any value.
Should I add them manually and try again.
Bart
Jim Young
I'm sorry that getting MSDE has been such a hassle for you. I wrote and
support an application that uses MSDE which is installed on hundreds of
workstations and I must admit your situation is one of the more extreme ones
I've seen. In general MSDE has been a very reliable and robust platform to
store our data.
It looks like COM objects for the SQL Server drivers are not registered. Let
try this:
First see if the file C:\Program Files\Common Files\system\ole
db\msdasql.dll is on your system.
If it is then open up a command prompt window and cd to the above directory.
Type this at the command prompt: REGSRV32 MSDASQL.DLL
and hit the Enter key. This will register the COM objects contained in the
DLL and put in the registry entries that are missing.
If regsvr32 reports back that the file sucessfully registered then see if
the SQL Drivers are now installed on your system. If they are then try
re-installing MSDE.
Jim
"BartC" <Ba...@discussions.microsoft.com> wrote in message
news:F21AA74B-13F2-4D63...@microsoft.com...
BartC
OK , maybe one part of this problem is solved.
I have registered MSDASQL.DLL and then, I reran the MDAC install. It ended
with the same error message that it did before. I don't understand the
error message because it sez two different things.
1- MDAC 2.8 RTM is incompatible with this version of Windows.
2- All of its features are currently part of Windows.
However, the good news is that the componet check now shows no missing
registry keys, and all files present.
Howeverr, the bad news is that the MSDE 2000A install still bombs with the
same message that it can not configure the server.
I am going to do a reboot and see if the componet checker still sez that
MDAC is still good. Then I will do yet another manual UNinstall of MSDE,
and another reboot. And then attempt another reinstall of MSDE.
BTW, you said to use REGSRV32 to register that DLL. That is a virus. I'm
sure you meant REGSVR32. This for those who might have that virus on their
system and inadvertently start it up.
Bart...
Jim Young
>sure you meant REGSVR32.
Yes, my mistake. Good luck with your re-install. Let me know how it goes.
Jim
"BartC" <Ba...@discussions.microsoft.com> wrote in message
news:BBFE702B-3B6E-4CC4...@microsoft.com...
HReid
I came across this information from ACT which deals with your issue.
I believe it can help you resolve it.
http://itdomino.act.com/act.nsf/docid/200482410543
Best regards,
Harry Reid III
HReid
closely. If you find a solution, please, post it.
Here are the steps I am having one, very patient, user try; maybe they
will work for you as well:
Prerequisites:
The server service must be started.
File and print sharing must be enabled. This is a must for XP (often
disabled by admins)
The Firewall and Antivirus software must be disabled.
1. Go to the run command and type regedt32.
2. Go to HKEY_LOCAL_MACHINE and do a search for mssql*
3. Delete each entry found with the exceptions of those found in the
following keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Advanced INF
Setup\MDAC_CORE\
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\ LEGACY_MSSQLSERVER
4. Run the installer, "setup /i SqlRun01.msi /l*v c:\sql.log
DISABLEROLLBACK=1"
The disablerollback being set to true will cause the installer to
continue despite failing.
5. Reboot the machine.
6. Once the machine has been rebooted open a command prompt.
7. Browse to and type in the following syntax: C:\Program
Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -dbdebug 1 -M 1
-U sa -Q "SQL_Latin1_General_Cp1_CI_AS"
8. This will force the cnfgsvr executable to report where it is
failing. It will tell you that the SQL service is not started.
9. Right click on the my computer icon, on the desktop
and select manage.
10. Go to the services and applications located on the tree hierarchy
on the right and select services.
11. Start the MSSQLSERVER service and set it to automatic.
12. Go back and execute same syntax as in step 7.
13. It should terminate with a message saying server
successfully configured .
14. Reboot the machine.