What are the challenges you face when working across database platforms? Take the survey

Loading Profiler Failed


when starting a profiling session for a windows service I always receive this error:

.NET Runtime version 4.0.30319.0 - Loading profiler failed.  The profiler COM object was instantiated, but the profiler failed during its initialization callback.  Profiler CLSID: '{44ACFE8F-33B4-4951-B831-CB92214BCB07}'.  HRESULT: 0x80004004.  Process ID (decimal): 4416.  Message ID: [0x2505].

Can you give me any advice? I checked the requirements for the ANTS memory profiler and it all looks good. We are running .net 4.8.3. and all other .net applications on the server are doing just fine.
Sign In or Register to comment.