Fixed Issues and Known Issues

5 min read

Copy
Link copied
Print
Download

Fixed Issues in Aras DevOps Release 1.14.1

Issue #	Description
IH-17414	`repo-init.ps1` now defaults to .NET 10, automatically installing it if a suitable version is not available on the machine.
IH-10961	Aras DevOps has been extended to support deploying Aras Innovator releases, which are running on .NET 10.
IH-10618	Introduced the Release Innovator pipeline that provides a standardized and automated way to deliver updates to Aras Innovator SaaS environments while keeping release operations simple, predictable, and governed.
IH-9215	Baseline updates are now picked up automatically after being uploaded to the SDE feed, allowing CI/CD pipelines to run without additional manual steps or support involvement.
IH-9214	Automated the downloading of baseline artifacts during `repo-init.ps1` script when they are not found locally by the path specified in `Machine.Specific.include` file.
IH-8436	SaaS infrastructure has been migrated to Traefik to align with the modern SaaS platform architecture.
IH-10973	Deploy pipeline running with update strategy in SaaS environment is no longer fail when deployments are provisioned with multiple regions. Delta deployments now succeed consistently regardless of how many times they are applied to an existing multi-region deployment.
IH-11616	GenerateBaseline pipeline is no longer failing with an out-of-memory error when processing baselines with a large number of files. Baseline generation now succeeds consistently, regardless of the number or size of archived files.
IH-11210	`New-ArasDevOpsRepository` `cmdlet` is no longer failing due to the deprecated Nuget list command. Repository creation now succeeds consistently without errors.
IH-10956	Continuous integration pipeline in SaaS environments is no longer failing on the Disable High Availability step. The High Availability disable operation now completes successfully without unnecessary retries or delays.

Known Issues in Aras DevOps Release 1.14.1

Issue #	Description	Workaround
I-050998	When a user executes The Get-ArasDevopsPackagesList of the Powershell module, only the latest versions are displayed for IOM and InnovatorConfigs. It should display this package’s latest version of the current Innovator version.	The commandlet was originally created due to nuget.exe failure to display upstream package versions when listing. Standard Find-Package is capable of properly listing packages and this commandlet is not needed anymore. Get-ArasDevopsPackagesList command is therefore obsolete and will be deprecated.
I-058395	In the Local Development Environment, the BuildAndDeploy.ps1 fails on the install step of Visual Studio 2022 Build Tools when there is a pre-existing installation of Visual Studio Build Tools.	1. Uninstall Visual Studio Installer and all build tools with their dependencies. `> choco uninstall visualstudio2019-workload-webbuildtools` `> choco uninstall visualstudio2019-workload-databuildtools` `> choco uninstall visualstudio2019buildtools` `> choco uninstall visualstudio2022buildtools` `> choco uninstall visualstudio-installer` 2. Reset Powershell session. 3. Run the script again and let the tool install everything it needs: Import-Module Aras.DevOps Install-BuildMachinePrerequisites -InnovatorVersion <version> 4. In case the problem is not resolved by following the steps above, or the choco packages are not installed in the first place, download visual studio installer (if not already installed) and perform the following steps: Open Visual Studio Installer, for both 2022 and 2019 versions, export the configuration separately to dedicated files. The export option is under the More button. These files will be modified and re-imported. Open a Powershell terminal and run> explorer (join-Path (Get-Module Aras.DevOps).Path "\..\nesources”) For reference, open vsbuildtools2019.vsconfig file in your text editor. DO NOT Modify the file. Edit the 2019 configuration exported in step 4 a, to remove all components listed in the vsconfig file. Import 2019 configuration back into the Visual Studio Installer, by clicking on “More” and selecting “Import configuration.” Perform steps 3 & 4 for the 2022 version of visual studio, using vsbuildtools2022.vsconfig file. Note: If only one of the two versions above exists, perform the steps only for that version.
I-058883	In the Local Development Environment, ContinuousIntegration.ps1 fails if using Aras Innovator Container Deployment in Aras Enterprise and displays the following error: <The sp_configure value “contained database authentication” must be set to 1 in order to restore a contained database. You may need to “RECONFIGURE” to set the value_in_use. RESTORE DATABASE is terminating abnormally>	In the SQL Server on the local machine, enable the contained database authentication option. The option can be enabled by two ways: 1. Follow steps in: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/contained-database-authentication-server-configuration-option?view=sql-server-ver16 2. Configure the option using SQL Server Management Studio properties
I-059096	When deploying on a local machine, users may see an error message directly from SQL Server that the password validation failed. The error message may look like:"System.Data.SqlClient.SqlException: Password validation failed. The password does not meet the operating system policy requirements because it’s too short”	Deployment of Aras Innovator on a user’s machine relies on local SQL Server that defines policies for SQL user passwords. Aras uses 2 SQL users named “innovator” and “innovator_regular”. Passwords used during deployment are defined in Machine.Settings.include Make sure that both users can log into SQL Server using defined password before launching new deployment.
I-059899	When an existing project moves to a container-based deployment, it is possible that the initial repository contains some modified configuration files. In this case, the deployment will not be successful.	A customer repository should not contain any configuration files. The modifications to configuration files that might be required in the context of a project needs be described using Config Transformations feature available with the service.
I-072044	Chocolatey Version Update In Aras DevOps 1.10, an updated version of Chocolatey is now used to meet enhanced security requirements. Since two versions of Chocolatey cannot run simultaneously on the same machine, users must manually downgrade Chocolatey if they need to work on projects that reference an older version of Aras DevOps.	Manually downgrade the version of Chocolatey.
I-073506	The Generate Baseline pipeline may intermittently fail when used with unpatched Aras Innovator versions lower than Release 32.	Retry the Generate Baseline pipeline execution.
IH-10423	After upgrading to Aras DevOps 1.13, the Selenium Tests pipeline may fail (pipeline status turns yellow) when used on Software Development Environments (SDEs) running Aras Innovator 14.0.6 or earlier. This occurs because updated test logic in BDS 1.13 is no longer compatible with end-of-life Aras Innovator versions. Upgrade Aras Innovator to a supported version to restore compatibility.