I've been looking into this all day and haven't gotten anywhere. I'm using
InstallShield to install a .Net application, the application uses MSDE as
its database. I've added InstallShield's MSDE object to the install, works
fine sometimes but most of the time I get the following error message when
the MSDE is almost installed.
"Setup failed to configure the server. Refer to the server error logs and
setup errors for more information."
I've scoured the internet looking into this error and nothing seems to
correct this issue. I've remove all files, registry keys and anything
related to MSDE and I still get the same error. I've generated an install
log (attached in an email to follow as "MSDELog.log").
Thanks in advance,
Dave
ERRORLOG
2004-11-16 14:01:09.51 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)
2004-11-16 14:01:09.51 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-11-16 14:01:09.51 server All rights reserved.
2004-11-16 14:01:09.51 server Server Process ID is 4060.
2004-11-16 14:01:09.51 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$INSPPRO\LOG\ERRORLOG'.
2004-11-16 14:01:09.57 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-11-16 14:01:09.62 server SQL Server configured for thread mode
processing.
2004-11-16 14:01:09.62 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-11-16 14:01:09.63 spid3 Warning ******************
2004-11-16 14:01:09.63 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2004-11-16 14:01:09.68 spid3 Starting up database 'master'.
2004-11-16 14:01:10.13 server Using 'SSNETLIB.DLL' version '8.0.760'.
2004-11-16 14:01:10.13 spid5 Starting up database 'model'.
2004-11-16 14:01:10.20 server SQL server listening on 192.168.0.119:
1395.
2004-11-16 14:01:10.20 server SQL server listening on 127.0.0.1: 1395.
2004-11-16 14:01:10.20 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-11-16 14:01:10.20 server SQL Server is ready for client connections
2004-11-16 14:01:10.24 spid3 Server name is 'CHRISTABLET\INSPPRO'.
2004-11-16 14:01:10.24 spid3 Skipping startup of clean database id 5
2004-11-16 14:01:10.24 spid3 Skipping startup of clean database id 6
2004-11-16 14:01:10.24 spid3 Starting up database 'msdb'.
2004-11-16 14:01:10.84 spid5 Clearing tempdb database.
2004-11-16 14:01:11.78 spid5 Starting up database 'tempdb'.
2004-11-16 14:01:12.18 spid3 Recovery complete.
2004-11-16 14:01:12.18 spid3 SQL global counter collection task is
created.
2004-11-16 14:01:12.25 spid3 Warning: override, autoexec procedures
skipped.
2004-11-16 14:03:15.07 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
cnfgsvr.out
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
################################################## #############################
Hi ,
net helpmsg 1460: This operation returned because the timeout period
expired.
This may occur due the following reasons:
1) You are using terminal services /RDP to install msde which opens a
different session and is NOT the same as being on the console.
Try to logon on locally to the machine and then run the installation with
the following command line
setup /L*v c:\msde.log disablerollback=1 disablenetworkprotocols=0
sapwd="some password"
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
|||This is absolutely the solution.
I just solved the SAME problem described in the first message in this
way.
To Microsoft: please WRITE somewhere that you CAN NOT install SQL or
MSDE on Windows XP from Remote Desktop!!
Marco
> 1) You are using terminal services /RDP to install msde which opens a
> different session and is NOT the same as being on the console.
> Try to logon on locally to the machine and then run the installation with
> the following command line
> setup /L*v c:\msde.log disablerollback=1 disablenetworkprotocols=0
> sapwd="some password"
> Girish Sundaram
> This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label configure. Show all posts
Showing posts with label configure. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
failed logins
Does any one here know how configure the server, so it can catch the failed
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
ThanksMatthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Enterprise Manager, right-click your server, properties, security tab.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the faile
d
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>|||I don't think so, EM should have said so if that were the case. just do a te
st and you will se...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...[vbcol=seagreen]
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
>|||I tested and I did not see the change, thought may need restart the server o
r
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a
test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come int
o
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
>
>
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
ThanksMatthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Enterprise Manager, right-click your server, properties, security tab.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the faile
d
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>|||I don't think so, EM should have said so if that were the case. just do a te
st and you will se...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...[vbcol=seagreen]
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
>|||I tested and I did not see the change, thought may need restart the server o
r
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a
test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come int
o
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
>
>
failed logins
Does any one here know how configure the server, so it can catch the failed
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
Thanks
Matthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||Enterprise Manager, right-click your server, properties, security tab.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the failed
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>
|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>
|||I don't think so, EM should have said so if that were the case. just do a test and you will se...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...[vbcol=seagreen]
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
|||I tested and I did not see the change, thought may need restart the server or
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>
|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>
|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come into
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
>
>
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
Thanks
Matthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||Enterprise Manager, right-click your server, properties, security tab.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the failed
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>
|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>
|||I don't think so, EM should have said so if that were the case. just do a test and you will se...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...[vbcol=seagreen]
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
|||I tested and I did not see the change, thought may need restart the server or
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>
|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>
|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come into
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
>
>
failed logins
Does any one here know how configure the server, so it can catch the failed
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
ThanksMatthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> > Does any one here know how configure the server, so it can catch the
> > failed logins? I can see the failed logins from one of the servers,
> > but not all other servers, I want to make SQL server log to catch the
> > failed logins.
> >
> > Thanks
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Enterprise Manager, right-click your server, properties, security tab.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the failed
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> > Does any one here know how configure the server, so it can catch the failed
> > logins? I can see the failed logins from one of the servers, but not all
> > other servers, I want to make SQL server log to catch the failed logins.
> >
> > Thanks
> >
>|||I don't think so, EM should have said so if that were the case. just do a test and you will se...
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
>> Enterprise Manager, right-click your server, properties, security tab.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
>> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>> > Does any one here know how configure the server, so it can catch the failed
>> > logins? I can see the failed logins from one of the servers, but not all
>> > other servers, I want to make SQL server log to catch the failed logins.
>> >
>> > Thanks
>> >
>>|||I tested and I did not see the change, thought may need restart the server or
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> > Thanks, this is what I need, do I have to restart the server?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Enterprise Manager, right-click your server, properties, security tab.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> >> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> >> > Does any one here know how configure the server, so it can catch the failed
> >> > logins? I can see the failed logins from one of the servers, but not all
> >> > other servers, I want to make SQL server log to catch the failed logins.
> >> >
> >> > Thanks
> >> >
> >>
> >>
>|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>> Thanks, this is what I need, do I have to restart the server?
>> "Tibor Karaszi" wrote:
>> Enterprise Manager, right-click your server, properties, security tab.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
>> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>> > Does any one here know how configure the server, so it can catch the
>> > failed
>> > logins? I can see the failed logins from one of the servers, but not
>> > all
>> > other servers, I want to make SQL server log to catch the failed
>> > logins.
>> >
>> > Thanks
>> >
>>
>|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come into
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> > I don't think so, EM should have said so if that were the case. just do a
> > test and you will se... :-)
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > Blog: http://solidqualitylearning.com/blogs/tibor/
> >
> >
> > "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> > news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> >> Thanks, this is what I need, do I have to restart the server?
> >>
> >> "Tibor Karaszi" wrote:
> >>
> >> Enterprise Manager, right-click your server, properties, security tab.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> >> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> >> > Does any one here know how configure the server, so it can catch the
> >> > failed
> >> > logins? I can see the failed logins from one of the servers, but not
> >> > all
> >> > other servers, I want to make SQL server log to catch the failed
> >> > logins.
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >
>
>
logins? I can see the failed logins from one of the servers, but not all
other servers, I want to make SQL server log to catch the failed logins.
ThanksMatthew Z wrote:
> Does any one here know how configure the server, so it can catch the
> failed logins? I can see the failed logins from one of the servers,
> but not all other servers, I want to make SQL server log to catch the
> failed logins.
> Thanks
You can run a server-side trace and capture all Failed Login events. You
can start the server-side trace from a SQL Agent job, by executing a
stored procedure or batch when needed, or by creating a procedure that
auto-starts with SQL Server. You'll need to stop the trace to see the
captured events or write some code to routinely stop the trace and dump
the exising data into a table (or copy the trace file to another name).
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Thnaks .
SQL server should be able to catch these info and displayed in the SQL sever
error log, I just don't know how to do it.
"David Gugick" wrote:
> Matthew Z wrote:
> > Does any one here know how configure the server, so it can catch the
> > failed logins? I can see the failed logins from one of the servers,
> > but not all other servers, I want to make SQL server log to catch the
> > failed logins.
> >
> > Thanks
> You can run a server-side trace and capture all Failed Login events. You
> can start the server-side trace from a SQL Agent job, by executing a
> stored procedure or batch when needed, or by creating a procedure that
> auto-starts with SQL Server. You'll need to stop the trace to see the
> captured events or write some code to routinely stop the trace and dump
> the exising data into a table (or copy the trace file to another name).
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Enterprise Manager, right-click your server, properties, security tab.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> Does any one here know how configure the server, so it can catch the failed
> logins? I can see the failed logins from one of the servers, but not all
> other servers, I want to make SQL server log to catch the failed logins.
> Thanks
>|||Thanks, this is what I need, do I have to restart the server?
"Tibor Karaszi" wrote:
> Enterprise Manager, right-click your server, properties, security tab.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> > Does any one here know how configure the server, so it can catch the failed
> > logins? I can see the failed logins from one of the servers, but not all
> > other servers, I want to make SQL server log to catch the failed logins.
> >
> > Thanks
> >
>|||I don't think so, EM should have said so if that were the case. just do a test and you will se...
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> Thanks, this is what I need, do I have to restart the server?
> "Tibor Karaszi" wrote:
>> Enterprise Manager, right-click your server, properties, security tab.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
>> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>> > Does any one here know how configure the server, so it can catch the failed
>> > logins? I can see the failed logins from one of the servers, but not all
>> > other servers, I want to make SQL server log to catch the failed logins.
>> >
>> > Thanks
>> >
>>|||I tested and I did not see the change, thought may need restart the server or
else..
"Tibor Karaszi" wrote:
> I don't think so, EM should have said so if that were the case. just do a test and you will se...
> :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> > Thanks, this is what I need, do I have to restart the server?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Enterprise Manager, right-click your server, properties, security tab.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> >> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> >> > Does any one here know how configure the server, so it can catch the failed
> >> > logins? I can see the failed logins from one of the servers, but not all
> >> > other servers, I want to make SQL server log to catch the failed logins.
> >> >
> >> > Thanks
> >> >
> >>
> >>
>|||Hi,
We need to restart the MSSQL Servere service to make this setting come into
effect. But on applying Enterprise manager will not
say any message but still we need to restart the service.
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> I don't think so, EM should have said so if that were the case. just do a
> test and you will se... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
>> Thanks, this is what I need, do I have to restart the server?
>> "Tibor Karaszi" wrote:
>> Enterprise Manager, right-click your server, properties, security tab.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
>> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
>> > Does any one here know how configure the server, so it can catch the
>> > failed
>> > logins? I can see the failed logins from one of the servers, but not
>> > all
>> > other servers, I want to make SQL server log to catch the failed
>> > logins.
>> >
>> > Thanks
>> >
>>
>|||Thanks , I will try when people are done using the server.
"Hari Prasad" wrote:
> Hi,
> We need to restart the MSSQL Servere service to make this setting come into
> effect. But on applying Enterprise manager will not
> say any message but still we need to restart the service.
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Og8nF2emFHA.2852@.TK2MSFTNGP15.phx.gbl...
> > I don't think so, EM should have said so if that were the case. just do a
> > test and you will se... :-)
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > Blog: http://solidqualitylearning.com/blogs/tibor/
> >
> >
> > "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> > news:653EB97A-7ED4-478D-A90A-251ACB584F8A@.microsoft.com...
> >> Thanks, this is what I need, do I have to restart the server?
> >>
> >> "Tibor Karaszi" wrote:
> >>
> >> Enterprise Manager, right-click your server, properties, security tab.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Matthew Z" <MatthewZ@.discussions.microsoft.com> wrote in message
> >> news:BCB2DF9B-BB82-430D-83E9-04CF37864440@.microsoft.com...
> >> > Does any one here know how configure the server, so it can catch the
> >> > failed
> >> > logins? I can see the failed logins from one of the servers, but not
> >> > all
> >> > other servers, I want to make SQL server log to catch the failed
> >> > logins.
> >> >
> >> > Thanks
> >> >
> >>
> >>
> >
>
>
Monday, March 12, 2012
Fail to setup sql 2000 on win standard 2003
I can not install SQl 2000 on my new win 2003 server.
It says: setup failed to configure the server.
What should I do?
This is my Sqlstp.log file
01:51:11 Begin Setup
01:51:11 8.00.194
01:51:11 Mode = Normal
01:51:11 ModeType = NORMAL
01:51:11 GetDefinitionEx returned: 0, Extended: 0x0
01:51:11 ValueFTS returned: 1
01:51:11 ValuePID returned: 1
01:51:11 ValueLic returned: 1
01:51:11 System: Windows NT Terminal Server
01:51:11 SQL Server ProductType: Standard Edition [0x2]
01:51:11 Begin Action: SetupInitialize
01:51:11 End Action SetupInitialize
01:51:11 Begin Action: SetupInstall
01:51:11 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi
lesDir ...
01:51:11 CommonFilesDir=C:\Program Files\Common Files
01:51:11 Windows Directory=C:\WINDOWS\
01:51:11 Program Files=C:\Program Files\
01:51:11 TEMPDIR=C:\WINDOWS\TEMP\
01:51:11 Begin Action: SetupInstall
01:51:11 digpid size : 256
01:51:11 digpid size : 164
01:51:11 Begin Action: CheckFixedRequirements
01:51:11 Platform ID: 0xf00
01:51:11 Version: 5.2.3790
01:51:11 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
01:51:11 End Action: CheckFixedRequirements
01:51:11 Begin Action: ShowDialogs
01:51:11 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
01:51:11 Begin Action ShowDialogsHlpr: 0x1
01:51:11 Begin Action: DialogShowSdWelcome
01:51:12 End Action DialogShowSdWelcome
01:51:12 Dialog 0x1 returned: 1
01:51:12 End Action ShowDialogsHlpr
01:51:12 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
01:51:12 Begin Action ShowDialogsHlpr: 0x2
01:51:12 Begin Action: DialogShowSdMachineName
01:51:14 ShowDlgMachine returned: 1
01:51:14 Name = ETOUCHHOST, Type = 0x1
01:51:14 Begin Action: CheckRequirements
01:51:14 Processor Architecture: x86 (Pentium)
01:51:14 ComputerName: ETOUCHHOST
01:51:14 User Name: Administrator
01:51:14 IsAllAccessAllowed returned: 1
01:51:14 OS Language: 0xc09
01:51:14 End Action CheckRequirements
01:51:14 This combination of Package and Operating System allows a full product install.
01:51:14 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134168, returned : 0
01:51:14 CreateSetupTopology returned : 0, Handle : 0x1134168
01:51:14 Topology Type : 1, Return Value : 0
01:51:14 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:14 PN_EnumerateEx returned : 0
01:51:14 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:14 PN_StartScan [0x11341b8] returned : 0
01:51:14 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:14 No more items in enumeration.
01:51:14 ReleaseSetupTopology
01:51:14 Named instance limit: 100, quota: 0
01:51:14 End Action DialogShowSdMachineName
01:51:14 begin ShowDialogsUpdateMask
01:51:14 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
01:51:14 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
01:51:14 Dialog 0x2 returned: 0
01:51:14 End Action ShowDialogsHlpr
01:51:14 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
01:51:14 Begin Action ShowDialogsHlpr: 0x4
01:51:14 Begin Action: DialogShowSdInstallMode
01:51:15 ShowDlgInstallMode returned: 1
01:51:15 InstallMode : 0x1
01:51:15 End Action DialogShowSdInstallMode
01:51:15 begin ShowDialogsUpdateMask
01:51:15 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
01:51:15 Updated Dialog Mask: 0x1bf40037, Disable Back = 0x1
01:51:15 Dialog 0x4 returned: 1
01:51:15 End Action ShowDialogsHlpr
01:51:15 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
01:51:15 Begin Action ShowDialogsHlpr: 0x10
01:51:15 Begin Action: DialogShowSdRegisterUserEx
01:51:24 End Action DialogShowSdRegisterUserEx
01:51:24 Dialog 0x10 returned: 1
01:51:24 End Action ShowDialogsHlpr
01:51:24 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
01:51:24 Begin Action ShowDialogsHlpr: 0x20
01:51:24 Begin Action: DialogShowSdLicense
01:51:27 End Action DialogShowSdLicense
01:51:27 Dialog 0x20 returned: 1
01:51:27 End Action ShowDialogsHlpr
01:51:27 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
01:51:27 Begin Action ShowDialogsHlpr: 0x40000
01:51:27 Begin Action: DialogShowSdCliSvr
01:51:27 DisplaySystemPreReq
01:51:28 ShowDlgClientServerSelect returned: 1
01:51:28 Type : 0x2
01:51:28 End Action DialogShowSdCliSvr
01:51:28 begin ShowDialogsUpdateMask
01:51:28 nFullMask = 0x1bf40037, nCurrent = 0x40000, nDirection = 1
01:51:28 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:28 Dialog 0x40000 returned: 1
01:51:28 End Action ShowDialogsHlpr
01:51:28 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
01:51:28 Begin Action ShowDialogsHlpr: 0x80000
01:51:28 Begin Action: DialogShowSdInstanceName
01:51:28 Begin Action: ShowDlgInstanceName
01:51:29 End Action: ShowDlgInstanceName
01:51:29 ShowDlgInstanceName returned : 1
01:51:29 InstanceName : MSSQLSERVER
01:51:29 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134730, returned : 0
01:51:29 CreateSetupTopology returned : 0, Handle : 0x1134730
01:51:29 Topology Type : 1, Return Value : 0
01:51:29 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:29 PN_EnumerateEx returned : 0
01:51:29 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:29 PN_StartScan [0x11341b8] returned : 0
01:51:29 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:29 No more items in enumeration.
01:51:29 ReleaseSetupTopology
01:51:29 End Action DialogShowSdInstanceName
01:51:29 begin ShowDialogsUpdateMask
01:51:29 nFullMask = 0x1bfc0037, nCurrent = 0x80000, nDirection = 1
01:51:29 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:29 Dialog 0x80000 returned: 1
01:51:29 End Action ShowDialogsHlpr
01:51:29 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
01:51:29 Begin Action ShowDialogsHlpr: 0x100000
01:51:29 Begin Action: DialogShowSdSetupType
01:51:29 Begin Action: Setup Type
01:51:31 SQL program folder: C:\Program Files\Microsoft SQL Server
01:51:31 SQL data folder: C:\Program Files\Microsoft SQL Server
01:51:31 Windows system folder: C:\WINDOWS\system32\
01:51:31 Prog req: 38205, Data req: 34432, Sys req: 182917
01:51:31 Prog avail: 73899760, Data avail: 73899760, Sys avail: 73899760
01:51:31 Prog req vs. avail, 255554, 73899760
01:51:31 Data req vs. avail, 34432, 73899760
01:51:31 Sys req vs. avail, 217349, 73899760
01:51:31 DisplaySystemPreReq
01:51:31 [SetupTypeSQL]
01:51:31 szDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 Result = 301
01:51:31 szDataDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 End Action: Setup Type
01:51:31 Setup Type: Typical (301)
01:51:31 End Action DialogShowSdSetupType
01:51:31 begin ShowDialogsUpdateMask
01:51:31 nFullMask = 0x1bfc0037, nCurrent = 0x100000, nDirection = 301
01:51:31 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:31 Dialog 0x100000 returned: 301
01:51:31 End Action ShowDialogsHlpr
01:51:31 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
01:51:31 Begin Action ShowDialogsHlpr: 0x400000
01:51:31 Begin Action: DlgServices
01:51:36 ShowDlgServices returned: 1
01:51:36 [DlgServices]
01:51:36 Local-Domain = 3855
01:51:36 AutoStart = 15
01:51:36 Result = 1
01:51:36 End Action DlgServices
01:51:36 begin ShowDialogsUpdateMask
01:51:36 nFullMask = 0x1bdc0037, nCurrent = 0x400000, nDirection = 1
01:51:36 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:36 Dialog 0x400000 returned: 1
01:51:36 End Action ShowDialogsHlpr
01:51:36 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
01:51:36 Begin Action ShowDialogsHlpr: 0x800000
01:51:36 Begin Action: DlgSQLSecurity
01:51:38 ShowDlgSQLSecurity returned: 1
01:51:38 LoginMode = 1,szPwd
01:51:38 End Action DlgSQLSecurity
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x800000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x800000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned:nCurrent=0x1000000,index=24
01:51:38 Begin Action ShowDialogsHlpr: 0x1000000
01:51:38 Begin Action: DlgCollation
01:51:38 ShowDlgCollation returned: 1
01:51:38 collation_name = Latin1_General_CI_AS,locale_name = Latin1_General,lcid = 0xc09,SortId = 0,dwCompFlags = 0x30001
01:51:38 End Action DlgCollation
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x1000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x1000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
01:51:38 Begin Action ShowDialogsHlpr: 0x2000000
01:51:38 Begin Action: DlgNetwork
01:51:38 ShowDlgNetwork returned: 1
01:51:38 [DlgServerNetwork]
01:51:38 NetworkLibs = 255
01:51:38 TCPPort = 1433
01:51:38 TCPPrxy = Default
01:51:38 NMPPipeName = \\.\pipe\sql\query
01:51:38 Result = 1
01:51:38 End Action DlgNetwork
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x2000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x2000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
01:51:38 Begin Action ShowDialogsHlpr: 0x8000000
01:51:38 Begin Action: DialogShowSdStartCopy
01:51:38 End Action DialogShowSdStartCopy
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x8000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x8000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
01:51:38 Begin Action ShowDialogsHlpr: 0x10000000
01:51:38 Begin Action: DialogShowSdLicenseMode
01:51:40 ShowDlgLicense returned: 1
01:51:40 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 5
01:51:40 End Action DialogShowSdLicenseMode
01:51:40 Dialog 0x10000000 returned: 1
01:51:40 End Action ShowDialogsHlpr
01:51:40 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
01:51:40 End Action ShowDialogs
01:51:40 Begin Action ProcessBeforeDataMove:
01:51:40 DeinstallStart returned (C:\Program Files\Microsoft SQL Server\MSSQL): 0
01:51:40 End Action ProcessBeforeDataMove:
01:51:40 Begin Action SetToolsComponentSelection:
01:51:40 End Action SetToolsComponentSelection:
01:51:40 Begin Action ProcessComponentSelection:
01:51:40 End Action ProcessComponentSelection
01:51:40 Begin Action LogSelectedComponents:
01:51:40 SQLProg
01:51:40 SQLProg\SQLServr
01:51:40 SQLProg\SQLServr\Help
01:51:40 SQLProg\SQLServr\SCMDev
01:51:40 SQLProg\SQLServr\SCMDev\SCMh
01:51:40 SQLProg\SQLServr\SCMDev\SCMX86Lb
01:51:40 SQLProg\SQLServr\SCMDev\SCMALb
01:51:40 SQLProg\SQLServr\Rs1033
01:51:40 SQLProg\SQLServr\RsIntl
01:51:40 SQLProg\SQLServr\ActiveX
01:51:40 SQLProg\SQLServr\System
01:51:40 SQLProg\UpgTools
01:51:40 SQLProg\UpgTools\UpgSys
01:51:40 SQLProg\UpgTools\ActiveX
01:51:40 SQLProg\UpgTools\Res1033
01:51:40 SQLProg\UpgTools\ResOther
01:51:40 SQLProg\UpgTools\Resld
01:51:40 SQLProg\ReplSupp
01:51:40 SQLProg\ReplSupp\ReplDat
01:51:40 SQLProg\ReplSupp\RepComm
01:51:40 SQLProg\ReplSupp\RepNoDk
01:51:40 SQLProg\ReplSupp\ActiveX
01:51:40 SQLProg\Install
01:51:40 SQLProg\System
01:51:40 SQLProg\SvrExt
01:51:40 SQLProg\SvrExt\Help
01:51:40 SQLProg\SvrExt\SvrExtRs
01:51:40 SQLProg\SvrExt\ResIntl
01:51:40 SQLProg\Dat
01:51:40 SQLProg\DatSmpl
01:51:40 SQLProg\BaseSys
01:51:40 SQLProg\BaseBinn
01:51:40 SQLProg\MSSearch
01:51:40 SQLProg\MSSearch\Help
01:51:40 SQLProg\MSSearch\ActiveX
01:51:40 SQLProg\BaseInst
01:51:40 SQLProg\Symbols
01:51:40 SQLProg\Symbols\EXE
01:51:40 SQLProg\Symbols\DLL
01:51:40 SQLProg\Perfmon
01:51:40 SQLProg\Perfmon\System
01:51:40 SQLProg\Root
01:51:40 MgtTool
01:51:40 MgtTool\SEM
01:51:40 MgtTool\SEM\HTML
01:51:40 MgtTool\SEM\MSD98
01:51:40 MgtTool\SEM\MSD98SYS
01:51:40 MgtTool\SEM\MSD98Res
01:51:40 MgtTool\SEM\MSD98Hlp
01:51:40 MgtTool\SEM\Help
01:51:40 MgtTool\SEM\Res1033
01:51:40 MgtTool\SEM\ResIntl
01:51:40 MgtTool\SEM\MSD98RsI
01:51:40 MgtTool\SEM\ActiveX
01:51:40 MgtTool\SEM\ActiveX\Res1033
01:51:40 MgtTool\SEM\ActiveX\ResIntl
01:51:40 MgtTool\SEM\Scripts
01:51:40 MgtTool\SEM\OLEDB
01:51:40 MgtTool\SEM\OLEDB\Res1033
01:51:40 MgtTool\SEM\OLEDB\ResIntl
01:51:40 MgtTool\Profiler
01:51:40 MgtTool\Profiler\Help
01:51:40 MgtTool\Profiler\Res1033
01:51:40 MgtTool\Profiler\ResIntl
01:51:40 MgtTool\Qryanlz
01:51:40 MgtTool\Qryanlz\Help
01:51:40 MgtTool\Qryanlz\Res1033
01:51:40 MgtTool\Qryanlz\ResIntl
01:51:40 MgtTool\DTCCLi
01:51:40 MgtTool\Wzcnflct
01:51:40 MgtTool\Wzcnflct\WzcnHlp
01:51:40 MgtTool\Wzcnflct\Wzcn1033
01:51:40 MgtTool\Wzcnflct\WzcnOthr
01:51:40 MgtTool\Wzcnflct\WzcnCmn
01:51:40 MgtTool\UtilSys
01:51:40 MgtTool\UtilBinn
01:51:40 Connect
01:51:40 Connect\ConnSys
01:51:40 Books
01:51:40 Books\Bookso
01:51:40 Books\Bookso\Utils
01:51:40 DevTools
01:51:40 DevTools\Dbg Int
01:51:40 DevTools\Dbg Int\Dbg Int Common
01:51:40 DevTools\Dbg Int\EXE
01:51:40 CoreRepl
01:51:40 CoreRepl\Res1033
01:51:40 CoreRepl\ResIntl
01:51:40 Core
01:51:40 Core\Res1033
01:51:40 Core\ResOther
01:51:40 Repostry
01:51:40 Repostry\RepstSys
01:51:40 Repostry\Res1033
01:51:40 Repostry\ResIntl
01:51:40 CoreMisc
01:51:40 CoreMisc\ActiveX
01:51:40 CoreMisc\ActiveX\Res1033
01:51:40 CoreMisc\ActiveX\ResIntl
01:51:40 CoreMisc\Res1033
01:51:40 Monarch
01:51:40 Monarch\Monr1033
01:51:40 Monarch\MonrIntl
01:51:40 Jet
01:51:40 CoreInst
01:51:40 CoreCOM
01:51:40 CoreCOM\Res1033
01:51:40 CoreCOM\ResIntl
01:51:40 CoreTool
01:51:40 CoreTool\Res1033
01:51:40 CoreTool\ResOther
01:51:40 DBLibCli
01:51:40 SFExt
01:51:40 SFExt\ActiveX
01:51:40 SFExt\ActiveX\Res1033
01:51:40 SFExt\ActiveX\ResIntl
01:51:40 SFExt\Res1033
01:51:40 SFExt\ResIntl
01:51:40 Trace
01:51:40 Trace\Res1033
01:51:40 Trace\ResOther
01:51:40 MiscCore
01:51:40 MC
01:51:40 MC\MC1033
01:51:40 MC\MCIntl
01:51:40 MC\Help
01:51:40 SQLMgr
01:51:40 SQLMgr\Res1033
01:51:40 SQLMgr\ResIntl
01:51:40 SvrTool
01:51:40 SvrTool\Res1033
01:51:40 SvrTool\ResIntl
01:51:40 DTSUI
01:51:40 DTSUI\Res1033
01:51:40 DTSUI\ResIntl
01:51:40 MSOlap
01:51:40 MSOlap\Res1033
01:51:40 MSOlap\ResIntl
01:51:40 ATL
01:51:40 ATL\winnt
01:51:40 ATL\win9x
01:51:40 MFC42U
01:51:40 VC
01:51:40 VB
01:51:40 OCX1
01:51:40 SQLAdHlp
01:51:40 SQLAdHlp\Res1033
01:51:40 SQLAdHlp\ResOther
01:51:40 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
01:51:40 End Action LogSelectedComponents
01:51:40 Begin Action InstallPkgs:
01:51:40 Begin Action: Locked Connectivity Files Check
01:51:40 ConnectivityLocked returned: 0
01:51:40 The operation completed successfully.
01:51:40 End Action: Locked Connectivity Files Check
01:51:41 Setup is installing Microsoft Data Access Components (MDAC) ...
01:51:41 C:\INETPUB\FTPROOT\x86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
01:51:58 ExitCode: 0
01:51:58 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
01:51:58 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir "C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg "C:\INETPUB\FTPROOT\x86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
01:51:58 Process Exit Code: (0)
01:51:58 InstallMSSearch instance: MSSQLSERVER
01:51:58 Software\Microsoft\Search\Install:Version not present
01:51:58 MSSearch 2.0 or greater version check returned -1
01:51:58 Setup is installing the Microsoft Full-Text Search Engine ...
01:51:58 " C:\INETPUB\FTPROOT\x86\FullText\MSSearch\Search\Se
archStp.exe" /s /a:SQLServer
01:52:11 Process Exit Code: (0)
01:52:11 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
01:52:11 Setup is installing HTML Help ...
01:52:11 HTML Help installer exit code: 0
01:52:32 End Action InstallPkgs
01:52:32 Begin Action MoveFileData:
01:52:32 Enabled SELFREGISTERBATCH
01:52:32 Enabled CORECOMPONENTHANDLING
01:52:54 Begin Action: MoveFileDataSpecial|||01:52:55 End Action: MoveFileDataSpecial
01:52:55 End Action MoveFileData
01:52:55 Begin Action ProcessAfterDataMove:
01:52:55 C:\INETPUB\FTPROOT\x86\Binn\hhcol.exe C:\Program Files\Microsoft SQL Server\80\Tools\Books
01:52:55 End Action ProcessAfterDataMove
01:52:55 Begin Action BuildServer:
01:52:55 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5 -ExePath "C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
01:52:55 Process Exit Code: (0)
01:52:55 Begin Action: CreateRegistrySetSQL
01:52:55 End Action: CreateRegistrySetSQL
01:52:55 Begin Action: RegWriteSetupEntry
01:52:55 End Action: RegWriteSetupEntry
01:52:55 Begin Action: CreateSer
01:52:55 End Action: CreateSer
01:52:55 Begin Action: SkuIt
01:52:55 End Action: SkuIt
01:52:56 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL Server\MSSQL returned: 0, 0
01:52:56 SetRegSecuritySQLAndAdmin for Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
01:52:56 Begin Action: UpdateSystemPath
01:52:56 Path successfully updated.
01:52:56 %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy
stem32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
01:52:56 End Action: UpdateSystemPath
01:52:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Latin1_General_CI_AS" -H 131390 -U sa -P
01:52:57 Process Exit Code: (193)
01:54:06 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
01:54:06 Action CleanUpInstall:
01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
01:54:06 Process Exit Code: (1060) The specified service does not exist as an installed service.
01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
01:54:07 Process Exit Code: (0)
01:54:07 StatsGenerate returned: 2
01:54:07 StatsGenerate (0x0,0x1,0xf00,0x0,1033,303,0x0,0x1,0,0,0
01:54:07 StatsGenerate -1,Administrator)
01:54:07 Installation Failed.|||Check the sqlstp.log under c:\winnt. Also look for information in the event logs. I am not sure if these will exist yet, but check for errorlog files under the sql server directory.|||there is no errorlog files under the sql server directory. I already check it. Also the above is my Sqlstp.log file.
I have try so many way to solve the problem, however I can't ...pls help|||How about sqlsp.log and event logs ? Did the log end on "01:52:54 Begin Action: MoveFileDataSpecial" ?|||Its end with 01:54:07 Installation Failed.|||This is another one
06:20:21 Begin Setup
06:20:21 8.00.194
06:20:21 Mode = Normal
06:20:21 ModeType = NORMAL
06:20:21 GetDefinitionEx returned: 0, Extended: 0x0
06:20:21 ValueFTS returned: 1
06:20:21 ValuePID returned: 1
06:20:21 ValueLic returned: 1
06:20:21 System: Windows NT Terminal Server
06:20:21 SQL Server ProductType: Standard Edition [0x2]
06:20:21 Begin Action: SetupInitialize
06:20:21 End Action SetupInitialize
06:20:21 Begin Action: SetupInstall
06:20:21 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
06:20:21 CommonFilesDir=C:\Program Files\Common Files
06:20:21 Windows Directory=C:\WINDOWS\
06:20:21 Program Files=C:\Program Files\
06:20:21 TEMPDIR=C:\WINDOWS\TEMP\
06:20:21 Begin Action: SetupInstall
06:20:21 digpid size : 256
06:20:21 digpid size : 164
06:20:21 Begin Action: CheckFixedRequirements
06:20:21 Platform ID: 0xf00
06:20:21 Version: 5.2.3790
06:20:21 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
06:20:21 End Action: CheckFixedRequirements
06:20:21 Begin Action: ShowDialogs
06:20:21 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
06:20:21 Begin Action ShowDialogsHlpr: 0x1
06:20:21 Begin Action: DialogShowSdWelcome
06:20:23 End Action DialogShowSdWelcome
06:20:23 Dialog 0x1 returned: 1
06:20:23 End Action ShowDialogsHlpr
06:20:23 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
06:20:23 Begin Action ShowDialogsHlpr: 0x2
06:20:23 Begin Action: DialogShowSdMachineName
06:20:29 ShowDlgMachine returned: -1
06:20:29 ShowDlgMachine: GetLastError returned: 0
06:20:29 The operation completed successfully.
06:20:29 End Action DialogShowSdMachineName
06:20:29 End Action ShowDialogs
06:20:29 Action CleanUpInstall:
06:20:29 StatsGenerate returned: 2
06:20:29 StatsGenerate (0x0,0x0,0xf00,0x0,1033,0,0x0,0x0,0,0,0
06:20:29 StatsGenerate -1,)
06:20:29 Installation Failed.|||I missed the 3rd post with the log dump. Anyway, try running the sql setup in debug mode - using \x86\setup\setupsql.exe k=Dbq. When you get to the server configuration portion - see if you can start the sql server service.|||hi,
It doesn't work. samw problem. any more suggestion?|||What happens when you are in debug and the configure server prompts and you attempt to start the sql server service - without proceeding with the configure server (just leave it at the prompt) ?|||it quit automatically after it says setup failed to configure the server
It says: setup failed to configure the server.
What should I do?
This is my Sqlstp.log file
01:51:11 Begin Setup
01:51:11 8.00.194
01:51:11 Mode = Normal
01:51:11 ModeType = NORMAL
01:51:11 GetDefinitionEx returned: 0, Extended: 0x0
01:51:11 ValueFTS returned: 1
01:51:11 ValuePID returned: 1
01:51:11 ValueLic returned: 1
01:51:11 System: Windows NT Terminal Server
01:51:11 SQL Server ProductType: Standard Edition [0x2]
01:51:11 Begin Action: SetupInitialize
01:51:11 End Action SetupInitialize
01:51:11 Begin Action: SetupInstall
01:51:11 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi
lesDir ...
01:51:11 CommonFilesDir=C:\Program Files\Common Files
01:51:11 Windows Directory=C:\WINDOWS\
01:51:11 Program Files=C:\Program Files\
01:51:11 TEMPDIR=C:\WINDOWS\TEMP\
01:51:11 Begin Action: SetupInstall
01:51:11 digpid size : 256
01:51:11 digpid size : 164
01:51:11 Begin Action: CheckFixedRequirements
01:51:11 Platform ID: 0xf00
01:51:11 Version: 5.2.3790
01:51:11 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
01:51:11 End Action: CheckFixedRequirements
01:51:11 Begin Action: ShowDialogs
01:51:11 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
01:51:11 Begin Action ShowDialogsHlpr: 0x1
01:51:11 Begin Action: DialogShowSdWelcome
01:51:12 End Action DialogShowSdWelcome
01:51:12 Dialog 0x1 returned: 1
01:51:12 End Action ShowDialogsHlpr
01:51:12 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
01:51:12 Begin Action ShowDialogsHlpr: 0x2
01:51:12 Begin Action: DialogShowSdMachineName
01:51:14 ShowDlgMachine returned: 1
01:51:14 Name = ETOUCHHOST, Type = 0x1
01:51:14 Begin Action: CheckRequirements
01:51:14 Processor Architecture: x86 (Pentium)
01:51:14 ComputerName: ETOUCHHOST
01:51:14 User Name: Administrator
01:51:14 IsAllAccessAllowed returned: 1
01:51:14 OS Language: 0xc09
01:51:14 End Action CheckRequirements
01:51:14 This combination of Package and Operating System allows a full product install.
01:51:14 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134168, returned : 0
01:51:14 CreateSetupTopology returned : 0, Handle : 0x1134168
01:51:14 Topology Type : 1, Return Value : 0
01:51:14 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:14 PN_EnumerateEx returned : 0
01:51:14 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:14 PN_StartScan [0x11341b8] returned : 0
01:51:14 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:14 No more items in enumeration.
01:51:14 ReleaseSetupTopology
01:51:14 Named instance limit: 100, quota: 0
01:51:14 End Action DialogShowSdMachineName
01:51:14 begin ShowDialogsUpdateMask
01:51:14 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
01:51:14 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
01:51:14 Dialog 0x2 returned: 0
01:51:14 End Action ShowDialogsHlpr
01:51:14 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
01:51:14 Begin Action ShowDialogsHlpr: 0x4
01:51:14 Begin Action: DialogShowSdInstallMode
01:51:15 ShowDlgInstallMode returned: 1
01:51:15 InstallMode : 0x1
01:51:15 End Action DialogShowSdInstallMode
01:51:15 begin ShowDialogsUpdateMask
01:51:15 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
01:51:15 Updated Dialog Mask: 0x1bf40037, Disable Back = 0x1
01:51:15 Dialog 0x4 returned: 1
01:51:15 End Action ShowDialogsHlpr
01:51:15 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
01:51:15 Begin Action ShowDialogsHlpr: 0x10
01:51:15 Begin Action: DialogShowSdRegisterUserEx
01:51:24 End Action DialogShowSdRegisterUserEx
01:51:24 Dialog 0x10 returned: 1
01:51:24 End Action ShowDialogsHlpr
01:51:24 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
01:51:24 Begin Action ShowDialogsHlpr: 0x20
01:51:24 Begin Action: DialogShowSdLicense
01:51:27 End Action DialogShowSdLicense
01:51:27 Dialog 0x20 returned: 1
01:51:27 End Action ShowDialogsHlpr
01:51:27 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
01:51:27 Begin Action ShowDialogsHlpr: 0x40000
01:51:27 Begin Action: DialogShowSdCliSvr
01:51:27 DisplaySystemPreReq
01:51:28 ShowDlgClientServerSelect returned: 1
01:51:28 Type : 0x2
01:51:28 End Action DialogShowSdCliSvr
01:51:28 begin ShowDialogsUpdateMask
01:51:28 nFullMask = 0x1bf40037, nCurrent = 0x40000, nDirection = 1
01:51:28 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:28 Dialog 0x40000 returned: 1
01:51:28 End Action ShowDialogsHlpr
01:51:28 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
01:51:28 Begin Action ShowDialogsHlpr: 0x80000
01:51:28 Begin Action: DialogShowSdInstanceName
01:51:28 Begin Action: ShowDlgInstanceName
01:51:29 End Action: ShowDlgInstanceName
01:51:29 ShowDlgInstanceName returned : 1
01:51:29 InstanceName : MSSQLSERVER
01:51:29 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134730, returned : 0
01:51:29 CreateSetupTopology returned : 0, Handle : 0x1134730
01:51:29 Topology Type : 1, Return Value : 0
01:51:29 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:29 PN_EnumerateEx returned : 0
01:51:29 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:29 PN_StartScan [0x11341b8] returned : 0
01:51:29 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:29 No more items in enumeration.
01:51:29 ReleaseSetupTopology
01:51:29 End Action DialogShowSdInstanceName
01:51:29 begin ShowDialogsUpdateMask
01:51:29 nFullMask = 0x1bfc0037, nCurrent = 0x80000, nDirection = 1
01:51:29 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:29 Dialog 0x80000 returned: 1
01:51:29 End Action ShowDialogsHlpr
01:51:29 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
01:51:29 Begin Action ShowDialogsHlpr: 0x100000
01:51:29 Begin Action: DialogShowSdSetupType
01:51:29 Begin Action: Setup Type
01:51:31 SQL program folder: C:\Program Files\Microsoft SQL Server
01:51:31 SQL data folder: C:\Program Files\Microsoft SQL Server
01:51:31 Windows system folder: C:\WINDOWS\system32\
01:51:31 Prog req: 38205, Data req: 34432, Sys req: 182917
01:51:31 Prog avail: 73899760, Data avail: 73899760, Sys avail: 73899760
01:51:31 Prog req vs. avail, 255554, 73899760
01:51:31 Data req vs. avail, 34432, 73899760
01:51:31 Sys req vs. avail, 217349, 73899760
01:51:31 DisplaySystemPreReq
01:51:31 [SetupTypeSQL]
01:51:31 szDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 Result = 301
01:51:31 szDataDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 End Action: Setup Type
01:51:31 Setup Type: Typical (301)
01:51:31 End Action DialogShowSdSetupType
01:51:31 begin ShowDialogsUpdateMask
01:51:31 nFullMask = 0x1bfc0037, nCurrent = 0x100000, nDirection = 301
01:51:31 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:31 Dialog 0x100000 returned: 301
01:51:31 End Action ShowDialogsHlpr
01:51:31 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
01:51:31 Begin Action ShowDialogsHlpr: 0x400000
01:51:31 Begin Action: DlgServices
01:51:36 ShowDlgServices returned: 1
01:51:36 [DlgServices]
01:51:36 Local-Domain = 3855
01:51:36 AutoStart = 15
01:51:36 Result = 1
01:51:36 End Action DlgServices
01:51:36 begin ShowDialogsUpdateMask
01:51:36 nFullMask = 0x1bdc0037, nCurrent = 0x400000, nDirection = 1
01:51:36 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:36 Dialog 0x400000 returned: 1
01:51:36 End Action ShowDialogsHlpr
01:51:36 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
01:51:36 Begin Action ShowDialogsHlpr: 0x800000
01:51:36 Begin Action: DlgSQLSecurity
01:51:38 ShowDlgSQLSecurity returned: 1
01:51:38 LoginMode = 1,szPwd
01:51:38 End Action DlgSQLSecurity
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x800000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x800000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned:nCurrent=0x1000000,index=24
01:51:38 Begin Action ShowDialogsHlpr: 0x1000000
01:51:38 Begin Action: DlgCollation
01:51:38 ShowDlgCollation returned: 1
01:51:38 collation_name = Latin1_General_CI_AS,locale_name = Latin1_General,lcid = 0xc09,SortId = 0,dwCompFlags = 0x30001
01:51:38 End Action DlgCollation
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x1000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x1000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
01:51:38 Begin Action ShowDialogsHlpr: 0x2000000
01:51:38 Begin Action: DlgNetwork
01:51:38 ShowDlgNetwork returned: 1
01:51:38 [DlgServerNetwork]
01:51:38 NetworkLibs = 255
01:51:38 TCPPort = 1433
01:51:38 TCPPrxy = Default
01:51:38 NMPPipeName = \\.\pipe\sql\query
01:51:38 Result = 1
01:51:38 End Action DlgNetwork
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x2000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x2000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
01:51:38 Begin Action ShowDialogsHlpr: 0x8000000
01:51:38 Begin Action: DialogShowSdStartCopy
01:51:38 End Action DialogShowSdStartCopy
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x8000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x8000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
01:51:38 Begin Action ShowDialogsHlpr: 0x10000000
01:51:38 Begin Action: DialogShowSdLicenseMode
01:51:40 ShowDlgLicense returned: 1
01:51:40 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 5
01:51:40 End Action DialogShowSdLicenseMode
01:51:40 Dialog 0x10000000 returned: 1
01:51:40 End Action ShowDialogsHlpr
01:51:40 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
01:51:40 End Action ShowDialogs
01:51:40 Begin Action ProcessBeforeDataMove:
01:51:40 DeinstallStart returned (C:\Program Files\Microsoft SQL Server\MSSQL): 0
01:51:40 End Action ProcessBeforeDataMove:
01:51:40 Begin Action SetToolsComponentSelection:
01:51:40 End Action SetToolsComponentSelection:
01:51:40 Begin Action ProcessComponentSelection:
01:51:40 End Action ProcessComponentSelection
01:51:40 Begin Action LogSelectedComponents:
01:51:40 SQLProg
01:51:40 SQLProg\SQLServr
01:51:40 SQLProg\SQLServr\Help
01:51:40 SQLProg\SQLServr\SCMDev
01:51:40 SQLProg\SQLServr\SCMDev\SCMh
01:51:40 SQLProg\SQLServr\SCMDev\SCMX86Lb
01:51:40 SQLProg\SQLServr\SCMDev\SCMALb
01:51:40 SQLProg\SQLServr\Rs1033
01:51:40 SQLProg\SQLServr\RsIntl
01:51:40 SQLProg\SQLServr\ActiveX
01:51:40 SQLProg\SQLServr\System
01:51:40 SQLProg\UpgTools
01:51:40 SQLProg\UpgTools\UpgSys
01:51:40 SQLProg\UpgTools\ActiveX
01:51:40 SQLProg\UpgTools\Res1033
01:51:40 SQLProg\UpgTools\ResOther
01:51:40 SQLProg\UpgTools\Resld
01:51:40 SQLProg\ReplSupp
01:51:40 SQLProg\ReplSupp\ReplDat
01:51:40 SQLProg\ReplSupp\RepComm
01:51:40 SQLProg\ReplSupp\RepNoDk
01:51:40 SQLProg\ReplSupp\ActiveX
01:51:40 SQLProg\Install
01:51:40 SQLProg\System
01:51:40 SQLProg\SvrExt
01:51:40 SQLProg\SvrExt\Help
01:51:40 SQLProg\SvrExt\SvrExtRs
01:51:40 SQLProg\SvrExt\ResIntl
01:51:40 SQLProg\Dat
01:51:40 SQLProg\DatSmpl
01:51:40 SQLProg\BaseSys
01:51:40 SQLProg\BaseBinn
01:51:40 SQLProg\MSSearch
01:51:40 SQLProg\MSSearch\Help
01:51:40 SQLProg\MSSearch\ActiveX
01:51:40 SQLProg\BaseInst
01:51:40 SQLProg\Symbols
01:51:40 SQLProg\Symbols\EXE
01:51:40 SQLProg\Symbols\DLL
01:51:40 SQLProg\Perfmon
01:51:40 SQLProg\Perfmon\System
01:51:40 SQLProg\Root
01:51:40 MgtTool
01:51:40 MgtTool\SEM
01:51:40 MgtTool\SEM\HTML
01:51:40 MgtTool\SEM\MSD98
01:51:40 MgtTool\SEM\MSD98SYS
01:51:40 MgtTool\SEM\MSD98Res
01:51:40 MgtTool\SEM\MSD98Hlp
01:51:40 MgtTool\SEM\Help
01:51:40 MgtTool\SEM\Res1033
01:51:40 MgtTool\SEM\ResIntl
01:51:40 MgtTool\SEM\MSD98RsI
01:51:40 MgtTool\SEM\ActiveX
01:51:40 MgtTool\SEM\ActiveX\Res1033
01:51:40 MgtTool\SEM\ActiveX\ResIntl
01:51:40 MgtTool\SEM\Scripts
01:51:40 MgtTool\SEM\OLEDB
01:51:40 MgtTool\SEM\OLEDB\Res1033
01:51:40 MgtTool\SEM\OLEDB\ResIntl
01:51:40 MgtTool\Profiler
01:51:40 MgtTool\Profiler\Help
01:51:40 MgtTool\Profiler\Res1033
01:51:40 MgtTool\Profiler\ResIntl
01:51:40 MgtTool\Qryanlz
01:51:40 MgtTool\Qryanlz\Help
01:51:40 MgtTool\Qryanlz\Res1033
01:51:40 MgtTool\Qryanlz\ResIntl
01:51:40 MgtTool\DTCCLi
01:51:40 MgtTool\Wzcnflct
01:51:40 MgtTool\Wzcnflct\WzcnHlp
01:51:40 MgtTool\Wzcnflct\Wzcn1033
01:51:40 MgtTool\Wzcnflct\WzcnOthr
01:51:40 MgtTool\Wzcnflct\WzcnCmn
01:51:40 MgtTool\UtilSys
01:51:40 MgtTool\UtilBinn
01:51:40 Connect
01:51:40 Connect\ConnSys
01:51:40 Books
01:51:40 Books\Bookso
01:51:40 Books\Bookso\Utils
01:51:40 DevTools
01:51:40 DevTools\Dbg Int
01:51:40 DevTools\Dbg Int\Dbg Int Common
01:51:40 DevTools\Dbg Int\EXE
01:51:40 CoreRepl
01:51:40 CoreRepl\Res1033
01:51:40 CoreRepl\ResIntl
01:51:40 Core
01:51:40 Core\Res1033
01:51:40 Core\ResOther
01:51:40 Repostry
01:51:40 Repostry\RepstSys
01:51:40 Repostry\Res1033
01:51:40 Repostry\ResIntl
01:51:40 CoreMisc
01:51:40 CoreMisc\ActiveX
01:51:40 CoreMisc\ActiveX\Res1033
01:51:40 CoreMisc\ActiveX\ResIntl
01:51:40 CoreMisc\Res1033
01:51:40 Monarch
01:51:40 Monarch\Monr1033
01:51:40 Monarch\MonrIntl
01:51:40 Jet
01:51:40 CoreInst
01:51:40 CoreCOM
01:51:40 CoreCOM\Res1033
01:51:40 CoreCOM\ResIntl
01:51:40 CoreTool
01:51:40 CoreTool\Res1033
01:51:40 CoreTool\ResOther
01:51:40 DBLibCli
01:51:40 SFExt
01:51:40 SFExt\ActiveX
01:51:40 SFExt\ActiveX\Res1033
01:51:40 SFExt\ActiveX\ResIntl
01:51:40 SFExt\Res1033
01:51:40 SFExt\ResIntl
01:51:40 Trace
01:51:40 Trace\Res1033
01:51:40 Trace\ResOther
01:51:40 MiscCore
01:51:40 MC
01:51:40 MC\MC1033
01:51:40 MC\MCIntl
01:51:40 MC\Help
01:51:40 SQLMgr
01:51:40 SQLMgr\Res1033
01:51:40 SQLMgr\ResIntl
01:51:40 SvrTool
01:51:40 SvrTool\Res1033
01:51:40 SvrTool\ResIntl
01:51:40 DTSUI
01:51:40 DTSUI\Res1033
01:51:40 DTSUI\ResIntl
01:51:40 MSOlap
01:51:40 MSOlap\Res1033
01:51:40 MSOlap\ResIntl
01:51:40 ATL
01:51:40 ATL\winnt
01:51:40 ATL\win9x
01:51:40 MFC42U
01:51:40 VC
01:51:40 VB
01:51:40 OCX1
01:51:40 SQLAdHlp
01:51:40 SQLAdHlp\Res1033
01:51:40 SQLAdHlp\ResOther
01:51:40 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
01:51:40 End Action LogSelectedComponents
01:51:40 Begin Action InstallPkgs:
01:51:40 Begin Action: Locked Connectivity Files Check
01:51:40 ConnectivityLocked returned: 0
01:51:40 The operation completed successfully.
01:51:40 End Action: Locked Connectivity Files Check
01:51:41 Setup is installing Microsoft Data Access Components (MDAC) ...
01:51:41 C:\INETPUB\FTPROOT\x86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
01:51:58 ExitCode: 0
01:51:58 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
01:51:58 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir "C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg "C:\INETPUB\FTPROOT\x86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
01:51:58 Process Exit Code: (0)
01:51:58 InstallMSSearch instance: MSSQLSERVER
01:51:58 Software\Microsoft\Search\Install:Version not present
01:51:58 MSSearch 2.0 or greater version check returned -1
01:51:58 Setup is installing the Microsoft Full-Text Search Engine ...
01:51:58 " C:\INETPUB\FTPROOT\x86\FullText\MSSearch\Search\Se
archStp.exe" /s /a:SQLServer
01:52:11 Process Exit Code: (0)
01:52:11 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
01:52:11 Setup is installing HTML Help ...
01:52:11 HTML Help installer exit code: 0
01:52:32 End Action InstallPkgs
01:52:32 Begin Action MoveFileData:
01:52:32 Enabled SELFREGISTERBATCH
01:52:32 Enabled CORECOMPONENTHANDLING
01:52:54 Begin Action: MoveFileDataSpecial|||01:52:55 End Action: MoveFileDataSpecial
01:52:55 End Action MoveFileData
01:52:55 Begin Action ProcessAfterDataMove:
01:52:55 C:\INETPUB\FTPROOT\x86\Binn\hhcol.exe C:\Program Files\Microsoft SQL Server\80\Tools\Books
01:52:55 End Action ProcessAfterDataMove
01:52:55 Begin Action BuildServer:
01:52:55 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5 -ExePath "C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
01:52:55 Process Exit Code: (0)
01:52:55 Begin Action: CreateRegistrySetSQL
01:52:55 End Action: CreateRegistrySetSQL
01:52:55 Begin Action: RegWriteSetupEntry
01:52:55 End Action: RegWriteSetupEntry
01:52:55 Begin Action: CreateSer
01:52:55 End Action: CreateSer
01:52:55 Begin Action: SkuIt
01:52:55 End Action: SkuIt
01:52:56 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL Server\MSSQL returned: 0, 0
01:52:56 SetRegSecuritySQLAndAdmin for Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
01:52:56 Begin Action: UpdateSystemPath
01:52:56 Path successfully updated.
01:52:56 %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy
stem32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
01:52:56 End Action: UpdateSystemPath
01:52:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Latin1_General_CI_AS" -H 131390 -U sa -P
01:52:57 Process Exit Code: (193)
01:54:06 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
01:54:06 Action CleanUpInstall:
01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
01:54:06 Process Exit Code: (1060) The specified service does not exist as an installed service.
01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
01:54:07 Process Exit Code: (0)
01:54:07 StatsGenerate returned: 2
01:54:07 StatsGenerate (0x0,0x1,0xf00,0x0,1033,303,0x0,0x1,0,0,0
01:54:07 StatsGenerate -1,Administrator)
01:54:07 Installation Failed.|||Check the sqlstp.log under c:\winnt. Also look for information in the event logs. I am not sure if these will exist yet, but check for errorlog files under the sql server directory.|||there is no errorlog files under the sql server directory. I already check it. Also the above is my Sqlstp.log file.
I have try so many way to solve the problem, however I can't ...pls help|||How about sqlsp.log and event logs ? Did the log end on "01:52:54 Begin Action: MoveFileDataSpecial" ?|||Its end with 01:54:07 Installation Failed.|||This is another one
06:20:21 Begin Setup
06:20:21 8.00.194
06:20:21 Mode = Normal
06:20:21 ModeType = NORMAL
06:20:21 GetDefinitionEx returned: 0, Extended: 0x0
06:20:21 ValueFTS returned: 1
06:20:21 ValuePID returned: 1
06:20:21 ValueLic returned: 1
06:20:21 System: Windows NT Terminal Server
06:20:21 SQL Server ProductType: Standard Edition [0x2]
06:20:21 Begin Action: SetupInitialize
06:20:21 End Action SetupInitialize
06:20:21 Begin Action: SetupInstall
06:20:21 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
06:20:21 CommonFilesDir=C:\Program Files\Common Files
06:20:21 Windows Directory=C:\WINDOWS\
06:20:21 Program Files=C:\Program Files\
06:20:21 TEMPDIR=C:\WINDOWS\TEMP\
06:20:21 Begin Action: SetupInstall
06:20:21 digpid size : 256
06:20:21 digpid size : 164
06:20:21 Begin Action: CheckFixedRequirements
06:20:21 Platform ID: 0xf00
06:20:21 Version: 5.2.3790
06:20:21 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
06:20:21 End Action: CheckFixedRequirements
06:20:21 Begin Action: ShowDialogs
06:20:21 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
06:20:21 Begin Action ShowDialogsHlpr: 0x1
06:20:21 Begin Action: DialogShowSdWelcome
06:20:23 End Action DialogShowSdWelcome
06:20:23 Dialog 0x1 returned: 1
06:20:23 End Action ShowDialogsHlpr
06:20:23 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
06:20:23 Begin Action ShowDialogsHlpr: 0x2
06:20:23 Begin Action: DialogShowSdMachineName
06:20:29 ShowDlgMachine returned: -1
06:20:29 ShowDlgMachine: GetLastError returned: 0
06:20:29 The operation completed successfully.
06:20:29 End Action DialogShowSdMachineName
06:20:29 End Action ShowDialogs
06:20:29 Action CleanUpInstall:
06:20:29 StatsGenerate returned: 2
06:20:29 StatsGenerate (0x0,0x0,0xf00,0x0,1033,0,0x0,0x0,0,0,0
06:20:29 StatsGenerate -1,)
06:20:29 Installation Failed.|||I missed the 3rd post with the log dump. Anyway, try running the sql setup in debug mode - using \x86\setup\setupsql.exe k=Dbq. When you get to the server configuration portion - see if you can start the sql server service.|||hi,
It doesn't work. samw problem. any more suggestion?|||What happens when you are in debug and the configure server prompts and you attempt to start the sql server service - without proceeding with the configure server (just leave it at the prompt) ?|||it quit automatically after it says setup failed to configure the server
Subscribe to:
Posts (Atom)