|
Home > Archive > microsoft.public.cert.mcdba > April 2003 > having trouble with Profiler
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
having trouble with Profiler
|
|
|
| I am trying to run SQL Profiler but after I define what I
want to trace, I go to run it and I get a message:
[Microsoft][ODBC SQL Server Driver][SQL Server] The
operation could not be completed because your security
context could not be impersonated.
Use the SQL Server Client Configuration application to
ensure that you are connecting using either the Named
Pipes or Multiprotocol network library.
I am using named pipes and tcp/ip. Why is it not logging
in? By the way, I can log into EM and query analyzer
without a problem.
| |
| Mario Londoņo 2003-04-06, 12:23 pm |
| You need to be a member of System Admin role in order to run Profiler.
"Adam" <asim@usa.net> wrote in message
news:019301c2f7dd$8ea730f0$a60
1280a@phx.gbl...
> I am trying to run SQL Profiler but after I define what I
> want to trace, I go to run it and I get a message:
>
> [Microsoft][ODBC SQL Server Driver][SQL Server] The
> operation could not be completed because your security
> context could not be impersonated.
>
> Use the SQL Server Client Configuration application to
> ensure that you are connecting using either the Named
> Pipes or Multiprotocol network library.
>
> I am using named pipes and tcp/ip. Why is it not logging
> in? By the way, I can log into EM and query analyzer
> without a problem.
|
|
|
|
|