Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment fails #96

Open
webbeld1975 opened this issue Aug 16, 2019 · 3 comments
Open

Deployment fails #96

webbeld1975 opened this issue Aug 16, 2019 · 3 comments
Labels

Comments

@webbeld1975
Copy link

Deployment using PartnerCenter link fails, so does redeployment in azure deployment.

Here is the error generated:

Installed:
59 package(s) to packages.config projects
D:\home\site\repository\packages\Microsoft.Net.Compilers.3.2.1\tools\Microsoft.Managed.Core.targets(63,60): error MSB4086: A numeric comparison was attempted on "$(MSBuildVersion)" that evaluates to "" instead of a number, in condition "$(MSBuildVersion) >= 16.1.0". [D:\home\site\repository\src\Storefront\Storefront.csproj]
Failed exitCode=1, command="D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" "D:\home\site\repository\src\Storefront\Storefront.csproj" /nologo /verbosity:m /t:Build /t:pipelinePreDeployCopyAllFilesToOneFolder /p:_PackageTempDir="D:\local\Temp\8d722518392faf9";AutoParameterizationWebConfigConnectionStrings=false;Configuration=Release;UseSharedCompilation=false /p:SolutionDir="D:\home\site\repository.\"
An error has occurred during web site deployment.
\r\nD:\Program Files (x86)\SiteExtensions\Kudu\82.10503.3890\bin\Scripts\starter.cmd "D:\home\site\deployments\tools\deploy.cmd"

@ghost
Copy link

ghost commented Aug 19, 2019

@webbeld1975 I just addressed this issue. Can you try deploying the storefront again?

@ghost ghost self-assigned this Aug 19, 2019
@ghost ghost added the bug label Aug 19, 2019
@webbeld1975
Copy link
Author

@IsaiahWilliams Thank's Isaiah for the quick response. I tried two different things:
a) upgrading an instance where the deployment failed last week : result is shown as success in PartnerCenter, appservice shows as running in Azure Deployment portal
b) deploying a new instance: shown as failed in PartnerCenter due to timing issue, the deployment is still running at this time. About 3 minutes later the deployment finished successfully.

However, both deployments don't show a website when I load it into a browser. The title of the website is shown (here german for name of your organisation), but the whole pages shows blank. Tried Chrome, Edge and Firefox.
As far as I understand the other posts here, there should show up a configuration wizard.
Does it maybe have to do with the activiation of "Multi tenancy" which is found in some posts here? I didn't find the correct setting for this, can you advise how to do this?

@ankbomb
Copy link

ankbomb commented May 4, 2020

Adding to @webbeld1975

Having the same issue in a US tenant. tried this as well as https://github.com/microsoft/Partner-Center-Storefront.

VS says successful, but in the logs it shows:

D:\home\site\repository\packages\Microsoft.Net.Compilers.3.3.1\tools\Microsoft.Managed.Core.targets(63,60): error MSB4086: A numeric comparison was attempted on "$(MSBuildVersion)" that evaluates to "" instead of a number, in condition "$(MSBuildVersion) >= 16.1.0". [D:\home\site\repository\src\Storefront\Storefront.csproj]
Failed exitCode=1, command="D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" "D:\home\site\repository\src\Storefront\Storefront.csproj" /nologo /verbosity:m /t:Build /t:pipelinePreDeployCopyAllFilesToOneFolder /p:_PackageTempDir="D:\local\Temp\8d7f0e3204af75e";AutoParameterizationWebConfigConnectionStrings=false;Configuration=Release;UseSharedCompilation=false /p:SolutionDir="D:\home\site\repository.\"
An error has occurred during web site deployment.
\r\nD:\Program Files (x86)\SiteExtensions\Kudu\86.20224.4450\bin\Scripts\starter.cmd "D:\home\site\deployments\tools\deploy.cmd"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants