I am getting these database errors in my asp.net website
[DBNETLIB][ConnectionOpen (Connect()).] |
| Query timeout expired |
Login timeout expired |
SQL Server does not exist or access denied
same errors are repeating twice in a week.I get more than 50 errors at a time.
I have checked the errors logs and I ran the queries causing these error there no problem with execution time of these queries.
I asked the sys admin and database admin if there errors in connection there seems to be no problem with the connections as well.
Same data or queries are running the another website on same database but I found no errors on that another website.
Any insights on what is causing these errors and how to troubleshoot further.
Related
I get this error whenever I want to access the database that I have created and it shows this message
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed
Does anyone know how to solve this?
After running for a couple of days Google Cloud Composer web UI returns the 502 Server Error indefinitely:
Error: Server Error
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.
The only way to fix it is to recreate the Composer environment. Though after running for a couple of days the new environment crashes with the same error.
Image version: composer-1.4.0-airflow-1.10.0
Python version: 3
Anyone knows what's the root cause?
I don't run Cloud Composer but I suspect that there's a case where the webserver has exited from all the web worker threads. This can sometimes happen when airflow has an extended timeout reading or writing to the database; either due to a held lock, or network connection issues. It probably is configured to restart if it fully exits, but there are some cases were the airflow webserver command will still hold on without exiting even though all web workers have exited.
Alternatively the 502 is about the identity provider implemented for GCP. If that's the case you might find you need to sign out of your Google login and use the sign in flow provided by Airflow (if it responds to a private browser session or a signed out session).
I was facing the same 502 error and it turned out to be an issue with the DAG itself. As mentioned:
https://cloud.google.com/composer/docs/how-to/using/troubleshooting-dags
"The web server parses the DAG definition files, and a 502 gateway timeout can occur if there are errors in the DAG."
Visible in Composer / Monitoring
Web server was affected by an issue with the DAG itself. We solved it by deleting the recently added DAGs, after couple of minutes the Airflow UI was up.
I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD
I'm refactoring a very old reports generating function in an ORACLE web application. It used JavaScript to construct a URL, sending to the reports server to run a reports. What I want to do is processing it in the database, in PL/SQL procedures(invoked through mod_pl/SQL). I tried to use utl_http.begin_request to do that, but sometimes when the output file is large(PDF format, about 20 pages, 1.5M), I received an error:
ORA-29259: end-of-input reached.
The test codes for sending requests are quite simple:
--------upgraded 2013/08/27----------------------------------------------------------
UTL_HTTP.set_transfer_timeout(1000);
--some params setting....
myIdent := SRW.RUN_REPORT(myPlist); --here raise the exception(ORA-29273:request_failed; ORA-29259: end-of-input reached.) and procedure stoped.
r_stat := SRW.report_status(myIdent,myPlist);
#ThinkJet, Thanks for your help.
I logon the report server, found that the report still running after I got this exception in my program, and finally finished succefully.I tested for many times, and found everytime I got the exception just 5 minutes after I started request,no matter what kind of reports I was running and what size it was (sure, all big size,running for over 5mins).I'm wondering if it's something about configuration on oracle application server?
Does anyone have idea about this? Many Thanks.
ORA-29259 while SRW.RUN_REPORT
is ias 10g , this is cause by httpd.conf timeout parameter configuration
just
1.edit $ORACLE_HOME /Apache/Apache/conf/httpd.conf
change "Timeout" great than your report running time
2.restart http server and test it.
opmnctl restartproc ias-component=HTTP_Server
It take a time on Oracle Reports side to produce a big reports so a timeouts can occur sometime. Try to increase timeout with utl_http.set_ransfer_timeout procedure before originate a request and look if it helps.
This morning I have tried to load all my websites on my local PC that has IIS 7.5 and straight away i get a HTTP 503 Error.
HTTPerr log says: 2012-08-17 08:43:26 127.0.0.1 49326 127.0.0.1 80 HTTP/1.1 GET / 503 3 AppOffline web80
So my application pool is not starting. I try restarting the app pool in IIS and I still get the error. When I look at the App pool I see that it has stopped. So I look in Event viewer:
Error: WAS : Application pool 'web80' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
Warning: WAS : The Windows Process Activation Service failed to create a worker process for the application pool 'web80'. The data field contains the error number.
Looking around the web and stackoverflow, the problem seems to be caused by app pools identity being apppoolidentity. I changed this to local system and it works.
But why out the blue would this just stop working? I've read another solution that you need to provide permission to
C:\Windows\System32\config\Schema but I don't have a Schema folder.Could that be the reason why?
Really all I want to know is how do I get the application pool to reuse the apppoolidentity or where can I look to try things out? I could try re-intall iis but if I can figure out what causes this, I might be able to prevent it in the future.
Thanks
I just ran into this recently. In my scenario, I had the Application Pool Identity set to my Active Directory account under the 'Custom account' setting. Recently I updated my password so I just reset my password for the 'Custom account' accordingly and I was able to reload my application.