Zip Deployment Failed

[Ogier Dudley]

Ihave tried to google the error code but my search has been unsucsessful as of yet. Has anyone else come accross this particular error? It would be helpful if it said what service in particular couldn't be started!

What version of LabVIEW are you running? Is this the only version that has been installed on your PC? [The reason to ask this is I, and others, have experienced installing, say, LabVIEW 2015 on a system which already has LabVIEW 2014, something that is "legal" and should work, but during the Installation, various NI Services are stopped and not restarted. One Service, necessary for the functioning of Shared Variables, is the NI Variable Service].

In fact, while composing this Post, I went to my Services (because I wanted to be sure to specify the correct Service), only to find that the Service is (again) missing, and the Shared Variable Engine is (again) not available. Indeed, I get exactly the same error message.

Well, that did, indeed, fix it -- the NI Variable Engine is running again as a Service (to see Services, go to the Start Menu, type "Services" in the Search box, choose the thing with the Gear icon). It took 34 minutes to repair LabVIEW 2015, then I had to repair 6 or 7 other things, so there was some disk-swapping ...

If it isn't completely dead, like Bob said, I have seen the service not start in time for deployment on slower machines. I then could abort the program, wait a bit, and it would start up fine after that.

If the Repair works, then you shouldn't need to "check it on Start Up" -- it should continue to work until you do another LabVIEW install (or install a patch from NI Update). You'll know when you do those, so you can easily check "manually", if you are worried.

Hi, so after upgrading forge/cli from 4.5.0 to 4.5.1, my every deployment failed. I tried registering new app, installing and it is still failing on deployment. I tried uninstalling forge/cli and installing again and then downgrading to 4.5.0 still nothing. But the thing is when I am deploying on production environment it gets deployed. I tried getting more info by using forge deploy --verbose but it says unknown error so there is no info on that side. Did anyone have troubles with forge deploy?

As already mentioned, we recommend deploying the managing agent as per the instructions in the KB in my previous post and then using a software install task to install Endpoint which is basically a trouble-free process.

Do not do a push install from ESET PROTECT. Instead use ESET Remote Deployment tool to deploy the managing agent if GPO or SCCM is not an option. Please refer to _admin/10.1/en-US/deployment_tool.html.

But after I clicking deploy I got a message: "Your function is active, but the last deployment failed"

While trying to find out the cause of of my failure, i have gone round and round of things I might need to do most of which lead to something else I need to do. I am afraid that by following some of these suggestions I might be causing more damage than good.

Can anyone tell me in a concise way what I need to do and how to do it. Or better yet a article or site that explains. it.

For example I'm being told to need to have IAM cloud/function deployment rights but I'm not sure that I accomplished that, because I think I need to establish a git account, which I did but I cannot reach it within the cloud desktop so I don't know what to do next. Is there a tutorial on how to deploy a cloud function?

@Marramirez

Thank you for the suggestion. I added the semicolon but no joy, still the same message.

I have no I idea what I'm doing. I just duplicated from an old youtube video which migh be outdated.

I am going through the training exercise and i have the same error, can you please restart my AppPoll, i have been facing this for more than 24 hours so obviously the self-healing did not work in my case as well

The self healing appears to be working but my problem is not resolved. I saw that the platform Heath status has been updated to OK, but when i try to deploy I get the same error and the environment health status changes back to "" . I tired this two times today so my deployment is somehow crashing the deployment service.

I am evaluating the platform as well. I have heard good things of it, however I am having the Service Unavailable (503) error on my environment. I have emailed suc...@outsystems.com, but have not recieved a reply. Is this where I can get a fix for this issue?

As you can see I was evaluating the platform for enterprise use. It turns out Outsystems sometimes has problems with personal environments (as they are free and they give priority to actual paying customers as they should). We did elect the platform for our use and let me tell you we have never looked back in regret.

We have had little problems that we couldn't solve ourselves (or with the help of a very active community). Certainly never something as serious as the complete environment being down. The couple of problems that we couldn't figure out ourselves, Outsystems support has been outstanding, quickly providing support and helpful answers every time. I highly recommend the platform. Feel free to message me for any additional info, I'm happy to help however I can.

Check bdd.log. Normally the 10 or so lines before that can help determine why it failed. 0x80004005 is too generic of an error to troubleshoot without some supporting info about what happened prior in the task sequence.

I see that some guy fixed this error using this article Windows 10 deployments fail with Microsoft Deployment Toolkit on computers with BIOS type firmware - Microsoft Support Please take a look at this.

I'm sorry this has happened to you. Let's see if we can't figure out the cause and get it fixed. Hopefully we will find more diagnostics than what we see in the Console. When we deploy a Cloud Function, we are telling Google "Hey .. here is a chunk of my code ... when an incoming request arrives, please send that request to my code and you take care of running it". The act of giving your code to Cloud Functions is called a "deployment". Now, if the code that is supplied to Cloud Functions contains an error, is missing a dependency or some other technical reason that Cloud Functions can't initiate an instance, it will (hopefully) tell us. And the message it may give us is "Failed to deploy". At this point, we need to figure out what has gone wrong ... debugging. When a deployment occurs, Google Cloud logs all the steps of the deployment in Cloud Logging. That would be where I would go first.

I would suggest we open up Cloud Logging's log explorer in the project and lets see what happened the last time we tried a deployment. If all goes well, we'll see a clear error message and get an "aha" moment, fix the error, redeploy and we'll be back on track.

Howdy vbgcp. I think we are getting closer. I'm sensing there is a problem in the source of the Python code as indicated in the logs. Yeah!!! That should be easily fixable. In our thread, we haven't described how we are deploying the Cloud Function. What recipe did you use to create the Cloud Function in the first place? Let's see if we can't capture that and take it apart and see what we can do next.

From there we can examine each step in turn. My hope is that once we look at the log steps you follow, we will see "Aha ... this is where I supply my source code" ... and then, when you need to update the source (eg. to fix a typo or bug or indent problem) ... we will immediately be able to say "Its there on step 4 we need to change".

My main point is, how to delete or fix this function which is in loop or stuck somewhere. Its surprising that GCP is behaving this way for a Indent issue (in other cases, if there was a Indent issue, it failed deployment and I was able to fix the code). But here, deployment failed and stuck in loop and does not allow me to delete too.

Oh OHHH ... I am so sorry. I missed the "looping" story ... your posts were clear it was my interpretation/reading that failed us. I am sensing that we are saying that the console is saying that the deployment is just "stuck". If I were with you, the first thing I'd do is refresh the browser just in case it is a bug in the UI alone and it is had gotten mismatched state. Some of our UIs show "busy" until an outcome is received from Google Cloud. If the outcome event "got lost" it may still show busy.

At the moment, the inconvenience you are experiencing with the Cloud Functions 2nd Gen being hung in a broken state seems to be related to a known issue with Cloud Run deployments we were reported of.

To follow up with the issue you are facing, if the button is still grayed out, could you try to redeploy via the Google Cloud CLI? You may find helpful information in this link [1]. To deploy the function with an HTTP trigger, run the following command in the directory that contains the sample code:

So, ultimately, looks like if you are in this situation, you can go to the version history of the function and restore to a prior version before the function went into a loop and restore to that version and go back to your function and make the necessary fixes or delete the function.

I just started using the MDT SCCM integrated task sequence to deploy Windows 7 and 8.1. my TS keeps failing shortly after "Applying Operating System". I copied the following logs and am trying to correlate them to the MDT Task Sequence. In particular I have been looking at the smsts.log, ztierrormsg.log, and DDB.log and they all have the same error in the logr and it says "ZTI deployment failed, Return Code = -2147024809 0x80070057" The only thing that I tried was Running Disk part and running the clean command on Disk 0. Didn't help a but. Any guidance would be appreciated. I attached all three logs

3a8082e126