Prev: failed to pause full-text catalog for backup
Next: SQL Server 2008 and PowerShell
From: goldenthroat via SQLMonster.com on 28 Dec 2008 14:48
Thanks for your response. I went to Books Online and found out about the
Startup Parameters. Thanks for telling me about them! Here is what they
currently are:

-dc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.
mdf;-ec:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\
ERRORLOG;-lc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\
DATA\mastlog.ldf

I notice that there is no "-e" option, but there is a "-ec" with the valid
path for the error log. Similarly the "-d" has been replaced with "-dc". I
will correct these two items and try to start SQL Server.

Jeffrey Williams wrote:
>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.
>
>> Thank you for your response. I used the NET START command as you
>> suggested
>[quoted text clipped - 67 lines]
>>>>
>>>> Please help.

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

From: Jeffrey Williams on 28 Dec 2008 15:27
No - they are correct as is. The -e parameter includes the 'c' drive so it
looks like -ec...

"goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message
news:8f59f83b1718f(a)uwe...
> Thanks for your response. I went to Books Online and found out about the
> Startup Parameters. Thanks for telling me about them! Here is what they
> currently are:
>
> -dc:\Program Files\Microsoft SQL
> Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.
> mdf;-ec:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\
> ERRORLOG;-lc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\
> DATA\mastlog.ldf
>
> I notice that there is no "-e" option, but there is a "-ec" with the valid
> path for the error log. Similarly the "-d" has been replaced with "-dc".
> I
> will correct these two items and try to start SQL Server.
>
> Jeffrey Williams wrote:
>>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.
>>
>>> Thank you for your response. I used the NET START command as you
>>> suggested
>>[quoted text clipped - 67 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 28 Dec 2008 15:37
Thanks for your question and interest in my problem.

The error log is still not getting updated today. There is no error log for
today. Another poster suggested that I check the Startup Parameters in SQL
Server Configuration Manager, which I did, and all three of them were wrong,
so I fixed them, but I still have the same problem. (The paths were correct,
but the switches were wrong. - "-ec" instead of "-e", etc.)

Somehow SQL Server never gets started enough to write to the log? Does that
make sense?

John Bell wrote:
>> Thanks again for your response. Here is what happened. When I typed the
>> first command, I got:
>[quoted text clipped - 62 lines]
>>>
>>>John
>
>Hi
>
>So the SQL server Error Log no longer has the "Starting up
>Adventureworks2008" messages?
>
>John

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

From: goldenthroat via SQLMonster.com on 28 Dec 2008 15:39
Thanks for telling me that. I put them back the way they were. Do you have
any other ideas? Thanks again for your help.

Jeffrey Williams wrote:
>No - they are correct as is. The -e parameter includes the 'c' drive so it
>looks like -ec...
>
>> Thanks for your response. I went to Books Online and found out about the
>> Startup Parameters. Thanks for telling me about them! Here is what they
>[quoted text clipped - 20 lines]
>>>>>>
>>>>>> Please help.

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

From: John Bell on 28 Dec 2008 16:39

"goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message
news:8f5a6422c4f6b(a)uwe...
> Thanks for your question and interest in my problem.
>
> The error log is still not getting updated today. There is no error log
> for
> today. Another poster suggested that I check the Startup Parameters in
> SQL
> Server Configuration Manager, which I did, and all three of them were
> wrong,
> so I fixed them, but I still have the same problem. (The paths were
> correct,
> but the switches were wrong. - "-ec" instead of "-e", etc.)
>
> Somehow SQL Server never gets started enough to write to the log? Does
> that
> make sense?
>
> John Bell wrote:
>>> Thanks again for your response. Here is what happened. When I typed the
>>> first command, I got:
>>[quoted text clipped - 62 lines]
>>>>
>>>>John
>>
>>Hi
>>
>>So the SQL server Error Log no longer has the "Starting up
>>Adventureworks2008" messages?
>>
>>John
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1
>
Hi

You may want to try starting SQL Server from a command prompt rather than
using the service see http://msdn.microsoft.com/en-us/library/ms180965.aspx
as you will see the startup messages.
On the command line you can also specify the flags as per the previous posts
and change the log file using the -e flag.

e.g

Change your directory to

C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\BINN

then run:

SQLSERVR -S "SQLEXPRESS" -eC:\temp\errorlog.txt

The startup messages will also be in C:\temp\errorlog.txt

John

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: failed to pause full-text catalog for backup
Next: SQL Server 2008 and PowerShell