Closed aetxebarria closed 5 years ago
How are you creating the container? Do you use clickonce?
I've created with this command:
New-CSideDevContainer -containerName BeteaBC -accept_eula -auth NavUserPassword -imageName "microsoft/bcsandbox:es" -licensefile "C:\6045219-desa2018.flf" -alwayspull -accept_outdated
You are using a very old version of NavContainerHelper. New-CsideDevContainer has been removed for several months. Update NavContainerHelper and use New-NavContainer - use -includecside if you need cside.
Hi Fredy,
I have the 0.5.0.11 version. according to your blog, the last one, am I right? I've removed the container, and created a new one with:
New-NAVContainer -containerName BeteaBC -accept_eula -auth NavUserPassword -imageName "microsoft/bcsandbox:es" -licensefile "C:\6045219-desa2018.flf" -alwayspull -accept_outdated -includecside
And I still have the problem. The error message jsut appears in the home landing page, if I go to another page, I don't see the error...
Appart from this issue, I have another dpubt. According to the last changes sghown in dierctions Asia, in where can I get the image version for 2019 fall?
Thanks for everything
We will start building fall images later - not sure when yet. 0.5.0.11 is the latest - what do you mean when referring to the home landing page - do you mean the new-navcontainer output? what error do you get?
When I log into the cliente, is the first I see:
If I chaneg to any other page, customer list for example, I don't see the error again.
i activated the debugger, retunr to the home page, and the debugger stops here:
Seems to be a problem with the O365 integration.
This of course shouldn't happen but in general, the sandbox images thinks they are an online saas service and as such thinks that they are connected to AAD, we have seen this give problems a number of times. You could consider using the onprem images instead, they won't have this problem.
So, instead of pulling the bcsandbos image, pulling a different one? Which would you recommend?
Thank you very much
Just tried to run the exact same line as you - I do not get an error:
use mcr.microsoft.com/businesscentral/onprem:es that is spring release.
/Freddy
Ok, Thank you as always!
Hi Freddy, Sorry for disturbing. I have tried to install the new image, but I don't have enough space. I read your article about cleaning the docker. So, i tried to delete all the content from "C:\ProgramData\docker". The content was very large, and at one time, I stopped the process, thinking that I will lose data for other developments. And when I try to deploy the image, I found errors like: After, with the aim of cleanning the content in a controlled way, I downloaded the script and I get this error:
What should I do? SHould I delete all the content from the docker folder? Did I broke something? Can I restore the missing folders?
Thank you very much
It says: Type yes to continue. You typed y Type yes - then it should clean your docker installation and navcontainerhelper folder.
I have had to restore all the docker feature in the server, and pull again the image. Now I don't get the error, but in the role center:
Anyway, it's not a big issue, it's just for developing so doesn't seem to be a problem
Very strange - it almost seems like the files are blocked so that the service tier cannot load the DLL's - maybe an antivirus problem?
I don't think so, it's an azure machine, I don't have any antivirus installed. The previos container didn't have this problem, seems to have relation wih the version....
Windows server 2016 or 2019?
Windows server 2016 datacenter
Ok, I am running 2019 - will try 2016.
Just tried with a new 2016 - works fine - cannot repro this.
Ok Freddy, really appreciate your help and view
Hi everyone, I've just created a new docker with the last version pulled from bcsandbox. Looks that everything has been allright, but when I open the windowsClient, I see this error:
Any hint about his issue?