cannot start trace

After going through all the configurations in Trace Properties, I clicked
Run, then I got this error back:
Failed to start a trace. SQL server does not exist or access denied.
The user I'm connecting to the server has full privileges on the databases.
Where should I check?
Thanks for any help,
Bingbing wrote:
> After going through all the configurations in Trace Properties, I
> clicked Run, then I got this error back:
> Failed to start a trace. SQL server does not exist or access denied.
> The user I'm connecting to the server has full privileges on the
> databases. Where should I check?
> Thanks for any help,
> Bing
You're not even getting to the server. Either the server name is
mistyped or your login name/password is incorrect.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Oh? In SQL Profiler, clicking File->New->Trace, then a window with title
'Connect to Server' pops up, in this window, SQL Server is set to local,
Connecting using Windows authentication. Clicking Ok in this window brings
up another window Trace Properties.
I think at this point I've already connected to the server fine. No?
Anyway, I tried changing server name from local to its hostname, it worked.
Odd, I was doing all this on the database server, how doesn't 'local' work?
Bing
"David Gugick" wrote:

> bing wrote:
> You're not even getting to the server. Either the server name is
> mistyped or your login name/password is incorrect.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||bing wrote:
> Oh? In SQL Profiler, clicking File->New->Trace, then a window with
> title 'Connect to Server' pops up, in this window, SQL Server is set
> to local, Connecting using Windows authentication. Clicking Ok in
> this window brings up another window Trace Properties.
> I think at this point I've already connected to the server fine. No?
> Anyway, I tried changing server name from local to its hostname, it
> worked. Odd, I was doing all this on the database server, how doesn't
> 'local' work?
"(local)" not "local". I prefer using the real server name just as you
ended up doing. I'm not exacly sure what the problem was. The error
message you posted indicated you never made it to the server (my
username/pwd comment aside). But if what you're saying is you get past
the login screen, then you are in fact logging in successfully to the
server. It's just that at that point the trace has not started. You have
only verified with Profiler that you have a valid admin login to the
server. Just stick with the real server name and you should be fine.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Sorry about not being precise. It's my typo. Yes, it is '(local)' rather
than 'local'.
Bing
"David Gugick" wrote:

> bing wrote:
> "(local)" not "local". I prefer using the real server name just as you
> ended up doing. I'm not exacly sure what the problem was. The error
> message you posted indicated you never made it to the server (my
> username/pwd comment aside). But if what you're saying is you get past
> the login screen, then you are in fact logging in successfully to the
> server. It's just that at that point the trace has not started. You have
> only verified with Profiler that you have a valid admin login to the
> server. Just stick with the real server name and you should be fine.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>