I install and config SSRS-2016 on windows server-2012 and IIS-7 everything is good until i restart server or power failure then i get HTTP Error 503. The service is unavailable.i find a alternative solution to solve this.when i change web portal URL and apply changes the problem disappear.how to solve this problem?
after 10 day nobody answer my question.but i find answer
just change SSRS-2016 service from automatic to automatic delay
Related
I used cPanel's Transfer Tool to move my websites to a new IP address. It was a temporary move and I wanted to revert back to my old server today. First thing I noticed was the transfer tool changed all the A records for all sites. I changed these back using swapip, and then tried accessing the sites. They load for a very long time and finally fail with:
Service Unavailable The server is temporarily unable to service your
request due to maintenance downtime or capacity problems. Please try
again later.
Additionally, a 503 Service Unavailable error was encountered while
trying to use an ErrorDocument to handle the request.
From numerous threads, I realized 503 usually occurs when System PHP-FPM is on. However, I didn't set this on niether before nor after moving. I didn't change any other settings except the DNS, so I'm guessing it should be a DNS issue, not sure if DNS issues can cause 503 errors. I've been struggling with this for a day now.
Checking Apache Error log, I see attempts to connect to the server I temporarily moved to:
[proxy_http:error] [pid 1659:tid 47454830633216] (110)Connection timed out: AH00957: HTTPS: attempt to connect to [new.ip.address]:443
After a few days digging, I found my mistake and how to rectify it thanks to the cPanel Support. I thought it worthwhile sharing in case anyone else faces the same problem:
First, I had to disable the live transfer feature before doing the transfer. It prevents the tool from disabling IPs and proxying domains.
Given I hadn't I had to rever the changes the tool had made, which basically involved running the following scripts from the command prompt:
$ whmapi1 unset_all_service_proxy_backends username=$USER
$ /scripts/xfertool --unblockdynamiccontent $username
$ whmapi1 unset_manual_mx_redirects domain=domain.tld
The link above explains what each of these scripts does.
In our application we have a REST integration with another service
It worked fine untill recently, however, sometimes we are returned with 502 Bad Gateway in the application
We send HTTP requests through curl and it seems that to be working but then we are presented with the error I described above
The client is believed to have a firewall installed
Whenever we face the problem, I usually ask the administrator to turn this thing off and it does the trick but I'm not sure whether it has something to do with the code?
My question is what causes such behaviour and how to avoid it in the future?
Search in Sharepoint 2013 gives
Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator.
The Search Operational Log shows
w3wp.exe: Query processing component 'net.tcp://server/06CE4A/QueryProcessingComponent1/ImsQueryInternal' changes its status to 'Failed'.
Same errors are shown in the ULS logs.
What has been tried (several times)
Resetting the index
Recreating QPC
Recreating complete search service
Clearing cache
Restarting search service and host controller
Restarting IIS
Restarting Server
Running PSConfig
Running Configuration Wizard.
Banging head on the wall as well as hitting the server ;)
Any help would be appreciated, thanks in advance
Imran
We had a similar issue that we resolved by looking at the firewall of the Search Server. We turned on dropped packet logging and noticed that every time one of our front end servers performed a search, packets were dropped from port 808. We enabled incoming TCP on port 808 on the search server and that resolved our issue.
I'm having a difficult time with SignalR. It connects from time to time. Sometimes it gives a 404 and automatically re-connects and works just fine.
Most of others fails I recieve Server timeout elapsed without receiving a message from the server.
I've set the timeout to 100 secs and still nothing.
Am I missing some IIS configuration? I've found this answer with no further details...
WebSockets don't work with SignalR Core when deployed to Prod
All installed software and apps are in their latest version
Well nevermind, I just fixed it with the most bizarre way....
IIS CONFIG
just set Websockets to disabled!!
We are connecting to a webdav server through IIS 6 using iPads running iAnnotate. Friday we performed some maintenance where all we really did was pause the virtual server/domain controller where the webdav is setup.
Ever since we did that, we are able to browse the webdav connection from iAnnotate on the iPads but when we try to sync a file back (PUT method I'm assuming) we get an error 411, which actually appears to be error "HTTP Error 401.2 - Unauthorized. You are not authorized to view this page due to invalid authentication headers", according to IIS.
Does anyone have any thoughts or ideas on this?
We figured out what was causing our issue although I may not be able to explain entirely why it mattered.
In IIS there is a setting in the "HTTP Response Headers" under "Set Common Headers" called "Enable HTTP keep-alive". We check marked this option as true and our Windows Authentication started working again.
It seemed to have something to do with the connection not staying open between requests and the application or IIS not realizing the connection was restarted during the SYNC operation.