Troubleshooting App Volumes Deployment on Azure

If you have any deployment errors, including database-related, when configuring App Volumes Manager on the Azure virtual machine image, deployed using Azure Marketplace, the information present in this section helps you understand and troubleshoot these errors.

ERROR [08001] [Microsoft][ODBC Driver XX for SQL Server] A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct

This error message occurs in the Azure Marketplace offer wizard when configuring remote SQL server database for App Volumes Manager in the Azure Marketplace. The error is seen during deployment when the setup-script fails.

Problem

SQL server is not accessible.

Cause

This error can occur due to the following reasons:

• Certain firewall setting that allows Azure services and resources access the SQL server is turned off.
• An incorrect host name (for example: mismatch in the host name or an incorrect IP address) is provided for the remote SQL server database.
• An on-premises SQL server is used and remote connections are not allowed from the server.
• The virtual network in which the database is configured might not be accessible by the virtual network of the virtual machine where App Volumes Manager is installed.

Solution

To resolve this error, you can try one of these solutions:

• Ensure that the appropriate firewall and virtual network settings are enabled.

  1. In the Azure portal, navigate to your SQL server database > Security > Networking tab.
  2. In the Firewall rules section, ensure that the appropriate IP addresses or IP address range are allowed.
  3. Ensure that the TCP port 1433 for Microsoft SQL server is allowed as an inbound rule on the SQL server virtual machine.
  4. In the Exceptions section, ensure that Allow Azure services and resources to access this server setting is turned on.

• When deploying Omnissa App Volumes, ensure that the correct host name is provided in the database connection details when configuring App Volumes Manager in the Azure Marketplace offer wizard (App Volumes configuration tab).

• If using an on-premises SQL server, ensure that remote connections are allowed.

  To configure this setting, you can use SQL Server Management Studio (SSMS).

• Ensure that the network security group and Azure virtual network are correctly configured so that the App Volumes Manager virtual machine can communicate with the SQL server virtual machine.

ERROR [18456] [Microsoft][ODBC Driver XX for SQL Server] Login failed for user '<username>'

This error message occurs in the Azure Marketplace offer wizard when configuring remote SQL server database for App Volumes Manager in the Azure Marketplace. The error is seen during deployment when the setup-script fails.

Problem

Database login failed.

Cause

This error can occur due to the following reasons: incorrect SQL server configuration, incorrect credentials provided for the SQL server, user is not mapped to the database, user account is not enabled, or the password policy has expired.

Solution

To resolve this error, you can try one of these solutions:

• If the SQL server is configured to only allow Windows authentication, ensure that you enable SQL server authentication also.
• Ensure that the correct user name and password are entered in the database connection details when configuringApp Volumes Manager in the Azure Marketplace offer wizard (App Volumes configuration tab).
• Ensure that the user is mapped to the SQL server database specified in the database connection details.
• Ensure that the user account is enabled.
• If your SQL server is set to enforce password policy and the user's password has expired, ensure that you reset the password.

ERROR [4060] [Microsoft][ODBC Driver XX for SQL Server] Cannot open database "YourDatabaseName" requested by the login

This error message occurs in the Azure Marketplace offer wizard when configuring remote SQL server database for App Volumes Manager in the Azure Marketplace. The error is seen during deployment when the setup-script fails.

Problem

Database is not accessible.

Cause

This error can occur due to the following reasons: the database specified in the database connection details when configuring App Volumes Manager in the Azure Marketplace offer wizard does not exist, user is not mapped to the database, or database is offline.

Solution

To resolve this error, you can try one of these solutions:

• Ensure that the name provided to configure the App Volumes database configuration is present as a valid database in the SQL server virtual machine.
• Ensure that the user is mapped to the database specified and user has the required database roles assigned.
• Ensure that the database is online.
• Ensure that you have configured the appropriate permissions for the user to access the database.

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.

This error message occurs when configuring file shares for App Volumes Manager in the Azure Marketplace. The entire error message appears as follows: The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/{subscription-id}/resourceGroups/{resource-group-id}/providers/Microsoft.Compute/virtualMachines/{virtual-machine-name}/extensions/setup-script).

Problem

File shares are not reachable from the App Volumes Manager virtual machine using the DNS name.

Cause

This error can occur because the DNS for the provisioned Azure storage account is not configured.

Solution

1. Establish RDP (Remote Desktop Connection) with the App Volumes Manager virtual machine using the local administrator user name and password as specified in the Basics tab of the deployment wizard.

2. Open the setup-script log file %programdata%\Omnissa\AppVolumes\Log\setup.log.

3. If you see certain specific log messages, the messages indicate that the deployment script could not configure the file shares within App Volumes Manager as the file shares are not reachable from the App Volumes Manager virtual machine.

   The following log messages indicate that the deployment script could not configure the file shares:

   
   About to register fileshare: staging-xxxxxxxx
   
   Registered fileshare staging-xxxxxxxx. API response: {"success":"Added path to available storage","data":{"id":1,"path":"\\\\xxxxxxxx.file.core.windows.net\\staging-xxxxxxxx","created_at":"yyyy-mm-ddThh:mm:ssZ","updated_at":"yyyy-mm-ddThh:mm:ssZ","credential_id":1,"domain":"AZURE"}}
   
   About to set datastore defaults for staging-xxxxxxxx
   AVM service error: System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
      at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
      at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord(). Retrying in 30000 ms.
   
   ...
   ...
   AVM service error: System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
      at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
      at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord(). Retrying in 480000 ms.
   
   

4. If you have selected an existing virtual network in the Basics > Configure virtual networks section in the deployment wizard, ensure that you add a virtual network link to the virtual network in the private DNS zone selected in the App Volumes configuration > Private endpoint DNS settings section.

5. After you have completed the previous step, ensure that the file share is reachable from within the App Volumes Manager virtual machine using the DNS name (\\xxxxxxxx.file.core.windows.net\staging-xxxxxxxx).

6. Open the App Volumes Manager admin UI from the App Volumes Manager virtual machine RDP session and navigate to the Storage tab.

7. If you see the following error App Volumes Manager cannot create files on this share in the Permissions section for the configured file share staging-xxxxxxxx, then you must remove the existing file share configuration from App Volumes Manager.

   • To add the file share configuration again, use the Remove button on the Storage tab and click Add File Share.

     Note: Before you click Remove, ensure that you copy the file share path, which is listed on the Storage tab, because you need this path when adding the file share again.

     If the fileshare is still not reachable from App Volumes Manager virtual machine using the DNS name (\\xxxxxxxx.file.core.windows.net\staging-xxxxxxxx), you can alternatively use the Private Endpoint IP Address to configure the file shares in App Volumes Manager using the \\<private-endpoint-ip-address>\staging-xxxxxxx path. For example: \\10.0.0.5\staging-qwreqweqe.

8. Repeat the previous step to configure the delivery file share using the DNS name (\\xxxxxxxx.file.core.windows.net\delivery-xxxxxxxx) or using the Private Endpoint IP address(\\<private-endpoint-ip-address>\delivery-xxxxxxx).

   For example: \\10.0.0.5\delivery-qwreqweqe.