Is XEvent ETW target operable in CTP4?


I've been trying out the XEvent functionality and like what I see so far. But

I'm unable to get the ETW target working at all. Host operating system is Windows 2K3 SP1.

I've tried a few examples from BOL, crufted up a few CREATE/ALTER EVENT SESSION

statements of my own, tried accepting ETW target defaults (a join of the

sys.dm_xe* tables says that there are no manditory parameters for this target),

and also tried specifying each parameter...no luck.

I'm running SQL Server as a low-privileged service account, but I did pick a

directory that I knew it had access to for the .etl file.

The symptoms are always the same. CREATE EVENT SESSION works fine with the ETW

target specified, then ALTER EVENT SESSION...STATE=START always produces:

Msg 25602, Level 17, State 17, Line 1
The target, "CE79811F-1A80-40E1-8F5D-

7445A3F375E7.package0.etw_classic_sync_target", encountered a configuration

error during initialization. Object cannot be added to the event session.

No information about what exactly the configuration error is.

I've done a "logman -query providers" and the providers all appear to be there.

In fact I can start a session by pointing logman at all three ETW providers

(sqlserver, XEvent Provider 0, sqlos). Nothing gets traced but no error occurs.

The error on ALTER EVENT SESSION always occurs whether I have an ETW session

going or not. And the BOL seems to indicate that a pre-existing ETW session

with the SQL Server 2008 providers is not a requirement; that CREATE/ALTER

EVENT SESSION will start one.

What am I missing? The other event targets (bucketizer, pairing target) appear

to work fine. And the "direct to file system" target is not supposed to be

available in this CTP. But the ETW target is supposed to be available...

Thanks,
Bob Beauchemin
SQLskills

[2994 byte] By [BobBeauchemin] at [2008-2-15]
# 1

Hi Bob,

The ETW target is fully functional in CTP4. It sounds like the startup account for SQL Server doesn't have the proper permissions to actually create a session. Make sure the SQL Server startup account is a member of the "Performance Log Users" and "Performance Monitor Users" group.

There appears to be an oversight in the BOL topics mentioning this requirement.

Thanks,

Jerome Halmans

Program Manager SQLOS

JeromeHalmans at 2007-10-2 > top of Msdn Tech,SQL Server Katmai,SQL Server Katmai Database Engine...
# 2

Thanks Jerome, that was what I was missing.

The service account (no special privs, member of only Users group before install, privs/groups assigned during install) was a member of Performance Monitor Users but was not a member of Performance Log Users. Once I added the account to this group and restarted, the ETW target works like a charm.

Cheers,

Bob Beauchemin

SQLskills

BobBeauchemin at 2007-10-2 > top of Msdn Tech,SQL Server Katmai,SQL Server Katmai Database Engine...

SQL Server Katmai

Site Classified