Welcome to Sql Developer's world

Could not initiate the EventLog Service for the key 'MSSQLSERVER', last error code is 5. Startup error: Unable to initialize error reporting system (reason: 5) in cluster

kagana — Tue, 25 Oct 2011 06:05:00 GMT

Hi everyone, I have come across following issue and wanted to share resolution with you.

When you install Sql Server 2008 on to windows 2008 cluster, sql server agent might fail with following error message and resource may not become online.

SQL Agent:

2011-10-25 11:44:48 - ! [241] Startup error: Unable to initialize error reporting system (reason: 5)

2011-10-25 11:44:48 - ? [098] SQLServerAgent terminated (normally)

You may get similar error message in Sql Server Error logs as well.

SQL Server:

2011-10-25 10:49:48.31 Server Error: 17156, Severity: 16, State: 1.

2011-10-25 10:49:48.31 Server initeventlog: Could not initiate the EventLog Service for the key 'MSSQLSERVER', last error code is 5.

2011-10-25 10:49:48.31 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)

Apr 2 2010 15:48:46

Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

It seems issue is more related about access problem to security event log.

when I execute Wevtutil on failing machine and compare it with working machine:

Failing Machine:

C:\Users\!hardinb1>Wevtutil gl application

name: application

enabled: true

type: Admin

owningPublisher:

isolation: Application

channelAccess: O:BAG:SYD:(D;;0xf0007;;;AN)(D;;0xf0007;;;BG)(A;;0xf0005;;;SY)(A;;

0x5;;;BA)(A;;0x1;;;S-1-5-21-2680824871-1255999119-832436803-429284)

logging:

logFileName: %SystemRoot%\System32\Winevt\Logs\application.evtx

retention: false

autoBackup: false

maxSize: 52428800

publishing:

fileMax: 1

“Wevtutil gl application”

On working machine:

name: application

enabled: true

type: Admin

owningPublisher:

isolation: Application

channelAccess: O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)

logging:

logFileName: %SystemRoot%\System32\Winevt\Logs\application.evtx

retention: false

autoBackup: false

maxSize: 52428800

publishing:

fileMax: 1

They are different, so on failing machine, I have executed following command to roll back permission to original state:

wevtutil sl application /ca:O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)

Then tried to bring sql server agent online and it worked! One thing you need to remember, if these settings were overwritten by policies, you will get same error on next reboot! Please check with your AD team for policy comparison.

If you have any questions, please contact me.

Thanks

Kagan

SSAS Performance Monitor Counters

kagana — Sat, 05 Mar 2011 02:03:46 GMT

Just want to share a frequently asked question about SSAS perf counters. About key counters, here is list below:

Performance Object	Counter
Logical Disk	All/All
Process	Private Bytes – msmdsrv.exe
MSAS:Memory	Memory Usage Kb
MSAS:Threads	All
Memory	Cache Bytes
Memory	Standby Cache Normal Priority Bytes
Memory	Hard Page Faults/ sec
Memory	Page Reads/sec
Memory	Available Bytes
MSAS:Proc Aggregations	Temp File Bytes Written
MSAS:Processing	All Counters
MSAS: MDX	All Counters

Also you can find full list of counters below:

Object	Counter	Description
MSAS 2008:Cache	Current KB	Current memory used by the aggregation cache, in KB.
MSAS 2008:Cache	KB added/sec	Rate of memory added to the cache, KB/sec.
MSAS 2008:Cache	Current entries	Current number of cache entries.
MSAS 2008:Cache	Inserts/sec	Rate of insertions into the cache. This is per partition per cube per database.
MSAS 2008:Cache	Evictions/sec	Rate of evictions from the cache. This is per partition per cube per database. Typically due to background cleaner.
MSAS 2008:Cache	Total inserts	Insertions into the cache. This is per partition per cube per database.
MSAS 2008:Cache	Total evictions	Evictions from the cache. This is per partition per cube per database. Typically due to background cleaner.
MSAS 2008:Cache	Direct hits/sec	Rate of cache direct hits. Queries were answered from an existing cache entry.
MSAS 2008:Cache	Misses/sec	Rate of cache misses.
MSAS 2008:Cache	Lookups/sec	Rate of cache lookups.
MSAS 2008:Cache	Total direct hits	Total count of direct cache hits. Queries were answered from existing cache entries.
MSAS 2008:Cache	Total misses	Total count of cache misses.
MSAS 2008:Cache	Total lookups	Total number of lookups into the cache.
MSAS 2008:Cache	Direct hit ratio	Ratio of cache direct hits to cache lookups, for the period between obtaining counter values.
MSAS 2008:Cache	Total filtered iterator cache hits	Total number of cache hits that returned an indexed iterator over the filtered results
MSAS 2008:Cache	Total filtered iterator cache misses	Total number of cache hits that were unable to build an indexed iterator over the filtered results and had to build a new cache with the filtered results
MSAS 2008:Connection	Current connections	Current number of client connections established.
MSAS 2008:Connection	Requests/sec	Rate of connection requests. These are arrivals.
MSAS 2008:Connection	Total requests	Total connection requests. These are arrivals.
MSAS 2008:Connection	Successes/sec	Rate of successful connection completions.
MSAS 2008:Connection	Total successes	Total successful connections.
MSAS 2008:Connection	Failures/sec	Rate of connection failures.
MSAS 2008:Connection	Total failures	Total failed connection attempts.
MSAS 2008:Connection	Current user sessions	Current number of user sessions established.
MSAS 2008:Data Mining Model Processing	Cases/sec	Rate of processing cases.
MSAS 2008:Data Mining Model Processing	Current models processing	Current number of models being processed
MSAS 2008:Data Mining Prediction	Predictions/sec	Rate of Data Mining prediction queries
MSAS 2008:Data Mining Prediction	Rows/sec	Rate of predicting rows
MSAS 2008:Data Mining Prediction	Concurrent DM queries	Current number of Data Mining queries being actively worked on.
MSAS 2008:Data Mining Prediction	Queries/sec	Rate of Data Mining queries
MSAS 2008:Data Mining Prediction	Total Queries	Total Data Mining Queries received by the server
MSAS 2008:Data Mining Prediction	Total Rows	Total Rows returned by Data Mining queries
MSAS 2008:Data Mining Prediction	Total Predictions	Total Data Mining Prediction Queries received by the server
MSAS 2008:Locks	Current latch waits	Current number of threads waiting for a latch. These are latch requests that could not be given immediate grants and are in a wait state.
MSAS 2008:Locks	Latch waits/sec	Rate of latch requests that could not be granted immediately and had to wait before being granted.
MSAS 2008:Locks	Current locks	Current number of locked objects.
MSAS 2008:Locks	Current lock waits	Current number of clients waiting for a lock.
MSAS 2008:Locks	Lock requests/sec	Number of lock requests per second.
MSAS 2008:Locks	Unlock requests/sec	Number of unlock requests per second.
MSAS 2008:Locks	Lock grants/sec	Number of lock grants per second.
MSAS 2008:Locks	Lock denials/sec	Rate of lock denials.
MSAS 2008:Locks	Lock waits/sec	Number of lock waits per second. These are lock requests that could not be given immediate lock grants and were put in a wait state.
MSAS 2008:Locks	Total deadlocks detected	Total number of deadlocks detected.
MSAS 2008:MDX	Number of calculation covers	Total number of evaluation nodes built by MDX execution plans including active and cached
MSAS 2008:MDX	Current number of evaluation nodes	Current (approximate) number of evaluation nodes built by MDX execution plans including active and cached
MSAS 2008:MDX	Number of Storage Engine evaluation nodes	Total number of Storage Engine evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of cell-by-cell evaluation nodes	Total number of cell-by-cell evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of bulk-mode evaluation nodes	Total number of bulk-mode evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of evaluation nodes that covered a single cell	Total number of evaluation nodes built by MDX execution plans that covered only one cell
MSAS 2008:MDX	Number of evaluation nodes with calculations at the same granularity	Total number of evaluation nodes built by MDX execution plans for which the calculations were at the same granularity as the evaluation node
MSAS 2008:MDX	Current number of cached evaluation nodes	Current (approximate) number of cached evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of cached Storage Engine evaluation nodes	Total number of cached Storage Engine evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of cached bulk-mode evaluation nodes	Total number of cached bulk-mode evaluation nodes built by MDX execution plans
MSAS 2008:MDX	Number of cached 'other' evaluation nodes	Total number of cached evaluation nodes built by MDX execution plans that are neither Storage Engine nor Bulk-mode
MSAS 2008:MDX	Number of evictions of evaluation nodes	Total number of cache evictions of evaluation nodes due to collisions
MSAS 2008:MDX	Number of hash index hits in the cache of evaluation nodes	Total number of hits in the cache of evaluation nodes that were satisfied by the hash index
MSAS 2008:MDX	Number of cell-by-cell hits in the cache of evaluation nodes	Total number of cell-by-cell hits in the cache of evaluation nodes
MSAS 2008:MDX	Number of cell-by-cell misses in the cache of evaluation nodes	Total number of cell-by-cell misses in the cache of evaluation nodes
MSAS 2008:MDX	Number of subcube hits in the cache of evaluation nodes	Total number of subcube hits in the cache of evaluation nodes
MSAS 2008:MDX	Number of subcube misses in the cache of evaluation nodes	Total number of subcube misses in the cache of evaluation nodes
MSAS 2008:MDX	Total Sonar subcubes	Total number of subcubes that query optimizer generated
MSAS 2008:MDX	Total cells calculated	Total number of cell properties calculated
MSAS 2008:MDX	Total recomputes	Total number of cells recomputed due to error
MSAS 2008:MDX	Total flat cache inserts	Total number of cell values inserted into flat calculation cache
MSAS 2008:MDX	Total NON EMPTY	Total number of times NON EMPTY algorithms is used
MSAS 2008:MDX	Total NON EMPTY for calculated members	Total number of times NON EMPTY algorithm was looping over calculated members
MSAS 2008:MDX	Total NON EMPTY unoptimized	Total number of times unoptimized NON EMPTY algorithm is used
MSAS 2008:MDX	Total Autoexist	Total number of times autoexist performed
MSAS 2008:MDX	Total EXISTING	Total number of times EXISTING set operator performed
MSAS 2008:Memory	Page Pool 64 Alloc KB	Memory borrowed from system, in KB. This memory is given away to other parts of the server.
MSAS 2008:Memory	Page Pool 64 Lookaside KB	Current memory in 64KB lookaside list, in KB. (Memory pages ready to be used.)
MSAS 2008:Memory	Page Pool 8 Alloc KB	Memory borrowed from 64KB page pool, in KB. This memory is given away to other parts of the server.
MSAS 2008:Memory	Page Pool 8 Lookaside KB	Current memory in 8KB lookaside list, in KB. (Memory pages ready to be used.)
MSAS 2008:Memory	Page Pool 1 Alloc KB	Memory borrowed from 64KB page pool, in KB. This memory is given away to other parts of the server.
MSAS 2008:Memory	Page Pool 1 Lookaside KB	Current memory in 8KB lookaside list, in KB. (Memory pages ready to be used.)
MSAS 2008:Memory	Cleaner Current Price	Current price of memory, $/byte/time, normalized to 1000.
MSAS 2008:Memory	Cleaner Balance/sec	Rate of balance+shrink operations.
MSAS 2008:Memory	Cleaner Memory shrunk KB/sec	Rate of shrinking, in KB/sec.
MSAS 2008:Memory	Cleaner Memory shrinkable KB	Amount of memory, in KB, subject to purging by the background cleaner.
MSAS 2008:Memory	Cleaner Memory nonshrinkable KB	Amount of memory, in KB, not subject to purging by the background cleaner.
MSAS 2008:Memory	Cleaner Memory KB	Amount of memory, in KB, known to the background cleaner. (Cleaner memory shrinkable + Cleaner memory nonshrinkable.)
MSAS 2008:Memory	Memory Usage KB	Memory usage of the server process. Same as perfmon counter for Process\PrivateBytes.
MSAS 2008:Memory	Memory Limit Low KB	Low memory limit, from configuration file.
MSAS 2008:Memory	Memory Limit High KB	High memory limit, from configuration file.
MSAS 2008:Memory	AggCacheKB	Current memory allocated to aggregation cache, in KB.
MSAS 2008:Memory	Quota KB	Current memory quota, in KB. Memory quota is also known as a memory grant or memory reservation.
MSAS 2008:Memory	Quota Blocked	Current number of quota requests that are blocked until other memory quotas are freed.
MSAS 2008:Memory	Filestore KB	Current memory allocated to filestore (file cache), in KB.
MSAS 2008:Memory	Filestore Page Faults/sec	Filestore page fault rate.
MSAS 2008:Memory	Filestore Reads/sec	Filestore pages read/sec.
MSAS 2008:Memory	Filestore KB Reads/sec	Filestore KB read/sec.
MSAS 2008:Memory	Filestore Writes/sec	Filestore pages written/sec. The writes are asynchronous.
MSAS 2008:Memory	Filestore KB Write/sec	Filestore KB written/sec. The writes are asynchronous.
MSAS 2008:Memory	Filestore IO Errors/sec	Filestore IO Error rate.
MSAS 2008:Memory	Filestore IO Errors	Filestore IO Errors total.
MSAS 2008:Memory	Filestore Clock Pages Examined/sec	Rate of background cleaner examining pages for eviction consideration.
MSAS 2008:Memory	Filestore Clock Pages HaveRef/sec	Rate of background cleaner examining pages that have a current reference count (are currently in use).
MSAS 2008:Memory	Filestore Clock Pages Valid/sec	Rate of background cleaner examining pages that are valid candidates for eviction.
MSAS 2008:Memory	Filestore Memory Pinned KB	Current filestore memory pinned KB.
MSAS 2008:Memory	In-memory Dimension Property File KB	Current in-memory dimension property file KB.
MSAS 2008:Memory	In-memory Dimension Property File KB/sec	In-memory dimension property file KB rate.
MSAS 2008:Memory	Potential In-memory Dimension Property File KB	Potential in-memory dimension property file KB.
MSAS 2008:Memory	Dimension Property Files	Number of dimension property files.
MSAS 2008:Memory	In-memory Dimension Index (Hash) File KB	Current in-memory dimension index (hash) file KB.
MSAS 2008:Memory	In-memory Dimension Index (Hash) File KB/sec	In-memory dimension index (hash) file KB rate.
MSAS 2008:Memory	Potential In-memory Dimension Index (Hash) File KB	Potential in-memory dimension index (hash) file KB.
MSAS 2008:Memory	Dimension Index (Hash) Files	Number of dimension index (hash) files.
MSAS 2008:Memory	In-memory Dimension String File KB	Current in-memory dimension string file KB.
MSAS 2008:Memory	In-memory Dimension String File KB/sec	In-memory dimension string file KB rate.
MSAS 2008:Memory	Potential In-memory Dimension String File KB	Potential in-memory dimension string file KB.
MSAS 2008:Memory	Dimension String Files	Number of dimension string files.
MSAS 2008:Memory	In-memory Map File KB	Current in-memory map file KB.
MSAS 2008:Memory	In-memory Map File KB/sec	In-memory map file KB rate.
MSAS 2008:Memory	Potential In-memory Map File KB	Potential in-memory map file KB.
MSAS 2008:Memory	Map Files	Number of map files.
MSAS 2008:Memory	In-memory Aggregation Map File KB	Current in-memory aggregation map file KB.
MSAS 2008:Memory	In-memory Aggregation Map File KB/sec	In-memory aggregation map file KB rate.
MSAS 2008:Memory	Potential In-memory Aggregation Map File KB	Potential in-memory aggregation map file KB.
MSAS 2008:Memory	Aggregation Map Files	Number of aggregation map files.
MSAS 2008:Memory	In-memory Fact Data File KB	Current in-memory fact data file KB.
MSAS 2008:Memory	In-memory Fact Data File KB/sec	In-memory fact data file KB rate.
MSAS 2008:Memory	Potential In-memory Fact Data File KB	Potential in-memory fact data file KB.
MSAS 2008:Memory	Fact Data Files	Number of fact data files.
MSAS 2008:Memory	In-memory Fact String File KB	Current in-memory fact string file KB.
MSAS 2008:Memory	In-memory Fact String File KB/sec	In-memory fact string file KB rate.
MSAS 2008:Memory	Potential In-memory Fact String File KB	Potential in-memory fact string file KB.
MSAS 2008:Memory	Fact String Files	Number of fact string files.
MSAS 2008:Memory	In-memory Fact Aggregation File KB	Current in-memory fact aggregation file KB.
MSAS 2008:Memory	In-memory Fact Aggregation File KB/sec	In-memory fact aggregation file KB rate.
MSAS 2008:Memory	Potential In-memory Fact Aggregation File KB	Potential in-memory fact aggregation file KB.
MSAS 2008:Memory	Fact Aggregation Files	Number of fact aggregation files.
MSAS 2008:Memory	In-memory Other File KB	Current in-memory other file KB.
MSAS 2008:Memory	In-memory Other File KB/sec	In-memory other file KB rate.
MSAS 2008:Memory	Potential In-memory Other File KB	Potential in-memory other file KB.
MSAS 2008:Memory	Other Files	Number of other files.
MSAS 2008:Proactive Caching	Notifications/sec	Rate of notifications from relational database.
MSAS 2008:Proactive Caching	Processing Cancellations/sec	Rate of processing cancellations caused by notifications.
MSAS 2008:Proactive Caching	Proactive Caching Begin/sec	Rate of proactive caching begin.
MSAS 2008:Proactive Caching	Proactive Caching Completion/sec	Rate of proactive caching completion.
MSAS 2008:Proc Aggregations	Current partitions	Current number of partitions being processed.
MSAS 2008:Proc Aggregations	Total partitions	Total number of partitions processed (successfully or otherwise).
MSAS 2008:Proc Aggregations	Memory size rows	Size of current aggregations in memory. This count is an estimate.
MSAS 2008:Proc Aggregations	Memory size bytes	Size of current aggregations in memory. This count is an estimate.
MSAS 2008:Proc Aggregations	Rows merged/sec	Rate of rows merged or inserted into an aggregation.
MSAS 2008:Proc Aggregations	Rows created/sec	Rate of aggregation rows created.
MSAS 2008:Proc Aggregations	Temp file rows written/sec	Rate of writing rows to a temporary file. Temporary files are written when aggregations exceed memory limits.
MSAS 2008:Proc Aggregations	Temp file bytes written/sec	Rate of writing bytes to a temporary file. Temporary files are written when aggregations exceed memory limits.
MSAS 2008:Proc Indexes	Current partitions	Current number of partitions being processed.
MSAS 2008:Proc Indexes	Total partitions	Total number of partitions processed (successfully or otherwise).
MSAS 2008:Proc Indexes	Rows/sec	Rate of rows from MOLAP files used to create indexes.
MSAS 2008:Proc Indexes	Total rows	Total rows from MOLAP files used to create indexes.
MSAS 2008:Processing	Rows read/sec	Rate of rows read from all relational databases.
MSAS 2008:Processing	Total rows read	Count of rows read from all relational databases.
MSAS 2008:Processing	Rows converted/sec	Rate of rows converted during processing.
MSAS 2008:Processing	Total rows converted	Count of rows converted during processing.
MSAS 2008:Processing	Rows written/sec	Rate of rows written during processing.
MSAS 2008:Processing	Total rows written	Count of rows written during processing.
MSAS 2008:Storage Engine Query	Current measure group queries	Current number of measure group queries being actively worked on.
MSAS 2008:Storage Engine Query	Measure group queries/sec	Rate of measure group queries
MSAS 2008:Storage Engine Query	Total measure group queries	Total number of queries to measure group.
MSAS 2008:Storage Engine Query	Current dimension queries	Current number of dimension queries being actively worked on.
MSAS 2008:Storage Engine Query	Dimension queries/sec	Rate of dimension queries
MSAS 2008:Storage Engine Query	Total dimension queries.	Total number of dimension queries.
MSAS 2008:Storage Engine Query	Queries answered/sec	Rate of queries answered.
MSAS 2008:Storage Engine Query	Total queries answered	Total number of queries answered.
MSAS 2008:Storage Engine Query	Bytes sent/sec	Rate of bytes sent by server to clients, in response to queries.
MSAS 2008:Storage Engine Query	Total bytes sent	Total bytes sent by server to clients, in response to queries.
MSAS 2008:Storage Engine Query	Rows sent/sec	Rate of rows sent by server to clients.
MSAS 2008:Storage Engine Query	Total rows sent	Total rows sent by server to clients.
MSAS 2008:Storage Engine Query	Queries from cache direct/sec	Rate of queries answered from cache directly.
MSAS 2008:Storage Engine Query	Queries from cache filtered/sec	Rate of queries answered by filtering existing cache entry.
MSAS 2008:Storage Engine Query	Queries from file/sec	Rate of queries answered from files.
MSAS 2008:Storage Engine Query	Total queries from cache direct	Total number of queries derived directly from cache. Note that this is per partition.
MSAS 2008:Storage Engine Query	Total queries from cache filtered	Total queries answered by filtering existing cache entries.
MSAS 2008:Storage Engine Query	Total queries from file	Total number of queries answered from files.
MSAS 2008:Storage Engine Query	Map reads/sec	Number of logical read operations using the Map file.
MSAS 2008:Storage Engine Query	Map bytes/sec	Bytes read from the Map file.
MSAS 2008:Storage Engine Query	Data reads/sec	Number of logical read operations using the Data file.
MSAS 2008:Storage Engine Query	Data bytes/sec	Bytes read from the Data file.
MSAS 2008:Storage Engine Query	Avg time/query	Average time per query, in milliseconds. Response time based on queries answered since the last counter measurement.
MSAS 2008:Storage Engine Query	Network round trips/sec	Rate of network round trips. This includes all client/server communication.
MSAS 2008:Storage Engine Query	Total network round trips	Total network round trips. This includes all client/server communication.
MSAS 2008:Storage Engine Query	Flat cache lookups/sec	Rate of flat cache lookups. This includes global, session, and query scope flat caches.
MSAS 2008:Storage Engine Query	Flat cache hits/sec	Rate of flat cache hits. This includes global, session, and query scope flat caches.
MSAS 2008:Storage Engine Query	Calculation cache lookups/sec	Rate of calculation cache lookups. This includes global, session, and query scope calculation caches.
MSAS 2008:Storage Engine Query	Calculation cache hits/sec	Rate of calculation cache hits. This includes global, session, and query scope calculation caches.
MSAS 2008:Storage Engine Query	Persisted cache lookups/sec	Rate of persisted cache lookups. Persisted caches are created by the MDX script CACHE statement.
MSAS 2008:Storage Engine Query	Persisted cache hits/sec	Rate of persisted cache hits. Persisted caches are created by the MDX script CACHE statement.
MSAS 2008:Storage Engine Query	Dimension cache lookups/sec	Rate of dimension cache lookups.
MSAS 2008:Storage Engine Query	Dimension cache hits/sec	Rate of dimension cache hits.
MSAS 2008:Storage Engine Query	Measure group cache lookups/sec	Rate of measure group cache lookups.
MSAS 2008:Storage Engine Query	Measure group cache hits/sec	Rate of measure group cache hits.
MSAS 2008:Storage Engine Query	Aggregation lookups/sec	Rate of aggregation lookups.
MSAS 2008:Storage Engine Query	Aggregation hits/sec	Rate of aggregation hits.
MSAS 2008:Threads	Short parsing idle threads	Number of idle threads in the short parsing thread pool.
MSAS 2008:Threads	Short parsing busy threads	Number of busy threads in the short parsing thread pool.
MSAS 2008:Threads	Short parsing job queue length	Number of jobs in the queue of the short parsing thread pool.
MSAS 2008:Threads	Short parsing job rate	Rate of jobs through the short parsing thread pool.
MSAS 2008:Threads	Long parsing idle threads	Number of idle threads in the long parsing thread pool.
MSAS 2008:Threads	Long parsing busy threads	Number of busy threads in the long parsing thread pool.
MSAS 2008:Threads	Long parsing job queue length	Number of jobs in the queue of the long parsing thread pool.
MSAS 2008:Threads	Long parsing job rate	Rate of jobs through the long parsing thread pool.
MSAS 2008:Threads	Query pool idle threads	Number of idle threads in the query thread pool.
MSAS 2008:Threads	Query pool busy threads	Number of busy threads in the query thread pool.
MSAS 2008:Threads	Query pool job queue length	Number of jobs in the queue of the query thread pool.
MSAS 2008:Threads	Query pool job rate	Rate of jobs through the query thread pool.
MSAS 2008:Threads	Processing pool idle threads	Number of idle threads in the processing thread pool.
MSAS 2008:Threads	Processing pool busy threads	Number of busy threads in the processing thread pool.
MSAS 2008:Threads	Processing pool job queue length	Number of jobs in the queue of the processing thread pool.
MSAS 2008:Threads	Processing pool job rate	Rate of jobs through the processing thread pool.

How to cancel long running queries in Analysis Services 2005

kagana — Tue, 18 Jan 2011 04:19:42 GMT

Here are steps to kill spid.

1-Open management Studio.

2-Connect AS instance

3-Choose XMLA command (shown below)

4-Execute following xmla command to find out spids

DISCOVER_SESSIONS

5-Output will be similar to following:

6-Copy SPID number and run following XMLA command (Change your spid number to your own spid number):

https://schemas.microsoft.com/analysisservices/2003/engine">

28147

How to Configure HTTP Access to SQL Server 2008 Analysis Services on IIS7

kagana — Tue, 18 Jan 2011 04:18:25 GMT

Client applications communicate with Analysis Services using XML for Analysis (XMLA) over TCP/IP or HTTP. Analysis Services provides an XMLA listener component that handles all XMLA communications between Analysis Services and its clients. The Analysis Services Session Manager controls how clients connect to an Analysis Services instance.

AS uses IIS as middleware component to enable access to data via HTTP. Communication between client and server is as follows:

1-Client sends an HTTP post request to IIS using the IIS servername and path to service component (msmdpump.dll) as url.

2-IIS receives the request, authenticates the sender, and creates a security context in which the in the pump will be executed.

3-IIS starts pump and uses ISAPI to communicate with pump.

4-The pump connects to AS via TCP/IP and sends data received from client without any change, 5-AS executes the request and sends response to pump which passes response to client.

If you run SSAS and IIS on separate box, you should pay attention to user credential delegation since OS doesn’t allow delegation as default. If you want to run IIS and SSAS on separate box, you need to configure Kerberos authentication.

You can still compress content of request and response in binary similar to TCP/IP protocol.

The default instance of Analysis Services uses port 2383, but that can be changed. Named instances of Analysis Services use dynamic ports. For more information about how to configure for the use of a specific port, see How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager). If you are running a default instance of Analysis Services only, using the SQL Server Browser service is optional. To use SQL Server Browser, you must open TCP port 2382.You must configure Windows Firewall to enable access to the relevant port for authorized users or computers, including configuring Analysis Services to use a specific TCP/IP port..

https://msdn.microsoft.com/en-us/library/ms174937.aspx

The Port server property for an instance of Analysis Services determines the port number on which the instance listens for client connections. The Port property has a default value of 0. This means that the instance uses the default port, 2383. An Analysis Services administrator can change the default port value to a specific port number or can leave the default value as is. If set to the default value, the instance tries to use the default port, 2383

https://msdn.microsoft.com/en-us/library/ms174906.aspx

Start->Run->Type IIS (if IIS is not installed, you can install it,

- Open Add or Remove Programs in Control Panel,

- Select Add/Remove Windows Components.

-Then add IIS to Windows)

-On IIS, click Application Pools -> Right Click-> Add New Application Pool and change it like below:

-Create folder called OLAP under C:\Inetpub\wwwRoot

-Copy two files (msmdpump.dll, msmdpump.ini) under installation isapi folder \Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\bin\isapi and paste them to C:\Inetpub\wwwRoot\OLAP folder.

-Go to IIS and Click OLAP folder under Default Web Site -> Right Click->Convert to Application-> then Click OK.

-Go to Handler Mappings option

Click Open Feature then Edit Feature Permission and make sure the directoy has Read and Script Permission.

In the top right coner of the Handler Mappings screen, click “Add Script Map…”

And add following information.

Then Click OK and when you click OK, you will get following warning message:

Then Click Yes.

After that, On IIS, click Server Name and go to ISAPI and CGI Restrictions under security

and change your extension description to OLAP like below:

Next step is to configure security.

Click OLAP virtual directory and select Authentication from menu.

Choose your authentication type you want to use.

Anonymous access

When this mode is selected, Pump (msmdpump.dll) is running with credentials; in our case, the credentials of IUSR_MACHINENAME user. Therefore, every connection to Analysis Services is opened as IUSR_MACHINENAME user. When this mode is selected, there is no distinction between users who are connecting to IIS and those who are connecting to Analysis Services. There is no way to distinguish between users.

This mode is to be used when the security infrastructure does not take advantage of the security functionality of Analysis Services. This is most likely an extremely controlled environment, where users are given or denied access to the virtual directory.

Basic authentication

This mode requires that the user enter a user name and password. The user name and password are transmitted over the HTTP connection to IIS. IIS will try to impersonate the user using the provided credentials.

Please note that it is absolutely imperative for anyone building a system where the password is transmitted to have ways of securing the communication channel. IIS provides a great set of tools for setting up and requiring that all communications be encrypted using HTTPS protocol.

The steps required for setting up HTTPS for a virtual directory are described later in this paper.

Integrated Windows authentication

This is the most secure and the recommended mode.

It requires that IIS Server be able to access user domain credentials. This could be done using Microsoft Active Directory® or another mechanism. It is beyond the scope of this paper to discuss in depth all the possible configurations.

Let’s open the msmdpump.ini file located in your folder and take a look at the contents of this file. It should have following in it:

localhost

3600

100

The only setting you are interested in at this point is .

If the Analysis Services instance that you need to provide access to is located on the local machine and installed as a default instance, there is no reason to change this setting. Otherwise, you need to specify the machine name and instance name ( mymachine\inst1).

It is also possible to specify a pointer to the virtual directory on another IIS server that is set up for HTTP access to Analysis Services.

For example you can have https://secondmachine/olap/msmdpump.dll

You can connect your Analysis Services instance with following syntax from you clients:

Also you can find steps for SSAS 2005 below:

https://technet.microsoft.com/hi-in/library/cc917712(en-us).aspx

As conclusion, we have three ports involved here:

1- http port : port 80 for clients to access IIS

2-SSAS port: 2383 is default port for SSAS

3-Browser port: 2382 UDP for SQL Browser Service

Analysis Services 2005 Log File (msmdsrv.log) Readability

kagana — Sun, 11 Jul 2010 06:13:41 GMT

Question:You may want to know why msmdsrv.log file is not easy readable and includes extra spaces between each characters in log file?

Answer:This happen because the SSAS 2005 RTM version run first and create the Unicode file without the correct header.This issue was fixed later (SSAS 2005 SP1). If you would like to start a clean file, stop SSAS and delete the file.A new correct one will be created as SSAs starts.

I hope this helps.

Kagan Arca

Defragmentation Best Practices for Analysis Services

kagana — Sun, 11 Jul 2010 06:08:59 GMT

One of my customer asked about best practice for Analysis Services about defragmentation. Answer is, yes we recommend defragmentation if you see fragmentation when using analysis services or after processing. There isn’t really anything special for AS here – like any other server system, you would want to defrag whenever the AS data files became too fragmented. The defrag tool can help you detect that, so you can just run it once a day, once a week or once a month depending on the frequency of data update and volumes of data. I would do it weekly to start with and if experimentation shows no significant fragmentation for multiple weeks in succession then I would do it less often and vice versa. If you have any questions, feel free to contact with me.

Kagan Arca

Tabular property causes different resultset to Reporting Services

kagana — Tue, 30 Mar 2010 02:30:11 GMT

I have two ways of executing same statement. In following two scenarios, both returns different result. Basically my query runs against AdventureWorks DW.

select {[Measures].[Reseller Sales Amount]} on columns,

[Geography].[Country].[All Geographies]

on rows

from [Adventure Works]

When I looked at profiler trace, When I run query from BID environment, I can see following propertly list is passed:

Adventure Works DW

2057

Tabular

SchemaData

true

However, when I run same query, I can see following parameter list is passed:

Microsoft SQL Server Management Studio - Query

2057

6904

Adventure Works DW

Native

TupleFormat

SchemaData

After working with issue a bit more detailed, I have found out that Tabular attribute in XMLA causes All Geographies Caption to disappear.

If you run following xmla script against AdventureWorks DW with format attribute and without format attribute, you will see difference.

https://schemas.xmlsoap.org/soap/envelope/">

https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">

select {[Measures].[Reseller Sales Amount]} on columns,

{[Geography].[Country].[All Geographies], [Geography].[Country].&[Australia]}

on rows

from [Adventure Works]

Adventure Works DW

I have also pasted screenshots from Management Studio and BID environment:

Management Studio:

Visual Studio Query Designer window.

Repro above was simplified for audience to make issue more clear. You can see more complex query results below:

There is a standard algorithm to flatten multi-dimensional results to a tabular result. You can find details about that below:

https://msdn.microsoft.com/en-us/library/ms709733(VS.85).aspx

If you check following link it clearly states that The "All" level of a dimension is not included in the field set that is returned to Reporting Services.

https://msdn.microsoft.com/en-us/library/aa902647(SQL.80).aspx

“Another behavior of the flattening algorithm is that the "[(ALL)]" level is not included in the dataset. This has a couple of implications. The first is that if you want to include data from the "All" member of a dimension, you'll need to create a calculated member to represent this member.”

I think this explains why we see different behaviour in both scenario.

Many Thanks

Kagan Arca

Connection Pooling for Analysis Services Datasource in Reporting Services

kagana — Tue, 23 Mar 2010 04:00:11 GMT

Problem description

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

I just wanted to write about how reporting services manages connections with Analysis Services Data Source. Reporting Services, when connecting to Analysis Services as a data source initiates a separate connection for each user and each query. Once the data is returned, the connection is closed by the Reporting Services client, so there is no connection pooling when using Analysis Services as a data source. As a principle of Reporting Services connecting to analysis Services, It opens a connection->runs query->retrieves result->Closes Connection.

I run profiler trace and saw following behaviour for every report render request.

Conclusion, Reporting Services opens new connection for each request and closes this connection at the end of request.Since Reporting Services uses ADOMD.NET and ADOMD.NET doesn’t support connection pooling

As 2005/AS 2008 /Vista/win7/win2k8/SSPI=Anonymous behaves differently

kagana — Fri, 08 Jan 2010 08:00:59 GMT

I hope that you are doing well. I have found out that when using SSPI=Anonymous keyword in connection string to connect Analysis Services which is hosted on Vista or later versions like Windows 7, Windows 2008 etc.., you get following error message:

Either the user, NT AUTHORITY\ANONYMOUS LOGON, does not have access to the test database, or the database does not exist.

Problem description

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

When you move your analysis services 2005 to windows 2008 machine. After this stage, your application (which uses anonymous logon access) may start to throw following exception.

Either the user, NT AUTHORITY\ANONYMOUS LOGON, does not have access to the test database, or the database does not exist.

Although NT AUTHORITY\ANONYMOUS LOGON account is added to roles of Database. Require Client Authentication is set to false as well. (like described in following article (https://msdn.microsoft.com/en-us/library/ms174933.aspx )

For now as a workaround, he is using http access to analysis services and I have seen that when he configures http access, it uses IUSR account (not anonymous logon account).

Work done so far:

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

Basically Here are steps to reproduce problem:

-Create UDL file and change your connection string to following ( of course your own server name and catalog name) :

Provider=MSOLAP;Persist Security Info=False;Initial Catalog=Analysis Services Project1;Data Source=win2k3sql05\sql2005;SSPI=Anonymous

-Try to connect Analysis Services 2005 instance on Windows 2008 machine ( you can try it locally as well if you think that authentication might be issue)

-Run profiler trace and you will get exactly same error message.

-If you follow same instructions AS 2005 on windows 2003 machine and you will get success result.

We have been investigating this scenario and have found that it appears that there is a new part to the windows security model for vista and windows 2008 that did not exist in windows 2003 or xp.

This is described further in this article:

https://msdn.microsoft.com/en-us/library/bb625963.aspx Windows Integrity Mechanism Design

This change is causing Analysis Services to fail to authenticate anonymous logon user

Workaround: I would suggest you to use http access and setting web site identity to particular domain account which has permission in AS Databases or adding IUSR_ account to roles in Database.

Please let me know if you have any questions

Kagan

How to: Verify path for SQL Server Error Log Files

kagana — Wed, 21 Oct 2009 05:58:27 GMT

In this post, you can find how to find out sql server error logs files.

SQL SERVER 2005

Using SQL Server Configuration Manager:

SQL Server Configuration Manager is a tool to manage the services associated with SQL Server. The features however are more:

1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.

2. In SQL Server Configuration Manager, expand Services, and then click SQL Server

3. In the details pane, right-click the name of the instance you want to start automatically, and then click Properties

4. Click the Advanced tab, and Verify Startup Parameters.

· -e The fully qualified path for the error log file

Please let me know if you have any questions.

Kagan