FAQs - Application

This section will help you to identify common issues encountered during installation or during an update of lexbizz/Acumatica instance. Application logs are helpful to identify the problem and following points will help you to solve issues without any assistance.

❔ Not able to load Build Names and Versions

✔️ Please restart the tool and login with your CRM Credentials.

❔ Application Installation/Update Progress is stuck at 20%

✔️ Application queue is full or broken and is not able to resume it’s operation. You need to delete a temporary file generated at the install location and restart the service.

  • Delete this file - C:\Program Files\Haufe\lz-devops\lzdtbroker.db

  • Restart lexbizz DevOps tool service. You can either do it with a powershell script (mentioned below) or using Windows Service Manager

    1sc stop lzdservice
2sc start lzdservice

  • Start the tool and login

❔ Application do not have sufficient permission to CREATE/RESTORE/DROP database

✔️ If you have installed the lexbizz DevOps tool for the first time, then use the option to grant access to Local System Account Manage System Account Permissions

After applying script if you are still receiving the same error message then try to restart the service. Restart SQL Service

❔ Named Pipes Provider: Could not open a connection to SQL Server, Login timeout expired

✔️ If you receive this error, then it means that your local SQL Server is not working or you have selected an incorrect database server name. Select the correct database name before starting the installation/update process.

❔ OSError: [WinError 145] The folder is not empty ‘C:\location\Website\Files

✔️ IIS or some other process on Windows might block some files on the mentioned location. This will cause application installation or update to fail.

  • Try manually deleting ‘C:\location\Website’ folder and retry application installation

❔ Bei der Konvertierung eines varchar-Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Bereichs

✔️ This happens if the datatime format is somehow changed on the local database. This can happen by importing a snapshot from a cloud instance. You need to install a fresh copy of a lexbizz Instance. Make sure you have installed a SQL Server with English languages.

❔ Snapshot restoration failed TargetTenant:<company>. Could not allocate space for object ‘x’.’x’ in database ‘database’ because the ‘PRIMARY’ filegroup is full

✔️ You may encounter this issue during restoration of a large snapshot on a local instance. In order to solve this problem please use the following steps,

  • Open SQL Management Studio

  • Login to the SQL Server

  • Right click on the Database -> Properties -> Files

  • Under ‘Autogrowth/Maxsize’ column, for each line set Maximum File Size = Unlimited

❔ ERROR: The command requires the extension azure-devops. Unable to prompt for extension install confirmation as no tty available. Run ‘az config set extension.use_dynamic_install=yes_without_prompt’ to allow installing extensions without prompt.

✔️ This occurs because of an old configuration of the Azure CLI and Azure DevOps Tool extension. In order to solve this problem, just reinstall Azure DevOps Extension using the lexbizz DevOps Tool -> Install Extensions. Installing Azure DevOps extension under logged in user is not going to work. You have to instll it using the tool itself. See Azure DevOps Extension for more information.

FAQs
FAQs - Dependencies