We have a Cloud Service that we have been deploying/updating without issue. In the past two weeks every time we try to deploy the package we are getting the error "Deployment could not be created - There was an error processing your request. Try again in a few moments".
I am at a loss as to how to even debug the issue to get more detail. if anybody has any advice on how to get a better error description would be appreciated.
The only changes in this deployment are some changes to the static files in the package so it is unclear what is causing the issue. The process we use is (1) build the package, (2) upload the package, (3) deploy in the staging environment. The package gets uploaded but fails to deploy (step 3).
Any help as to what the issue is or how to get better diagnostic information woudl be great.
I have a jenkins server on Openshift, The server goes down during the build even
after upgrading my plan to the bronze plan and using a large gear.
Each time I run a jenkins build on Openshift I get this message in the middle of the build:
The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.
And then the build disapear from the build history.
Is there a way to know why jenkins goes down during the build ? which logs should I check ?
I set the Builder size to large and the Builder type to jbossas-7, is there a better configuration to use to be able to finish the build?
Is there a way to set my maven repository in the slave so I can save some of my disk quota ?
In advance,Thanks.
The Deployment of ARM template for creating a new VM was successful when new storage account was created. But on using existing storage account it failed with the following error.
/usr/local/rvm/gems/ruby-2.1.8/gems/ms_rest_azure-0.1.1/lib/ms_rest_azure/azure_service_client.rb:72:in `get_put_operation_result': Long running operation failed with status Failed (MsRestAzure::AzureOperationError)
The same was observed in portal with status as failed and all the resources been provisioned
I would try tweeting #AzureSupport on this one.
I had been publishing a Lightswitch app to an Azure website and a linked SQL database. Publishing quit working with the following error in Lightsswitch.
Error 1 An exception occurred when deploying the database for the application.
An error occurred during deployment plan generation. Deployment cannot continue. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\LightSwitch\v4.5\Publish\v2.4\Microsoft.LightSwitch.Publish.targets 1565 10
I recreated the application and setup a new and website and link SQL database on an Azure account and continue to get the same error.
After being able to publish a different app to a different Azure Subscription from the same computer I started from scratch in VS and Azure (again) and was able to publish. I conclude that something was wrong with the project.
I am trying to get started with Azure and am trying to use the Caching feature. I created a cloud service project and added a Cache worker role and a web role. I installed "Windows Azure Caching" nuget into projects for both the roles and added the name of cache worker role as identifier in DataCacheClients element in web.config of the web role.
I added the following code into the web role:
DataCacheFactory cf = new DataCacheFactory();
DataCache c = cf.GetDefaultCache();
When I try to run this locally on the emulator, I get the following exception:
ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure.
Please retry later. (One or more specified cache servers are unavailable,
which could be caused by busy network or servers. For on-premises cache clusters,
also verify the following conditions. Ensure that security permission has been granted
for this client account, and check that the AppFabric Caching Service is allowed through
the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater
than or equal to the serialized object size sent from the client.).
Additional Information : The client was trying to communicate with the server: net.tcp://MvcWebRole1:24233.
Inner Exception : No such host is known
Can you please tell me what I am missing here?
Azure SDK used : v2.0
Timing of your question couldn't be better. We also faced exactly the same issue and were scrathing our head as to what the problem could be. We had one project where everything worked perfectly fine and in one we were getting the same error. Based on our research, we have identified the problem with the Nuget package for caching. It seems a new version (2.1.0.0) was released yesterday and we found that if we install that package, we get this error. Can you check the package version in your case? The documentation states that this new version can only be used with the latest SDK (2.1) released today.
One solution would be to uninstall version 2.1.0.0 and install version 2.0.0.0. To install version 2.0.0.0, open Package Manager Console (View --> Other Windows --> Package Manager Console) and type following command there:
Install-Package Microsoft.WindowsAzure.Caching -Version 2.0.0.0
This fixed our problem. Hopefully it should fix yours too.
Here is a link to the Windows Azure Cloud Integration Engineering blog on how to deal with this same issue. They recommend upgrading to Azure SDK v 2.1 or rolling back as the accepted answer states.
http://blogs.msdn.com/b/cie/archive/2013/08/08/windows-azure-caching-2-1-0-0-no-such-host-is-known.aspx
This exception could also occur under compute emulator if for the role in the client library configuration there is no cache configured. In my case this happened on purpose, since the cache emulator has some problems that can slow down the test and debugging on the service.
In previous version of Windows Azure Caching, in this scenario the construction of DataCacheFactory would fail with an exception (handled by my code); with Windows Azure Caching 2.1 (and Azure SDK 2.1) in this same scenario the code would consider the role name as a server address and thus on DataCache construction would try to communicate with the non existing cache -- this leads to a 3 minute wait and the exception reported in the question.
I have changed my code to detect the new situation for this scenario -- you can find more detail in this SO question.