Analysis Services Error Log
Contents |
Christen - MSFTJanuary 2, 20123 0 0 0 Today's blog will cover the types of logs/data that we typically analysis services 2000 error log request when investigating Analysis Services issues. Most of these logs analysis services log file (excluding dumps) are easily readable and you can use them for your own investigation. MS support
Msmdsrv.log Location
uses a number of tools (mps reports, Support Diagnostic Platform, pssdiag, sqldiag) for automated data collection. Unfortunately these tools are not suitable for SSAS data collection
Sql Server Analysis Services Error Log
yet. This will hopefully change in the near future. Until then we are stuck with manual or semi-automated data collection. The kind of data we need to analyze will obviously depend on the nature of the problemunder investigation. In the next section I list data that will be required for almost every problem ssas logging cube processing analysis. General data:
1. msmdsrv.ini The configuration file for the SSAS instance "msmdsrv.ini" can be found in the "\config" folder of the SSAS instance. Typically something like "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config". If you are unsure about the location, then have a look at the properties of the SSAS service under "services.msc". The "path to executable" field will have the config file folder as "-s" startup parameter: f.i. "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\bin\msmdsrv.exe" -s "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config" "msmdsrv.ini"contains the server properties in XML format. You should not edit it unless MS support asks you to do so. And even then do it very carefully. The supported interface for changinginstance properties is SQL Server Management Studio. 2. windows event logs I guess I won't have to tell you much about windows event logs. They have been around forever and you can access them via "Administrative Tools" -> "Event Viewer". SSAS error messages will appear in the appliresources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student
Ssas Query Log
Partners ISV Startups TechRewards Events Community Magazine Forums Blogs msmdsrv.log, type: 3, category: 256, event id: 0xc1000016 Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The ssas log user activity content you requested has been removed. You’ll be auto redirected in 1 second. SQL Server 2016 Technical Documentation SQL Server Installation SQL Server https://blogs.msdn.microsoft.com/as_emea/2012/01/02/data-collection-for-troubleshooting-analysis-services-issues/ Setup User Interface Reference SQL Server Setup User Interface Reference Analysis Services Configuration - Data Directories Analysis Services Configuration - Data Directories Analysis Services Configuration - Data Directories Complete Image Rules Cluster Security Policy Cluster Resource Group Cluster Node Configuration (Complete) Cluster Node Configuration Cluster Network Configuration https://msdn.microsoft.com/en-us/library/cc281997.aspx Cluster Disk Selection Analysis Services Configuration - Data Directories Analysis Services Configuration - Account Provisioning Add SQL Server Failover Cluster Node Accept License Terms Verify Uninstall Options Feature Rules (Upgrade) Upgrade Progress Uninstallation rules Install Rules Ready to Upgrade SQL Server Failover Cluster Wizard - Prepare SQL Server Failover Cluster Wizard - Install SQL Server Failover Cluster Wizard - Complete Setup Role Server Configuration - Service Accounts Server Configuration - Collation Select a Prepared Instance Reporting Services SharePoint Mode Authentication Reporting Services SharePoint Mode Upgrade Reporting Services Configuration Options Repair Progress Remove SQL Server Failover Cluster Node Ready to Repair Ready to Prepare Image Ready to Install Ready to Complete Image Progress (Uninstall) Product Key Prepare Image Rules Prepare Image Type Prepare Image Progress Post Uninstall Select Instance Instance Selection (Upgrade) Instance Selection (Uninstall) Instance Configuration Installation Ty
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business http://dba.stackexchange.com/questions/82624/huge-analysis-services-log-file-msmdsrv-log Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise analysis services to the top Huge Analysis Services log file: msmdsrv.log up vote 2 down vote favorite I've just discovered our prod analysis services is writing to a log that is 1.6 GB in size. I was able to get a copy of the log file saved off to an alternate location and open it in WordPad (Notepad, Word, etc.. said the file was too large). It appears this log has been churning along for almost 4 years without analysis services error a problem. But now the problem is that it is too big. The msmdsrv.ini file doesn't appear to have a setting for rolling over the log or limiting it's size. What is the best approach to preventing this from happening in the future? How do you properly manage your Analysis Services log file? sql-server-2008-r2 ssas share|improve this question asked Nov 13 '14 at 21:46 Geoff Dawdy 3921422 On unix/linux we normally use logrotate. I am sure there are ports for windows environment. I think that could help you. –Raj Jan 12 '15 at 17:07 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted +50 You can't recycle the SSAS log in a similar manner to SQL Server. You need to do this manually by building a script and then scheduling it to run either inside of SQL Agent or Windows Task Scheduler. Here is a sample Powershell script you can use: [Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") #Get a list of installed SSAS instances on this server that are running #We need a service to be started in order to rename the log file $SSASServices = Get-WmiObject -query "select * from win32_service where DisplayName LIKE 'SQL Server Analysis%' and State = 'Running'" #for each installed instance, update the logfile name ForEach ($sname in $SSASServices) { # Connect to the SSAS server $SSASServer = New