Error when using the ALOps.ExternalDeployer

HodorNV / ALOps

ALOps

59 stars 24 forks source link

Error when using the ALOps.ExternalDeployer #553

Closed panas78 closed 2 years ago

panas78 commented 2 years ago

When Trying to use the ALOps.ExternalDeployer to publish a custom "Base" extension from Page 2507 i get the following error

Could not find file 'C:\Program Files\WindowsPowerShell\Modules\ALOps.ExternalDeployer\1.38\bin\db\00000000-0000-0000-0000-000000000000.json'.

Screenshot 2022-08-12 201037

waldo1001 commented 2 years ago

Few questions:

you have installed the ALOps.ExternalDeployer on the service tier?
is the service tier decently installed (with the installation procedure) or manually set up (by copy/past - usually done when having multiple versions of BC)?

waldo1001 commented 2 years ago

I just got feedback for the developer that this can happen when you opened this page when the job wasn't done yet. Don't open the status-page when the job is still running, because when you do, it will try to find the feedback (which is in a json), but since the job is not done yet, it will fail - and even fail the job along the way.

So: deploy, wait for the feedback, if failed or succeeded, only THEN open the page.

waldo1001 commented 2 years ago

@panas78 , can you give feedback on the above? We're pretty sure that it's the "opening of the deployment status page" that caused this ..

panas78 commented 2 years ago

@waldo1001 You are probably right regarding the page open. It was a rather big app . When i left it do its thing without open the status page the deployment completed successfully

waldo1001 commented 2 years ago

Yeah - it seems clumsy, but it's the only way tot get the "unsupported onprem"-thing to work ;-). Thanks!