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.

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