---
title: "CM2WebShare Troubleshooting Guide"
slug: "cm2webshare-troubleshooting-guide"
updated: 2023-11-27T03:58:32Z
published: 2023-11-27T03:58:32Z
canonical: "helpfiles.fybsoftware.com.au/cm2webshare-troubleshooting-guide"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://helpfiles.fybsoftware.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# CM2WebShare Troubleshooting Guide

## OVERVIEW

The following guide lists some of the common CM2WebShare issues you may experience along with the possible cause and resolution.

## UNABLE TO WRITE TO EVENT LOG

### DESCRIPTION

An error shows in the event log that states CM2WebShare cannot write to the event log due to security restrictions.

### CAUSE

Incorrect Local Security Policy settings.

### RESOLUTION

Follow the steps in this guide: [https://mohsartawi.wordpress.com/2014/12/16/give-non-administrator-user-an-access-to-read-the-event-logs-in-active-directory/](https://mohsartawi.wordpress.com/2014/12/16/give-non-administrator-user-an-access-to-read-the-event-logs-in-active-directory/)

## SITE BLOCKED BY CORS POLICY

### DESCRIPTION

You see an error stating that the site has been blocked by the CORS policy.

### CAUSE

The site is being blocked by the CORS policy or the IIS CORS module is not installed.

### RESOLUTION

Ensure that the IIS CORS module is installed on the server: [https://www.iis.net/downloads/microsoft/iis-cors-module](https://www.iis.net/downloads/microsoft/iis-cors-module)

## VALUE CANNOT BE NULL (PATH1)

### DESCRIPTION

You receive the following error when attempting to load CM2WebShare. **Value cannot be null. Parameter name: path1**

### CAUSE

The 64bit Content Manager client is not installed on the server which means CM2WebShare cannot access the SDK.

### RESOLUTION

Ensure the 64bit Content Manager client is installed on the server. Or alternatively, use the clientless install feature.

## UNABLE TO ACCESS WEB.CONFIG FILE FROM IIS

### DESCRIPTION

After installation, if you attempt to access the web.config file via application settings in IIS you see this message. ![image.png](https://cdn.document360.io/d6552dbe-372e-441e-bf0c-dbc5e937f181/Images/Documentation/image-Z90CTZ5M.png)

### CAUSE

.NET Core pre-requisites haven't been installed properly.

### RESOLUTION

Confirm that both the .NET Core SDK and .NET Core Hosting Bundle have been installed on the server. If they have then make sure a full server restart has been completed as this allows them to bind to IIS. Details can be found in the pre-requisite and install guides.