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:
> > 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
>|||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:
> > 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
>
Showing posts with label trace. Show all posts
Showing posts with label trace. Show all posts
Wednesday, March 7, 2012
cannot start trace
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,
Bing
bing 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
>
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
bing 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
>
Labels:
backfailed,
clickedrun,
configurations,
database,
error,
microsoft,
mysql,
oracle,
properties,
server,
sql,
trace
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
>
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
>
Labels:
backfailed,
clickedrun,
configurations,
database,
error,
microsoft,
mysql,
oracle,
properties,
server,
sql,
trace
Cannot start SQL Trace (Profiler) on Windows 2000 Professional
Hello all!
I have installed SQL Server 7 Client components on a Windows 2000
Professional machine.
I can start the Query analyzer and I can use it to connect to servers.
However, when I try to start SQL trace, I am getting the following
error message
"sqltrace.exe, not a valid win32 application."
Have any of you come across this problem? Please suggest a solution.
If you need any more information, please let me know.
Thank you,
Martin.
The file could have been corrupted. Have you checked your disk to see if
there are any errors?
You may be able to fix it by reinstalling the client utilities, if that is
not a problem.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Martin Thomas" <martintms99@.yahoo.com> wrote in message
news:752207f2.0408090315.1eb0d689@.posting.google.c om...
> Hello all!
> I have installed SQL Server 7 Client components on a Windows 2000
> Professional machine.
> I can start the Query analyzer and I can use it to connect to servers.
> However, when I try to start SQL trace, I am getting the following
> error message
> "sqltrace.exe, not a valid win32 application."
> Have any of you come across this problem? Please suggest a solution.
> If you need any more information, please let me know.
> Thank you,
> Martin.
I have installed SQL Server 7 Client components on a Windows 2000
Professional machine.
I can start the Query analyzer and I can use it to connect to servers.
However, when I try to start SQL trace, I am getting the following
error message
"sqltrace.exe, not a valid win32 application."
Have any of you come across this problem? Please suggest a solution.
If you need any more information, please let me know.
Thank you,
Martin.
The file could have been corrupted. Have you checked your disk to see if
there are any errors?
You may be able to fix it by reinstalling the client utilities, if that is
not a problem.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Martin Thomas" <martintms99@.yahoo.com> wrote in message
news:752207f2.0408090315.1eb0d689@.posting.google.c om...
> Hello all!
> I have installed SQL Server 7 Client components on a Windows 2000
> Professional machine.
> I can start the Query analyzer and I can use it to connect to servers.
> However, when I try to start SQL trace, I am getting the following
> error message
> "sqltrace.exe, not a valid win32 application."
> Have any of you come across this problem? Please suggest a solution.
> If you need any more information, please let me know.
> Thank you,
> Martin.
Tuesday, February 14, 2012
cannot save trace output to a local file?
Hi,
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bing
bing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
David Gugick
Quest Software
www.imceda.com
www.quest.com
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bing
bing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
David Gugick
Quest Software
www.imceda.com
www.quest.com
cannot save trace output to a local file?
Hi,
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bingbing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bingbing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
cannot save trace output to a local file?
Hi,
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bingbing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
David Gugick
Quest Software
www.imceda.com
www.quest.com
This is SQL 2000 on a win2k3 box.
In Trace Properties, when I checked 'Save to file' and clicked the folder
icon and specified a local file name, I got the following message:
For SQL server to write to a file, file path should have the following
format \\servername\sharename\filename
But I'm trying to write to a local file on the database server. How do I
have to use that format? Also in the Save As window, there is no way to
specify the path name like that given in the above message.
Thanks for any help,
Bingbing wrote:
> Hi,
> This is SQL 2000 on a win2k3 box.
> In Trace Properties, when I checked 'Save to file' and clicked the
> folder icon and specified a local file name, I got the following
> message:
> For SQL server to write to a file, file path should have the following
> format \\servername\sharename\filename
> But I'm trying to write to a local file on the database server. How
> do I have to use that format? Also in the Save As window, there is
> no way to specify the path name like that given in the above message.
> Thanks for any help,
>
> Bing
You don't. You can specify any local drive with a drive letter.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Subscribe to:
Posts (Atom)