MSDE on Windows 2003 R2 box, new DL385G6 - Install Fails during SQL Services
smileyville
XI installation failing when it's dealing with SQL.
So, as a thought and in case there was something wrong with my SQL portion of
the isntall. I thought ok, I'll try installing the actual MSDE application
direct from Microsoft. So, I downloaded the MSDE for SQL 2000 (which is
msde2000a.exe), set my switches and off to the races. It quit when it noted
there was about 4 seconds left to the installation and bombed with the same
errors as the Crystal Reports Server install.
The error is the same whether I try to install MSDE by itself or install
using Crystal Reports XI Server. The error is, "Setup failed to configure
the server. Refer to the server error logs and setup error logs for more
information. I have done so, but still cannot figure out what is getting
hung up, though it seems to be right after it creates the SQL services (from
my untrained eye though).
Is there a known trick to get around this? IS there a potential hardware
conflict? The OS Is Windows 2003 R2, SP2, the hardware is a brand new HP
Proliant DL385 G6. (**With the ERP app, this version of Crystal Reports
server is the only one that is supported and they are not supported via 2008
or 64-bit, so installed at the SmartStart level, 32-bit version of Windows
2003.)
Thoughts???? This is becoming a critical issue. Crystal Reports Server for
Crystal XI, is our means of delivering reports. All other applications are
working correctly on this box and this is my hold up.
Yes, I've cleaned the registry and files before performing each install
according to MS Article on removing MSDE. However; if there is an odd entry
that is causing the problem, please let me know.
Any thoughts are desperately appreciated! Thanks.
Andrea Montanari
the "traditional" problem related to this event is described in
http://support.microsoft.com/kb/816499/en-us
please try having a look at the referenced KB article..
regards
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
http://www.hotelsole.com - http://www.hotelsolericcione.de
--------- remove DMO to reply
smileyville via SQLMonster.com
a couple of different directory locations specified either by command line or
by using the script. Incidentally since the install rolls back, all that
remains for cleanup is the program files directory but it only contains the
logs. The registry only contains the keys for MSSQL under the HKLM\Software\
Microsof key, but there are no setup or data keys there. So, went through
the document and then rebooted and tried again.
Result- Same result. Is there a possibility that the downloaded version is
corrupt? Will there be a conflict with other system components such as .NET
Framework or some other item?
Andrea Montanari wrote:
>hi,
>> I have been finding that I'm having trouble with the Crystal Reports
>> Server XI installation failing when it's dealing with SQL.
>[quoted text clipped - 30 lines]
>>
>> Any thoughts are desperately appreciated! Thanks.
>
>the "traditional" problem related to this event is described in
>http://support.microsoft.com/kb/816499/en-us
>please try having a look at the referenced KB article..
>regards
--
Message posted via http://www.sqlmonster.com
Andrea Montanari
smileyville via SQLMonster.com wrote:
> Hey thanks, I went through these documents step by step again. I
> have tried a couple of different directory locations specified either
> by command line or by using the script. Incidentally since the
> install rolls back, all that remains for cleanup is the program files
> directory but it only contains the logs. The registry only contains
> the keys for MSSQL under the HKLM\Software\ Microsof key, but there
> are no setup or data keys there. So, went through the document and
> then rebooted and tried again.
>
> Result- Same result. Is there a possibility that the downloaded
> version is corrupt? Will there be a conflict with other system
> components such as .NET Framework or some other item?
yes, it "can" be corrupted.. but please try as well to install enabling the
full verbose log indicating the additional
/L*v "c:\MsdeLog.txt"
command line parameter.. a text file of about 2mb (for a succesfull
installation) will be written, and you can inspect that file for
RETURN VALUE 3
entries indicating problems/exceptions at install time..
these are sometime litle cryptic, but those additional info are usually
helpfull troubleshooting the faling installation..
additional manual uninstall/cleanup instructions can be found at
http://support.microsoft.com/kb/320873/EN-US/ and
http://support.microsoft.com/kb/290991/EN-US/
smileyville via SQLMonster.com
to make sure I have no conflicts. So, I went through Smart Start like a
clean system and loaded the OS. I did not join to the domain, apply any
updates, completely bare bone. I downloaded a fresh copy of the MDSE from
Microsoft at
http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en#filelist
I am getting the same flippin message. My setup.ini file is this:
[Options]
DISABLENETWORKPROTOCOLS=0
SAPWD="mypassword"
INSTANCENAME="BOMSDE"
SECURITYMODE=SQL
TARGETDIR="d:\Program Files\Microsoft SQL Server\"
DATADIR="d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Data\"
I got these settings from other documented threads pertaining to setting up
MSDE.
The installation Log file has this around the RETURN VAUE 3, this is a snipet.
InstallSQLAgentSecurity succeeded
MSI (s) (84:88) [09:21:16:031]: Executing op: ActionStart(Name=SkuIt.
2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (84:88) [09:21:16:031]: Executing op: CustomActionSchedule
(Action=SkuIt.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,
Source=BinaryData,Target=SkuIt,)
MSI (s) (84:F4) [09:21:16:046]: Invoking remote custom action. DLL: C:\
WINDOWS\Installer\MSI3F.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-
D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-
D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\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) (84:88) [09:21:16:140]: Executing op: ActionStart(Name=ConfigServer.
2D02443E_7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (84:88) [09:21:16:140]: Executing op: CustomActionSchedule
(Action=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (84:BC) [09:21:16:140]: Invoking remote custom action. DLL: C:\
WINDOWS\Installer\MSI40.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-
D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-
D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\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 "BOMSDE" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (18:E4) [09:23:21:656]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (s) (84!68) [09:33:19:968]: 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 9:33:19: InstallFinalize. Return value 3.
MSI (s) (84:88) [09:33:19:984]: User policy value 'DisableRollback' is 0
Thoughts??? I am completely perplexed! Thanks
Andrea Montanari wrote:
>hi,
>> Hey thanks, I went through these documents step by step again. I
>> have tried a couple of different directory locations specified either
>[quoted text clipped - 8 lines]
>> version is corrupt? Will there be a conflict with other system
>> components such as .NET Framework or some other item?
>
>yes, it "can" be corrupted.. but please try as well to install enabling the
>full verbose log indicating the additional
>/L*v "c:\MsdeLog.txt"
>command line parameter.. a text file of about 2mb (for a succesfull
>installation) will be written, and you can inspect that file for
>RETURN VALUE 3
>entries indicating problems/exceptions at install time..
>these are sometime litle cryptic, but those additional info are usually
>helpfull troubleshooting the faling installation..
>additional manual uninstall/cleanup instructions can be found at
>http://support.microsoft.com/kb/320873/EN-US/ and
>http://support.microsoft.com/kb/290991/EN-US/
>regards
--
Andrea Montanari
smileyville via SQLMonster.com wrote:
> clean again to make sure I have no conflicts. So, I went through
> Smart Start like a clean system and loaded the OS. I did not join to
> the domain, apply any updates, completely bare bone. I downloaded a
> fresh copy of the MDSE from Microsoft at
> http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en#filelist
>
>
> I am getting the same flippin message. My setup.ini file is this:
>
> [Options]
> DISABLENETWORKPROTOCOLS=0
> SAPWD="mypassword"
> INSTANCENAME="BOMSDE"
> SECURITYMODE=SQL
> TARGETDIR="d:\Program Files\Microsoft SQL Server\"
> DATADIR="d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Data\"
>
> I got these settings from other documented threads pertaining to
> setting up MSDE.
hi,
ok, you wiped out the "system disk" (probably c:\), but did you clear the
d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE as well?
Erland Sommarskog
> - Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG? There could
be more information there.
The "standard" meaning of return value 3 is "The system cannot find the
path specified". That is, there is a reference to a non-existent directory.
However, I don't know whether this is such a return code.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
smileyville via SQLMonster.com
disk.
Andrea Montanari wrote:
>hi,
>> Ok, I am totally confused! I decided, ok, let's wipe the system
>> clean again to make sure I have no conflicts. So, I went through
>[quoted text clipped - 15 lines]
>> I got these settings from other documented threads pertaining to
>> setting up MSDE.
>
>hi,
>ok, you wiped out the "system disk" (probably c:\), but did you clear the
>d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE as well?
>regards
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-setup/201008/1
smileyville via SQLMonster.com
Erland Sommarskog wrote:
>> - Setup failed to configure the server. Refer to the server error logs and
>> setup error logs for more information.
>
>Did you look at
>d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG? There could
>be more information there.
>
>The "standard" meaning of return value 3 is "The system cannot find the
>path specified". That is, there is a reference to a non-existent directory.
>However, I don't know whether this is such a return code.
>
--
Erland Sommarskog
At this moment, I think the most interesting is the SQL Server error,
which is located in
>>d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG? There
I you still installed SQL Server on the D disk and with that instance name.
smileyville via SQLMonster.com
I formatted and then deleted the D Partition, there is no other partition on
this machine other than c (for the os).
I started SmartStart, installed the Operating System under the newly
formatted C partition, tried installing a fresh copy of MSDE from Microsoft
(2000 a) and same error. I have since, updated the patches, though the
server is still not joined to the domain or any other applications installed.
I did try the installation initally without even IIS, but added that with the
patches after the install bombed as it's required for Crystal Reports Server.
I am really wondering if I have a hardware conflict or what exactly is
stopping the installation.
What thoughts do you have? I considered copying the production version which
resides on an older server running Windows 2000 to have the directory
structure for Crystal Report Server XI (which is really my goal here) and
then try to install over to see if there is something mssing or what. The
MSDE install was simply to see if there was something wrong with the Crystal
Report Server installation, but since it is the same error, I am thinking I
have a hardware or OS conflict of some sort.
Any other thoughts?
Erland Sommarskog wrote:
>> Would it help if I attached the full log?
>
>At this moment, I think the most interesting is the SQL Server error,
>which is located in
>
>>>d:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG? There
>
>I you still installed SQL Server on the D disk and with that instance name.
>
--
Erland Sommarskog
>
> I formatted and then deleted the D Partition, there is no other
> partition on this machine other than c (for the os).
>
> I started SmartStart, installed the Operating System under the newly
> formatted C partition, tried installing a fresh copy of MSDE from
> Microsoft (2000 a) and same error. I have since, updated the patches,
> though the server is still not joined to the domain or any other
> applications installed. I did try the installation initally without even
> IIS, but added that with the patches after the install bombed as it's
> required for Crystal Reports Server. I am really wondering if I have a
> hardware conflict or what exactly is stopping the installation.
Excuse me for being repetitive, but did you look in the SQL Server
error log? Now when everything is on C, it should be in
C:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG, if
you still use that instance name.
smileyville via SQLMonster.com
I reinstalled to D as that is where this will have to reside anyway. I do
not have an error log because it cleans up the installation when it bombs and
rolls back.
I am running now and will look at the log at the bombing point and then
capture that for you. These are lengthy files, is there a particular portion
you are interested in or shall I send to you? The verbose installation log
that I had the installation create via script is intact, but will not post
here, must be too much info.
Erland Sommarskog wrote:
>> Ok, I am still at square one. To recap,
>>
>[quoted text clipped - 9 lines]
>> required for Crystal Reports Server. I am really wondering if I have a
>> hardware conflict or what exactly is stopping the installation.
>
>Excuse me for being repetitive, but did you look in the SQL Server
>error log? Now when everything is on C, it should be in
>C:\Program Files\Microsoft SQL Server\MSSQL$BOMSDE\Log\ERRORLOG, if
>you still use that instance name.
>
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-setup/201009/1
smileyville via SQLMonster.com
then force the BO install. Well, guess what?? It runs just fine, and then
boom, runs across an error, "THe SQL Server service failed to start. For
more informaiton, se the SQL Server books ONline Topics, "How to: View SQL
Server 2005 Setup Log Files" and "Starting SQL Server Manually".
I hit rety... nothing changes, tried to manually star service, trying local
user administrator, network service and local system. Nothing has worked.
I had completely removed remnants from the file structure and resgistry. So,
now what? There has to be some kind of conflict with the Processor maybe or
some other hardware feature? Thoughts?
Btw - Yes, I installed .NET Framework 2.0 as SQL Server 2005 Expresses
requires it. Thoughts? I have left it as soon as I hit Cancel rolls back.
and takes the logs ;(
smileyville wrote:
>It's ok, I was also recapping for the sake of discussion.
>
>I reinstalled to D as that is where this will have to reside anyway. I do
>not have an error log because it cleans up the installation when it bombs and
>rolls back.
>
>I am running now and will look at the log at the bombing point and then
>capture that for you. These are lengthy files, is there a particular portion
>you are interested in or shall I send to you? The verbose installation log
>that I had the installation create via script is intact, but will not post
>here, must be too much info.
>
>>> Ok, I am still at square one. To recap,
>>>
>[quoted text clipped - 6 lines]
Erland Sommarskog
> could then force the BO install. Well, guess what?? It runs just fine,
> and then boom, runs across an error, "THe SQL Server service failed to
> start. For more informaiton, se the SQL Server books ONline Topics,
> "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server
> Manually".
So now you tried to install SQL 2005 Express instead, and this failed too?
I hope you understand that it is very difficult to assist with a setup
problem on a distance without access to the machine.
For SQL 2005, there are setup logs in
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Logs.
Could you post the contents of Summary.txt for a start?
smileyville via SQLMonster.com
the time to work with me on this.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition
Service Pack 2 (Build 3790)
Time : Thu Sep 02 13:01:24 2010
Machine : DATA
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_SQLSupport_1.log
------------------------------------------------------------------------------
--
Machine : DATA
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_SQLNCLI_1.log
------------------------------------------------------------------------------
--
Machine : DATA
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_SqlWriter_1.log
------------------------------------------------------------------------------
--
Machine : DATA
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_MSXML6_1.log
------------------------------------------------------------------------------
--
Machine : DATA
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually."
------------------------------------------------------------------------------
--
Machine : DATA
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1053) The service did not respond to the start or control
request in a timely fashion.
Error Number : 29503
------------------------------------------------------------------------------
--
SQL Server Setup failed. For more information, review the Setup log file in %
ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Thu Sep 02 16:15:36 2010
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0001_DATA_WI.log
d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
Erland Sommarskog wrote:
>> For Kicks, decided to try SQL Server Express 2005 and then see if I
>> could then force the BO install. Well, guess what?? It runs just fine,
>> and then boom, runs across an error, "THe SQL Server service failed to
>> start. For more informaiton, se the SQL Server books ONline Topics,
>> "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server
>> Manually".
>
>So now you tried to install SQL 2005 Express instead, and this failed too?
>
>I hope you understand that it is very difficult to assist with a setup
>problem on a distance without access to the machine.
>
>For SQL 2005, there are setup logs in
>C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Logs.
>Could you post the contents of Summary.txt for a start?
>
--
smileyville via SQLMonster.com
smileyville wrote:
>Erland I appreciate and understand the distance thing. Thank you for taking
>the time to work with me on this.
>
>Microsoft SQL Server 2005 9.00.1399.06
>==============================
>OS Version : Microsoft Windows Server 2003 family, Standard Edition
>Service Pack 2 (Build 3790)
>Time : Thu Sep 02 13:01:24 2010
>
>Machine : DATA
>Product : Microsoft SQL Server Setup Support Files (English)
>Product Version : 9.00.1399.06
>Install : Successful
>Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
>LOG\Files\SQLSetup0001_DATA_SQLSupport_1.log
>------------------------------------------------------------------------------
>>> For Kicks, decided to try SQL Server Express 2005 and then see if I
>>> could then force the BO install. Well, guess what?? It runs just fine,
>[quoted text clipped - 11 lines]
smileyville via SQLMonster.com
--
smileyville via SQLMonster.com
There is the summary.txt Log.
smileyville via SQLMonster.com
--
smileyville via SQLMonster.com
smileyville via SQLMonster.com
Here is the rest:
Hopefully that stays now so you have the complete summary.txt.
Thanks.
smileyville via SQLMonster.com
Erland Sommarskog
Could you put
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
LOG\Files\SQLSetup0001_DATA_SQL.log
on a web site somewhere, preferrably zipped?
(That file is too big to post here.)
Also, if there is any file named ERRORLOG in
C:\Program Files\Microsoft SQL Server\MSSQL$SQLEXPRESS\MSSQL\LOG
it would be interesting to look at it.
Although given the error message, there may not be one.
smileyville via SQLMonster.com
have a place I can drop it?
Erland Sommarskog wrote:
>Thanks for the Summary.txt.
>
>Could you put
>C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\
>LOG\Files\SQLSetup0001_DATA_SQL.log
>on a web site somewhere, preferrably zipped?
>
>(That file is too big to post here.)
>
>Also, if there is any file named ERRORLOG in
>C:\Program Files\Microsoft SQL Server\MSSQL$SQLEXPRESS\MSSQL\LOG
>it would be interesting to look at it.
>
>Although given the error message, there may not be one.
>
--
Erland Sommarskog
> you have a place I can drop it?
although I don't recall any URL, but I've occasionally seen other
people do this, so I know they exists.
I prefer if to keep the discussion to the newsgroup.
smileyville via SQLMonster.com
Erland Sommarskog wrote:
>> I don't have a website to throw that on. Can I e-mail that to you or do
>> you have a place I can drop it?
>
>There are places on the web where you can upload stuff like this,
>although I don't recall any URL, but I've occasionally seen other
>people do this, so I know they exists.
>
>I prefer if to keep the discussion to the newsgroup.
>
--
Erland Sommarskog
"upload files" free
A quick browse of the hits looked promising.
smileyville via SQLMonster.com
http://www.mediafire.com/?a8b1fgrqikq5r
Thanks.
Erland Sommarskog wrote:
>> That's fine, does anyone have a suggestion where I can upload this log?
>I tried this site: http://www.google.com, and in the search box I entered
>
> "upload files" free
>
>A quick browse of the hits looked promising.
>
--
Erland Sommarskog
>
> http://www.mediafire.com/?a8b1fgrqikq5r
the D: disk, and that it failed when it tried to start SQL Server.
Is there any file
d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
on the machine?
Or is there anything else interesting in this directory like a dump file
of some sort?
Have you checked the Windows event log if there is anything error message
that coincides with this failure and which has some new information?
Do I conclude right when I say that you are running 32-bit Windows?
Which file system do you have? There were some messages that indicated
that you are using FAT rather than NTFS.
smileyville via SQLMonster.com
files/logs are intact, but there is no an error log in that directory.
I confirmed within Device Manager that both partitions (C and D), formatted
with NTFS which is what I selected during setup. And, yes, I ran the 32-bit
installation. I confirmed that as well. Hey... never hurts to check. ;)
I don't see any dump files, or am looking in the wrong place. Simliar errors
in the Event Viewer as I had with 2000 though.
Here they are.
EventID: 10005, Source: MSInstaller
Product: Microsoft SQL Server 2005 Express Edition - Error 29503. The SQL
Server service failed to start. For more ifnormation, see the SQL Server
Books Online topics, "HOw to View SQL Server 2005 Setup Log Files" and
"Starting SQL Server Manually".
The Error is (1053) The service did not respond to the start or control
request in a timley fashion.
EventID: 1000, Source: Application Error
Faulting Application, sqlserver.exe, version 2005.90.1399.0, faulting module
sqlserver.exe, version 2005.90.13999.0, fault address 0x01019027.
The interesting thing here is that the SQL 2005 installation left the SQL
Services in the Services list, but disabled them. The Crystal Report Server
and MSDE 2000 rolled them back when it bombed.
The ultimate goal is Crystal Reports Server, but still believe firmly that
there is some kind of conflict or issue with the SQL part of the install
which is reflective here when even a more current version bombs out. It's
very strange indeed.
I hope to spend some time on this tomorrow and may wipe the box or at least
follow the removal instructions again to see if I am missing something when I
go through that. But, not likely as the problem existed even after a brand
new configuration of the OS on the machine after a reformat.
Thanks again for your help. This is perplexing, but there has to be a
solution!
Erland Sommarskog wrote:
>> Sorry for the delay, I have placed the log file here for your review.
>>
>> http://www.mediafire.com/?a8b1fgrqikq5r
>
>Thanks for the log. It tells me that you tried to install SQL Server on
>the D: disk, and that it failed when it tried to start SQL Server.
>
>Is there any file
>d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
>on the machine?
>
>Or is there anything else interesting in this directory like a dump file
>of some sort?
>
>Have you checked the Windows event log if there is anything error message
>that coincides with this failure and which has some new information?
>
>Do I conclude right when I say that you are running 32-bit Windows?
>Which file system do you have? There were some messages that indicated
>that you are using FAT rather than NTFS.
>
--
Erland Sommarskog
> module sqlserver.exe, version 2005.90.13999.0, fault address
> 0x01019027.
Ah, that seems to be the ticket!
Does that apply to you?
Since you are installing Express, I think you can skip the acrobatics
mentioned in the blog post, and download the streamlined install. Get
it from
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&displaylang=en
smileyville via SQLMonster.com
have to pack it up for the day, but think we are close, it might just be a
combination of these suggestions. I went back to MSDE 2000 as that's what
the Crystal Report server uses. If I can get that to go, Crystal should go.
At least that's my hope.
In this article (I am using the SQL 2000 MSDE installation will fail if you
have number of CPUs on a box which is not in the power of 2), it refers to
running setup in debug mode so some reg entries can be added during the
installation. I am using the syntax as noted the install path, setup.exe
k=dbg. I tried both with and without the modified setup.ini script. It
bombs if I don't due to the SA password.
So, if the sytax is not correct, please let me know what it should be. It
would be another starting point at this point.
If this was your server, what would your next step be?
Erland Sommarskog wrote:
>> Faulting Application, sqlserver.exe, version 2005.90.1399.0, faulting
>> module sqlserver.exe, version 2005.90.13999.0, fault address
>> 0x01019027.
>
>Ah, that seems to be the ticket!
>
>Check out
>http://blogs.msdn.com/b/psssql/archive/2008/07/23/sql-server-2005-encounters-exception-during-install-when-system-has-odd-number-of-processors-or-logical-processors-per-core.aspx
>
>Does that apply to you?
>
>Since you are installing Express, I think you can skip the acrobatics
>mentioned in the blog post, and download the streamlined install. Get
>it from
>http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&displaylang=en
>
--
Erland Sommarskog
> you have number of CPUs on a box which is not in the power of 2), it
> refers to running setup in debug mode so some reg entries can be added
> during the installation. I am using the syntax as noted the install
> path, setup.exe k=dbg. I tried both with and without the modified
> setup.ini script. It bombs if I don't due to the SA password.
Due to the sa password?
> So, if the sytax is not correct, please let me know what it should be. It
> would be another starting point at this point.
I'm afraid that I have no experience of running Setup in debug mode.
> If this was your server, what would your next step be?
Seriously consider installing SQL 2008 Express SP1. Is there any particular
reason that you want to install MSDE 2000?
You could open a case with Microsoft to get help with the issue, but I don't
know how their support offering looks like for this ten year old product.
You could also investigate whether the BIOS permits you turn one of the
cores.