Closed FelixHaemsch closed 3 months ago
Is that output a result from that script?
vs.
I am sorry. It seems that I copied the output from a previous attempt. I tried using different versions in case 23.3 was corrupted. I got the same error no matter what version I used. I edited my original post to correct this issue.
I have a repro of this now - and it seems to go away if you use onprem artifacts. It works with artifacts prior to 23.0 with sandbox artifacts.
Please try to add -type onprem to your get-bcartifacturl and see if this solves the issue?
Thank you very much for your fast feedback. I will try it and report back asap.
@freddydk Thank you for your Feedback
I tried it with the following image and it worked and created the Container -artifactUrl "https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/onprem/24.3.21374.21517/ch"
So its a problem with the Sandbox image from Microsoft?
I was finally able to try it and it worked like a charm. Thank you very much for your assistance.
@freddydk so are we supposed to use the onprem artifacts now? this breaks our scripts... Will there be a proper fix for this?
I don't know what happened here - but could see that this problem persists with version 23 as well as 24. Due to that, I have to prioritize this lower as a lot of the other things I have. If somebody can find out why this happens, I am open to review a PR or create a bug on the responsible team - else it will have to wait until I have the time.
I don't know what happened here - but could see that this problem persists with version 23 as well as 24. Due to that, I have to prioritize this lower as a lot of the other things I have. If somebody can find out why this happens, I am open to review a PR or create a bug on the responsible team - else it will have to wait until I have the time.
Hi Freddy - since this ticket was closed, I had created a new one, but am not seeing any responses over there 3605. I have more details in that issue, but the point in the process that I am seeing differences and that usually it creates 3 databases(prefix-default, prefix-CRONUS and prefix-tenant) - it is no longer creating the prefix-tenant database, but still writing the log of 'Success' to the file databasescreated.txt(with the containername in front). Then it goes on to try to start the BC service and fails. I have also tried with a number of versions of bccontainerhelper(and preview versions), even older known working ones cannot create a sandbox container.
This issue has completely diminished our ability to work effectively. I have a team of 8 developers that cannot work on issues related to customer data. We use these bccontainerhelper tool extensively and have automated processes that happen when a ticket comes in - our tools generate a bacpac export, then it creates a docker container for their version of BC and mounts the customers database to the container. Many of these customers have databases greater than 10gb and cannot use SQL Express. Since all of them are on Cloud, they are all on v24, and no version of v24 currently creates a container successfully when using an external sql server.
@kevindstanley - you should respond to the open issue.
Description I want to create a BC 23.3 container with external database on local sql server 2019. The scripts fails when trying to start the bc server instance. When I create the container without an external database it works. I also tried combinations of windows and NAVUserPassword authentication and process and hyperv isolation. The database is created successfully on my local sql server. I tried using PS 7.42 and PS 5.1
Scripts used to create container and cause the issue
Full output of scripts
Container Event Log
Edit 1: corrected full output of script, becouse it was from a previous attempt with another version