My AS2005 (SP1) server ran out of drive space. To get drive space back, I
found a ton of cube files that weren't used by a cube anymore and hadn't been
updated in months. Now, everytime I start the analysis server, my log fills
with these errors:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 18
Date: 10/10/2006
Time: 11:49:12 AM
User: N/A
Computer: OVNCSQL01
Description:
Errors in the metadata manager. An error occurred when instantiating a
metadata object from the file, '\\?\E:\Program Files\Microsoft SQL
Server\MSSQL.2\OLAP\Data\ModelData.3.db\BPO DIAL CUBE.12987.dim.xml'.

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

Is there anyway I can delete references to these files?

I am also getting these errors too, and this file exists:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 11
Date: 10/10/2006
Time: 3:36:32 PM
User: N/A
Computer: OVNCSQL01
Description:
An error occurred while writing a trace event to the file, \\?\E:\Program
Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\FlightRecorderCurrent.trc.

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

Thanks,
SI

Hello,

I understand that you encountered errors 289 when starting AS 2005. The
second error occurs though the file referenced does exist in the folder. If
I'm off-base, please let's know.

The first error shall be related to a dimension in the database ModelData
and the metadata of the database might be in a inconsistent or corrupted
status. If it is possible, you may want to re-deploy the database from VS
2005 to AS again to fix the problem. As I know, the xml file is usually
referenced in ModelData.x.cub.xml. However, manually editing the files are
not supported and recommended.

If you want to re-deploy the database, you may want to first temporarily
back up the folder MSSQL.2\OLAP\Data\ModelData.3.db and
MSSQL.2\OLAP\Data\ModelData.3.db.xml. You may want to remove the
files/folder and then try to start AS 2005 again so that you could
re-deploy the database.

As for the second event, it may or may not relate to the first event.
However, to find the cause of the issue, we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. If the issue is urgent, I recommend that you open a
Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp


Also, for second event, it usually relates to memory issue on the server,
and you may want to see if there is memory pressure on the server.
FlightRecorderCurrent.trc. is trace enabled by the server property
FlightRecorder - Enabled. You may want to temporarily disable it management
studio of perperties page of AS server if the issue persists:

http://www.microsoft.com/technet/pro...roperties.mspx

Propety Name: General Page: Log\FlightRecorder

The concept of flight recorder trace is similar to “black box” recorders
used to record in-flight activity of an airplane. Flight Recorder trace,
when enabled, is constantly recording Analysis Server activity into a short
term log, enabling SSAS administrators to troubleshoot problems. The
Flight Recorder is logging activity into a FlightRecCurrent.trc file, which
is located under the folder specified by the LogDir server property. After
the amount of time specified by the FlightRecorder - LogDurationSec server
property is passed, or whenever FlightRecCurrent.trc is reaching the size
limit specified by the FlightRecorder - FileSizeMB server property, the
FlightRecCurrent.trc file is renamed to FlightRecBack.trc and a new
FlightRecCurrent.trc file is created. At the same moment, the old copy of
FlightRecBack.trc is deleted. You can open FlightRecCurrent.trc or
FlightRecBack.trc using the SQL Server Profiler application. You can also
try and replay events captured by the flight recorder using the replay
functionality of SQL Server Profiler. One of the problems administrators
will encounter when investigating a Flight Recorder trace is that some
trace events will be associated with sessions and
connections started before Analysis Server began logging into the current
FlightRecCurrent.trc or FlightRecBack.trc.

If you have further questions or concerns on the issue, please feel free to
let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,

I'm still interested in this issue. If you have any comments or questions,
please feel free to let's know. We look forward to hearing from you. :-)

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Hi Peter,
After going through the company I found no one used the data provided by the
cube anymore. I deleted the cube, and both issues seemed to have gone away.
I'm guessing if I republished the cube the errors would have stayed away.

Thanks,
-SI

"Peter Yang [MSFT]" wrote:

Hi,

Thank you for taking time to write in about your experience on the issue
and this shall benefit the community. Sometimes rebuilding or deleting the
problemtic cube under the sitution is the most efficient method to fix the
problem :-)

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===


This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====