I have an MVC 4 website using a WCF service. When I deploy to Windows Azure using the VS 2012 publish wizard, I get this error:
10:13:19 AM - The HTTP request to 'https://management.core.windows.net/42d4257b-5f38-400d-aac5-2e7acee9597d/services/hostedservices/myapp?embed-detail=true' has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.
After cleaning the project and publishing a few times, the error goes away. What am I doing wrong?
Whenever you start publish process from VS machine, a SSL tunnel is established first and once the tunnel is created, the package is transferred from your machine to Windows Azure Portal first. After the upload is completed, you will see the result notifications are posted back to Publish result windows and that is how it happens.
In your case, the time to build the SSL tunnel doe secure package transfer is longer then normal, this could be because of network latency between your machine and the Windows Azure Management Portal. For security reason the time to create the tunnel smaller windows and if the connection is not created, the retry cycle starts the process again and even if that fails you are greeted with the failure message. This could be caused by excessive traffic on either side or both sides. So this is mainly a networking related issue rather then specific to Windows Azure as after some time successive tries, you could upload your package.
In such failure/situation, you can run network capture utilities i.e netmon, wireshark, and see the time taken during failure and success to see the different in various transfer. This will help you to understand the underlying delaying issues.
Try to update your roles diagnostics
like below
then update your storage credentials because it may be expired.
Related
So...about 5pm 2 nights ago, all 14 of my listeners on my Azure Service Bus dropped. So I logged in to my on-prem SQL Server to check on my Hybrid Connections and both of them showed a status of "Status Unknown". I can't find anything on the internet about this specific status.
Nothing changed on my SQL Server other than the fact that I've pegged the RAM....it's at 100% usage.
If I go to the Azure Portal, navigate to either of my Hybrid Connection Overview pages and click on the "Hybrid Connection Url", I get the following message in the browser:
"error": {
"code":"TokenMissingOrInvalid",
"message":"MissingToken: Relay security token is required. TrackingId:*SOME GUID*, SystemTracker:*SERVICE BUS NAME*:*HYBRID CONNECTION NAME*, Timestamp:2021-08-04T04:19:16"}
}
Now....I didn't change anything on my Hybrid Connection configurations. I haven't changed anything about tokens. I have no idea what's going on other than my Azure App Services have been down for 2 days, now.
Any help would be greatly appreciated....
This looks like an authentication error where a token might not be generating when you are trying to make a call to the underlying On prem server
You can refer the SO thread for ServiceBusAuthorization and still if you are facing the issue kindly raise a ticket with MS-Q&A
Microsoft support led me to this article where I found the following information:
Make Sure that the Date and Time are Correct
The Hybrid Connection Manager connects to Azure Relay using Secure Sockets Layer (SSL) on port 443. If there's a problem with your SSL handshake or connection, it will break your Hybrid Connection. If you find that your Hybrid Connection works initially, and then it stops working after about 10 minutes, that's a sign that you need to check the date and time on the machine running the Hybrid Connection Manager. Make sure they are correct because if they're not, your SSL connection may not work.
Well...the time on my server was off by about 16 minutes b/c of a group policy that I had never bothered to fix b/c I don't know anything about group policies. So I looked up how to fix the server's clock and, once that done, resolved this issue.
I have migrated a windows server 2008 r2 to GCP, in the process of putting it into production recreate the disks from snapshot and image in another project where I made sure in its creation that the instance had the default service account with the default permissions among the which is writing to StackDriver Monitoring, even so when installing the agent in the operating system, it does it without any problem, when verifying the service is stopped, when it starts it automatically stops again and registers the following in the event viewer log:
error metadata
On the other hand, and verified that there is communication with metadata.google.internal and not, for this reason request the client to recreate the registry in the DNS for said resolution:
enter image description here
even so, metadata.google.internal still does not respond, despite the fact that the machine does have Internet access open in the firewall and the private access vpc is also enabled.
How can I solve this problem?
I have hosted an MVC application in Azure App Service. The application is not creating any problem when i am testing it in local host. I can easily connect to the Dynamics-365 through the SDK and can do easily CRUD operation.
But when i am trying to login which is hosted in Azure it is giving that error though am not getting this error if i restart the app service. If i restart the app service in every morning then i am not getting this error. But i don't want to restart the app service daily.
Here the same question also has been asked but there is not any solution which has been marked as Solved. Time zone difference between client and server has been discussed here but the part which confused me when i am restarting the app service it is working.
How to solve this issue? I am thinking about app service Auto Healing. Should this work?
Any solution would be appreciated.
Thanks in advance.
From your description of Question it looks like connection pool issue. You probably are not closing connection after your transaction is completed. Try force closing connection (threads) that might solve your issue.
OR
The clock on the Server hosting client application was out of sync with the server having the service.
This is almost always because of a server time skew. The remote server
and the client's system time must be within (typically) 10 minutes of
each other. If they are not, security validation will fail.
I'd check azure service bus and find out what their server time is, and
compare that to your server time.
WCF gives an unsecured or incorrectly secured fault error
https://social.msdn.microsoft.com/Forums/vstudio/en-US/ae4172dd-e215-4a72-b927-d164ce4cc318/an-unsecured-or-incorrectly-secured-fault-was-received-from-the-other-party?forum=wcf
EDIT: 3/16/17
Today we tried creating a new VM in the same private network and resource group (using the same network protection group as well), and ran the test, it worked perfectly. It makes no sense.
using PSping to diagnose this (using port 443 and 8001 to test) we can see the dropped traffic there as well, so it's not the application. The same tests on the other test Azure VM work flawlessly. So it seems it is this particular VM, I just don't understand why, since nothing has changed. We also see dropped traffic to other random sites over 443 (ping and http are flawless).
We've tried rebooting and redeploying with no luck
Original:
Our Azure VM is experiencing random failures in creating connections to several 3rd party systems. occurring in a seemingly random fashion. (every 5-10 min or so an http call will fail)
Since Monday morning, we are seeing web service (http) calls made from the Azure VM fail in a seemingly random fashion- We are getting error messages suggesting the endpoint host is simply not responding. We have engaged both 3rd parties and it appears that these http calls are not reaching their servers at all. Everything was working fine up until Monday, and no changes have been made to the system.
We think the Azure VM (or Azure Networking Limits) are causing the problem because:
We created and deployed the same “test” program on both the Azure VM and an on-prem test VM with the same specs, and the program works fine using our on premise VM.
a. This program simply makes information request calls- a single one to each 3rd party system; the program is run every minute. Thus, both servers (Azure VM and On-prem VM) are repeating identical calls on the same schedule.
b. On the test server, the success rate is 100%- we have seen no errors, even when I bumped it up to try every 10 seconds).
c. On the production server, we see frequent errors connecting to both systems.
In looking at the IIS logs from the 3rd Parties, We see blank spots when we see failed http calls In any event, no suspicious activity seems to be showing up in their case and their logs only show the successful calls.
We show only 10-20 TCP connections on the server, so we are not close to hitting the Azure 500k TCP connection limit.
Pings and tests to any site on the internet from the Azure VM seem to work fine, so network connectivity seems fine.
Are we hitting some other kind of limit on the Azure system, that could be causing these random errors?
I noticed this person had a similar issue but no resolution was found.(Azure VM outbound HTTP is unreliable)
We are running some long-running test apps with Azure Service Bus relay over http, hosted in a windows service and most of the time, these run fine for 2-3 days. However every so often an internal network glich may occur (e.g. firewall reboots) that kills the internet connection.
At this point, the relay is dropped in Azure and our web app can no longer communicate with the on-premise service.
I would have thought that the Azure relay client was fault-tolerant - in that if it realises that it's lost connection with Azure then it will re-establish the connection andf if it can't keep trying until it can.. but it appears that this is not the case. This seems pretty fundamental...?
Only once have I ever seen a "System.ServiceModel.CommunicationException" where the service can't communicate on the internet, and that was when the client was starting up and trying to establish the connection in the first place.
Is there any advice or feedback on handling transient disconnections through the relay service (as it's a cloud --> on-prem direction then the client can't AFAIK ping the server).
If you are still experiencing issues, you may want to contact Azure support to understand why it is disconnecting. The Relay client should reconnect if something happens to the existing connection.
You may want to add ConnectionStatusBehavior to your ChannelFactory to have it output when the status for the connection changes. It will contain the error that caused it to change status.
var connectionStatusBehavior = new ConnectionStatusBehavior();
connectionStatusBehavior.Online += ConnectionStatusOnlineMethod;
connectionStatusBehavior.Offline += ConnectionStatusOfflineMethod;
channelFactory.Endpoint.Behaviors.Add(connectionStatusBehavior);
This issue is solved by Microsoft in version 2.6.5 of Microsoft Azure Service Bus dll. After 1 month of testing it seems to work.