I have an Office365 accout. I'm developing autohosted app for sharepoint using VS2012. When starting application by F5, installation is successful and after redirect from sharepoint.com to localhost works well. But when I try to deploy it to Azure (rightclick on solution -> deploy), I'm always getting:
Error occurred in deployment step 'Install app for SharePoint': The operation has timed out.
I'm new to developing this kind of apps, so it might be a stupid mistake with configuration.
Any ideas, what could be wrong?
Solved.
Was just a matter of connection speed. Seems 2Mbit is a little slow and deployment times out. With faster connection it worked without a problem
In case someone else facing this issue and cannot resolve slow connection, I was able to avoid this error by changing ChannelOperationTimeout and HostProcessStartupTimeout config values in registry. Please check below post for details of it.
https://msdn.microsoft.com/en-us/library/ee471440.aspx
Related
I am trying to deploy an application to the Azure Service Fabric using the release definition task. When it gets to the task to deploy the server is returning the following error:
The type initializer for 'Microsoft.ServiceFabric.Powershell.Constants' threw an exception
I checked the Endpoint configuration and it appears to be set up as it is supposed to be:
No Authentication (this is an internal text box)
Cluster endpoint: tcp://[service fabric server]:19000
It downloads the artifacts without a problem, but in deploy it searches for the paths for publish profile and application package and finds them. After it finds them it throws the error. I have tried replacing TCP in the endpoint with http, added and removed the :19000 as well and all I get is this error. I have been searching online with little success. Any help to this end is much appreciated.
John
After lots of researching trying every suggestion I could find, we decided try and connect to the machine via Powershell on the box and it too was returning this error. So we uninstalled the SDK and re-installed it and the connection could be made and the builds started to work. I don't know exactly why it failed, but apparently a re-install did the trick. It may have been a bad install, or it could have been a versioning problem. Either way, try a re-install first.
I am working on Maximo Anywhere 7.5.2 - Work Execution Application. After deploying the app, On successful Login. I am getting "isFirstTimeWorkListDownloadFailure" for the querybase "getMyAssignedWork". Kindly help.
Thanks.
There're a lot of reasons for this issue try to open the app in chrome console check the error messages there
I have an MVC application that I've deployed to Azure. Offline it works with no issue with the code first development. However when deployed to Azure it just gives me a non-de-script Error advising me that there's been an error.
I have a look on the management console for further information but was only able to find an error telling me a fatal error had occurred causing a 500 error. Everything else works on the site with no issue it's just when I'm trying to do anything with the database attached to it.
To publish the app I used the downloaded publish settings from the server so I know connection string and what not are all fine. I've also set up code migrations to fill in gaps in the code first dev work so I can see what I'm missing and I don't know where to go now without a more detailed error message?
Any ideas on where I can possibly look next to try and solve this?
I've been successfully using Azure for months. Today I'm getting the following error when I publish from via Web Deploy from Visual Studio 2013
Error 5 Web deployment task failed. (Could not connect to the remote computer ("waws-prod-hk1-001.publish.azurewebsites.windows.net"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
I tried downloaded a new Publishing Profile from the Azure Dashboard and turning off my firewall - no change.
I can't ping the listed server.
It seems to be the same issue as http://social.msdn.microsoft.com/Forums/windowsazure/en-US/83d4e635-2851-4526-b21b-31101d00aa86/web-deployment-task-failed-errorcouldnotconnecttoremotesvc?forum=windowsazurewebsitespreview
Any ideas? Thank you.
I had the exact same problem for a couple of days (sometimes I could published and sometimes not).
The problem was my internet configuration (not related to Microsoft or Azure in anyway).
To solve this issue I disconnected my modem (its actually modem+router) for 10 min and reconnect it and it was fixed!
Hope it will help someone someday...
Nevermind. It would appear that Azure was in a 'challenged' state.
It's working fine now..
What worked for me was disabling and re-enabling my network adapter.
The reasoning is, quite possibly naive, that having Fiddler running during a deployment will fail but it also changes the network state and that state continues
to exist even after exiting Fiddler (which disables the proxy).
Recently I published to my Azure Staging server (Asp.Net MVC App) and my app wouldn't come up. I checked the Event logs on the machine, and this was the error:
.NET Runtime version 4.0.30319.18033 - Loading profiler failed during
CoCreateInstance. Profiler CLSID:
'{F1260058-1A1F-4738-8BE2-0BF9D3A64219}'. HRESULT: 0x8007007e. Process
ID (decimal): 1872. Message ID: [0x2504].
The thing is that I am not using a profiler, everything worked fine yesterday (day old publish) - any ideas what could be causing this, and how I could fix it? Thank you.
Not to say there is not a better fix (I tried all I could find elsewhere, nothing seemed to relate to my specific problem) but here is what I ended up doing. Simply delete your deployment, and re-publish. This must re-set whatever turning on your profiler sets.
Remember that if this is a non domain dns instance, your address will be changed. Hope this can save someone a few hours.
Blog Post Here