Troubleshooting and FAQ

This guide gathers common issues encountered when using AutoUpgradeTool and their solutions, as well as frequently asked questions.

Common Issues and Solutions

Launch Issues

The tool does not start

Symptoms:

• Double-clicking on AutoUpgradeTool.exe produces nothing
• Error message "Application cannot start"

Possible Causes:

1. .NET 8.0 Runtime not installed
2. Antivirus blocking execution
3. Corrupted files

Solutions:

dotnet --list-runtimes

eventvwr.msc

Copy-Item "S:\3-PRODUIT\ReleaseUpgrades\AutoUpgradeTool\v2.4\*" -Destination "C:\Avanteam\AutoUpgradeTool\" -Force

Error "This application requires .NET Desktop Runtime 8.0"

Solution:

1. Download .NET 8.0 Desktop Runtime:

   https://dotnet.microsoft.com/download/dotnet/8.0/runtime

2. Install the windowsdesktop-runtime-8.x.x-win-x64.exe package
3. Restart AutoUpgradeTool

Cannot access Bastille server

Symptoms:

• Error "Network path was not found"
• Timeout when accessing S:\3-PRODUIT\ReleaseUpgrades\

Solutions:

Test-Connection -ComputerName bastille -Count 2

net use S: \\bastille\S$ /persistent:yes

Test-Path "\\bastille\S$\3-PRODUIT\ReleaseUpgrades\"

Instance Detection Issues

AutoUpgradeTool detects no instance

Symptoms:

• The "Step 3 - Instance" page is empty
• Message "No instance detected"

Possible Causes:

1. Process Studio is not installed on the machine
2. Non-standard Process Studio installation
3. Insufficient access rights
4. Directory database inaccessible

Solutions:

Test-Path "C:\Program Files\Avanteam\"

Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"}

sqlcmd -S .\SQLEXPRESS -d APS_Directory -Q "SELECT TOP 1 * FROM Application"

Manual solution:

1. Manually note the installation paths
2. Enter them directly in the interface fields
3. Modify connection strings if necessary

The detected version is incorrect

Symptoms:

• The displayed version does not match the actual version
• Error "Invalid version" at the next step

Causes:

• Corrupted AssemblyInfo file
• Incomplete or partial installation

Solutions:

// Check version in AssemblyInfo.cs file
// Location: C:\Program Files\Avanteam\APP\PStudio.Net.Web\bin\
// Look for the line:
[assembly: AssemblyVersion("23.14.0.0")]

Workaround:

1. Manually modify the version in the dropdown menu
2. Continue the upgrade
3. After the upgrade, the version will be correct

Missing applications in detection

Symptoms:

• Some applications are not listed
• Only the master application is detected

Solution:

-- Check in the directory database
SELECT Id, ProfileName, Version 
FROM Application 
WHERE IsDeleted = 0
ORDER BY Id

If applications are missing in AutoUpgradeTool but present in the DB:

1. Check that web directories exist
2. Check that connection strings are valid in web.config

Patch Selection Issues

Error "The patch is incompatible with this version of the tool"

Complete message:

The script 'xxx/files.fix' of the patch is incompatible with this version 
of the upgrade tool. A more recent version of autoupgradetool is required.

Solution:

1. Download the latest version of AutoUpgradeTool from Bastille:

   S:\3-PRODUIT\ReleaseUpgrades\AutoUpgradeTool\

2. Extract and restart with the new version

Error "Missing patch for upgrade X.X → Y.Y"

Cause: You are attempting a progressive upgrade but an intermediate patch is missing.

Example:

Current version: 23.10
Target version: 23.14
Available patches: v23.10.v23.12, v23.13.v23.14
❌ Missing patch: v23.12.v23.13

Solutions:

1. Option A: Download the missing patch from Bastille

   S:\3-PRODUIT\ReleaseUpgrades\Patches\v23.x\aps.upgrade.v23.12.v23.13.7z

2. Option B: Perform separate upgrades:
   • Upgrade 1: 23.10 → 23.12
   • (Download the patch v23.12.v23.13)
   • Upgrade 2: 23.12 → 23.14

The selected patch does not match my version

Symptoms:

• You selected aps.upgrade.v23.15.v23.16.7z
• Your current version is 23.14
• Validation error

Solution: Select the correct patch corresponding to your source version from Bastille:

Version 23.14 → Patch S:\3-PRODUIT\ReleaseUpgrades\Patches\v23.x\aps.upgrade.v23.14.v23.15.7z

Error "Unable to open .7z file"

Symptoms:

• Error during patch extraction
• Message "Corrupted archive" or "Unexpected end of archive"

Causes:

• Incomplete download from Bastille
• Network corruption
• Insufficient disk space

Solutions:

$OriginalFile = "S:\3-PRODUIT\ReleaseUpgrades\Patches\v23.x\aps.upgrade.v23.14.v23.15.7z"
$LocalFile = "C:\Avanteam\Patches\aps.upgrade.v23.14.v23.15.7z"

(Get-Item $OriginalFile).Length
(Get-Item $LocalFile).Length

Remove-Item $LocalFile -Force
Copy-Item $OriginalFile -Destination $LocalFile

Get-PSDrive C | Select-Object Used,Free

Issues During Version Upgrade

Error "Unable to stop service XXX"

Message:

Error | Unable to stop service 'PStudio.Services.Remoting-instance-APP'

Causes:

1. The service is blocked by a process
2. Insufficient administrator rights
3. Service in "Stopping" state

Solutions:

Stop-Service -Name "PStudio.Services.Remoting*" -Force

Get-Process | Where-Object {$_.Name -like "*PStudio*"}

Stop-Process -Name "PStudio.Services.Remoting" -Force

Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"}

In AutoUpgradeTool:

1. Click "Retry" after manually forcing the stop
2. Or click "Ignore" to continue (you will need to stop the service manually)

Error "Unable to stop IIS pool XXX"

Message:

Error | Unable to stop application pool 'APP_Pool'

Solutions:

inetmgr

Import-Module WebAdministration
Stop-WebAppPool -Name "APP_Pool"

Restart-WebAppPool -Name "APP_Pool"

Get-Process w3wp | Stop-Process -Force

iisreset /restart

SQL error during script execution

Message:

Error | Error executing script 'db/directory/001-upgrade-schema.sql'
Msg 2714, Level 16, State 1: There is already an object named 'TableName' in the database.

Causes:

1. Script already partially executed
2. Previous incomplete version upgrade
3. Manual database modification

Solutions:

-- 1. Check database version
SELECT TOP 1 * FROM VersionHistory ORDER BY AppliedDate DESC

-- 2. Identify already applied scripts
SELECT ScriptName FROM VersionHistory

-- 3. Check existence of problematic object
SELECT * FROM sys.objects WHERE name = 'TableName'

-- 4. If necessary, drop the object before retrying
-- (CAUTION: Check with an expert before dropping)
-- DROP TABLE TableName

Caution

Ignoring SQL errors can cause database inconsistencies. Always analyze the error before clicking "Ignore".

If you are unsure, contact Avanteam support.

"Access denied" error during file copy

Message:

Error | Access denied: Unable to copy file to 'C:\Program Files\Avanteam\...'

Causes:

1. File locked by a process
2. Insufficient rights
3. Antivirus blocking the operation

Solutions:

icacls "C:\Program Files\Avanteam\"

takeown /F "C:\Program Files\Avanteam\" /R /D Y


Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | Select-Object Name, Status
Get-WebAppPoolState -Name "*APP*"

"Timeout" error during execution of large SQL script

Message:

Error | Timeout expired. The timeout period elapsed prior to completion of the operation.

Causes:

• SQL script too long (large database)
• SQL server overloaded

Solutions:

Get-Content "C:\Program Files\Avanteam\.autoupgrade\logs\upgrade_*.log" | Select-String "Timeout"

sqlcmd -S .\SQLEXPRESS -d APS_Directory -i "script.sql" -t 0

Post-Upgrade Issues

Unable to connect to Process Studio Web

Symptoms:

• White page or 503 error
• "Service Unavailable"
• Connection timeout

Diagnosis:

Get-WebAppPoolState -Name "*APP*"

Get-Content "C:\inetpub\logs\LogFiles\W3SVC1\u_exYYMMDD.log" -Tail 50

Get-Content "C:\Program Files\Avanteam\APP\PStudio.Net.Web\Logs\*.log" -Tail 100

Get-EventLog -LogName Application -Source "ASP.NET*" -Newest 20

Solutions:

iisreset /restart

Restart-WebAppPool -Name "APP_Pool"

$WebConfig = "C:\Program Files\Avanteam\APP\PStudio.Net.Web\app\web.config"
Get-Content $WebConfig | Select-String "connectionString"

sqlcmd -S .\SQLEXPRESS -d APS_Directory -E -Q "SELECT 1"

Remove-Item "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\*" -Recurse -Force -ErrorAction SilentlyContinue

"Version mismatch" error after version upgrade

Symptoms:

• Message "The database version does not match the application version"
• Unable to access certain functionalities

Causes:

• SQL scripts not completely executed
• Application cache not cleared

Solutions:

-- 1. Check versions
-- Directory base:
SELECT TOP 1 * FROM VersionHistory ORDER BY AppliedDate DESC

-- Applications:
SELECT Id, ProfileName, Version FROM Application

Remove-Item "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\*" -Recurse -Force

Restart-WebAppPool -Name "APP_Pool"
iisreset /restart

The Scheduler no longer works

Symptoms:

• Scheduled tasks do not execute
• Scheduler service started but inactive
• Errors in Scheduler logs

Diagnosis:

Get-Service | Where-Object {$_.DisplayName -like "*Scheduler*"}

$SchedulerLogs = "C:\Program Files\Avanteam\APP\PStudio.Services\instance APP\Logs\"
Get-Content "$SchedulerLogs*.log" -Tail 100 | Select-String -Pattern "Error|Exception"

Solutions:

Restart-Service -Name "PStudio.Scheduler*"

sc.exe qc "PStudio.Scheduler.instance-APP"


sc.exe config "PStudio.Scheduler.instance-APP" start= auto
sc.exe config "PStudio.Scheduler.instance-APP" obj= "DOMAIN\ServiceAccount" password= "Password"

Degraded performance after version upgrade

Symptoms:

• Process Studio Web is slow
• Frequent timeouts
• High CPU/RAM consumption

Diagnosis:

Get-Process w3wp | Select-Object Name, CPU, WorkingSet

Get-IISAppPool | Select-Object Name, State, @{n="Uptime";e={(Get-Date) - $_.StartTime}}

Get-Counter '\Process(w3wp*)\% Processor Time' -SampleInterval 2 -MaxSamples 10

Solutions:

Get-IISAppPool | Where-Object {$_.Name -like "*APP*"} | Restart-WebAppPool



Remove-Item "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\*" -Recurse -Force

FAQ (Frequently Asked Questions)

General Questions

Q1: Does AutoUpgradeTool work with Oracle?

A: Yes, AutoUpgradeTool supports both SQL Server and Oracle as database systems. The tool automatically detects the type of database used.

Q2: Can I use AutoUpgradeTool to downgrade a version?

A: No, AutoUpgradeTool only supports upgrades, not downgrades. To revert to a previous version, you must restore your backups.

Q3: Can AutoUpgradeTool handle multiple instances on the same server?

A: AutoUpgradeTool detects and updates one instance at a time. If you have multiple instances on the same server, you must run the tool separately for each instance.

Q4: How long does a version upgrade take?

A: It depends:

• Minor upgrade (23.14 → 23.15): 10-20 minutes
• Major upgrade (21.25 → 23.0): 30-60 minutes
• Multi-application instance: Add 10 minutes per additional application
• Upgrade across multiple major versions (19.x → 26.x): 2-4 hours (with testing)

Q5: Do I need to manually stop services before running the tool?

A: No, AutoUpgradeTool automatically stops all necessary services and IIS pools. However, make sure no users are connected.

Q6: Can I use AutoUpgradeTool directly from the Bastille server?

A: Yes, but it's not recommended for production environments. Prefer copying the tool and patches locally to avoid network connection issues during the version upgrade.

Copy-Item "S:\3-PRODUIT\ReleaseUpgrades\AutoUpgradeTool\v2.4\*" -Destination "C:\Avanteam\AutoUpgradeTool\" -Recurse
Copy-Item "S:\3-PRODUIT\ReleaseUpgrades\Patches\v23.x\aps.upgrade.v23.14.v23.15.7z" -Destination "C:\Avanteam\Patches\"

Technical Questions

Q7: Where are version upgrade logs stored?

A: Logs are stored in a hidden directory:

C:\Program Files\Avanteam\APP\.autoupgrade\logs\
upgrade_YYYY-MM-DD_HH-MM-SS.log

You can access them via the "Open logs" button in the interface.

Q8: What does the generated README file contain?

A: The README file (readme_YYYY-MM-DD_HH-MM-SS.html) contains the list of manual actions to perform after the version upgrade, such as:

• Clear browser cache
• Recompile certain processes
• Update connectors
• Check specific configurations

Q9: Does AutoUpgradeTool modify business processes?

A: No, AutoUpgradeTool only modifies:

• Process Studio application binaries
• Database schemas (structure)
• System configuration files

Your business processes, workflows and application data are not modified.

Q10: Can I cancel a version upgrade in progress?

A: Yes, you can click "Abort" at any time. However, your instance will be in an intermediate state. You will then need to:

1. Analyze the logs to identify where the upgrade stopped
2. Either restore your backups
3. Or restart AutoUpgradeTool which will resume where it left off

Q11: How to verify that the version upgrade went well?

A: Perform these checks:

Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | Select-Object Name, Status

Get-WebAppPoolState -Name "*APP*"

Get-Content "C:\Program Files\Avanteam\APP\PStudio.Net.Web\Logs\*.log" -Tail 50 | Select-String -Pattern "Error|Exception"

sqlcmd -S .\SQLEXPRESS -d APS_Directory -Q "SELECT TOP 1 * FROM VersionHistory ORDER BY AppliedDate DESC"

Q12: Which Process Studio versions are supported?

A: AutoUpgradeTool supports the following versions:

• 19.x: from 19.0 to 19.25
• 21.x: from 21.0 to 21.25
• 23.x: from 23.0 to 23.18+
• 26.x: from 26.0 to the latest available version

Check the Bastille server to see all available patches: S:\3-PRODUIT\ReleaseUpgrades\Patches\

Questions About Errors

Q13: What to do if I get a SQL error "Transaction deadlock"?

A: This is generally a temporary problem. Solutions:

1. Click "Retry" in AutoUpgradeTool
2. If the error persists, check that no other connection is using the database:

   -- Identify active connections
   SELECT session_id, login_name, program_name, host_name
   FROM sys.dm_exec_sessions 
   WHERE database_id = DB_ID('APS_Directory')
   
   -- Kill blocking sessions if necessary (with caution)
   -- KILL [session_id]

Q14: "Timeout expired" error during SQL script execution

A: The script takes too long (large database). Solutions:

1. Identify the problematic script in the logs
2. Execute the script manually in SQL Server Management Studio with unlimited timeout
3. Click "Ignore" in AutoUpgradeTool after verifying that the script executed correctly

Q15: AutoUpgradeTool displays "out of memory"

A: This can happen with very large patches. Solutions:

1. Free up RAM (close unnecessary applications)
2. Increase Windows paging
3. Copy and extract the .7z patch locally rather than working from Bastille

Q16: Error "The file is being used by another process"

A: A file to be updated is locked. Solutions:

handle.exe "C:\Program Files\Avanteam\APP"

Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | Stop-Service -Force

Get-IISAppPool | Where-Object {$_.Name -like "*APP*"} | Stop-WebAppPool

iisreset /stop

Useful Diagnostic Commands

Complete diagnostic script

$Report = @()
$Report += "=" * 80
$Report += "PROCESS STUDIO DIAGNOSIS - $(Get-Date -Format 'yyyy-MM-dd HH:mm:ss')"
$Report += "=" * 80

$Report += "`n=== WINDOWS SERVICES ==="
Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | ForEach-Object {
    $Report += "$($_.Name.PadRight(50)) : $($_.Status)"
}

$Report += "`n=== IIS POOLS ==="
Get-IISAppPool | Where-Object {$_.Name -like "*APP*"} | ForEach-Object {
    $Report += "$($_.Name.PadRight(50)) : $($_.State)"
}

$Report += "`n=== FILE VERSIONS ==="
$AssemblyPath = "C:\Program Files\Avanteam\APP\PStudio.Net.Web\bin\PStudio.Net.dll"
if (Test-Path $AssemblyPath) {
    $Version = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($AssemblyPath).FileVersion
    $Report += "Binary version: $Version"
}

$Report += "`n=== DATABASE VERSION ==="
try {
    $SqlQuery = "SELECT TOP 1 Version, AppliedDate FROM VersionHistory ORDER BY AppliedDate DESC"
    $Result = Invoke-Sqlcmd -ServerInstance ".\SQLEXPRESS" -Database "APS_Directory" -Query $SqlQuery -ErrorAction Stop
    $Report += "DB version: $($Result.Version) (applied on $($Result.AppliedDate))"
} catch {
    $Report += "Error: Unable to retrieve DB version"
}

$Report += "`n=== DISK SPACE ==="
Get-PSDrive -PSProvider FileSystem | Where-Object {$_.Used -gt 0} | ForEach-Object {
    $FreeGB = [math]::Round($_.Free / 1GB, 2)
    $UsedGB = [math]::Round($_.Used / 1GB, 2)
    $TotalGB = [math]::Round(($_.Used + $_.Free) / 1GB, 2)
    $PercentFree = [math]::Round(($_.Free / ($_.Used + $_.Free)) * 100, 1)
    $Report += "$($_.Name): $UsedGB GB used / $TotalGB GB ($PercentFree% free)"
}

$Report += "`n=== LATEST WINDOWS ERRORS (Application) ==="
Get-EventLog -LogName Application -EntryType Error -Newest 5 | ForEach-Object {
    $Report += "$($_.TimeGenerated) - $($_.Source) : $($_.Message.Substring(0, [Math]::Min(100, $_.Message.Length)))..."
}

$Report | Out-String
$ReportPath = "C:\Temp\APS_Diagnostic_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
$Report | Out-File -FilePath $ReportPath -Encoding UTF8
Write-Host "`n✅ Report saved: $ReportPath" -ForegroundColor Green

Clean environment after failed upgrade

Write-Host "🧹 Cleaning Process Studio environment..." -ForegroundColor Yellow

Write-Host "`n1. Stopping services..." -ForegroundColor Cyan
Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | ForEach-Object {
    Write-Host "  - Stopping $($_.Name)..." -NoNewline
    Stop-Service $_.Name -Force -ErrorAction SilentlyContinue
    Write-Host " OK" -ForegroundColor Green
}

Write-Host "`n2. Stopping IIS pools..." -ForegroundColor Cyan
Get-IISAppPool | Where-Object {$_.Name -like "*APP*"} | ForEach-Object {
    Write-Host "  - Stopping pool $($_.Name)..." -NoNewline
    Stop-WebAppPool -Name $_.Name -ErrorAction SilentlyContinue
    Write-Host " OK" -ForegroundColor Green
}

Write-Host "`n3. Stopping residual processes..." -ForegroundColor Cyan
Get-Process | Where-Object {$_.Name -like "*PStudio*"} | ForEach-Object {
    Write-Host "  - Stopping process $($_.Name) (PID: $($_.Id))..." -NoNewline
    Stop-Process -Id $_.Id -Force -ErrorAction SilentlyContinue
    Write-Host " OK" -ForegroundColor Green
}

Write-Host "`n4. Clearing .NET caches..." -ForegroundColor Cyan
$CachePath = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\"
if (Test-Path $CachePath) {
    Remove-Item "$CachePath*" -Recurse -Force -ErrorAction SilentlyContinue
    Write-Host "  - Cache cleared" -ForegroundColor Green
}

Write-Host "`n5. Restarting IIS..." -ForegroundColor Cyan
iisreset /restart | Out-Null
Write-Host "  - IIS restarted" -ForegroundColor Green

Write-Host "`n6. Restarting Process Studio services..." -ForegroundColor Cyan
Start-Sleep -Seconds 5
Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | ForEach-Object {
    Write-Host "  - Starting $($_.Name)..." -NoNewline
    Start-Service $_.Name -ErrorAction SilentlyContinue
    Write-Host " OK" -ForegroundColor Green
}

Write-Host "`n✅ Cleanup completed!" -ForegroundColor Green

Log collection for support

$Date = Get-Date -Format "yyyyMMdd_HHmmss"
$OutputPath = "C:\Temp\APS_Logs_$Date"

Write-Host "📦 Collecting logs for Avanteam support..." -ForegroundColor Cyan

New-Item -ItemType Directory -Path $OutputPath -Force | Out-Null

Write-Host "`n1. AutoUpgradeTool logs..." -ForegroundColor Yellow
$AutoUpgradeLogs = "C:\Program Files\Avanteam\APP\.autoupgrade\logs\"
if (Test-Path $AutoUpgradeLogs) {
    Copy-Item "$AutoUpgradeLogs*" -Destination "$OutputPath\AutoUpgrade\" -Recurse -Force
    Write-Host "  ✅ Copied" -ForegroundColor Green
}

Write-Host "`n2. Process Studio logs..." -ForegroundColor Yellow
$PStudioLogs = "C:\Program Files\Avanteam\APP\PStudio.Net.Web\Logs\"
if (Test-Path $PStudioLogs) {
    Copy-Item "$PStudioLogs*" -Destination "$OutputPath\PStudioWeb\" -Recurse -Force
    Write-Host "  ✅ Copied" -ForegroundColor Green
}

$SchedulerLogs = "C:\Program Files\Avanteam\APP\PStudio.Services\instance APP\Logs\"
if (Test-Path $SchedulerLogs) {
    Copy-Item "$SchedulerLogs*" -Destination "$OutputPath\Scheduler\" -Recurse -Force
    Write-Host "  ✅ Copied" -ForegroundColor Green
}

Write-Host "`n3. Windows Event Logs..." -ForegroundColor Yellow
Get-EventLog -LogName Application -Newest 500 | Export-Csv "$OutputPath\EventLog_Application.csv" -NoTypeInformation
Get-EventLog -LogName System -Newest 500 | Export-Csv "$OutputPath\EventLog_System.csv" -NoTypeInformation
Write-Host "  ✅ Exported" -ForegroundColor Green

Write-Host "`n4. System configuration..." -ForegroundColor Yellow
systeminfo > "$OutputPath\SystemInfo.txt"
Get-Service | Where-Object {$_.DisplayName -like "*PStudio*"} | Out-File "$OutputPath\Services.txt"
Get-IISAppPool | Where-Object {$_.Name -like "*APP*"} | Out-File "$OutputPath\IIS_AppPools.txt"
Write-Host "  ✅ Exported" -ForegroundColor Green

Write-Host "`n5. Compression..." -ForegroundColor Yellow
$ZipPath = "C:\Temp\APS_Logs_$Date.zip"
Compress-Archive -Path $OutputPath -DestinationPath $ZipPath -Force
Write-Host "  ✅ Archive created" -ForegroundColor Green

Remove-Item $OutputPath -Recurse -Force

Write-Host "`n✅ Collection completed!" -ForegroundColor Green
Write-Host "`n📧 Send the following file to Avanteam support:" -ForegroundColor Cyan
Write-Host "   $ZipPath" -ForegroundColor White

Getting Help

Avanteam Support

If you cannot find a solution in this documentation:

1. Check detailed logs:

   C:\Program Files\Avanteam\.autoupgrade\logs\upgrade_*.log

2. Collect system information with the collection script above

3. Contact Avanteam support:

   • 📧 Email: support@avanteam.fr
   • 📞 Phone: [Your support number]
   • 🌐 Customer portal: [Your portal URL]

Information to provide to support

When requesting assistance, provide:

• Current Process Studio version
• Desired target version
• AutoUpgradeTool version used
• Log files (archive generated by the collection script)
• Screenshot of the error
• Step where the error occurred

Internal Avanteam Resources

• 📁 Bastille Server: S:\3-PRODUIT\ReleaseUpgrades\

  • Latest AutoUpgradeTool versions
  • All available patches
  • Technical documentation

• 📖 Online Documentation: https://docs.avanteam.fr

  • Process Studio user guides
  • Release notes
  • Technical articles

Additional Resources

• 📖 Introduction to AutoUpgradeTool
• 🛠️ Installation and configuration
• 📝 Step-by-step usage guide
• 🎯 Use cases and best practices
• 📁 Bastille Server: S:\3-PRODUIT\ReleaseUpgrades\

Related Articles

• AutoUpgradeTool
• ImportDocs
• Getting Started Guide