From: goldenthroat via SQLMonster.com on
Thank you for your response. Here is the last event on the system event
viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 12/28/2008
Time: 7:37:32 AM
User: N/A
Computer: ICHIBAN
Description:
The SQL Server (SQLEXPRESS) service terminated with service-specific error
17058 (0x42A2).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The event before that was this:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 12/28/2008
Time: 7:37:32 AM
User: N/A
Computer: ICHIBAN
Description:
The SQL Server (SQLEXPRESS) service entered the stopped state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

And the event before that was this:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 12/28/2008
Time: 7:37:29 AM
User: ICHIBAN\Larry
Computer: ICHIBAN
Description:
The SQL Server (SQLEXPRESS) service was successfully sent a start control.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Thanks again for your response.

John Bell wrote:
>>I recently installed SQL Server 2008 Express Edition with Advanced Tools.
>>
>[quoted text clipped - 119 lines]
>>
>> Please help.
>
>Hi
>
>The only reference to your WMI error seem to be
>http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic20786.aspx
>which implies that if you changed it to Local System it should have made the
>change!! Also http://support.microsoft.com/kb/955496 which seems to be on a
>Domain Controller which you are not, but again Local System should have been
>fine. What does the ERRORLOG for your SQL Server Express instance say?
>
>John

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1

From: John Bell on

"goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message
news:8f566b5d135a3(a)uwe...
> The Errorlog has no items since 12:09 pm yesterday, and I certainly did a
> lot
> of things since then. Here it is:
>

> 2008-12-27 11:55:35.34 spid54 Starting up database
> 'AdventureWorksLT2008'.
> 2008-12-27 11:55:35.62 spid33s Starting up database
> 'AdventureWorks2008'.
> 2008-12-27 11:55:35.85 spid54 Starting up database 'ReportServer
> $SQLEXPRESSTempDB'.
> 2008-12-27 11:55:37.73 spid32s Starting up database
> 'AdventureWorks2008'.
2008-12-27 12:09:09.31 spid47s Starting up database
'AdventureWorks2008'.
> 2008-12-27 12:09:11.64 spid43s Starting up database
> 'AdventureWorks2008'.
> 2008-12-27 12:09:12.64 spid42s Starting up database
> 'AdventureWorks2008'.
> 2008-12-27 12:09:13.76 Server SQL Server is terminating because of a
> system shutdown. This is an informational message only. No user action is
> required.
> 2008-12-27 12:09:13.93 spid48s Starting up database
> 'AdventureWorks2008'.
> 2008-12-27 12:09:16.78 Logon Error: 18456, Severity: 14, State: 23.
> 2008-12-27 12:09:16.78 Logon Login failed for user 'NT
> AUTHORITY\LOCAL
> SERVICE'. Reason: Access to server validation failed while revalidating
> the
> login on the connection. [CLIENT: <local machine>]
> 2008-12-27 12:09:17.09 spid51 Error: 17054, Severity: 16, State: 1.
> 2008-12-27 12:09:17.09 spid51 The current event was not reported to
> the
> Windows Events log. Operating system error = (null). You may need to clear
> the Windows Events log if it is full.
> 2008-12-27 12:09:17.28 spid51 Error: 18056, Severity: 20, State: 23.
> 2008-12-27 12:09:17.28 spid51 The client was unable to reuse a
> session
> with SPID 51, which had been reset for connection pooling. The failure ID
> is
> 23. This error may have been caused by an earlier operation failing. Check
> the error logs for failed operations immediately before this error
> message.
> 2008-12-27 12:09:27.14 spid48s Recovery completed for database
> AdventureWorks2008 (database ID 11) in 1 second(s) (analysis 335 ms, redo
> 0
> ms, undo 313 ms.) This is an informational message only. No user action is
> required.
> 2008-12-27 12:09:34.76 spid18s Service Broker manager has shut down.
> 2008-12-27 12:09:36.62 spid7s .NET Framework runtime has been
> stopped.
> 2008-12-27 12:09:40.42 spid7s SQL Trace was stopped due to server
> shutdown. Trace ID = '1'. This is an informational message only; no user
> action is required.
>
>
> John Bell wrote:
>>>I recently installed SQL Server 2008 Express Edition with Advanced Tools.
>>>
>>[quoted text clipped - 119 lines]
>>>
>>> Please help.
>>
>>Hi
>>
>>The only reference to your WMI error seem to be
>>http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic20786.aspx
>>which implies that if you changed it to Local System it should have made
>>the
>>change!! Also http://support.microsoft.com/kb/955496 which seems to be on
>>a
>>Domain Controller which you are not, but again Local System should have
>>been
>>fine. What does the ERRORLOG for your SQL Server Express instance say?
>>
>>John
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1


All the messages like

2008-12-27 11:55:37.73 spid32s Starting up database
'AdventureWorks2008'.


are not usual, I would only expect this once. Try starting

NET START "SQL SERVER (SQLExpress)" /f /m /T3608

then you can use

SQLCMD -S \SQLEXPRESS -E -Q "EXEC sp_detach_db AdventureWorks2008"

to detach the database and try stopping and starting the service normally.

John

From: Jeffrey Williams on
based upon this error - using SQL Server Configuration Manager verify the
setting for the error log. This will be the -e parameter in the Startup
Parameters.

"goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message
news:8f565ea05c9cb(a)uwe...
> Thank you for your response. I used the NET START command as you
> suggested
> and received this response:
>
> "The SQL Server <SQLEXPRESS> service is starting...
> The SQL Server <SQLEXPRESS> service could not be starated.
> A service specific error occurred: 17058.
> More help is available by typing NET HELPMSG 3547,"
>
> When I typed in the helpmsg I received:
>
> "...A service-specific error occurred. Refer to the Help or documentation
> for that service to determine the problem."
>
> This is the error message in in the Application Event Viewer:
>
> Event Type: Error
> Event Source: MSSQL$SQLEXPRESS
> Event Category: Server
> Event ID: 17058
> Date: 12/28/2008
> Time: 7:37:32 AM
> User: N/A
> Computer: ICHIBAN
> Description:
> initerrlog: Could not open error log file ''. Operating system error =
> 3(The
> system cannot find the path specified.).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a2 42 00 00 10 00 00 00 ¢B......
> 0008: 13 00 00 00 49 00 43 00 ....I.C.
> 0010: 48 00 49 00 42 00 41 00 H.I.B.A.
> 0018: 4e 00 5c 00 53 00 51 00 N.\.S.Q.
> 0020: 4c 00 45 00 58 00 50 00 L.E.X.P.
> 0028: 52 00 45 00 53 00 53 00 R.E.S.S.
> 0030: 00 00 00 00 00 00 ......
>
> Your last question about how I know the sample databases installed
> successfully is a good question. I don't know except that the installer
> reported success.
>
> Thanks again for your response. I am grateful for the help.
>
> Kalen Delaney wrote:
>>Wow... thanks for all the data points. After all the research you've
>>already
>>done, I hate to tell you should also have looked one more place, but
>>please
>>don't neglect SQL Server's own documentation, Books Online.
>>
>>http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
>>
>>If you had looked up the NET START command, it would have shown you the
>>syntax for starting an instance:
>>
>>NET START MSSQL$<instancename>
>>
>>so in your case, that would be
>>
>>NET START MSSQL$SQLExpress
>>
>>Also, how are you sure you successfully installed the sample databases if
>>you cannot connect to your SQL Server to verify?
>>
>>>I recently installed SQL Server 2008 Express Edition with Advanced Tools.
>>>
>>[quoted text clipped - 119 lines]
>>>
>>> Please help.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1
>
From: goldenthroat via SQLMonster.com on
Thanks again for your response. Here is what happened. When I typed the
first command, I got:
"The SQL Server <SQLEXPRESS> service is starting..
The SQL Server <SQLEXPRESS> could not be started.
A service-specific error occurred: 17058.
More help is available by typing NET HELPMSG 2547."

The second one resulted in this:
"HResult OxFFFFFFFF, Level 16, State 1.
SQL Server Network Interface: Error Locating Server/Instance Specified
[xFFFFFFFF].
Sqlcmd:Error: Microsoft SQL Server Native Client 10.0: A network-related or
instance-specific error has occurred while establishing a connection to SQL
Server. Server is not found or not accessible. Check if instance name is
correct and if SQL Server is configured to allow remote connections. For
more information see SQL Server Books Online.
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: Logout timeout
expired."

I don't know if SQL Server is configured to allow remove connections. One
thing to note. I'm running this on Windows XP Home Edition. Can it be used
as a server? It can't run MIS. I know because I tried. That being said,
can it be configured to allow remote connections? I don't know. It does
Remote Desktop Connection, although I've never set it up for that.

Thanks for your help. Is there anything else I can do, or other information
I can get you?

John Bell wrote:
>> The Errorlog has no items since 12:09 pm yesterday, and I certainly did a
>> lot
>> of things since then. Here it is:
>
>> 2008-12-27 11:55:35.34 spid54 Starting up database
>> 'AdventureWorksLT2008'.
>[quoted text clipped - 4 lines]
>> 2008-12-27 11:55:37.73 spid32s Starting up database
>> 'AdventureWorks2008'.
> 2008-12-27 12:09:09.31 spid47s Starting up database
>'AdventureWorks2008'.
>> 2008-12-27 12:09:11.64 spid43s Starting up database
>> 'AdventureWorks2008'.
>[quoted text clipped - 55 lines]
>>>
>>>John
>
>All the messages like
>
>2008-12-27 11:55:37.73 spid32s Starting up database
>'AdventureWorks2008'.
>
> are not usual, I would only expect this once. Try starting
>
>NET START "SQL SERVER (SQLExpress)" /f /m /T3608
>
>then you can use
>
>SQLCMD -S \SQLEXPRESS -E -Q "EXEC sp_detach_db AdventureWorks2008"
>
>to detach the database and try stopping and starting the service normally.
>
>John

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1

From: John Bell on

"goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message
news:8f5990f483fcf(a)uwe...
> Thanks again for your response. Here is what happened. When I typed the
> first command, I got:
> "The SQL Server <SQLEXPRESS> service is starting..
> The SQL Server <SQLEXPRESS> could not be started.
> A service-specific error occurred: 17058.
> More help is available by typing NET HELPMSG 2547."
>
> The second one resulted in this:
> "HResult OxFFFFFFFF, Level 16, State 1.
> SQL Server Network Interface: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd:Error: Microsoft SQL Server Native Client 10.0: A network-related
> or
> instance-specific error has occurred while establishing a connection to
> SQL
> Server. Server is not found or not accessible. Check if instance name is
> correct and if SQL Server is configured to allow remote connections. For
> more information see SQL Server Books Online.
> Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: Logout timeout
> expired."
>
> I don't know if SQL Server is configured to allow remove connections. One
> thing to note. I'm running this on Windows XP Home Edition. Can it be
> used
> as a server? It can't run MIS. I know because I tried. That being said,
> can it be configured to allow remote connections? I don't know. It does
> Remote Desktop Connection, although I've never set it up for that.
>
> Thanks for your help. Is there anything else I can do, or other
> information
> I can get you?
>
> John Bell wrote:
>>> The Errorlog has no items since 12:09 pm yesterday, and I certainly did
>>> a
>>> lot
>>> of things since then. Here it is:
>>
>>> 2008-12-27 11:55:35.34 spid54 Starting up database
>>> 'AdventureWorksLT2008'.
>>[quoted text clipped - 4 lines]
>>> 2008-12-27 11:55:37.73 spid32s Starting up database
>>> 'AdventureWorks2008'.
>> 2008-12-27 12:09:09.31 spid47s Starting up database
>>'AdventureWorks2008'.
>>> 2008-12-27 12:09:11.64 spid43s Starting up database
>>> 'AdventureWorks2008'.
>>[quoted text clipped - 55 lines]
>>>>
>>>>John
>>
>>All the messages like
>>
>>2008-12-27 11:55:37.73 spid32s Starting up database
>>'AdventureWorks2008'.
>>
>> are not usual, I would only expect this once. Try starting
>>
>>NET START "SQL SERVER (SQLExpress)" /f /m /T3608
>>
>>then you can use
>>
>>SQLCMD -S \SQLEXPRESS -E -Q "EXEC sp_detach_db AdventureWorks2008"
>>
>>to detach the database and try stopping and starting the service normally.
>>
>>John
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1
>
Hi

So the SQL server Error Log no longer has the "Starting up
Adventureworks2008" messages?

John