none
Profiler error in Windows Server 2003 RRS feed

  • Question

  • Hi,

    I have been using\developing the profiler API pretty well in Windows 7, windows 2008 etc. When I tried to install my profiler in a windows server 2003 machine. The profiler mainly concentrates on ASP.net applications.

    I get the following error in Windows Server 2003 machine. 

    My Machine has SP 2 installed and is a Datacenter edition with IIS 6. The machine is also installed with .net 2.0, 3.0, 3.5, 4.0 with their service packs.

    .NET Runtime version 4.0.30319.235 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{......}'.  HRESULT: 0x8007007f.  Process ID (decimal): 3752.  Message ID: [0x2504].

    It is strange because I have not come across the HRESULT error number so far.

    Does anyone know why I get this error, what it means and how to rectify it?

    PS: I use VS2010 to develop my profiler.

    -Jasper


    ..JPJ..


    • Edited by Jasper paul Wednesday, January 2, 2013 10:13 AM
    • Moved by Mike FengModerator Thursday, January 3, 2013 3:08 AM restructure .NET forums (From:Building Development and Diagnostic Tools for .Net)
    Wednesday, January 2, 2013 10:10 AM

Answers

  • Hi Jasper,

    Welcome to the MSDN Forum.

    How about this thread: http://social.msdn.microsoft.com/Forums/zh-CN/visualcshartzhchs/thread/42dac8f9-2c3c-4936-9860-ee7b264de97d/  

    I translated the language to English:

    Solution from Huan Li:

    Check the System Environment variable: %SystemRoot%\system32

    Check the User Environment variable: C:\WINDOWS\system32\

    And put the DLL into system32 folder.

    Solution from mazhou:

    Does it have extern "C"? There are several possibilities cause this exception:

    --There is no type metadata in the loading assembly (For managed code)

    -- LoadLibrary works successfully, but GetProcAddress, (For unmanaged code)

    Check the tlb file by A PE view tool for this function to make sure it had been exported correctly, and the Calling Conversion should be stdcal or cdecl

    I hope this will be helpful.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Jasper paul Tuesday, January 8, 2013 10:03 AM
    Thursday, January 3, 2013 6:13 AM
    Moderator

All replies

  • Hi Jasper,

    Welcome to the MSDN Forum.

    How about this thread: http://social.msdn.microsoft.com/Forums/zh-CN/visualcshartzhchs/thread/42dac8f9-2c3c-4936-9860-ee7b264de97d/  

    I translated the language to English:

    Solution from Huan Li:

    Check the System Environment variable: %SystemRoot%\system32

    Check the User Environment variable: C:\WINDOWS\system32\

    And put the DLL into system32 folder.

    Solution from mazhou:

    Does it have extern "C"? There are several possibilities cause this exception:

    --There is no type metadata in the loading assembly (For managed code)

    -- LoadLibrary works successfully, but GetProcAddress, (For unmanaged code)

    Check the tlb file by A PE view tool for this function to make sure it had been exported correctly, and the Calling Conversion should be stdcal or cdecl

    I hope this will be helpful.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by Jasper paul Tuesday, January 8, 2013 10:03 AM
    Thursday, January 3, 2013 6:13 AM
    Moderator
  • Thanks Mike, The solution worked.. 

    Copied the profiler COM dll to system32 folder and restarted the application and it worked.

    I don't know how it worked.. Any explanation as to how it worked would be insightful.

    -Jasper


    ..JPJ..


    • Edited by Jasper paul Tuesday, January 8, 2013 10:04 AM
    Tuesday, January 8, 2013 10:02 AM