Hi Sulfath,

The fact that it's going to the "CustomPages" directory in your URL suggests that your "Continue" button may have been modified on the "Lead screen" you referenced. 

Chances are the issue stems from a permissions in either IIS or the IUSR account's ability to access the Sage CRM directory on the application server. 

** For the sake of providing a disclaimer, everything that follows should be carried out under the supervision of your IT lead or firm responsible for the security and integrity of your IT systems and applications **

Run the "inetmgr" (Internet Information Services (IIS) Manager) and navigate to your CRM instance's "Authentication" settings. 

Once open, ensure that "Anonymous Authentication" is enabled. If you right click on that item in the list of authentication methods, you'll get the "Edit" option. Make sure the user that's selected is the impersonated user set up by your IT firm (by default, it's "IUSR").



If that looks good, the next stop is the Application directory where Sage CRM is installed. The default installation path is "C:\Program Files (x86)\Sage\CRM\[instanceName]". Navigate to your instance and you'll see a "WWWRoot" folder. Right click that, and select "Properties" option.



The IUSR (or the impersonated user set up by your IT team) should be listed as it is above in my test system. If it doesn't have the option and you have Administrator rights to the Sage CRM server, click the "Edit" button and give "Full control" to the IUSR (or impersonated user defined in IIS). 

Go back into Sage CRM and test the "Continue" button again in the same order that you received the error. If IIS and the impersonated user are both set up correctly, you should no longer receive the 403 Forbidden error.

I hope that helps.

Best Regards,
Basil Malik

Hi Sulfath,

The fact that it's going to the "CustomPages" directory in your URL suggests that your "Continue" button may have been modified on the "Lead screen" you referenced. 

Chances are the issue stems from a permissions in either IIS or the IUSR account's ability to access the Sage CRM directory on the application server. 

** For the sake of providing a disclaimer, everything that follows should be carried out under the supervision of your IT lead or firm responsible for the security and integrity of your IT systems and applications **

Run the "inetmgr" (Internet Information Services (IIS) Manager) and navigate to your CRM instance's "Authentication" settings. 

Once open, ensure that "Anonymous Authentication" is enabled. If you right click on that item in the list of authentication methods, you'll get the "Edit" option. Make sure the user that's selected is the impersonated user set up by your IT firm (by default, it's "IUSR").



If that looks good, the next stop is the Application directory where Sage CRM is installed. The default installation path is "C:\Program Files (x86)\Sage\CRM\[instanceName]". Navigate to your instance and you'll see a "WWWRoot" folder. Right click that, and select "Properties" option.



The IUSR (or the impersonated user set up by your IT team) should be listed as it is above in my test system. If it doesn't have the option and you have Administrator rights to the Sage CRM server, click the "Edit" button and give "Full control" to the IUSR (or impersonated user defined in IIS). 

Go back into Sage CRM and test the "Continue" button again in the same order that you received the error. If IIS and the impersonated user are both set up correctly, you should no longer receive the 403 Forbidden error.

I hope that helps.

Best Regards,
Basil Malik

Hi Basil,

Thanks for the reply.

Unfortunately it doesn't work. I am still getting the same error.

Any other options?