Error running trace under TCP/IP

[johnv20]

Hi,
I am trying to run a trace on sql 7.0 database however I keep getting the error msg - "the operation could not be completed because your security context could not be impersonated. Use sql server client config app to ensure you are connecting using either named pipes or multiprotocol"

However I can set an odbc connection to the database using TCP/IP with no problem, TCP/IP is in the server & client n/w utilities and I can also run a trace on another database on a different server which which should be configured the exact same under TCP/IP.

Has anyone any ideas of why the server cannot process TCP/IP ?


Thanks,
John

 

[qoqoqoqo]

IBM anywhere in that setup?

 

[johnv20]

Hi,
no IBM - dell 6400 server also dns configured correctly, server can be pinged no problem and its on the same domain as the stations which will be running the apps over TCP/IP

 

[qoqoqoqo]

I'm assuming that you have checked the client network utility and made TCP/IP the default library?
Additionally I assume you are running the trace remotely and thus you may have authentication issues that are not being resolved (ie using NT auth rather than SQL Server Auth) -- this in effect may force the two protocols requested in the error message??
Have you also created the appropriate alias in the Client Network Utility (TCP/IP port as your alias or instancename)?
Are you on port 1433 or another port?