SQLServer2005 Profiler (profiler90.exe) fails to launch with Application Error (0x0000005)

Question

This has been raised as a problem before in a different thread (by Mike Sailer on 11/01/2007) but the circumstances there were slightly different. That is the reason why I am starting a new thread:

I have both SQLServer 2000, SP4 Personal Edition, and SQLServer 2005, SP2 Developer Edition installed on WindowsXP SP2 machine.

SQLServer2005 is running as a named instance, and the SQLServer2000 is running as a default instance.

When I try to start the Profiler of SQLServer2005 (profiler90.exe), this failst to launch with the following error:
"Application Error: The application failed to initialize properly (0x0000005) ..."

 

The Profiler on the SQLServer2000 instance works perfectly well, while the Profiler90 from the SQLServer2005 fails to launch as already described above.

I have also tried installing the recently released SQLServer2005 SP2, but this did not help at all. 

Does anoybody have any idea what may be causing that error ?

Answer 1

This sounds like a tools issue, have you tried to test the profiler on a seperate machine with similar verison of components?

Answer 2

Yes. I did try on another machine which had SQLServer 2000SP4 installed on it and I experienced the same error.

Few of my colleagues have also experienced the same error while launching Profiler90 even without having SQLServer2000 installed on their machines (WindowsXP).

Answer 3

Attempted any installation of client tools in this case?

 

Answer 4

Client tools were already installed as part of the SQLServer2005 installation. What would a re-install of these change ?

Answer 5

I have the same problem on my machine.

My colleagues have the problem as well.

 

It seems to be related to some kind of patch or other thing installed by our IT department.

 

I have tried reinstalling the client tools but that did not help.

 

I have running: Windows XP SP2 with SQL Server 2005 SP2.

The problem appeared without SP2 for SQL Server 2005 as well.

 

Regards,

Ben

Answer 6

It seems that my problem has been solved.

When I tried launching profiler today it worked.

Recently I installed the .NET 3.0 runtime and so did my colleagues which had the same problem.

 

Regards,

Ben

Answer 7

Problem Resolved ! The original problem I had experienced with launching Profiler90.exe appeared to be down to a DLL (sysfer.dll) which seems to be added by the upgrade to a particular version of Symantec Protection Agent 5.1 (firewall) software.

The DLL is located in the ...WINDOWS\system32\    folder. The SPA software seems to be working fine even without this DLL.

Try renaming it first, but if it is already loaded in some process and cannot be renamed, then restart the machine in Safe Mode and then try again to rename or remove the DLL. Finally restart the machine in normal mode and try launching Profiler90.ex again.

This should resolve the issue.

 

This resolution does not require installation of .NET3.0 runtime.

Answer 8

Renaming "sysfer.dll" did not work for me. Profiler errors out with the "sysfer.dll" file cannot be located error msg. I've tried installing .NET Framework 3.0, but I can't seems to uninstall version 2.0. I had it uninstall 2.0 from Add/Remove and reboot the machine, but version 2.0 is still there and it won't let me install 3.0.

 

What'da great product!!!  If the problem existed with Profiler, I don't understand that it wasn't resolved with SQL Server 2005 SP2. 

 

By the way, I've installed SQL Server 2005 workstation components with SP2 installed on Win XP Pro SP2.

Answer 9

I got this error after installing Symantec Endpoint Protection 11.

Uninstalling SEP, reinstalling SQL Profiler, installing Framework 3.0 didn't help me. Only Windows reinstalling solved this problem. Be careful. Configuration: Windows XP Prof SP2, SQL Server 2005 Developer Edition.

Answer 10

In our installation, got this same error when the Symantec Protection Agent v 5.1 was installed onto our workstations.

Our workstation configuration:  Windows XP Prof SP2, SQL Server 2005 Std Edition or Developer Edition.

We found a workaround by editting the following registry on our workstation changing the value from hex zero to hex four:

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]

"Start"=dword:00000004

 

Reboot after editting the registry.

 

 

Answer 11

Renaming "sysfer.dll" resolved it for me too.  (XP sp2, MSSQL Server Developer/ Standard installed sp2).  Had to go into safe mode to do the rename (it was apparently being used by a ton of processes, not just Symantec, looked like everything trying to make a network connection...)  But then Profiler worked fine, and Symantic Endpoint Protection is not complaining either. 
Thanks!

Answer 12

This is what worked for me.  I had tried all the other fixes and nothing worked.  I need it to work.  I even reinstalled SQL.  But, after editing the registry key, then restarting, Profiler loaded up like a champ.

You the man, DB2SQLDBA

Answer 13

Please Ref Below About This Error

 

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/2c62c4ee0e697aae882573b000034ded?OpenDocument

 

Document ID: 2007121216360648
Last Modified: 2008/01/11
Date Created: 2007/12/12
Operating System(s): Windows 2000 Professional, Windows 2000 Server/Advanced Server, Windows XP Home Edition, Windows XP Professional Edition, Windows XP Tablet PC Edition, Windows Server 2003 Web/Standard/Enterprise/Datacenter Edition, Windows Vista, Windows XP Professional x64 Edition, Windows Server 2003 x64 Edition, Windows Vista x64 Edition
Product(s): Endpoint Protection 11
Release(s): Endpoint Protection 11.0, Endpoint Protection 11.0.1

 

Compatibility issue with Microsoft SQL profiler tool
Fix ID: 1146828
Symptom: Application popup: PROFILER90.EXE - Application Error : The application failed
to initialize properly (0xc0000005). Click on OK to terminate the application.
Solution: Resolved compatibility issue with sysplant driver.

Answer 14

Thank you DB2SQLDBA, just tried the registry fix on a client's machine with the same problem and it fixed the problem!! Thank you for sharing this.

Answer 15

 Hi,

I have som problems with profiler. I get this error message below. Do anyone have a clue how to solve this?

"Hanging application profiler90.exe, version 2005.90.3042.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000."

Thankful for all help!

Answer 16

As of 2009-04-17, I can confirm that the registry change and reboot works for SQL Server 2008 Service Pack 1 Developer Edition running on Windows XP Pro Service Pack 3 that also is running Symantec EndPoint Protection (unknown release level).

A partial dump of the registry key I changed appears below:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Type"=dword:00000001
"Start"=dword:00000004

Previously, the above key read as follows

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Type"=dword:00000001
"Start"=dword:00000000

I hope the above helps anyone using SQL Server 2008 Service Pack 1 that cannot get SQL Profiler to launch.

---

Fred Morrison

Answer 17

Setting the reg keys below, fixed it for several of my people as well:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Type"=dword:00000001
"Start"=dword:00000004

Answer 18

I had the same problem with SQL Server 2008 Profiler. I've resolved it with sysfer.dll renaming. Thanks!

Answer 19

I had the same problem with SQL Server 2008 Profiler on Windows XP. Renaming sysfer.dll did not work.
Registry changes suggested above worked.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Type"=dword:00000001
"Start"=dword:00000004

thanks for the help.

Answer 20

yea the problem is solved also into my machin ...thnx but very interesting how did you find the solution!?!?!?!??!