Unable to Connect to Profiler!

[PD]

Hi,
I am connected to SQl server 7.0 thru TCP/IP .when I run Profiler I get a message like this -
"[MS ODBC SQL Server Driver]The operation could not be completed b'coz your security context could not be impersonated."
I tried using NamedPipes/MultiProtocol N/wLibrary but then also it do not work?
Any idea....
TIA
Pd

[MAK]

change your client configuration to named pipes.
change your Server Network Utility to named pipes.


Profiler works only if it is connected using named pipes.


-MAK

------------
PD at 3/1/01 6:53:43 PM

Hi,
I am connected to SQl server 7.0 thru TCP/IP .when I run Profiler I get a message like this -
"[MS ODBC SQL Server Driver]The operation could not be completed b'coz your security context could not be impersonated."
I tried using NamedPipes/MultiProtocol N/wLibrary but then also it do not work?
Any idea....
TIA
Pd

[pd]

Hi Mak,
I changed it to NamedPies.Now it says unable to connect to server.
I am unable to connect to server even thru Enterprise manager.



------------
MAK at 3/2/01 8:40:00 AM

change your client configuration to named pipes.
change your Server Network Utility to named pipes.


Profiler works only if it is connected using named pipes.


-MAK

------------
PD at 3/1/01 6:53:43 PM

Hi,
I am connected to SQl server 7.0 thru TCP/IP .when I run Profiler I get a message like this -
"[MS ODBC SQL Server Driver]The operation could not be completed b'coz your security context could not be impersonated."
I tried using NamedPipes/MultiProtocol N/wLibrary but then also it do not work?
Any idea....
TIA
Pd

[CW Speer]

Check and see if Enterprise Manager on your desktop and on the server you are profiling is set to auto-login. If you can open up the server without logging in (supplying the password) then it will work.

Profiler needs to have this in order to log into the server.

Worth a try.


------------
pd at 3/2/01 10:24:16 AM

Hi Mak,
I changed it to NamedPies.Now it says unable to connect to server.
I am unable to connect to server even thru Enterprise manager.



------------
MAK at 3/2/01 8:40:00 AM

change your client configuration to named pipes.
change your Server Network Utility to named pipes.


Profiler works only if it is connected using named pipes.


-MAK

------------
PD at 3/1/01 6:53:43 PM

Hi,
I am connected to SQl server 7.0 thru TCP/IP .when I run Profiler I get a message like this -
"[MS ODBC SQL Server Driver]The operation could not be completed b'coz your security context could not be impersonated."
I tried using NamedPipes/MultiProtocol N/wLibrary but then also it do not work?
Any idea....
TIA
Pd

[Kevin Krause]

Just a thought...Are you connecting to a remote box? If so, what OS are you running locally? You'll have trouble running under Win9x and connecting remotely. -Kevin


------------
PD at 3/1/01 6:53:43 PM

Hi,
I am connected to SQl server 7.0 thru TCP/IP .when I run Profiler I get a message like this -
"[MS ODBC SQL Server Driver]The operation could not be completed b'coz your security context could not be impersonated."
I tried using NamedPipes/MultiProtocol N/wLibrary but then also it do not work?
Any idea....
TIA
Pd