--- title: "Azure Storage Printer (The Specified Container Does Not Exist)" slug: "azure-storage-printer-the-specified-container-does-not-exist" description: "This article provides a guide to troubleshooting and resolving the error you may see in Lasernet Monitor on the Azure Storage Printer module." updated: 2024-06-24T09:35:24Z published: 2024-06-24T09:35:24Z canonical: "kb.lasernetgroup.com/azure-storage-printer-the-specified-container-does-not-exist" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt > Use this file to discover all available pages before exploring further. # Error Message: 'Azure Storage Printer (The Specified Container Does Not Exist)' The purpose of this article is to provide a guide to troubleshooting and resolving the following error you may see in Lasernet Monitor on the Azure Storage Printer module when printing a report to a Lasernet cloud printer: > [!CAUTION] > Error > > Azure Storage - Azure Storage Printer > > (The specified container does not exist.) This error occurs because the **Azure Storage Printer** module cannot find an instance in the Azure storage with the Lasernet Connector configuration Identifier in the name. If you are not using a separate Azure storage account for Lasernet cloud printing, you need to ensure the Azure storage connection string in Dynamics 365 **Lasernet** > **Setup** > **Cloud Print connector setup** > **Parameters** is pointing to your environment's Azure storage (can be found in **Lasernet** > **Setup** > **Parameters** > **Performance**) and that an instance exists with the Connector configuration ID in it. If you are using a separate Azure storage account for Lasernet cloud printing, you need to make sure there is a connection with this information in **Lasernet Developer** > **Commands** > **Azure Storage** and that the Azure Storage printer points to it appropriately. ## Troubleshooting Steps 1. Open the Lasernet configuration in your Developer and navigate to **Modules** > **Azure Storage Printer** module. 2. Navigate to the **Setup** tab > **Connection** and note the connection. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1624282900901.png) 1. If the connection is **#DatabaseConnection#** you can find the Azure Storage by printing a report and looking for the **databaseConnection JobInfo** in the monitor. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-EWE2CUXZ.png) 1. Navigate to **Commands** > **Connections** > **Azure Storage** and click the **Test Connection** button for this storage. The test should succeed. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1624283128160.png) ## Verification of the Identifier To verify that the Lasernet Connector configuration Identifier has an instance in the Azure Storage used in the Lasernet connector parameters, follow these steps: 1. In Lasernet FO Connector, navigate to **Lasernet** > **Setup** > **Lists** > **Printers** and copy the identifier for the printer you are trying to use. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1624283395491.png) 1. Navigate to **Lasernet** > **Setup** > **Cloud Print connector setup** > **Parameters** and click the hyperlink for the **Azure Storage Connection-string** to open its settings. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1624283543853.png) 1. Click the dropdown on the instance field and verify there is an instance with the Connector configuration identifier in its name. This indicates the Azure Storage set up in Lasernet connector is the correct one that is configured to the Connector configuration that exists on the print server. ![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/1624283627272.png) 1. Verify that the connection string for this Azure Storage is the same as the connection information in the Lasernet Developer. Open Lasernet Developer and navigate to **Commands** > **Azure Storage** for the corresponding Azure Storage connection.