Resolving common issues

Issue	Resolution
Visual Studio doesn’t stop at your break point.	Make sure that the corresponding .pdb file for your custom .NET DLL is copied to the Storage location for custom .NET DLLs on the Sage CRM server. .NET Framework needs the .pdf file to find the source code.
The managed option is not available on the Inetinfo.exe process.	Reset IIS and run any .NET API code at least once.
The process isn't created in Component Services.	Verify that you have the correct version of DLLs and have set the correct password.
An error message similar to "Interface not supported" appears in Sage CRM when you invoke your .NET code.	Unregister your .NET DLL, and then register it again. The COM+ debugging method only works with Sage CRM version 7.2 and later. This error message may appear if you work with an earlier version of Sage CRM.
The debugging method you use stops working after a few days.	Make sure that you use the correct password on the Component Service.
The application process is created correctly on Component Services, but an error message similar to "Interface not supported" appears in Sage CRM.	Make sure you enable integrated Windows authentication in IIS. For more information, see the MSDN article titled "Error: Debugging Failed Because Integrated Windows Authentication Is Not Enabled" for your version of Visual Studio.

Visual Studio doesn’t stop at your break point.

Make sure that the corresponding .pdb file for your custom .NET DLL is copied to the Storage location for custom .NET DLLs on the Sage CRM server.

.NET Framework needs the .pdf file to find the source code.

The managed option is not available on the Inetinfo.exe process.

Reset IIS and run any .NET API code at least once.

The process isn't created in Component Services.

Verify that you have the correct version of DLLs and have set the correct password.

An error message similar to "Interface not supported" appears in Sage CRM when you invoke your .NET code.

Unregister your .NET DLL, and then register it again.

The COM+ debugging method only works with Sage CRM version 7.2 and later. This error message may appear if you work with an earlier version of Sage CRM.

The debugging method you use stops working after a few days.

Make sure that you use the correct password on the Component Service.

The application process is created correctly on Component Services, but an error message similar to "Interface not supported" appears in Sage CRM.

Make sure you enable integrated Windows authentication in IIS.

For more information, see the MSDN article titled "Error: Debugging Failed Because Integrated Windows Authentication Is Not Enabled" for your version of Visual Studio.