I'm trying to publish my web application to Azure existing web application with MSBuild from command line:
.\MSBuild.exe $solutionPath /T:$project /T:Rebuild /p:DeployOnBuild=true /p:WebPublishMethod=MSDeploy /p:PublishProfile=$publishProfilePath /p:password=$password /p:VisualStudioVersion=14.0 /p:AllowUntrustedCertificate=true
and I'm getting the following error:
msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task fail
ed. (Could not connect to the remote computer ("appName.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond.
But when I deploy the same application with same publishing profile from Visual Studio 15 it work fine. Do you have any idea what is wrong?
Thanks
OK, the problem was with our IT using a proxy server.
The solution is to add
<system.net>
<defaultProxy useDefaultCredentials="true" />
</system.net>
to the "MSBuild.exe.config" file
Related
My IIS was crashed - Services are not starting due to the following changes done by me in the IIS due to unaware of version migration.
I have taken the back of IIS 7.5 from Windows Server 2008 R2 using the below command
%windir%\system32\inetsrv\appcmd.exe add backup "mySite20210818"
and restored the backup in IIS 8.5 in Windows server 2019 using the below command
%windir%\system32\inetsrv\appcmd.exe restore backup "mySite20210818"
Due to the above changes the IIS is not working and also i could able to start the IIS service itself...i tried to remove the role and then added the role still its not working..
When restoring, why doesn't it say not to install version incompatible, I have to install windows server 2019 again?
Please suggest solution. I will not use appcmd backup again.
what i tried
I copied the files from "C:\inetpub\history\CFGHISTORY_0000000001" into "%windir%\system32\inetsrv\Config".
iisreset /stop
iisreset /start
iisreset /start
The IIS Management Service or the World Wide Web Publishing Service or a dependent service failed to start. The service or dependent services may have encountered an error or been disabled during startup.
iisreset /status
Status: IIS Management Service ( IISADMIN ): Stopped
Status: Windows Process Activation Service (WAS): Stopped
Status: Net.Pipe Listener Adapter ( NetPipeActivator ): Stopped
Status: Net.Tcp Listener Adapter ( NetTcpActivator ): Stopped
Status: World Wide Web Publishing Service ( W3SVC ): Stopped
Removed iis from roles and reinstalled. But it doesn't come off completely.
Regards
When I am using PostgreSQL and MongoDB with .Net 5. It Working Perfectly on the local system. After Complete my project and deploy to the server.
Then Shows
HTTP Error 500.30 - ASP.NET Core app failed to start
almost all solutions try with my code and server.
Please follow these steps:
Install the proper runtime with the Hosting Bundle
Check DLL issue
Navigate to the root directory and type CMD on the folder path bar:
Type in command dotnet {yourApplicationName}.dll
Open your browser and navigate to http://localhost:5000/
If all is okay, your site will be working on the local host.
Exit CMD and Config in IIS
You can refer to Host ASP.NET Core on Windows with IIS to republish your app.
Just deploy to IIS server my .NET Core 2.1 webapi. Got error 502.5 HTTP Error 502.5 - Process Failure from the URL http://localhost/api. Open the Event Viewer, it is IIS AspNetCore Module eror.
Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE/API' with physical root 'C:\apps\api\' failed to start process with commandline 'dotnet .\Webapi.dll', ErrorCode = '0x8007010b : 0.
Remote to the server and run dotnet .\Webapi.dll successfully.
Any idea please
Error code 0x8007010b means IIS could not find dotnet.exe but i havr all dotnetcore frameworks installed. Finally the issue is the windows previdge. The default account for iis pool doesnt have enough power to access the folder c:\dotnet... It is resolved by running more powerful account.
We have .Net project build definition on VSTS and it's using Azure Storage Emulator for running tests. And we want to use Hosted 2017 agents for the build definition.
I saw this question (Azure SDK not available on Hosted VS2017 VSTS Build Agent) and the comment that I can use command "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe init /server (localdb)\MSSQLLocalDb" to initialize Azure Storage Emulator.
However, when I tried to start Azure Storage Emulator with command "C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe start", it failed with Error: Unable to start the storage emulator.
Is there any way to start Azure Storage Emulator on VSTS Hosted 2017 agent?
Command and Error
It is now possible.
See the other answer:
https://stackoverflow.com/a/51726177/1830814
Some more info here:
https://developercommunity.visualstudio.com/content/problem/238481/hosted-visual-studio-2017-errorno-available-sql-in.html#
The VSTS Hosted agent is running as service that you can’t start storage emulator (init is ok).
A related thread: VSO Hosted Build Controller - Is the Azure Storage Emulator supported?
Update:
Based on the test, the Azure Storage Emulator can be started on Hosted VS2017 agent now.
Error:
There was an error attaching the debugger to the IIS worker process for URL http://127.255.0.0:82/ for role instance ...
So basically I have:
Windows 8 Enterprise
Visual Studio 2012
Azure SDK 1.7
Project with two roles:
Worker role
Web Role (ASP.NET MVC 4)
What have I tried
Enabled running 32-bit applications in AppPool
Checked for <compilation debug="true"> in Web.config
aspnet_regiis.exe -i
Azure project is configured to run at Full IIS (with Express it's working like a charm, but need full IIS)
aspnet_regiis.exe -ir from C:\Windows\Microsoft.NET\Framework\v4.0.30319 solved the problem. I've done this from developer command promt which has 64-bit path enviroment. This is for 32-bit.