> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/sage-crm-add-ons/crm-event-manager/user-guide/troubleshooting.md).

# Troubleshooting

This section provides troubleshooting information, support contact details, and version history for CRM Event Manager.

### 1 Troubleshooting

If you experience issues while accessing or using CRM Event Manager within Sage CRM, verify the following:

#### Verify User Access

* Ensure that you are logged in to Sage CRM as an **Administrator** or with a user account that has the required administrative privileges.
* Navigate to **Administration → Users → Users**.
* Select the required user and verify that **Event Manager Access** is enabled.
* Open the **Security** section for the user and ensure that the appropriate **View**, **Insert**, **Update**, and **Delete** permissions are granted.

#### Verify Required CRM Data

CRM Event Manager is designed to operate on a populated Sage CRM database.

If CRM Event Manager is installed on a newly installed Sage CRM system without sample or existing data, errors may occur during use.

The system requires at least:

* One Company
* One Person
* One additional User account (other than Administrator)

#### Document Plug-in

When running reports that generate PDF or Microsoft Word documents for the first time, Sage CRM may prompt you to install a document plug-in.

Click **Install** and follow the on-screen instructions to complete the installation.

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2Fg36rulnxYW6MfIg54EWd%2FTroubleshooting.png?alt=media&amp;token=917ca2f0-fc1b-42cf-b657-1f875d5d935c" alt=""><figcaption></figcaption></figure>

#### Windows Server 2008 Configuration

If you are running CRM Event Manager on **Windows Server 2008**, verify that **Active Server Pages (ASP)** are enabled.

To enable ASP:

1. Click **Start → Run**.
2. Type **INETMGR** and press **Enter**.
3. Select **ISAPI and CGI Restrictions**.
4. Ensure that **Active Server Pages** are set to **Allowed**.

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2Fc00Ii6zBEPqmjrCdCXK0%2FIIS.png?alt=media&amp;token=cb8684b3-5c40-42dd-b26a-61942d903ba1" alt=""><figcaption></figcaption></figure>

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2FjZEGDWZKF5pO5Puu8izy%2FISAPI.png?alt=media&amp;token=8f1d1500-35d3-456e-b62a-393ac8f894c5" alt=""><figcaption></figcaption></figure>

#### Enable 32-Bit Applications

If Sage CRM and CRM Event Manager are running on **Windows Server 2008**, IIS does not allow Application Pools to run 32-bit applications by default. This may result in an **HTTP 500** error when accessing CRM.

To enable 32-bit applications:

1. Click **Start → Run**.
2. Type **INETMGR** and press **Enter**.
3. Select **Application Pools**.
4. Right-click the **CRM AppPool** and select **Advanced Settings**.
5. Set **Enable 32-Bit Applications** to **True**.

Save the changes.

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2FAoJItjWrfxgZzxXqdEFY%2FApplication%20pool.png?alt=media&amp;token=6edbb641-11ce-47e8-ad69-16d99d9643dd" alt=""><figcaption></figcaption></figure>

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2F8Lm8HDQ3VAbgfecEz6mn%2FSettings.png?alt=media&amp;token=a55826b7-1039-4bd4-857e-bbffd5fee581" alt=""><figcaption></figcaption></figure>