Closed MODUSCarstenScholling closed 1 year ago
This only happens with NextMajor? Will have a look whether this is another dotnet 6 problem. Thanks for reporting.
Hi Freddy, no, it is not. It is general für all images at least beginning with 20.2, most likely lower.
I have implemented a 10 times loop, waiting 5 seconds each and trying to get the test $form in PsTestFunctions.ps1 But still after 50 seconds, the $form could not be created (Write-Warning is not shown, but it takes 50 seconds to process).
$tries = 10;
do
{
$form = $clientContext.OpenForm($testPage)
if (!($form)) {
Write-Warning -Message "Could not open page $($testPage). Retrying in 5 seconds.";
Start-Sleep -Seconds 5;
$tries -= 1;
}
}
while(!$form -and ($tries -gt 0));
if (!($form)) {
throw "Cannot open page $testPage. You might need to import the test toolkit to the container and/or remove the folder $PSScriptRoot and retry. You might also have URL or Company name wrong."
}
2023-02-06T09:05:13.8395047Z Compilation ended at '10:05:12.930'.
2023-02-06T09:05:13.8400052Z
2023-02-06T09:05:13.9878003Z _____ _ _ _ _ _ _ _ _ _
2023-02-06T09:05:13.9890237Z |_ _| | | (_) | | | | | | | | | (_) |
2023-02-06T09:05:13.9901448Z | | _ __ ___ _ __ ___ _ __| |_ _ _ __ __ _ | |_ ___ ___| |_ | |_ ___ ___ | | | ___| |_
2023-02-06T09:05:13.9919428Z | | | '_ ` _ \| '_ \ / _ \| '__| __| | '_ \ / _` | | __/ _ \/ __| __| | __/ _ \ / _ \| | |/ / | __|
2023-02-06T09:05:13.9936482Z _| |_| | | | | | |_) | (_) | | | |_| | | | | (_| | | || __/\__ \ |_ | || (_) | (_) | | <| | |_
2023-02-06T09:05:13.9953356Z |_____|_| |_| |_| .__/ \___/|_| \__|_|_| |_|\__, | \__\___||___/\__| \__\___/ \___/|_|_|\_\_|\__|
2023-02-06T09:05:13.9970963Z | | __/ |
2023-02-06T09:05:13.9989375Z |_| |___/
2023-02-06T09:05:17.0478718Z Synchronizing Permissions Mock on default
2023-02-06T09:05:17.3269554Z App successfully synchronized
2023-02-06T09:05:17.3632716Z Installing Permissions Mock on default
2023-02-06T09:05:36.6053777Z App successfully installed
2023-02-06T09:05:36.6553507Z Synchronizing Test Runner on default
2023-02-06T09:05:37.1986779Z App successfully synchronized
2023-02-06T09:05:37.2134873Z Installing Test Runner on default
2023-02-06T09:05:37.9339340Z App successfully installed
2023-02-06T09:05:37.9830532Z Synchronizing Any on default
2023-02-06T09:05:38.0367530Z App successfully synchronized
2023-02-06T09:05:38.0508610Z Installing Any on default
2023-02-06T09:05:38.2544135Z App successfully installed
2023-02-06T09:05:38.3024361Z Synchronizing Library Assert on default
2023-02-06T09:05:38.3565039Z App successfully synchronized
2023-02-06T09:05:38.3732974Z Installing Library Assert on default
2023-02-06T09:05:38.5773439Z App successfully installed
2023-02-06T09:05:38.6223285Z Skipping app 'C:\Applications.DE\Microsoft_Permissions Mock_21.2.49946.52834.app' as it is already installed
2023-02-06T09:05:38.6707622Z Synchronizing Library Variable Storage on default
2023-02-06T09:05:38.7283196Z App successfully synchronized
2023-02-06T09:05:38.7426757Z Installing Library Variable Storage on default
2023-02-06T09:05:38.9774064Z App successfully installed
2023-02-06T09:05:48.5274371Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\e2331b51-946d-4faf-b088-cfe180ff8cb1\Microsoft_System Application Test Library_21.2.49946.52834.app
2023-02-06T09:05:54.4178304Z Synchronizing System Application Test Library on tenant default
2023-02-06T09:05:55.2567032Z Installing System Application Test Library on tenant default
2023-02-06T09:05:57.9721930Z App Microsoft_System Application Test Library_21.2.49946.52834.app successfully published
2023-02-06T09:06:08.0213970Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\aa51ae12-42e7-4b67-8652-0ad2f8277eab\Microsoft_Tests-TestLibraries_21.2.49946.52834.app
2023-02-06T09:06:17.9136434Z Synchronizing Tests-TestLibraries on tenant default
2023-02-06T09:06:19.2833481Z Installing Tests-TestLibraries on tenant default
2023-02-06T09:06:25.6515193Z App Microsoft_Tests-TestLibraries_21.2.49946.52834.app successfully published
2023-02-06T09:06:26.0971281Z TestToolkit successfully imported
2023-02-06T09:06:26.5539326Z
2023-02-06T09:06:26.5557410Z Importing Test Toolkit took 73 seconds
2023-02-06T09:06:26.5574624Z _____ _ _ _ _ _
2023-02-06T09:06:26.5592913Z / ____| (_) (_) | | | |
2023-02-06T09:06:26.5611075Z | | ___ _ __ ___ _ __ _| |_ _ __ __ _ | |_ ___ ___| |_ __ _ _ __ _ __ ___
2023-02-06T09:06:26.5628985Z | | / _ \| '_ ` _ \| '_ \| | | | '_ \ / _` | | __/ _ \ __| __| / _` | '_ \| '_ \/ __|
2023-02-06T09:06:26.5646742Z | |____ (_) | | | | | | |_) | | | | | | | (_| | | |_ __\__ \ |_ | (_| | |_) | |_) \__ \
2023-02-06T09:06:26.5664818Z \_____\___/|_| |_| |_| .__/|_|_|_|_| |_|\__, | \__\___|___/\__| \__,_| .__/| .__/|___/
2023-02-06T09:06:26.5684166Z | | __/ | | | | |
2023-02-06T09:06:26.5702056Z |_| |___/ |_| |_|
2023-02-06T09:06:26.5713868Z
2023-02-06T09:06:26.5732591Z Compiling C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\test
2023-02-06T09:06:28.6871320Z Updated C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\test\app.json preprocessorSymbols to PROD, CLEAN12, CLEAN13, CLEAN14, CLEAN15, CLEAN16, CLEAN17, CLEAN18, BC12, BC13, BC14, BC15, BC16, BC17, BC18, BC19, BC20, BC21.
2023-02-06T09:06:28.6896808Z Copying current dependencies to packages folder C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\.packages.
2023-02-06T09:06:33.3587095Z Using Symbols Folder: C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\.packages
2023-02-06T09:06:34.1341175Z Processing dependency Microsoft_Application_21.2.0.0 ()
2023-02-06T09:06:34.1364121Z Dependency App exists
2023-02-06T09:06:34.1383592Z Processing dependency Microsoft_System_21.0.0.0 ()
2023-02-06T09:06:34.1407448Z Dependency App exists
2023-02-06T09:06:34.1427699Z Processing dependency Microsoft_Tests-TestLibraries_21.2.0.0 (5d86850b-0d76-4eca-bd7b-951ad998e997)
2023-02-06T09:06:34.1466729Z Downloading symbols: Microsoft_Tests-TestLibraries_21.2.49946.52834.app
2023-02-06T09:06:34.1484420Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=5d86850b-0d76-4eca-bd7b-951ad998e997&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:34.1504796Z Using WebClient
2023-02-06T09:06:37.0460980Z Adding dependency to System Application Test Library from Microsoft
2023-02-06T09:06:37.0480739Z Adding dependency to Library Variable Storage from Microsoft
2023-02-06T09:06:37.0503022Z Adding dependency to Permissions Mock from Microsoft
2023-02-06T09:06:37.0523328Z Processing dependency MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.0.0 (b52e4deb-ef6a-45ce-8f0e-95b24e270862)
2023-02-06T09:06:37.0548784Z Dependency App exists
2023-02-06T09:06:37.0567766Z Processing dependency MODUS Consult GmbH_MODUS M365 Base_20.2.22121402.22121402 (ba5e92a6-b5c1-471d-ad51-1f407e627c27)
2023-02-06T09:06:37.0591494Z Dependency App exists
2023-02-06T09:06:37.0611602Z Processing dependency MODUS Consult GmbH_MODUS M365 Base Test_20.2.22121402.22121402 (80ae93f1-8e1d-4e59-a265-0f8141ffe6af)
2023-02-06T09:06:37.0635948Z Dependency App exists
2023-02-06T09:06:37.0655362Z Processing dependency MODUS Consult GmbH_MODUS M365 Delivery Date Determination_20.2.22113001.0 (2d749fca-44f5-49fa-bb4d-c4dd55f5711e)
2023-02-06T09:06:37.0677105Z Dependency App exists
2023-02-06T09:06:37.0697051Z Processing dependency MODUS Consult GmbH_MODUS M365 Delivery Date Determination Test_20.2.22113001.0 (06b17c18-e1b3-458b-8bbc-73846bf8883e)
2023-02-06T09:06:37.0720539Z Dependency App exists
2023-02-06T09:06:37.0746035Z Processing dependency MODUS Consult GmbH_MODUS M365 Tests-TestLibraries_18.0.22100401.22100401 (64d70f09-c534-4b17-948c-0d06a83cc8a7)
2023-02-06T09:06:37.0772363Z Dependency App exists
2023-02-06T09:06:37.0787911Z Processing dependency Microsoft_System Application Test Library_21.2.0.0 (9856ae4f-d1a7-46ef-89bb-6ef056398228)
2023-02-06T09:06:37.0886520Z Downloading symbols: Microsoft_System Application Test Library_21.2.49946.52834.app
2023-02-06T09:06:37.0905283Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=9856ae4f-d1a7-46ef-89bb-6ef056398228&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:37.0924367Z Using WebClient
2023-02-06T09:06:38.7563521Z Adding dependency to System Application from Microsoft
2023-02-06T09:06:38.7584003Z Adding dependency to Any from Microsoft
2023-02-06T09:06:38.7603189Z Processing dependency Microsoft_Library Variable Storage_21.2.0.0 (5095f467-0a01-4b99-99d1-9ff1237d286f)
2023-02-06T09:06:38.7642080Z Downloading symbols: Microsoft_Library Variable Storage_21.2.49946.52834.app
2023-02-06T09:06:38.7660085Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=5095f467-0a01-4b99-99d1-9ff1237d286f&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:38.7681113Z Using WebClient
2023-02-06T09:06:40.4516527Z Adding dependency to Library Assert from Microsoft
2023-02-06T09:06:40.4537135Z Processing dependency Microsoft_Permissions Mock_21.2.0.0 (40860557-a18d-42ad-aecb-22b7dd80dc80)
2023-02-06T09:06:40.4576243Z Downloading symbols: Microsoft_Permissions Mock_21.2.49946.52834.app
2023-02-06T09:06:40.4594651Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=40860557-a18d-42ad-aecb-22b7dd80dc80&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:40.4615225Z Using WebClient
2023-02-06T09:06:43.1775943Z Processing dependency Microsoft_System Application_21.2.0.0 (63ca2fa4-4f03-4f2b-a480-172fef340d3f)
2023-02-06T09:06:43.1797613Z Dependency App exists
2023-02-06T09:06:43.1817614Z Processing dependency Microsoft_Any_21.2.0.0 (e7320ebb-08b3-4406-b1ec-b4927d3e280b)
2023-02-06T09:06:43.1914665Z Downloading symbols: Microsoft_Any_21.2.49946.52834.app
2023-02-06T09:06:43.1932192Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=e7320ebb-08b3-4406-b1ec-b4927d3e280b&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:43.1950709Z Using WebClient
2023-02-06T09:06:44.8313344Z Processing dependency Microsoft_Library Assert_21.2.0.0 (dd0be2ea-f733-4d65-bb34-a28f4624fb14)
2023-02-06T09:06:44.8354433Z Downloading symbols: Microsoft_Library Assert_21.2.49946.52834.app
2023-02-06T09:06:44.8371710Z Url : http://172.20.147.44:7049/BC/dev/packages?appId=dd0be2ea-f733-4d65-bb34-a28f4624fb14&versionText=21.2.0.0&tenant=default
2023-02-06T09:06:44.8392018Z Using WebClient
2023-02-06T09:06:46.5587186Z Compiling...
2023-02-06T09:06:46.5620707Z .\alc.exe /project:"c:\sources\test" /packagecachepath:"c:\sources\.packages" /out:"c:\sources\.output\MODUS Consult GmbH_MODUS M365 Furniture Base Test_21.2.23020601.0.app" /assemblyprobingpaths:"C:\Program Files\Microsoft Dynamics NAV\210\Service","C:\Program Files (x86)\Open XML SDK\V2.5\lib","c:\Windows\Microsoft.NET\Assembly","C:\Test Assemblies\Mock Assemblies"
2023-02-06T09:06:51.7001675Z C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\.output\MODUS Consult GmbH_MODUS M365 Furniture Base Test_21.2.23020601.0.app successfully created in 23 seconds
2023-02-06T09:06:51.7058278Z MODUS Consult GmbH_MODUS M365 Furniture Base Test_21.2.23020601.0.app copied to C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\.packages
2023-02-06T09:06:52.1607658Z Microsoft (R) AL Compiler version 10.4.11.25929
2023-02-06T09:06:52.1626791Z Copyright (C) Microsoft Corporation. All rights reserved
2023-02-06T09:06:52.1638504Z
2023-02-06T09:06:52.1656825Z Compilation started for project 'MODUS M365 Furniture Base Test' containing '9' files at '10:06:46.831'.
2023-02-06T09:06:52.1668696Z
2023-02-06T09:06:52.1680643Z
2023-02-06T09:06:52.1698923Z Compilation ended at '10:06:51.647'.
2023-02-06T09:06:52.1710229Z
2023-02-06T09:06:52.1953252Z
2023-02-06T09:06:52.1971508Z Compiling apps, test apps and importing test toolkit took 184 seconds
2023-02-06T09:06:52.1990899Z _____ _ _
2023-02-06T09:06:52.2009867Z / ____(_) (_)
2023-02-06T09:06:52.2027738Z | (__ _ __ _ _ __ _ _ __ __ _ __ _ _ __ _ __ ___
2023-02-06T09:06:52.2045460Z \___ \| |/ _` | '_ \| | '_ \ / _` | / _` | '_ \| '_ \/ __|
2023-02-06T09:06:52.2063780Z ____) | | (_| | | | | | | | | (_| | | (_| | |_) | |_) \__ \
2023-02-06T09:06:52.2082545Z |_____/|_|\__, |_| |_|_|_| |_|\__, | \__,_| .__/| .__/|___/
2023-02-06T09:06:52.2100749Z __/ | __/ | | | | |
2023-02-06T09:06:52.2119848Z |___/ |___/ |_| |_|
2023-02-06T09:06:56.9252183Z Downloading Signing Tools
2023-02-06T09:06:57.1080746Z Installing Signing Tools
2023-02-06T09:07:02.5976666Z Signing c:\sources\.output\MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23020601.0.app
2023-02-06T09:07:03.2406865Z Done Adding Additional Store
2023-02-06T09:07:03.9808541Z Successfully signed: c:\sources\.output\MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23020601.0.app
2023-02-06T09:07:03.9825092Z
2023-02-06T09:07:04.4295099Z
2023-02-06T09:07:04.4313141Z Signing apps took 12 seconds
2023-02-06T09:07:04.4331104Z _____ _ _ _ _ _
2023-02-06T09:07:04.4350305Z |_ _| | | | | (_) (_)
2023-02-06T09:07:04.4368661Z | | _ __ ___| |_ __ _| | |_ _ __ __ _ _ __ _ __ _____ ___ ___ _ _ ___ __ _ _ __ _ __ ___
2023-02-06T09:07:04.4386382Z | | | '_ \/ __| __/ _` | | | | '_ \ / _` | | '_ \| '__/ _ \ \ / / |/ _ \| | | / __| / _` | '_ \| '_ \/ __|
2023-02-06T09:07:04.4404789Z _| |_| | | \__ \ || (_| | | | | | | | (_| | | |_) | | | __/\ V /| | (_) | |_| \__ \ | (_| | |_) | |_) \__ \
2023-02-06T09:07:04.4423112Z |_____|_| |_|___/\__\__,_|_|_|_|_| |_|\__, | | .__/|_| \___| \_/ |_|\___/ \__,_|___/ \__,_| .__/| .__/|___/
2023-02-06T09:07:04.4440781Z __/ | | | | | | |
2023-02-06T09:07:04.4458277Z |___/ |_| |_| |_|
2023-02-06T09:07:12.4959791Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\c888ffb4-a5e1-45c0-ac39-fa7dbbf0c3b9\MODUS Consult GmbH_MODUS M365 Foundation_20.0.23010403.23010501_app.app
2023-02-06T09:07:14.9086525Z Synchronizing MODUS M365 Foundation on tenant default
2023-02-06T09:07:15.4466133Z Installing MODUS M365 Foundation on tenant default
2023-02-06T09:07:17.3598886Z App MODUS Consult GmbH_MODUS M365 Foundation_20.0.23010403.23010501_app.app successfully published
2023-02-06T09:07:25.7427045Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\9c936f66-a197-4eaa-897f-2b52e42163e1\MODUS Consult GmbH_MODUS M365 Base_20.2.22121402.22121402_app.app
2023-02-06T09:07:29.6439064Z Synchronizing MODUS M365 Base on tenant default
2023-02-06T09:07:39.4902259Z Installing MODUS M365 Base on tenant default
2023-02-06T09:08:10.3665336Z App MODUS Consult GmbH_MODUS M365 Base_20.2.22121402.22121402_app.app successfully published
2023-02-06T09:08:18.4211765Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\33277b94-8e84-4332-947b-79988171e84b\MODUS Consult GmbH_MODUS M365 Packing Unit Management_20.2.22101302.22101302_app.app
2023-02-06T09:08:19.9881140Z Synchronizing MODUS M365 Packing Unit Management on tenant default
2023-02-06T09:08:21.3041644Z Installing MODUS M365 Packing Unit Management on tenant default
2023-02-06T09:08:24.5993786Z App MODUS Consult GmbH_MODUS M365 Packing Unit Management_20.2.22101302.22101302_app.app successfully published
2023-02-06T09:08:32.3635150Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\76859c06-ad85-46fa-95f1-0a908f47e166\MODUS Consult GmbH_MODUS M365 Delivery Date Determination_21.0.23011102.23011102_app.app
2023-02-06T09:08:33.2092115Z Synchronizing MODUS M365 Delivery Date Determination on tenant default
2023-02-06T09:08:33.7298020Z Installing MODUS M365 Delivery Date Determination on tenant default
2023-02-06T09:08:35.5028045Z App MODUS Consult GmbH_MODUS M365 Delivery Date Determination_21.0.23011102.23011102_app.app successfully published
2023-02-06T09:08:43.4980283Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\aec23b6e-b157-4805-9816-3167f399ecdf\MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23011201.23011201_app.app
2023-02-06T09:08:44.0812468Z Synchronizing MODUS M365 Furniture Base on tenant default
2023-02-06T09:08:49.0763211Z Installing MODUS M365 Furniture Base on tenant default
2023-02-06T09:08:55.7393382Z App MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23011201.23011201_app.app successfully published
2023-02-06T09:08:56.1997763Z
2023-02-06T09:08:56.2016897Z Installing apps took 112 seconds
2023-02-06T09:08:56.2034858Z _____ _ _ _ _ _
2023-02-06T09:08:56.2052427Z | __ \ | | | (_) | | (_)
2023-02-06T09:08:56.2069784Z | |__) | _| |__ | |_ ___| |__ _ _ __ __ _ __ _ _ __ _ __ ___
2023-02-06T09:08:56.2088005Z | ___/ | | | '_ \| | / __| '_ \| | '_ \ / _` | / _` | '_ \| '_ \/ __|
2023-02-06T09:08:56.2106828Z | | | |_| | |_) | | \__ \ | | | | | | | (_| | | (_| | |_) | |_) \__ \
2023-02-06T09:08:56.2124448Z |_| \__,_|_.__/|_|_|___/_| |_|_|_| |_|\__, | \__,_| .__/| .__/|___/
2023-02-06T09:08:56.2142602Z __/ | | | | |
2023-02-06T09:08:56.2160564Z |___/ |_| |_|
2023-02-06T09:08:57.6163261Z Publishing Current Dependent Apps
2023-02-06T09:08:59.2787253Z VERBOSE: Collecting and processing apps...
2023-02-06T09:08:59.3641379Z VERBOSE: Calculating app dependencies...
2023-02-06T09:08:59.4649019Z VERBOSE: Added app MODUS M365 Foundation 20.0.23010403.23010501 MODUS Consult GmbH.
2023-02-06T09:08:59.4670071Z VERBOSE: Added app MODUS M365 Base 20.2.22121402.22121402 MODUS Consult GmbH.
2023-02-06T09:08:59.4922585Z VERBOSE: Added app MODUS M365 Packing Unit Management 20.2.22101302.22101302 MODUS Consult GmbH.
2023-02-06T09:08:59.4944481Z VERBOSE: Added app MODUS M365 Delivery Date Determination 21.0.23011102.23011102 MODUS Consult GmbH.
2023-02-06T09:08:59.5130082Z VERBOSE: Added app MODUS M365 Tests-TestLibraries 18.0.22100401.22100401 MODUS Consult GmbH.
2023-02-06T09:08:59.5485629Z VERBOSE: Added app MODUS M365 Base Test 20.2.22121402.22121402 MODUS Consult GmbH.
2023-02-06T09:08:59.5507929Z VERBOSE: Added app MODUS M365 Delivery Date Determination Test 21.0.23011102.23011102 MODUS Consult GmbH.
2023-02-06T09:09:02.6719113Z Publishing MODUS M365 Tests-TestLibraries 18.0.22100401.22100401.
2023-02-06T09:09:09.9329314Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\fe321726-c713-480f-81f3-a2e511830e90\MODUS Consult GmbH_MODUS M365 Tests-TestLibraries_18.0.22100401.22100401_app.app
2023-02-06T09:09:10.1725701Z Synchronizing MODUS M365 Tests-TestLibraries on tenant default
2023-02-06T09:09:10.2653059Z Installing MODUS M365 Tests-TestLibraries on tenant default
2023-02-06T09:09:11.1710217Z App MODUS Consult GmbH_MODUS M365 Tests-TestLibraries_18.0.22100401.22100401_app.app successfully published
2023-02-06T09:09:11.6936887Z Publishing MODUS M365 Base Test 20.2.22121402.22121402.
2023-02-06T09:09:19.2845192Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\6afc66b5-d0dd-46fd-ae3e-4059b9147bc9\MODUS Consult GmbH_MODUS M365 Base Test_20.2.22121402.22121402_app.app
2023-02-06T09:09:19.8141232Z Synchronizing MODUS M365 Base Test on tenant default
2023-02-06T09:09:19.9138449Z Installing MODUS M365 Base Test on tenant default
2023-02-06T09:09:20.4170296Z App MODUS Consult GmbH_MODUS M365 Base Test_20.2.22121402.22121402_app.app successfully published
2023-02-06T09:09:20.9669527Z Publishing MODUS M365 Delivery Date Determination Test 21.0.23011102.23011102.
2023-02-06T09:09:28.2841277Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\60700f50-2b1b-43ad-9e99-f99aa86fc93c\MODUS Consult GmbH_MODUS M365 Delivery Date Determination Test_21.0.23011102.23011102_app.app
2023-02-06T09:09:28.4934978Z Synchronizing MODUS M365 Delivery Date Determination Test on tenant default
2023-02-06T09:09:28.5965075Z Installing MODUS M365 Delivery Date Determination Test on tenant default
2023-02-06T09:09:28.9438243Z App MODUS Consult GmbH_MODUS M365 Delivery Date Determination Test_21.0.23011102.23011102_app.app successfully published
2023-02-06T09:09:36.8707339Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\f4f73707-68da-4c98-9111-42d610e1cd86\MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23020601.0.app
2023-02-06T09:09:37.6680773Z Synchronizing MODUS M365 Furniture Base on tenant default
2023-02-06T09:09:38.8059462Z Upgrading MODUS M365 Furniture Base on tenant default
2023-02-06T09:09:41.0717058Z App MODUS Consult GmbH_MODUS M365 Furniture Base_21.2.23020601.0.app successfully published
2023-02-06T09:09:49.2319795Z Publishing C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\a617e56f-01bc-4982-83d7-1053f30f154c\MODUS Consult GmbH_MODUS M365 Furniture Base Test_21.2.23020601.0.app
2023-02-06T09:09:49.4114083Z Synchronizing MODUS M365 Furniture Base Test on tenant default
2023-02-06T09:09:49.5225553Z Installing MODUS M365 Furniture Base Test on tenant default
2023-02-06T09:09:49.8556653Z App MODUS Consult GmbH_MODUS M365 Furniture Base Test_21.2.23020601.0.app successfully published
2023-02-06T09:09:50.3212532Z
2023-02-06T09:09:50.3232723Z Publishing apps took 54 seconds
2023-02-06T09:09:50.3271753Z _____ _ _ _
2023-02-06T09:09:50.3290504Z | __ \ (_) | | | |
2023-02-06T09:09:50.3309072Z | |__) | _ _ __ _ __ _ _ __ __ _ | |_ ___ ___| |_ ___
2023-02-06T09:09:50.3326788Z | _ / | | | '_ \| '_ \| | '_ \ / _` | | __/ _ \/ __| __/ __|
2023-02-06T09:09:50.3344967Z | | \ \ |_| | | | | | | | | | | | (_| | | || __/\__ \ |_\__ \
2023-02-06T09:09:50.3363197Z |_| \_\__,_|_| |_|_| |_|_|_| |_|\__, | \__\___||___/\__|___/
2023-02-06T09:09:50.3381898Z __/ |
2023-02-06T09:09:50.3400326Z |___/
2023-02-06T09:09:50.4103776Z Running tests for App a319f893-1a48-4200-87c2-5be63a4d1b7d in C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\test
2023-02-06T09:09:58.1776506Z Connecting to http://localhost:80/BC/cs?tenant=default
2023-02-06T09:10:04.7696957Z Run-Tests, open page 130455
2023-02-06T09:10:55.1232005Z at Run-Tests, C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\PsTestTool\PsTestFunctions.ps1: line 551
2023-02-06T09:10:55.1252947Z at <ScriptBlock>, <No file>: line 75
2023-02-06T09:10:55.1554864Z Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\BcContainerHelper\Extensions\s16220-de21-2-49946-52834\PsTestTool and retry. You might also have URL or Company name wrong.
2023-02-06T09:10:55.1568557Z
Updated Information: Trying to open page 1 just before the test page fails too...
Running tests for App a319f893-1a48-4200-87c2-5be63a4d1b7d in C:\BuildAgents\MODUSSOLDEVAGT11\_work\10\s\test
Connecting to http://localhost:80/BC/cs?tenant=default
Run-Tests, open page 130455
Could not open page Company Information. What a worst!
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
Could not open page 130455. Retrying in 5 seconds.
at Run-Tests, C:\ProgramData\BcContainerHelper\Extensions\s16222-de21-4-52563-52836\PsTestTool\PsTestFunctions.ps1: line 557
In this state? does the container work? can you open the webclient and open the page manually?
I can try, but as this is a pipeline process and the last two debug attempts worked and did not show the error, how would I hold the process? Hmm...
I will try to send an email as soon as the issue occurs and then go to sleep for 5 mins in the script. Let me check if that works.
Or maybe - after the run-tests fails - download the event log from the container to see the reason. You can also try to downgrade containerhelper and the generic image to see whether this is a problem with a spceific version? Alternatively, if you could extract the script to a script I can run locally and troubleshoot - that would help.
I was also reported this issue in our Build pipelines.
_____ _ _______ _
| __ \ (_) |__ __| | |
| |__) | _ _ __ _ __ _ _ __ __ _ | | ___ ___| |_ ___
| _ / | | | '_ \| '_ \| | '_ \ / _` | | |/ _ \ __| __/ __|
| | \ \ |_| | | | | | | | | | | | (_| | | | __\__ \ |_\__ \
|_| \_\__,_|_| |_|_| |_|_|_| |_|\__, | |_|\___|___/\__|___/
__/ |
|___/
Test Company Name () and/or TestCompany Datapack () missing for YTEMPL
Connecting to http://localhost:80/BC/cs?tenant=default
at Run-Tests, C:\ProgramData\BcContainerHelper\Extensions\cicd03-YWHSRF-current\PsTestTool\PsTestFunctions.ps1: line 537
at <ScriptBlock>, <No file>: line 75
Cannot open page 130455. You might need to import the test toolkit to the container and/or remove the folder C:\ProgramData\BcContainerHelper\Extensions\cicd03-YWHSRF-current\PsTestTool and retry. You might also have URL or Company name wrong.
Exception Script Stack Trace:
at Run-Tests, C:\ProgramData\BcContainerHelper\Extensions\cicd03-YWHSRF-current\PsTestTool\PsTestFunctions.ps1: line 537
at <ScriptBlock>, <No file>: line 75
PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\4.0.14\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at Run-TestsInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\4.0.14\AppHandling\Run-TestsInNavContainer.ps1: line 377
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 568
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 1286
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 1240
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 1235
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 616
at global:Run-AlPipelineINECTA, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\Run-AlPipelineINECTA.ps1: line 585
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\DevOps-Pipeline2.ps1: line 150
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\45\s\scripts\DevOps-Pipeline.ps1: line 48
at <ScriptBlock>, C:\Users\vmadmin\Downloads\vsts-agent-win-x64-2.210.1\_work\_temp\a9ce0b2f-5c1b-480a-b777-14fd67127ee4.ps1: line 4
at <ScriptBlock>, <No file>: line 1
I will provide more details as I dig in.
For now I can confirm that the toolkit was successfully imported.
Listng Apps before Test Toolkit Import iNECTA App: cicd02-YEXLOT-current : YIBASE - Base App 2023.1.15.1 Synchronizing Permissions Mock on default App successfully synchronized Installing Permissions Mock on default App successfully installed Synchronizing Test Runner on default App successfully synchronized Installing Test Runner on default App successfully installed Synchronizing Any on default App successfully synchronized Installing Any on default App successfully installed Synchronizing Library Assert on default App successfully synchronized Installing Library Assert on default App successfully installed Skipping app 'C:\Applications.US\Microsoft_Permissions Mock_21.4.52563.52939.app' as it is already installed Synchronizing Library Variable Storage on default App successfully synchronized Installing Library Variable Storage on default App successfully installed Publishing C:\ProgramData\BcContainerHelper\Extensions\cicd02-YEXLOT-current\9a24f175-78ef-410a-8553-1860a69c59b8\Microsoft_System Application Test Library_21.4.52563.52939.app Synchronizing System Application Test Library on tenant default Installing System Application Test Library on tenant default App Microsoft_System Application Test Library_21.4.52563.52939.app successfully published Publishing C:\ProgramData\BcContainerHelper\Extensions\cicd02-YEXLOT-current\3c1d2ca8-666a-4936-9fa6-e272b992e64b\Microsoft_Tests-TestLibraries_21.4.52563.52939.app Synchronizing Tests-TestLibraries on tenant default Installing Tests-TestLibraries on tenant default App Microsoft_Tests-TestLibraries_21.4.52563.52939.app successfully published TestToolkit successfully imported
@freddydk I was able to access the container when in failed state. The page was available through page=130455. I was also able to download the event log, but have problems to identify potential issues. Sending the full log by email. The login issues at the end (tenant stuff) was caused by me when logging in).
How would I force creating an image like on Tuesday? I know to downgrade BCCH but assume changes to the image causing the errors.
@MODUSCarstenScholling - looking at the eventlog - you are still using the old image:
Generic Tag: 1.0.2.13
Looking in the eventlog - it looks like a tenant is not specified (which os strange because the url states ?tenant=default
Will try to repro the problem. Easiest thing was if you could extract the code from your pipeline and run it locally with the same result - then I can run with that script
Hmm, not sure from where exactly the generic tag comes, but all of our latest (failing) runs referencing the new one:
Multitenant: Yes
Version: 20.2.41144.51968
Platform: 20.0.41086.51784
Generic Tag: 1.0.2.14
Container OS Version: 10.0.17763.3887 (ltsc2019)
Host OS Version: 10.0.17763.3887 (ltsc2019)
it looks like a tenant is not specified
Was this on the top of the log? That was me, trying to login without a tenant.
I'll try to get this "working" within a simple script, hold on.
Thanks - I have tried all kinds of settings in various AL-Go repos, but cannot repro this problem.
Well, unfortunately that was not quite as successful as expected. I am not able to recreate the problem outside of the Azure DevOps Agent. All attempts, both on Windows 11 and Windows Server 2019 were successful without errors. Even an "original call*" worked flawlessly several times. That means 10 runs with 3 containers each (21.2, 21.4, 22.0) on 3 computers, multiple times. I have done nothing else the entire day.
*Original call:
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'C:\Temp\tests\run\start-run.ps1'"
However, the problem still occurs in the Azure DevOps Agent context, even after a downgrade to BCContainerHelper 4.0.10, with which it worked perfectly until Wednesday.
Doesn't this suggest that a change to the generic image is causing it? How can I test the old image with the generic tag: 1.0.2.13? How can I force it?
You can use the setting genericImageName (which you can set in c:\programdata\bccontainerhelper\bccontainerhelper.config.json or in code:
$bcContainerHelperConfig.genericImageName = "mcr.microsoft.com/businesscentral:{0}-1.0.2.13"
then it will select 1.0.2.13 for you. The {0} will be replaced by the windows version
Oh, I was not aware of this particular notation. Thank you, will test and get back.
@vivek-jindal Were you able to gather more information regarding your issue?
Not yet but this is on my high priority list.
For me this issue is intermittent. I am not able to reproduce the issue always.
If I rerun the same pipeline multiple times it gets completed in third or fourth attempt.
Same here, except for the priority which is on top of the list. We are currently running on mcr.microsoft.com/businesscentral:{0}-1.0.2.13 and latest ContainerHelper 4.0.14. No unexpected issues so far. I have expected only BC 22 builds to fail, but have not seen errors yet.
@freddydk From what I can say after dozens of runs: All containers except newer .NET 6 BC22 containers work. BC22 with .NET 6 raises intermittent errors when calling any page from the client context. This is based on mcr.microsoft.com/businesscentral:{0}-1.0.2.13 generic image and the latest ContainerHelper 4.0.14.
Before, this applied to all images/containers containing the .NET 6 installation, independent of the used BC version 20, 21, 22. You see, only the installation itself causes the bug. We have around 60% fails (one of the 3 containers) in pipelines when .NET 6 is installed.
What can we do to avoid this? Unfortunately, this error only occurs in Azure DevOps context and started with the latest changes in BCContainerHelper and the generic image, without changing something in our scripts.
So, you are saying if you use:
mcr.microsoft.com/businesscentral:{0}-1.0.2.14
then everything fails?
if you use
mcr.microsoft.com/businesscentral:{0}-1.0.2.13
then 22.0 (next major) fails
On Azure DevOps agents.
Do you have dotnet6 on the agents?
That is correct regarding the generic images if started from the Azure DevOps agent service. But it is intermittent. It does not always fail, but if, then like you described above.
.NET 6 is not installed on the agent computers itself. I had thought of this, but dismissed the idea at first, as the problem does not always occur. But I will keep that in mind.
I would first like to pursue another idea that came to me while driving earlier: Run-AlPipeline runs with Isolation process. I would like to switch this to hyperv as a test and observe it for some runs. I'll keep you updated.
I am cautiously optimistic that the switch to hyperv isolation could solve the problem. No test page errors after 20 runs (3 containers each) since yesterday evening using generic image 1.0.2.14 for everything again.
Maybe - when using process isolation - dotnet6 needs to be installed on the host? I mean when using process isolation, it uses the windows version on the host and not what's in the container.
I can no longer reproduce the issue using hyperv isolation.
Maybe - when using process isolation - dotnet6 needs to be installed on the host?
The issue may be something else as it can't be reproduced all the time.
@freddydk I will test process isolation with installed .NET 6 after my vacation before the end of February and let you know the result.
@vivek-jindal Great, good to know.
Maybe - when using process isolation - dotnet6 needs to be installed on the host?
The issue may be something else as it can't be reproduced all the time.
Agree
Looking for other people with the same problem and a consistent repro in order to investigate more.
What I see after 2 weeks now is that running with hyperv isolation makes the builds much more stable. No more timeout or other issues since the change. Probably worth thinking about an "isolation" parameter for Run-AlPipeline to make it easier to handle?
Thanks for the feedback - will make sure to incorporate this somehow.
My customer was having this issue only on parallel builds. Just switched to hyperv and the problem is solved.
Our pipelines thus build vms are experiencing the same problem. After setting the generic image to mcr.microsoft.com/businesscentral:{0}-1.0.2.13 and installing the latest dotnet 6 the problem seems to be solved. Nonetheless we are looking forwared to a general solution.
What I see after 2 weeks now is that running with hyperv isolation makes the builds much more stable. No more timeout or other issues since the change. Probably worth thinking about an "isolation" parameter for Run-AlPipeline to make it easier to handle?
The way to do this today is to use
$bcContainerHelperConfig.defaultNewContainerParameters = @{
"isolation" = "hyperv"
}
or set this in the config file - then all new containers on that machine runs hyperv. I am running 4 agents per computer with everything default and haven't seen any issues. I use https://aka.ms/getbuildagent or the script listed here: https://github.com/microsoft/AL-Go/issues/518
If somebody have a consistent repro that you would like me to investigate, please ping me.
Closing this one
I added the hyperv isolation config to all my build machines some weeks ago and I have the same results.
Cannot open page 130455 - Problems since Thursday, beginning with 4.0.11
Description
Our pipelines started to raise ContainerHelper and/or container/image releated errors on 02-02-2023 around noon after BcContainerHelper was updated to version 4.0.11 in the process. The issue changed up to 4.0.14. We are running our pipelines on Azure DevOps Server, local agent machines with 2 agents each. Our pipeline code did not change in the last days. We usually test run against Sandbox images Minimum (min. application version), Current, NextMajor.
We did image cleanups in the middle to find issues, which caused new image creations with newer builds.
Cannot open page 130455
The final issue is that the test page cannot be opened, not only for NextMajor but for 20, 21, 22... Sometimes it works, most times this error is raised.
Our release day is Wednesday this week, but we have no reliable builds, no reliable pipelines anymore. Even skipping NextMajor does not work anymore. My assumption is, it could be some timing issue, probably in the image scripts.
PLEASE HELP AND ASSIST.
Below I have outlined the way to this error, paved with other errors.
Parameters and overrides
Command
SKIPPED OTHER ISSUES DUE TO SIZE LIMIT
ISSUE 03-02-2023 0913 AGENT1 (FAILING)
We had several failing builds with this error. Then we recreated the agents, updated BCCC, Updated Docker.
BCCC 4.0.14 (Minimum, working)
BCCC 4.0.14 (Current, working)
BCCC 4.0.14 (NextMajor, FAILED)