Azure Functions Deployment Error - "Number of entries expected in End Of Central Directory"

hawthorne91 230

I am experiencing an issue when deploying one of my Azure Function APIs using the Virtual Studio Code Azure Function extension. I deploy my code into an Azure Function for my APIs, and when I try to deploy my code now, I get the error "Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory" inside of the terminal. The error is with the "Azure Functions" extension. I tried reverting to another version of the "Azure Functions" extension and deploying, however I get the same error. I'm not sure what to do. For reference, I am using the Azure Functions extension, version 1.13.1 in Visual Studio code.

Lindsay Shelton 46 Reputation points MVP

2023-12-13T21:56:21.2733333+00:00

Getting the same error - perhaps an outage?
hawthorne91 230 Reputation points

2023-12-13T22:00:52.64+00:00

That might be the case! Earlier when I was deploying it was working. It seems like it just starting happening in the last 30 minutes or so?
Jeremy Voss 5 Reputation points Microsoft Employee

2023-12-13T22:07:32.9466667+00:00

Same here.
Miguel Angel Carrizo 5 Reputation points

2023-12-13T22:17:34.5+00:00

I had the same problem. After re-installing all the Azure extensions, I didn't encounter the error when I tried again.
Jeremy Voss 5 Reputation points Microsoft Employee

2023-12-13T22:29:36.25+00:00
After uninstalling and reinstalling all Azure extensions, no change. After signing back in, error changes to "

Offset to Central Directory cannot be held in an Int64
Syed Umair Hasan 0 Reputation points

2023-12-14T00:01:28.72+00:00

Getting the same error
Pedro Eduardo 5 Reputation points

2023-12-14T01:16:19.4733333+00:00

Go to VS Code and change the version of Extension "Azure Functions" to 1.12.4. It will work!
benben 0 Reputation points

2023-12-14T01:18:18.3666667+00:00

我在VS Code用Azure App Service部署Nuxt專案時遇到一樣的問題
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Emmanuel Cote 0 Reputation points

2023-12-14T01:55:26.6266667+00:00

Experiencing the same problem when deploying using VS Code. DevOps pipeline deployment works fine.

Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/....zip (39.27 MB) to /tmp/zipdeploy/extracted Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.
Yugesh KC 21 Reputation points

2023-12-14T02:42:32.1566667+00:00

Just encountered the issue not certain about the cause of issue. I have resolved the issue by setting up github actions.

You could setup the CI/CD pipeline using Deployment center of a function APP
Dylan Chapman 0 Reputation points

2023-12-14T02:44:34.9966667+00:00
Also getting the same issue. I am currently studying deploying Azure functions, so it could entirely be user error, but I have attempted deploying to multiple resource groups and using the default python http trigger function with no luck after many attempts. I had no issue deploying last night.

I've gotten 3 errors -

Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory

Central Directory corrupt.

Offset to Central Directory cannot be held in an Int64.

I've attempted the solutions in this thread with no success (Reinstall all azure extensions, downgrade functions to 1.12.4.

EDIT - Finally worked for me. I believe this to have been some sort of outage on Azure's side
Lu Di (DHL Group) 0 Reputation points

2023-12-14T03:08:42.32+00:00

Go to VS Code and change the version of Extension "Azure Functions" to 1.12.4. It will work!--> it doesn't work for me !!!!
JDR 90 Reputation points

2023-12-14T03:13:47.0333333+00:00

Getting the same error
JDR 90 Reputation points

2023-12-14T03:18:29.1233333+00:00
Brand new function, brand new deployement fails as well, same error:

Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.
benben 0 Reputation points

2023-12-14T03:19:27.39+00:00
Stopping the azure function using azure portal

Redeploy

is doesn't work for me

and after restart my website show ":( Application Error" page
Maxwell Bauer 5 Reputation points

2023-12-14T04:04:22.43+00:00

Same issue, I just setup a new computer and thought I was doing something wrong in setup but looks like others are having the same issue.
62600895 0 Reputation points

2023-12-14T04:28:29.0066667+00:00

has anyone found a fix yet or do we have any news on what the issue is?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Kenneth Andrew Sutherland 0 Reputation points

2023-12-14T05:00:59.3966667+00:00

As of 14th December, this issue still persists. I've changed versions a few times and after running pre-deployment tasks and starting to work with the zip file, I get the following error report:

"Number of entries expected in End Of Central Directory"
Daniel Marin 0 Reputation points Microsoft Employee

2023-12-14T05:15:55.1733333+00:00

I hadn't notice the date of these comments. I've been trying everything for over 3 hours. I set up a different machine, created a new function app, and tried to deploy the default javascript function. Thanks God this seems to be an outage. I can go to sleep now :D
Cho Phan 0 Reputation points

2023-12-14T06:22:10.6733333+00:00

After change the version of Extension to 1.12.4 still not work. You can sign out and sign in azure account.
Devesh Tiwari 180 Reputation points

2023-12-14T07:46:10.6066667+00:00

After decreasing the version of Azure extension, It started working for me.

Following settings worked for me:

App Service -> 0.25.0

Azure Functions -> v1.12.4

Azure Resources -> v0.8.0
Martin Meeser 1 Reputation point

2023-12-14T14:11:05.47+00:00

I have the same issue with an azure webapp
Grzegorz Wieczorek 0 Reputation points

2023-12-14T14:49:21.99+00:00

I can confirm that downgrading VSC's Azure Resources to v0.8.0 WORKED, but only with changing subscription tier to higher (B1 to B3). Once subscription was downgraded again, problem reocurred regardless of Azue Resources version.

I didn't change Azure Functions version, I left the newest one. I don't use Azure App Services.

Thank you, @Devesh Tiwari !

Accepted answer

Devesh Tiwari 180 Reputation points

2023-12-14T07:45:01.41+00:00

After decreasing the version of Azure extension, It started working for me.

Following settings worked for me:

App Service -> 0.25.0

Azure Functions -> v1.12.4

Azure Resources -> v0.8.0
Please sign in to rate this answer.

14 people found this answer helpful.
Daniel Pichlmeier 0 Reputation points

2023-12-14T08:07:17.8366667+00:00

Removing the 'Azure Storage' plugin resolved the issue for me.

Sarah Ghaya 0 Reputation points

2023-12-14T08:39:28.94+00:00

reverting to 0.0.8 for the azure tool extension worked for me as well. But I am not sure what is the implication of this decrease in versions in other cases.

Petrus Dimas Eriyatno 0 Reputation points

2023-12-14T09:14:43.8266667+00:00

Thanks, it works!

Daniel Orelius 0 Reputation points

2023-12-14T09:23:52.25+00:00

Thanks! it also worked for me!

BHARATH KUMAR 0 Reputation points

2023-12-14T09:25:59.77+00:00

Reverting to the older versions still not working for me
Azure tool extension to v0.0.8 and Azure App Service to V0.25.0

Marcos Aurélio Hermogenes Boriola 0 Reputation points

2023-12-14T12:55:24.1333333+00:00

This worked for me! Thank you!

Nander Vilar Castellar 0 Reputation points

2023-12-14T13:23:12.1366667+00:00

Awesome this works

hawthorne91 230 Reputation points

2023-12-14T14:09:01.21+00:00

Devesh Tiwari Thank you this worked for me too.

Daniel Bordeleau 25 Reputation points

2023-12-14T14:47:06.1566667+00:00

Thanks! Wasted 2h on that this morning

Grzegorz Wieczorek 0 Reputation points

2023-12-14T14:50:18.48+00:00

In my case, the problem was with Azure Resources AND subscription tier. I left Functions at v1.13.1, I don't have App Services installed at all.

Problem vanished only with changing subscription tier to higher (B1 to B3). Once subscription was downgraded again, problem reocurred regardless of Azue Resources version.

Lindsay Shelton 46 Reputation points MVP

2023-12-14T15:07:07.22+00:00

Thanks so much! I just needed to do Functions and then Resources for success, don't have App Service either.

Ilan 0 Reputation points

2023-12-14T15:35:06.52+00:00

Yeah, for me it was rolling back Azure Resources to v0.8.0.
0.8.1 and 0.8.2 were rolled out in the last 24 hours and probably had introduced this issue

MuthuKumaranMurugaachari-MSFT 22,321 Reputation points

2023-12-14T15:39:29.9833333+00:00

Update:
Sorry for the inconvenience caused by this issue. Our product team is actively investigating this issue and will keep you posted with updates. Meanwhile, please follow the workaround to rollback Azure Resources to v0.8.0

H, Jason 0 Reputation points

2023-12-14T15:40:42.1933333+00:00

This worked for me!

Jean Van Iddekinge 0 Reputation points

2023-12-14T16:11:46.44+00:00

This worked but OMG did it take me a long time to figure out where to set the "version of Azure extension" I looked in the sln, csproj, host.json, vs, appsettings, I even trawled through the kudo console and every flippin place.

Then finally after hours FINALLY I realized he meant the VISUAL STUDIO CODE EXTENSIONS!!!

fml thanks though, it's greatly appreciated.

Microsoft fix your bugs plz :)

Martin Nitschke 0 Reputation points

2023-12-14T17:26:26.8033333+00:00

This solution is what worked for me

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Djurovic, Rosie 0 Reputation points

2023-12-15T10:23:04.54+00:00

Reverting to previous version of Azure Functions extension worked for me, thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

3 additional answers

Jie 85 Reputation points

2023-12-14T05:12:58.3466667+00:00

Changing Extension "Azure Resources" version to 0.8.0 works for me.

Not sure why my last comment was eaten.
Please sign in to rate this answer.

17 people found this answer helpful.
Kenneth Andrew Sutherland 0 Reputation points

2023-12-14T05:37:10.7533333+00:00

Well done Jie, there must be a bug in the latest Azure Resources version. I can confirm downgrading from Azure Resources v0.8.2 to v0.8.0 worked.

Lu Di (DHL Group) 0 Reputation points

2023-12-14T05:49:41.13+00:00

this work for me , after degrapde azure resource to v0.8.0 and reload vscode, the error gone. thanks

Tom 0 Reputation points

2023-12-14T06:12:41.98+00:00

Can confirm this worked for me. rolling back to v0.8.0 worked for me

Henry Chan 0 Reputation points

2023-12-14T07:12:27.1+00:00

v0.8.0 works for me. There must be something wrong in the latest version. Thanks!

Amplified Ge 0 Reputation points

2023-12-14T07:25:21.42+00:00

Hello there,

How may I downgrade, can you give me instructions?

Amplified Ge 0 Reputation points

2023-12-14T07:41:47.88+00:00

It is little triangle within uninstall button.
That resolved the issue.
Thank you!

Sarah Ghaya 0 Reputation points

2023-12-14T08:40:30.32+00:00

worked for me

Bjørn Kristian Punsvik 0 Reputation points

2023-12-14T10:07:03.6966667+00:00

Worked for me too.

Muhammad Al-Osayli 0 Reputation points

2023-12-14T11:54:59.7133333+00:00

Very helpful. Thanks
Works for me

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Michael 5 Reputation points

2023-12-14T16:16:39.3733333+00:00

Downgrading to 0.8.0 is indeed sufficient to resolve the issue. That version is now 3 weeks old, 0.8.1 is 1 day old and 0.8.2 was updated 20 hours ago at the time of writing. Azure functions was last updated 3 months ago and this issue just started happening today for me, so logically it was introduced with the Azure resources update 0.8.1 or 0.8.2 in the past 24 hours.

Michael 5 Reputation points

2023-12-14T16:21:10.2333333+00:00

For anyone wondering where to downgrade:
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
MuthuKumaranMurugaachari-MSFT 22,321 Reputation points

2023-12-14T17:59:43.51+00:00

Devesh Tiwari Thanks for the answer and it really helped lot of users with similar issues for a quick resolution.

Update:

Our product team has fixed the issue in the Azure Resources extension, and we just released 0.8.3 version with the fix. Please update to this version for mitigation and let us know if any issues or have any questions.

We are sincerely sorry for the inconvenience caused by this issue.
Please sign in to rate this answer.

6 people found this answer helpful.
Harald Gerhardsen 5 Reputation points

2023-12-14T19:49:37.51+00:00

Updating to the release 0.8.3 fixed the issue for me.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Ramón F. López-Imizcoz 0 Reputation points

2023-12-15T14:17:32.0433333+00:00

I don't have Azure Resources installed, but the Function Apps extension. I had to downgrade it to v1.12.4. When will it be also fixed?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Functions Deployment Error - "Number of entries expected in End Of Central Directory"

3 additional answers

Your answer