Closed ralf-escher closed 2 years ago
If I can get the full output from both, I might be able to see what's wrong
I did update my first posting with the full logs of the Run Pipeline script (I only removed most of the compiler warnings)
I think you pasted the successful attempt in both
Sorry! 😢 Fixed
I can see that you are restarting the container in the middle of things - what code do you use for doing this?
Write-Host "Installation of .NET AddIns requires restart of container" -ForegroundColor Yellow
Restart-BCContainer -containerName $containerName
Start-Sleep 2
I just remember that I made an update for the license file this morning (using secure files).
Update: replaced the license with an old version. It's working now. Thanks @freddydk for your help.
Remark: any chance to get a better error message for missing license for depending third-party apps?
Very strange that a bad license file would cause the session to be uninitialized. You could email me the faulty license file and I could have a look why this causes this. I might be able to solve this and give a better error.
Thanks
We've the same issue specifically after restarting the container due to a .NET dependency. We'll try a fresh license, but otherwise is there a root cause we can look for here?
Our license is the same as it's always been, so I'm surprised this has just started coming up now.
We had to exchange our license (expired), therefore I thought this is the cause for this issue. Meanwhile our IT has created several new versions of the license, but we still keep getting that error randomly for the On Premises version (we also have a .NET dependency). The .bclicense file is not working for us and with the .flf file we have major problems with the limited size (120kB).
Perhaps it is time related. We don't do a sleep after restart, so we've not had a success in builds as yet.
If your sleep is longer, say 5-10 seconds, any change?
We have found out, that the problem is "somehow" related to BcContainerHelper version 3.0.11.
Currently we force our routines to work with version 3.0.10 and (almost) everything works again.
"bcContainerHelperVersion": "3.0.10"
we have same problem we are using this function sequence: New-BcContainer Add-FontsToNavContainer Import-TestToolkitToBcContainer New-BCContainerBCUser Get-BcContainerServerConfiguration
Last function ends with mentioned error. We do not use container restart.
@freddydk , any thoughts here please?
We also use those same function @fridrichovsky .
If somebody can provide me access to a machine, which can repro the problem and a repro script - I will gladly connect, troubleshoot and fix the issue if possible.
Freddy I am also having this problem and I have a machine that I can give you access. Our license expires in 1 day and has been flashing a warning. It does not always fail however bc16 is doing it consistently. Just reach out to me if you still need. I'll try my new license later.
I get again this error on different machines. Thanks to freddy I have workaround (from another issue). Temporarily disable defender or other antivirus. It hepled me. I hope it wasn't just a coincidence. Maybe it will help you too.
Disabling AV temporarily doesn't appear to resolve this.
@ShadowXVII - please create a new issue with script and full output
The issue is exactly the same? I'm not sure what creating a new issue will provide here. Same scenario. Note that the OP is specifically using .NET addons, not Fonts as @fridrichovsky was. So perhaps fonts specifically are affected by AV whereas .NET isn't?
You can also paste your script and output here - the more info I can get the higher the chance is that I can see what is going on and why things are failing. What looks similar to you, might not be so similar after all.
The error that Get-NavServerInstance is not recognized - was fixed with this: https://github.com/microsoft/navcontainerhelper/commit/4739382992859f5fea3ab1e27921133d9553a0c4 (in 4.0.2)
That said - there might still be things failing, but I don't think you will get another case of Get-NavServerInstance is not recognized.
Therefore I always request full scripts (also to see whether people are running the latest version)
Shipped in 4.0.3
Fab, will try with 4.0.3+ to see if it's resolved for us.
We have no longer problems, using 4.02 currently
Yep, had two successful runs. Looks OK now.
We are using your CI/CD scripts for our pipelines. A few hours ago our Build Pipelines started to throw the following error for installing depended Apps for On Premises (Cloud works):
The term 'Get-NavServerInstance' is not recognized as the name of a cmdlet...
The routines are using BcContainerHelper version 3.0.11. This version was also used for the last successful run this early morning. We haven't changed anything within our pipelines, therefore we are clueless at the moment. Any idea?
last succesful run was this morning: