Closed petertijsma closed 2 years ago
waldo1001
commented
2 years ago Hi,
The ALOps Extension API is merely the API call - since this is working, it seems find.
The deployment is (educated guess) ALOps.ExternalDeployer - and that one is ging back the error, I assume.
Is this always happening with every deploy or just once? If once - could it be that at that point, someone was either opening the deployment status page (which you shouldn't do), or working in the extension management page?
petertijsma
commented
2 years ago I've seen this at (almost) every deployment in BC20. One difference with BC18 is that for this TST Environment with BC20, I'm not first stopping the Client Service Instances. On the other hand, this should not be necessary. Also, I was not even actively working in the system when the Deployment ran, so no-one was even on the Deployment Page, nor am I updating something related to this page.
Latest output from the ALOps.ExternalDeployer (the last one from approx 1 hour ago):
2022-08-24T13:44:35.1378Z *** Package Data File => [C:\Users\svc_navision\AppData\Local\Temp\tmp5779.tmp.app]
2022-08-24T13:44:35.1458Z *** ServerInstance = [CLIENT-CLEANBC20]
2022-08-24T13:44:35.1508Z *** ContainerId = []
2022-08-24T13:44:35.1538Z *** Tenant = [default]
2022-08-24T13:44:35.1588Z *** Loading ALOps.ExternalDeployer
2022-08-24T13:44:35.8468Z *** Loading assemblies from: [C:\program files\microsoft dynamics 365 business central\200\service]
2022-08-24T13:44:36.0178Z * App.ID = 86f674f1-0913-437a-955d-d6e5b062ce46
2022-08-24T13:44:36.0228Z * App.Name = OGDT Core
2022-08-24T13:44:36.0278Z * App.Publisher = Optimum Group
2022-08-24T13:44:36.0328Z * App.Version = 20.1.202235.9703
2022-08-24T13:44:36.4838Z => Publishing App 'OGDT Core v20.1.202235.9703'
2022-08-24T13:44:36.4898Z *** Publish per Tenant
2022-08-24T13:44:46.6559Z *** Get Tenants
2022-08-24T13:44:46.8449Z *** Sync Tenant default
2022-08-24T13:44:46.8819Z *** Sync App [OGDT Core] on tenant [default]
2022-08-24T13:44:49.0499Z *** Tenant Dataupgrade default
2022-08-24T13:45:28.8917Z *** Install App [OGDT Core] on tenant [default]
2022-08-24T13:45:28.9577Z * UnPublishing Old App 'OGDT Core v20.1.202235.9663'.
And the Pipeline shows this:
waldo1001
commented
2 years ago Can you check upgrade/install code, try to debug? Can you check if you're doing something funky in your extension? For example anything that has extended objects that are necessary during deployment?
The upload on page is a different feedback than the API:
We need to search for the thing that fails the deployment throught the API .. 🤔. I'm assuming it's only 1 app that fails? or is this is general failure of all apps?
petertijsma
commented
2 years ago Can you check upgrade/install code, try to debug?
No Upgrade Code active in the latest deployments, nor any debugging going on
Can you check if you're doing something funky in your extension? For example anything that has extended objects that are necessary during deployment?
Not to my knowledge, and why should this then only occur in BC20 and not in BC18
page shows output of the ExternalDeployer (is a json-file somewhere on the server)
If you can tell me where to find this, I will have a look
I'm assuming it's only 1 app that fails? or is this is general failure of all apps?
Currently only one App, but will try to deploy another one to see how that goes
petertijsma
commented
2 years ago I'm assuming it's only 1 app that fails? or is this is general failure of all apps?
How frustrating! Indeed only that app......
Will try to find what weird 'funky' stuff is going on in the app...
waldo1001
commented
2 years ago Good luck ;-)
petertijsma
commented
2 years ago Issue probably found:
Already requested a fix in the suppliers app code. Problem is that we extended their User Setup table through our code and of course hat's updated.
I think this issue can now be closed
waldo1001
commented
2 years ago Yep - any "OnXXCompanyXX" are events to be avoided ;-)
Thanks for reporting back!
Bug Description When using the ALOpsExtension API on a BC20 (OnPrem) installation, the app is published without issues, but the pipeline fails because of the error:
The used yaml
The output
Expected behavior Expected behaviour is that the pipeline continues without this error
Screenshots
Additional context This error does not occur on our BC18 environment