Solved

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

Posted on 2006-06-14
6
2,256 Views
Last Modified: 2008-05-06
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
Comment
Question by:sriniram
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 11

Accepted Solution

by:
Ved Prakash Agrawal earned 200 total points
ID: 16903998
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
 
LVL 11

Expert Comment

by:Ved Prakash Agrawal
ID: 16904030
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
 

Author Comment

by:sriniram
ID: 16904032
I am using Standard Edition of SQL Server 2005.

Thanks
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:sriniram
ID: 16904053
Is this service pack for SQL Server 2000 or 2005?

Thanks
0
 

Author Comment

by:sriniram
ID: 16915332
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
 

Expert Comment

by:mattjk
ID: 21505312
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

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question