Execute package failed in Sitecore Azure deployment - sitecore

I have started the deployment of Editing farm and after some time got this error. Before that Databases are created in Azure.
Execute package failed System.ApplicationException: advaiyawebsiteDevScusCe01Role01SSc5e3Staging [S]
Execute package failed ---> System.ApplicationException: Execute package is failed ---> System.InvalidOperationException:
Build Package failed: Searching for imported module Caching at
C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\plugins\Caching\Caching.csplugin...
Copying 'C:\InetPub\Sitecoredemo\Data\AzurePackages\(7) Azure\Sitecore.Azure.CacheWorkerRole'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreCacheWorkerRole\approot... Copying
'C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\runtimes\base\x64'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreCacheWorkerRole\base\x64... Copying
'C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\runtimes\base\x86'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreCacheWorkerRole\base\x86... Copying
'C:\InetPub\Sitecoredemo\Data\AzurePackages\(7) Azure\SitecoreWebSite' to
C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreWebRole\approot... Copying
'C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\runtimes\base\x64'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreWebRole\base\x64... Copying
'C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\runtimes\base\x86'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreWebRole\base\x86... Copying
'C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin\plugins\Caching'
to C:\Windows\TEMP\odbndccq.v4c\roles\SitecoreCacheWorkerRole\plugins\Caching...
UCPack_Command_Line: Error : CloudServices41 : The entrypoint Sitecore.Azure.CacheWorkerRole.dll is not a valid assembly.
Please provide a relative path to the binary that implements the entrypoint.
at Sitecore.Diagnostics.Assert.IsFalse(Boolean condition, String message)
at Sitecore.Azure.Pipelines.CreateAzurePackage.Azure.ExecutePackage.Action(RolePipelineArgsBase arguments)
at Sitecore.Azure.Pipelines.BasePipeline.RolePipelineProcessor.Process(RolePipelineArgsBase args)
--- End of inner exception stack trace --- --- End of inner exception stack trace ---

It looks like you have incorrect version of Microsoft Azure SDK installed.
Sitecore Azure 8.0 rev. 150522 supports only version 2.5.1
Sitecore Azure 8.0 rev. 150522 Hotfix 68545-1 supports only version 2.7.1
Sitecore Azure 8.0 rev. 161110 supports only version 2.9.1
For more details, please check the following article: https://kb.sitecore.net/articles/026831

Related

wrong version of expo-cli after upgrade

for many time i get the following info message after start expo projects, and it seems its not possible to upgrade expo-cli:
There is a new version of expo-cli available (4.2.1). You are currently using expo-cli 3.28.0 Install expo-cli globally using the package manager of your choice; for example: npm install -g expo-cli to get the latest version
This seems easier as it looks. After installing expo-cli globally without errors
+ expo-cli#4.2.1
OK, now im typing expo -V to check the new Version but wait: its 3.28.0
My project package.json dont have expo-cli in. Is there a way to locate the used expo version?
edit:
i found 1 PATH file till now.
(C:\Users\myuser.expo) it contents:
C:\Users\SYSTEM~1\AppData\Local\Temp\yarn--1615049876273-0.687029522126771;
C:\Users\myuser\WfManager\fmapp\node_modules\.bin;
C:\Users\myuser\AppData\Local\Yarn\Data\link\node_modules\.bin;
C:\Program Files\libexec\lib\node_modules\npm\bin\node-gyp-bin;
C:\Program Files\lib\node_modules\npm\bin\node-gyp-bin;
C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;
C:\Program Files (x86)\Lenovo\FusionEngine;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0\;
C:\Program Files (x86)\Common Files\lenovo\easyplussdk\bin;
C:\Program Files (x86)\Common Files\Apple\Apple Application Support;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\WINDOWS\System32\OpenSSH\;
C:\xampp\php;
C:\Program Files\Git\cmd;
C:\Program Files\PuTTY\;
C:\Program Files\Symfony;
C:\Program Files (x86)\Yarn\bin\;
C:\Program Files\nodejs\;
C:\composer;
C:\Users\myuser\AppData\Local\Microsoft\WindowsApps;
C:\Users\myuser\AppData\Local\Programs\Microsoft VS Code\bin;
C:\Users\myuser\AppData\Roaming\Composer\vendor\bin;
C:\Users\myuser\AppData\Local\Yarn\bin;
C:\Users\myuser\AppData\Local\GitHubDesktop\bin;
C:\Users\myuser\AppData\Roaming\npm
after writing this down and check the entries i found one entry which
links to an old version:
C:\Users\myuser\AppData\Local\Yarn\Data\link\node_modules\.bin; //old version
C:\Users\myuser\AppData\Roaming\npm //new version`
i want to update expo-cli with xarn global now and we will see what happens.
You can check path to binary with command -v expo.
In this case you most likely installed expo-cli globally both with npm and yarn, version 3.28.0 is just earlier in your PATH. It's also possible that you have two node versions (and 2 npm versions) installed, but it's less likely.

Visual C++ build tools seems to be installed But Bazel can't find the following tools: cl.exe, link.exe, lib.exe, ml64.exe

I am trying to build Angular on windows server 2019 AWS Virtual Machine.
I downloaded angular-master.zip from https://github.com/angular/angular
I unzipped this angular-master.zip
I downloaded following Prerequisite softwares.
1. Prerequisite Software
• Git and/or the GitHub app (for Mac or Windows); GitHub's Guide to Installing Git is a good source of information.
• Node.js, (version specified in the engines field of package.json) which is used to run a development web server, run tests, and generate distributable files.
• Yarn (version specified in the engines field of package.json) which is used to install dependencies.
• Java Development Kit which is used to execute the selenium standalone server for e2e testing.
I have done - yarn install
I have done - yarn global add windows-build-tools. It has installed C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools on my Virtual machine. It has also installed - C:\Users\Administrator.windows-build-tools\python27
I have done - node ./scripts/build/build-packages-dist.js
it is giving following error –
INFO: Analyzed 18 targets (1 packages loaded, 179 targets configured).
INFO: Found 18 targets...
ERROR: C:/users/administrator/_bazel_administrator/e2kq7fn3/external/com_google_protobuf/BUILD:267:11: C++ compilation of rule '#com_google_protobuf//:protoc_lib' failed (Exit 1)
The target you are compiling requires Visual C++ build tools.
Bazel couldn't find a valid Visual C++ build tools installation on your machine.
Visual C++ build tools seems to be installed at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC
But Bazel can't find the following tools:
cl.exe, link.exe, lib.exe, ml64.exe
Please check your installation following https://docs.bazel.build/versions/master/windows.html#using
INFO: Elapsed time: 2210.447s, Critical Path: 1095.73s
INFO: 18 processes: 16 local, 2 worker.
FAILED: Build did NOT complete successfully
child_process.js:669
throw err;
^
Error: Command failed: yarn --cwd "c:\angular\angular-master" --silent bazel build --config=release --config=view-engine //packages/upgrade:npm_package //packages/service-worker:npm_package //packages/router:npm_package //packages/platform-webworker-dynamic:npm_package //packages/platform-webworker:npm_package //packages/platform-server:npm_package //packages/platform-browser-dynamic:npm_package //packages/platform-browser:npm_package //packages/localize:npm_package //packages/language-service:npm_package //packages/forms:npm_package //packages/elements:npm_package //packages/core:npm_package //packages/compiler-cli:npm_package //packages/compiler:npm_package //packages/common:npm_package //packages/bazel:npm_package //packages/animations:npm_package
at checkExecSyncError (child_process.js:630:11)
at execSync (child_process.js:666:15)
at exec (c:\angular\angular-master\scripts\build\package-builder.js:122:18)
at buildTargetPackages (c:\angular\angular-master\scripts\build\package-builder.js:81:3)
at Object.<anonymous> (c:\angular\angular-master\scripts\build\build-packages-dist.js:18:1)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12) {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 6708,
stdout: null,
stderr: null
}

Jhipster failure build war file

I use this mvn -Pprod and I get errors like this:
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:yarn (webpack build prod) on project jhi: Failed to run task: 'yarn run webpack:prod' failed. org.apache.commons.exec.ExecuteE
xception: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Arguments:
E:\vaqtinchalik\Vaqf\jhiProject\node\node.exe E:\vaqtinchalik\Vaqf\jhiProject\node\yarn\dist\bin\yarn.js install --force
PATH:
E:\vaqtinchalik\Vaqf\jhiProject\node;E:\vaqtinchalik\Vaqf\jhiProject\node\yarn\dist\bin;E:\vaqtinchalik\Vaqf\jhiProject\node_modules.bin;C:\Program Files (x86)\Google\Chrome\Application;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Java\jdk1.8.0_66\bin;E:\maven\apache-maven-3.5.4\bin;C:\Program Files (x86)\Yarn\bin\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\nodejs\;C:\Program Files\PuTTY\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\WinMerge;C:\Program Files\Git\cmd;C:\Users\JavaProgUZ\AppData\Local\Microsoft\WindowsApps;C:\Users\JavaProgUZ\AppData\Local\Yarn\bin;C:\Users\JavaProgUZ\AppData\Roaming\npm;
Yarn version:
1.3.2
Node version:
8.9.4
Trace:
Error: EPERM: operation not permitted, unlink 'E:\vaqtinchalik\Vaqf\jhiProject\node_modules\node-sass\vendor\win32-x64-57\binding.node'

nuget restore failing in team services build

I have 2 local assemblies referenced via nuget (packed the dll's up) using vs2017 on a asp.net core solution, builds fine locally.
Now trying to generate a build via VSTS i am getting the following error,
Detected NuGet version 4.0.0.2283 / 4.0.0
SYSTEMVSSCONNECTION exists true
Saving NuGet.config to a temporary config file.
d:\a\_tool\NuGet\4.0.0\x64\nuget.exe restore d:\a\1\s\TestFrameworkCoreAPI.sln -Verbosity Detailed -NonInteractive -ConfigFile d:\a\1\Nuget\tempNuGet_37.config
NuGet Version: 4.0.0.2283
MSBuild auto-detection: using msbuild version '15.3.409.57025' from 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\bin'. Use option -MSBuildVersion to force nuget to use a specific version of MSBuild.
MSBuild P2P timeout [ms]: 120000
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\bin\msbuild.exe /t:GenerateRestoreGraphFile /nologo /nr:false /p:RestoreUseCustomAfterTargets=true /p:BuildProjectReferences=false /v:q /p:NuGetRestoreTargets="d:\a\_temp\NuGet-Scratch\w53qa5rr.4sd.targets" /p:RestoreTaskAssemblyFile="d:\a\_tool\NuGet\4.0.0\x64\nuget.exe" /p:RestoreGraphOutputPath="d:\a\_temp\NuGet-Scratch\4mlmlfgh.mmy.result" /p:ExcludeRestorePackageImports=true /p:RestoreRecursive=False /p:RestoreProjectFilterMode=exclusionlist /p:RestoreContinueOnError=WarnAndContinue /p:RestoreGraphProjectInput="d:\a\1\s\TestFrameworkCoreAPI\TestFrameworkCoreAPI.csproj;" "d:\a\_temp\NuGet-Scratch\w53qa5rr.4sd.targets"
Running restore with 2 concurrent jobs.
Reading project file d:\a\1\s\TestFrameworkCoreAPI\TestFrameworkCoreAPI.csproj.
Reading project file d:\a\1\s\TestFrameworkCoreAPI\TestFrameworkCoreAPI.csproj.
Restoring packages for d:\a\1\s\TestFrameworkCoreAPI\TestFrameworkCoreAPI.csproj...
Restoring packages for d:\a\1\s\TestFrameworkCoreAPI\TestFrameworkCoreAPI.csproj...
Restoring packages for .NETCoreApp,Version=v1.1...
Restoring packages for .NETCoreApp,Version=v2.0...
System.AggregateException: One or more errors occurred. ---> NuGet.Protocol.Core.Types.FatalProtocolException: Failed to retrieve information about 'Microsoft.VisualStudio.Web.CodeGeneration.Tools' from remote source 'D:\TestFrameworkAssemblies'.
at NuGet.Protocol.LocalV3FindPackageByIdResource.GetVersionsCore(String id, ILogger logger)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at NuGet.Protocol.LocalV3FindPackageByIdResource.GetAllVersionsAsync(String id, SourceCacheContext cacheContext, ILogger logger, CancellationToken token)
at NuGet.Commands.SourceRepositoryDependencyProvider.<FindLibraryAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
Error: d:\a\_tool\NuGet\4.0.0\x64\nuget.exe failed with return code: 1
Packages failed to restore
I have a nuget.config file in a .nuget folder located in the root of solution,
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<!-- remove any machine-wide sources with <clear/> -->
<clear />
<add key="Test Framework" value="D:\TestFrameworkAssemblies" />
<add key="nuget.org" value="https://www.nuget.org/api/v2/" />
</packageSources>
<activePackageSource>
<add key="All" value="(Aggregate source)" />
</activePackageSource>
</configuration>
This is what is in the VSTS build def, NuGet restore step
It looks like it always references my local assembly and not the standard nuget.org, now in the config file, if i take out my local entry to framework assemblies, the nuget part works but i get a primary reference error as it cannot find the 2 assemblies i have packed locally.
Been going round in circles with this at the moment, how can you get VSTS to restore local packed assemblies as well as from nuget.org. I am using Hosted 2017 as well.
thanks in advance
It seems you were queue the build on Hosted agent. Since there has the packages located on your local machine, you should build with the private agent which located on your local machine.
Additional, if you need to queue the build on Hosted agent, you should add the local packages in repository, and then reference the packages with the new path and change the value in nuget.config.

Unable to install exenstions and updates for Visual Studio 2017 RC (15.0.26014.0)

I recently installed Visual Studio 2017 RC (15.0.26014.0) and was trying to install extensions. However while installing any extension using Tools->Extensions and Updates menu fails. Following is installation log.
27-Dec-16 10:35:19 AM - Beginning to install extension to Microsoft Visual Studio Enterprise 2017 RC...
27-Dec-16 10:35:19 AM - Install Error : System.IO.FileNotFoundException: Unable to find the specified file.
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.GetCurrentSetupInstance()
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformSetupEngineInstall(InstallableExtensionImpl extension, Boolean installPerMachine, Boolean isPackComponent, IDictionary`2 extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, IProgress`1 progress, InstallFlags installFlags, AsyncOperation asyncOp, IInstalledExtension& newExtension)
Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallInternal (InstallableExtensionImpl extension, InstallFlags installFlags, IDictionary`2 extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar,
IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, IProgress`1 progress)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.BeginInstall(IInstallableExtension installableExtension, InstallFlags installFlags, AsyncOperation asyncOp)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallWorker(IInstallableExtension extension, InstallFlags installFlags, AsyncOperation asyncOp)
I checked and found corresponding VSIX file is present in temp folder (C:\Users\xxxxx\AppData\Local\Temp)
I'm currently having the same problems. According to this post, repairing the installation might help.