Posts

Web Deploy detected insufficient space on disk in Azure

Error:  Web Deploy detected insufficient space on disk. Explanation: In Azure Portal, When you run release pipeline using Web Deploy method and you have subscription that is free or provide less storage then you can face this error. Solution: To overcome this issue either you need to reduce the size of your project if you want to use free subscription or update your plan either to shared or some other plan that has required configuration. Thanks!

Azure - Failed to deploy web package to App Service. Internal Server Error (CODE: 500)- Fixed

Image
Error:  Failed to deploy web package to App Service. Internal Server Error (CODE: 500) Explanation: I was getting this error when trying to deploy azure functions with release pipeline. I got this and there was no additional information logs with this. I wasted my one day on this issue. Find Error: You can see the actual error by changing  deploy method for  web deploy   by editing your pipeline. My Root Cause:  "Web Deploy detected insufficient space on disk." So this was the issue for me, it may be because of my subscription.  For different persons root cause might be vary but you can see actual error using this deploy method and can apply your fixes accordingly. Thanks!!!

Swagger for Azure functions: Undocumented TypeError: Failed to execute 'fetch' on 'Window': Request with GET/HEAD method cannot have body. Fixed.

Error -  Undocumented TypeError: Failed to execute 'fetch' on 'Window': Request with GET/HEAD method cannot have body.  Root Cause: I have my Azure functions Project for which I am configuring swagger documentation using Nuget Package " AzureExtensions.Swashbuckle ". When I am opening swagger url in browser and I try one get method then I face this error because 'Get' method has body that should not. My function code is:  public async Task<IActionResult> Test(             [HttpTrigger(AuthorizationLevel.Anonymous, Http.Methods.Get, Route = Version + "/test")] HttpRequest request,             ExecutionContext context, IBinder binder)         { } Solution: To remove the body from 'Get' method, I need to specify some ignore attribute to function parameters as below.  public async Task<IActionResult> GetTest(             [HttpTrigger(AuthorizationLevel.Anonymous, Http.Methods.Get, Route = Version + "/test")] HttpRequ

npm ERR! Unable to authenticate, need: Bearer authorization_uri=https://login.windows.net/*********, Basic realm="https://pkgsprodcus1.pkgs.visualstudio.com/", TFS-Federated Fixed

Error -  npm ERR ! Unable to authenticate , need : Bearer authorization_uri = https : //login.windows.net/*********, Basic realm="https://pkgsprodcus1.pkgs.visualstudio.com/", TFS-Federated Root Cause - When you have configured your package registry in .npmrc file as below. registry =https://<your-organization-cloud>.pkgs.visualstudio.com/_packaging/bdcNpmFeed/npm/registry/ And your credentials are not updated or has expired then you can face the authentication issue. Solution - run below command in visual studio code to get authenticated. vsts - npm - auth - config . npmrc Thanks

Unexpected token T in JSON at position 0 in Angular CLI 6 - Fixed

Error -  Unexpected token T in JSON at position 0  Root Cause - When upgrading to Angular CLI 6 and then you run build or install command then you can face this error. Solution - Make sure correct version of Angular CLI is installed. For me Angular CLI 6 did not work so finally I upgraded directly to Angular 7 instead of Angular 6 first as per angular upgrade guide . Thanks

The serve command requires to be run in an Angular project, but a project definition could not be found - Fixed

Error -  The serve command requires to be run in an Angular project, but a project definition could not be found Root Cause - When there is no project definition file in your project then you will see this error when you will run ng-serve or ng-build commands. Project definition file - In Angular project definition file is generated when you create new application or upgrade existing application. In Angular versions lesser than 6 this file name is .angulat-cli.json  and in Angular version 6 and above it's name is angular.json . Solution -   So while running the angular build or run commands make sure you have correct project definition file. If you are upgrading your application from Angular 5 or lesser versions to Angular 6 and greater versions then you need to run below command to generate new project definition and other related files. ng update @angular/cli   // run it twice, If it's not generating then again try to run below commands in same sequence. npm install -g @angu

Your global Angular CLI version (8.3.3) is greater than your local version (1.6.5). The local Angular CLI version is used.

Warning -  Your global Angular CLI version (8.3.3) is greater than your local version (1.6.5). The local Angular CLI version is used. Explanation - When you run an angular application and you have different versions of Angular CLI installed globally and in local project then you can see this warning or error. Solution - There are 3 things here. Either you can continue with this warning You can install matching version of angular CLI to global in local project by using below command.           npm install @angular/cli@version         3. Install Latest version of Angular CLI globally and in project as well.          To install latest angular CLI globally use below command.           npm install -g @angular/cli          To install latest angular CLI in project use below command.           npm install @angular/cli Thanks