Counter settings: logs

Showing posts with label logs. Show all posts

Tuesday, March 20, 2012

Could not start SQL Server

SQL server is not starting, logs following error in
windows log
Error: 9003, Severity: 20,State: 1
The LSN (4:482:1) passed to log scan in database 'model'
is invalid
Is any one having solution for this?Manoj
It looks like the model database has become corrupted due to the power
failure.
Try to start the SQL Server as an application from a command prompt. For
more information, please refer to the topics: 'Starting SQL Server
Manually' and 'Using Startup Options' on Microsoft SQL Server Books Online.
Look if it does not help you so in this situation your best bet is to call
MS PSS
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Hi,
Seems your Model database is corrupt,
1. Stop SQL server
2. Copy the .MDF and .LDF files (Belongs to MODEL database) to a different
ent location
3. From a different SQL Serevr copy the Model databases .MDF and .LDF files
to the same folder. Overwrite the old files
4. Now start the SQL server.
Most probably this will work out.
Thanks
Hari
MCDBA
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Thanks Hari !! I will try this option
>--Original Message--
>Hi,
>Seems your Model database is corrupt,
>1. Stop SQL server
>2. Copy the .MDF and .LDF files (Belongs to MODEL
database) to a different
>ent location
>3. From a different SQL Serevr copy the Model
databases .MDF and .LDF files
>to the same folder. Overwrite the old files
>4. Now start the SQL server.
>
>Most probably this will work out.
>Thanks
>Hari
>MCDBA
>
>"Manoj" <manoj_raheja@.hotmail.com> wrote in message
>news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
>> SQL server is not starting, logs following error in
>> windows log
>> Error: 9003, Severity: 20,State: 1
>> The LSN (4:482:1) passed to log scan in database 'model'
>> is invalid
>> Is any one having solution for this?
>
>.
>|||Make sure that other SQL Server has the same collation. SQL Server does not
support different collations across the system databases.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:d07801c3eeee$ed440170$a401280a@.phx.gbl...
> Thanks Hari !! I will try this option
> >--Original Message--
> >Hi,
> >
> >Seems your Model database is corrupt,
> >
> >1. Stop SQL server
> >2. Copy the .MDF and .LDF files (Belongs to MODEL
> database) to a different
> >ent location
> >3. From a different SQL Serevr copy the Model
> databases .MDF and .LDF files
> >to the same folder. Overwrite the old files
> >4. Now start the SQL server.
> >
> >
> >Most probably this will work out.
> >
> >Thanks
> >Hari
> >MCDBA
> >
> >
> >"Manoj" <manoj_raheja@.hotmail.com> wrote in message
> >news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> >> SQL server is not starting, logs following error in
> >> windows log
> >>
> >> Error: 9003, Severity: 20,State: 1
> >> The LSN (4:482:1) passed to log scan in database 'model'
> >> is invalid
> >>
> >> Is any one having solution for this?
> >>
> >
> >
> >.
> >|||Hi! Hari Prasad,
Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||What's the error? Could you post the error form the error log?
--
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Community)
SQLTips, SQL Scripts, SQL Forums, SQL Articles, SQL Radio, SQL Server 2008,
SQL Blogs, SQL Clinic and a lot of SQL Server fun.
"Girish Sharma (QA Engg.)" wrote:
> Hi! Hari Prasad,
> Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
>
> From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

Monday, March 19, 2012

could not obtain information about...

I am getting the following message in my event logs since hitting windows up
date and installing, among others SP4 for win2k.
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Michaels B
ackup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) - Status: Failed - Invoked
on: 2004-01-19 02:00:00 - Message: The job failed. Unable to determine if
the owner (MYSERVER\mylogin) of job DB Backup Job for DB Maintenance Plan 'M
ichaels Backup Plan' has server access (reason: Could not obtain information
about Windows NT group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 819
8))."
the only thing that changed was the updates, which can be significant but I
certainly didn't change anything related to my account. I have recreated th
e plan with the same result.
I can open the LOGON section of SQLadmin and see my name there, I can open i
t and close it but if I try to make any changes it says messages similar to
the above on.
KB articles suggested ading the everyone group to the pre2000 users group bu
t that sounds dangerous.
Help? what else can I look at. I am the sysop and should have all the necess
ary rightsIn message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
writes

quote:

>I am getting the following message in my event logs since hitting windows
>update_and installing, among others _SP4 for win2k.
>"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
>'Michaels Backup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) -
>Status: Failed - Invoked on: 2004-01-19 02:00:00 - Message: The job
>failed._ Unable to determine if the owner (MYSERVER\mylogin) of job DB
>Backup Job for DB Maintenance Plan 'Michaels Backup Plan' has server
>access (reason: Could not obtain information about Windows NT
>group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 8198))."
>the only thing that changed was the updates, which can be significant but
>_I certainly didn't change anything related to my account. I have recreated
>the plan with the same result.
>I can open the LOGON section of SQLadmin and see my name there, I
>can open it and close it but if I try to make any changes it says messages
>similar to the above on.
>KB articles suggested ading the everyone group to the pre2000 users
>group but that sounds dangerous.
>Help? what else can I look at. I am the sysop and should have all the
>necessary rights

I assume you have seen KB 241643, but have you tried the first
workaround "Change the job owner to a standard SQL Server user or system
administrator (sa)."? I have read this many times, and the second option
has never worked for me, so I go straight for option 1. I suspect there
may be other causes, perhaps network issues between SQL and the DC.
PRB: 8198 Error Message Returned from Job Owned by Windows NT
Authenticated User
http://support.microsoft.com?kbid=241643
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org|||"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...

quote:

> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>

|||Lets try that again.
I saw the KB article and I couldn't make option 2 work either so that is
encouraging :-?
The DC and the SQL server are the same machine so comms shouldn't be an
issue.
I'll try creating a new backup plan under sa but could you tell me what a
"Standard Sql Server User " is?
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...

quote:

> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>

|||In message <u1fxN$d4DHA.2612@.tk2msftngp13.phx.gbl>, mmac <no@.thanks.com>
writes

quote:

>Lets try that again.
>I saw the KB article and I couldn't make option 2 work either so that is
>encouraging :-?
>The DC and the SQL server are the same machine so comms shouldn't be an
>issue.
>I'll try creating a new backup plan under sa but could you tell me what a
>"Standard Sql Server User " is?
>

A standard SQL Server user, or SQL (Server) login, is what you use as
opposed to and integrated or NT authentication login. This option is
only available if the server is set to Mixed Mode security.
sa is a SQL login, but BUILTIN\Administrators is a integrated login.
Make sense?
Darren

quote:

>"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in messag
e
>news:7r2qD3R8WFEAFwOw@.sqldts.com...
>recreated
>messages
>

Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Tuesday, March 20, 2012

Could not start SQL Server

Could not start SQL Server

Monday, March 19, 2012

could not obtain information about...

Counter settings

Blog Archive

About Me