Troubleshooting the deployable packages installation from the command line on a development (one box) environment

Overview

The deployment package installation in a development environment is a common task when you need to install an ISV solution or another partner. The installation process is well described in the standard guide. Theoretically, the process should go smoothly. In reality, you may face various errors during this process.

Time out issue

Sometimes, the installation process can fail with the error:

Generated runbook with id: Runbook20230907093027

Start executing runbook : Runbook20230907093027

Executing step: 1

Stop script for service model: AOSService on machine: localhost

Stop AOS service and Batch service

Error during AOS stop: File locks found on K:\AosService\WebRoot\bin\AOSKernel.dll for more than 300 seconds. Check previous logs for identified locking processes. [Log: C:\Temp\ZZZ_10.02.15.12\RunbookWorkingFolder\Runbook20230907093027\localhost\AOSService\1\Log\AutoStopAOS.log]

The step failed

In this case, you need to stop IIS Express in your dev box and repeat the installation process.

Don't forget to run database synchronization. You must run database synchronization from Microsoft Visual Studio after you install the deployable package. 

Check in issue

When you try to check in the installed binary files in Visual Studio you may face the issue below: 

**:\AosService\PackageLocalDirectory\ModelName\bin\file_name

TFS30063: You are not authorized to access.

You  can try to do the following:

• Reopen Visual Studio 
• Try to do a check-in again

If the previous actions have not worked:

• Reopen Visual Studio
• Stop The Batch Service and IIS Express in the Dev Box  
• Try to do a check-in again