Failed Assertion Logmgr.cpp -- help!

Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:11/1/2004
Time:9:19:23 PM
User:HENT\Administrator
Computer:HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.
Hi Kevin,
Your best bet is goign to be to contact Microsoft CSS - they can help you get to the bottom of this.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Kevin Anderson" <Kevin Anderson@.discussions.microsoft.com> wrote in message news:700E664C-667C-4C82-A08E-81E8647598F9@.microsoft.com...
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/1/2004
Time: 9:19:23 PM
User: HENT\Administrator
Computer: HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.

Failed Assertion Logmgr.cpp -- help!

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/1/2004
Time: 9:19:23 PM
User: HENT\Administrator
Computer: HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.Hi Kevin,
Your best bet is goign to be to contact Microsoft CSS - they can help you ge
t to the bottom of this.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Kevin Anderson" <Kevin Anderson@.discussions.microsoft.com> wrote in message
news:700E664C-667C-4C82-A08E-81E8647598F9@.microsoft.com...
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/1/2004
Time: 9:19:23 PM
User: HENT\Administrator
Computer: HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.

Failed Assertion

I'm getting the following in the Event log. Has anyone seen this? Any help
is greatly appreciated!
I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
disk array.
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.
Thanks!!
Eric ward
had this problem before try out this kba, not a fix but trace flag 806 gives
better reporting on Disk IO
http://support.microsoft.com/default...b;en-us;841776
"Eric Ward" wrote:

> I'm getting the following in the Event log. Has anyone seen this? Any help
> is greatly appreciated!
> I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> disk array.
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1374
> Failed Assertion = 'm_nVars > 0'.
>
> Thanks!!
> Eric ward
>
|||might need to upgrade the firmwar for your disk controllers to resolve the
problem.
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:41041293-32B2-44A5-AA84-502C335F6681@.microsoft.com...
> had this problem before try out this kba, not a fix but trace flag 806
gives[vbcol=seagreen]
> better reporting on Disk IO
> http://support.microsoft.com/default...b;en-us;841776
> "Eric Ward" wrote:
help[vbcol=seagreen]

Failed Assertion

I'm getting the following in the Event log. Has anyone seen this? Any help
is greatly appreciated!
I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
disk array.
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.
Thanks!!
Eric wardhad this problem before try out this kba, not a fix but trace flag 806 gives
better reporting on Disk IO
http://support.microsoft.com/default.aspx?scid=kb;en-us;841776
"Eric Ward" wrote:
> I'm getting the following in the Event log. Has anyone seen this? Any help
> is greatly appreciated!
> I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> disk array.
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1374
> Failed Assertion = 'm_nVars > 0'.
>
> Thanks!!
> Eric ward
>|||might need to upgrade the firmwar for your disk controllers to resolve the
problem.
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:41041293-32B2-44A5-AA84-502C335F6681@.microsoft.com...
> had this problem before try out this kba, not a fix but trace flag 806
gives
> better reporting on Disk IO
> http://support.microsoft.com/default.aspx?scid=kb;en-us;841776
> "Eric Ward" wrote:
> > I'm getting the following in the Event log. Has anyone seen this? Any
help
> > is greatly appreciated!
> >
> > I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> > disk array.
> >
> > 17066 :
> > SQL Server Assertion: File: <recbase.cpp>, line=1374
> > Failed Assertion = 'm_nVars > 0'.
> >
> >
> > Thanks!!
> >
> > Eric ward
> >
> >

Fail to start Analysis Services Engine

Why I am not able to start the Analysis Services Engine again as the error message from event viewer as:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 0
Date: 04/07/2007
Time: 10:45:48
User: N/A
Computer: computer_name
Description:
The service cannot be started: Message-handling subsystem: The message manager for the default locale cannot be found. The locale will be changed to US English. Message-handling subsystem: The message manager for the default locale cannot be found. The locale will be changed to US English. The following system error occurred: The filename, directory name, or volume label syntax is incorrect. . File system error: Error occurred during the creation of directory: '\\?\'.

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

On SQL Server, when I start the Analysis services, the error message is : The SQL Server Analysis Services (MSSQLSERVER) service on local computer started and then stopped. Some services stop automatically if they have no work to do, for example, the performance logs and Alerts service.

Why is that? That is really frustrated and please any of you give me any advices or help on it. Thanks a lot in advance.

With best regards,

Yours sincerely,

I'm facing the similar problem as well. Fed up with SSAS 2005 on vista. Xp works fine.

I attempt to start my analysis serivces and it just failed. A check in the
Event Viewer --> Application log has uncover the below error detail.
Further googled and found 3 suggested solutions
1. Upgrade to Vista Ultimate. --> Doesn't work for me since i'm using Vista
Ultimate
2. Change locale to English (US) --> Doesn;t work as well. Same error
message.
3. Delete the folder MsSql.2 --> Doesn't work. Same error message.

Is this a bug in SSAS2005? Any more remedy? Hi Microsoft Guys, can you
help?

This is the detailed of the error:-

Log Name: Application
Source: MSSQLServerOLAPService
Date: 7/6/2007 12:04:13 AM
Event ID: 0
Task Category: (289)
Level: Error
Keywords: Classic
User: N/A
Computer: MyVista
Description:
The service cannot be started: Message-handling subsystem: The message
manager for the default locale cannot be found. The locale will be changed
to US English. Errors in the metadata manager. LOG file extension can be
only .LOG. Message-handling subsystem: The message manager for the default
locale cannot be found. The locale will be changed to US English.
Message-handling subsystem: The message manager for the 17417 locale cannot
be found. Internal error: Failed to generate a hash string.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSSQLServerOLAPService" />
<EventID Qualifiers="49441">0</EventID>
<Level>2</Level>
<Task>289</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-07-05T16:04:13.000Z" />
<EventRecordID>15488</EventRecordID>
<Channel>Application</Channel>
<Computer>MyVista</Computer>
<Security />
</System>
<EventData>
<Data>Message-handling subsystem: The message manager for the default
locale cannot be found. The locale will be changed to US English. Errors in
the metadata manager. LOG file extension can be only .LOG. Message-handling
subsystem: The message manager for the default locale cannot be found. The
locale will be changed to US English. Message-handling subsystem: The
message manager for the 17417 locale cannot be found. Internal error: Failed
to generate a hash string.</Data>
</EventData>
</Event>

|||

Found the solution. Change the service for SSAS to run under different
account with EN-US locale. LSA was configured to use EN-MY locale.

If you insists to use LSA account. Start your registry editor. Goto
HKEY_USERS
look for LSA entry @. S-1-5-18
Search for Locale
Change
Locale = 00000409
LocaleName = en-US
sCountry = United States

Done. You can start your SSAS 2005 now

extremely slow query

I have this querys, and when I run it, it took 15 minutes trowing the result, for the momment event is a table with 101 tuples and leftjets are near to 700 tuples, im gonna chech if I see where is the bottleneck.

Code Snippet

/**********************************************************************/
/* Jet Veto Cut 2
* leftJets jetbs should have Pt not bigger then maxAllowedPtForOtherJets
* see Hadronic Top Cut 2
* m_maxAllowedPtForOtherJets: ptOJets
*/
/*
* TTreeCut::SelectTopCombination, m_theTopComb
* min of m_okTopComb
*/

create view mTopComb
As
select j.*
from topComb as j
where (abs(sqrt(abs((j.j1Ee+j.j2Ee + j.Ee)*(j.j1Ee+j.j2Ee +j.Ee) -
((j.j1px +j.j2px + j.px)*(j.j1px +j.j2px + j.px) +
(j.j1py +j.j2py + j.py)*(j.j1py +j.j2py + j.py) +
(j.j1pz +j.j2pz + j.pz)*(j.j1pz +j.j2pz + j.pz))))
- 174.3))
=
(select min(abs(sqrt(abs((t.j1Ee+t.j2Ee + t.Ee)*(t.j1Ee+t.j2Ee +t.Ee) -
((t.j1px +t.j2px + t.px)*(t.j1px +t.j2px + t.px) +
(t.j1py +t.j2py + t.py)*(t.j1py +t.j2py + t.py) +
(t.j1pz +t.j2pz + t.pz)*(t.j1pz +t.j2pz + t.pz))))
- 174.3))
from topComb as t
where t.eventid=j.eventid)

GO

/*
* TTreeCut::SelectTopCombination, m_theLeftOverJets
* select m_okJets which are not contained in m_theTopComb
*/

create view leftjets
As
select distinct o.*
from okJets as o
where not exists (select o.idap from mtopcomb as j where j.idap=o.idap);

GO

create view jetVetoCut
AS
select distinct e.*
from events e
where not exists (select * from leftjets j where e.idevent=j.eventid and dbo.pt(j.idap)>70);

GO

The WHERE clause contains expressions that are extremely complex and that makes it very hard for the Query Optimizer to do accurate estimation. Typically column expressions at the WHERE clause cause optimziation problems, with plan choice or plan execution and they make the use of indexes impossible. I am guessing that for these reasons the query optimizer produces a suboptimal plan and hence your query is slow.

The following article describes a way to deal with complex expressions and enable the query optimizer to do proper estimation . I hope that you find this useful: http://blogs.msdn.com/queryoptteam/archive/2006/03/24/560089.aspx

Regards,

Leo Giakoumakis

|||

hi,

here's another alternative.. the idea of mTopCombComputed is to return the same result as your mTopCombView but the difference is that we minimized the query so that it would require less number of reads.

CREATE FUNCTION mTopCombComputed()
RETURNS @.mTopComb TABLE (
eventid int
, idap numeric -- just changed datatype according to your DDL
, Computed numeric -- just changed datatype according to your DDL
)
AS
BEGIN
INSERT
INTO @.mTopComb
SELECT j.eventid
, j.idap
, Computed = (abs(sqrt(abs((j.j1Ee+j.j2Ee + j.Ee)*(j.j1Ee+j.j2Ee +j.Ee) -
((j.j1px +j.j2px + j.px)*(j.j1px +j.j2px + j.px) +
(j.j1py +j.j2py + j.py)*(j.j1py +j.j2py + j.py) +
(j.j1pz +j.j2pz + j.pz)*(j.j1pz +j.j2pz + j.pz))))
- 174.3))
FROM topComb j
DELETE j
FROM @.mTopComb j INNER JOIN
(
SELECT eventid
, MIN(Computed) AS MinComputed
FROM @.mTopComb
GROUP BY
eventid
) t ON j.eventid = t.eventid
WHERE j.Computed <> t.MinComputed

RETURN
END
GO

ALTER VIEW leftjets
AS

SELECT DISTINCT
o.*
FROM okJets o LEFT OUTER JOIN
dbo.mTopCombComputed() c ON o.idap = c.idap
WHERE c.idap IS NULL

GO

ALTER VIEW jetVetoCut
AS

SELECT DISTINCT
e.*
FROM events e LEFT OUTER JOIN
leftjets j ON e.idevent = j.eventid
and dbo.pt(j.idap) > 70
WHERE j.eventid IS NULL

GO