Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2332
  • Last Modified:

sql server 2005 - profiler - "failed to start a new trace"

I have installed SQL Server 2005 in my laptop and testing an ASP application. I want to run the SQL profiler to findout the database activities.

When I open a new trace in SQL Server 2005 profiler, I am getting the rror "failed to start a new trace". I could not get much help in the net. Many places it is referred to SQL Server 2000 and apply a patch.

Can anyone help me to fix this problem? Do I need to download any patches to make this work?

Thanks
0
sriniram
Asked:
sriniram
  • 3
  • 2
1 Solution
 
Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
No. Not needed at all.

I think there are some problem with the installation that's why this happening.
please tell me which version of sql u r using.
enterprise or developer.

0
 
Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
Hi you can tried this with SP1 for sql server 2005.

and you have full installed sql server 2005.



http://www.kbalertz.com/kbNamed_295461/environment.variable.changed.nonexisting.Server.Profiler.fail.will.result.following.Failed.start.trace.Server.Profiler.allocates.temporary.storage.aspx

But i think you can tried to installed again sql profiler.
0
 
sriniramAuthor Commented:
I am using Standard Edition of SQL Server 2005.

Thanks
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
sriniramAuthor Commented:
Is this service pack for SQL Server 2000 or 2005?

Thanks
0
 
sriniramAuthor Commented:
I think this problem was due to the problem with the permissions for the execution of the stored procedure.

I dropped the new user created by me (created after the restoration of data). Using "exec sp_change_users_login 'update_one', 'login name', 'user name' ".

It is working now.

Thanks
0
 
mattjkCommented:
I found the problem was the folder specified in the server's TMP environment variable had to much junk in it. After clearing it out, the problem disappeared.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now