I have been making requests to my cloud REST Service over the two past weeks. Everything was fine until yesterday.
Over the past days, I kept re-publishing my service to the cloud to test some of its operations with a client. I DID NOT change anything in my web.config, just some method bodies.
Yesterday, by making the simplest GET request to my service, through my browser or Advanced Rest Client, i started getting the following error:
The server encountered an error processing the request. Please see the service help page for constructing valid requests to the service. The exception message is 'The underlying provider failed on Open.'. and so on
I suspect after doing my research that this means I clearly have a connection error with my database which I don't get since it was working fine so far.
I also tried to Stop and Start my service in the Azure Production Enviroment but without any luck. Also the server firewall is configured as it should be.
Any answers would be much appreciated.
Thanks.
In my experience these generally tend to be azure service outages. There is currently 'Scheduled maintenance' occurring on all DB instances which may be affecting you.
http://www.windowsazure.com/en-us/support/service-dashboard/
Related
As part of a project we are implementing Azure OAuth authentication for a SQL Server instance hosted in the Azure cloud. We are using the MS-TDS (Tabular Data Stream) protocol to create the federated authentication packet which contain the access token data and the other parts needed in the packet.
We are now stuck at a point where no matter what we do, we are not able to get a successful response. As of now we are getting the below error from the server
(47089) Reason: Login failed because Azure Dns Caching feature extension is malformed
Even though we are not populating anything related to DNS Caching in the packet knowingly. A major part of the problem is that we don't understand the error much by itself. We have looked over the internet and haven't really found much help yet. Do we have any resource we can refer to be able to understand this better? I mean the packet itself is huge and it is proving to be really difficult to debug this without any kind of documentation from Azure side.
Any help on this is much appreciated.
I have a servlet hosted within Google App Engine. As part of the business logic, it performs a HTTPS request to another webservice. I started getting SSL connection reset exceptions but they appear to be happening in a random fashion. I haven't been able to repeat the exception and they start happening even more over time but then can fade away and come back. I've performed stress testing on the remote service directly from other machines and never receive a single issue. The only way I've been able to deal with this is by redeploying the application but it can take a few redeployments before the issue goes away. I am confident it isnt an issue with the remote service but something happening within Google App Engine.
Thank you for your comments, we just got to the bottom of this yesterday. It was a dynamic application being deployed, so the instances should be managing their resources by themselves. However, what was happening is that an instance was running low on memory which resulted in SSL connection resets. This is why they were appearing in a random manner and degrading even worse overtime. The way this was resolved was to upgrade the resources, changing the deployment configuration to use an F2 instance rather than the default F1 instance. Since doing so there hasn't been a connection dropped. Thanks again for your responses and I hope this helps anyone who may experience something similar.
Google Cloud Server suddenly stopped working. Yesterday I got the error , " Error establishing database connection".
Today it is "Request Timeout
Server timeout waiting for the HTTP request from the client"
Any suggestions to get over this issue??
This could happen based on the configuration you have on your app.yaml. If the instances are overloaded you might encounter a 408 when trying to communicate with the server, in that case changing the scaling configuration on your yaml file might fix the issue.
This document can help you with configuration of your yaml file, information with auto and manual scaling, healthcheck, readiness check etc.
And this article would give you general information on how scaling work on App Engine and best practices.
Also, if you’re using WordPress, this is a common issue with WordPress
I've been trying for a while to call an existing SOAP web service from InTouch Wonderware or MS SQL 2014. It doesn't matter which of the two calls it, as the Wonderware project reads/writes to the SQL Server database anyway.
My knowledge is mostly limited to Wonderware and its in-program options to access the SQL Server database, which doesn't work well with the usual guides on the web service topic.
The web service is provided by the customer, over a decade old and outsourced, which rules out any changes to it. The goal is to request raw material data from the web service by ID, and later returning the produced material data. The parameters of each function is documented, but the only existing URL requires username/password and directly shows the content of the WSDL file. That file (when saved locally) works on SoapUI, and test cases deliver the required results.
My problem is the first step - connecting to the web service and sending/receiving the messages. WebSVC (the InTouch web service client) cannot handle the basic authentification, even failing to connect when including username and password in the link (which works in any browser). Guides on that topic are often outdated, or don't match the problem at hand.
As my knowledge of databases and web programming is limited, how can I use the web service (in a preferably uncomplicated way)? Performance doesn't matter - the database handles less than 10 requests per minute on average, and delays don't disrupt anything essential.
To quote Jeroen Mostert's comment: "if you're on Windows, PowerShell's New-WebServiceProxy allows you to wire up SOAP services quite easily, and inserting things into SQL Server from it is equally simple (Invoke-Sqlcmd)."
This approach works. To sum up the steps until I got an answer from the web service:
Upgrade to PowerShell 5.1 (Win7 VM didn't have it)
Set up WebServiceProxy by microsoft guide
Add credentials, attributes and test method by external guide, solving the authentication issue and getting the required input format
My cloud sql instance became unresponsive today (unable to connect using my normal credentials via mysql-client or the google cloud console) so I decided to restart it to see if that would help, since I couldn't find any better debug suggestions. That was over two hours ago and the db still shows as restarting in my cloud sql dashboard. Others that had this issue were told to email cloud-sql#google.com but it's been over an hour already with no response. I wonder if trying to kill the instance via google's api would clear things up but don't want to screw myself even more.
is this still happening? Would you send an email to cloud-sql#google.com with the link of this stackoverflow post and your instance name? Thank you.