CODEWITHSUNDEEP
deploymentazure
Jezbers
Jezbers

Reputation: 814

Azure Deployment Error: cannot find ClientPerfCountersInstaller.exe

I recently tried setting up the Preview Cache for Azure on an existing site and deployment, which I had to abort due to errors. However since then I now get the following error when I try and deploy to Azure...

Cannot find file named approot\bin\Microsoft.WindowsAzure.Caching\ClientPerfCountersInstaller.exe

This file does exist on disk, presuming approot is the base folder for my ASP project.

Any ideas and help greatly appreciated, am banging my head against the wall currently!

Upvotes: 6

Views: 3477

Answers (4)

moudrick
moudrick

Reputation: 2336

I resolved my issue with absence of Microsoft.WindowsAzure.Caching\ClientPerfCountersInstaller.exe by just removing the Microsoft.WindowsAzure.Caching package from my solution using "Manage Nuget Packages for Solution...". It was not referenced but still was mentioned in packages.config... Especially after information that this way of caching support is discontinued and going to be eliminated.

Duplicate of my answer in other question enter link description here For those who just quickly overviews the answers to find the most appropriate way of solving their exact issue after searching by just error message.

Upvotes: 0

moudrick
moudrick

Reputation: 2336

I resolved my issue with absence of Microsoft.WindowsAzure.Caching\ClientPerfCountersInstaller.exe by just removing the Microsoft.WindowsAzure.Caching package from my solution using "Manage Nuget Packages for Solution...". It was not referenced but still was mentioned in packages.config... Especially after information that this way of caching support is discontinued and going to be eliminated.

Upvotes: 0

Bart Verkoeijen
Bart Verkoeijen

Reputation: 17753

In my case the file was created by the Azure SDK tools, but TFVC did not check-in the .exe.

After explicitly adding the missing .exe the build runs successfully.

Upvotes: 2

Jezbers
Jezbers

Reputation: 814

Found the solution. The ServiceDefinition.csdef file had a new startup task that had been created somehow during the cache setup process. Removing this superfluous task resolved the issue and I cannot see any down side or negative impact.

Commented out line is shown below...

<Startup priority="-2">
  <!--<Task commandLine="Microsoft.WindowsAzure.Caching\ClientPerfCountersInstaller.exe install" executionContext="elevated" taskType="simple" />-->
</Startup>

Upvotes: 13

Related Questions