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.
Where can I find the logs?¶
You will be able to look at the application logs under ⚙️Settings section. Have a look at Application Logs
⁉️ 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 execute the SQL Script mentioned inside Post Installation Instructions
⁉️ 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.