SSRS Performance degradation - sql-server

I have a fairly busy SSRS Instance and the redering performance is consistently degrading to the point where we have set the recyle time config to 60 as work around and im still getting significant reduction in rendering performance within the hour. once the 60 minutes passes the performance goes back to an acceptable level and begins to degrade once more.
I have played with the memory settings within the config but it doesnt seem to have made a difference. The server is dedicated to SSRS and there doesnt seem to be any memory pressure. at this second theres 32gb of memory and 28gb free with SSRS using around a gig.
Looking in the log we have a lot of the following error
httpruntime!ReportServer_0-193!2b84!05/17/2018-15:14:52:: e ERROR: Failed to
create worker request: pipeline=0x56C27945E0, exception=Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_INST130_0-193-131710375157483972. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: An error occurred in the HTTP Runtime object for application domain ReportServer_INST130_0-193-131710375157483972. Most likely, the HTTP request contains an unsupported verb or invalid syntax.
rshost!rshost!2b84!05/17/2018-15:14:52:: e ERROR: HttpPipelineCallback::SendResponse(): failed writing response.
rshost!rshost!2b84!05/17/2018-15:14:52:: e ERROR: Failed with win32 error 0x10DD, pipeline=0x00000056C27945E0.
httpruntime!ReportServer_0-193!2b84!05/17/2018-15:14:52:: i INFO: RsHttpRuntime::ProcessRequest(): calling EndOfRequest() from exception handler of worker request constructor. Runtime=ReportServer_INST130_0-193-131710375157483972. Pipeline=0x56C27945E0.
rshost!rshost!2b84!05/17/2018-15:14:52:: e ERROR: Failed to process request 0x800710dd, pipeline=0x00000056C27945E0.
library!ReportServer_0-193!2218!05/17/2018-15:14:53:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: Unsupported HTTP verb 3., Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: An error occurred in the HTTP Runtime object for application domain ReportServer_INST130_0-193-131710375157483972. Most likely, the HTTP request contains an unsupported verb or invalid syntax.;
library!ReportServer_0-193!2218!05/17/2018-15:14:53:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: Failed to fill worker request, Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_INST130_0-193-131710375157483972. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: An error occurred in the HTTP Runtime object for application domain ReportServer_INST130_0-193-131710375157483972. Most likely, the HTTP request contains an unsupported verb or invalid syntax.
at ReportingServicesHttpRuntime.BaseWorkerRequest.FillWorkerRequest()
I have been looking into this on and off for a while and im coming up blank.

Try turning on the Report Server HTTP Log.
You can then cross reference when the error occurs in the trace log, with the request that was logged in the HTTP log.
Note that the timestamps in the trace log use local time, while the timestamps in the HTTP log use GMT.
I have the same issue as you and found that unsupported verb was OPTIONS, which looks like it is being sent by a Microsoft Office application:
11/21/2018 22:04:17 xx.xx.xx.xx DOMAIN\user xx.xx.xx.xx 20480 ssrsServer OPTIONS /Reports/Pages/ 405 2589 0 1.1 Microsoft Office Protocol Discovery - - -
I have not yet been able to determine how I can stop this error.

Related

running commands from cloud-builders-community/sonarqube/

gcloud builds submit . --config=cloudbuild.yaml
Creating temporary tarball archive of 6 file(s) totalling 3.2 KiB before compression.
Uploading tarball of [.] to [gs://training_cloudbuild/source/1670817617.242895-f55df2adc5e04b5ca65f2ed1a6a12fe4.tgz]
ERROR: (gcloud.builds.submit) 403 Could not upload file [/tmp/tmprwqmw411/file.tgz] to [training_cloudbuild/source/1670817617.242895-f55df2adc5e04b5ca65f2ed1a6a12fe4.tgz]: Access denied.
running commands from cloud-builders-community/sonarqube/ in the instance and getting this error .Need help how to run sonar scanner in cloud build .Need to use sonarqube while running the code in cloud build.
From Troubleshooting build errors documentation
4xx client errors
This group of errors indicates that the build
request is not successful presumably by fault of the user sending the
request. Some examples of 4xx client errors are:
**Error**: 404 : Requested entity was not found
**Error**: 404 : Trigger not found
**Error**: 400 : Failed Precondition
**Error**: 403 : Permission denied
Error message:
ERROR: (gcloud.builds.submit) 403 Could not upload file [/tmp/tmprwqmw411/file.tgz] to [training_cloudbuild/source/1670817617.242895-f55df2adc5e04b5ca65f2ed1a6a12fe4.tgz]: Access denied.
The error stats, the Service Account does not have access to [gs://training_cloudbuild/]
Try adding below permission to build Service Account:
storage.objects.create
storage.objects.get
storage.objects.list

Protocol error when executing cpp-driver datastax

I am currently workinig on datastax cpp-driver in C and was working around some examples when I came across a very trivial problem. While trying to execute the Basic Authentication Script here, I found this error showing up and the code execution getting stuck.
The Error:
1587040775.210 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.3 because of the following error: Underlying connection error: Connect error 'connection refused'
1587040775.210 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.2 because of the following error: Underlying connection error: Connect error 'connection refused'
1587040775.211 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.1 because of the following error: Underlying connection error: Received error response 'Invalid or unsupported protocol version (66); supported versions are (3/v3, 4/v4, 5/v5-beta)' (0x0200000A)
1587040775.211 [WARN] (cluster_connector.cpp:289:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Host 127.0.0.1 does not support protocol version DSEv2. Trying protocol version DSEv1...
1587040775.212 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.1 because of the following error: Underlying connection error: Received error response 'Invalid or unsupported protocol version (65); supported versions are (3/v3, 4/v4, 5/v5-beta)' (0x0200000A)
1587040775.212 [WARN] (cluster_connector.cpp:289:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Host 127.0.0.1 does not support protocol version DSEv1. Trying protocol version v4...
What could be these protocols that are not supported by my machine? Also, after it comes to the last warning, which is trying protocol v4 it gets stuck.
I'm using Casssandra 3.10+, Cpp-driver 2.13.
Anybody with a workaround or a solution would be of much help. Thanks in advance
I've looked around a bunch to find some documentation to back this up but I can't find any, so this part is conjecture. It appears that server version 3 uses protocol V3. It looks like server version 4 (still in beta) will use protocol V4. I suspect V5 is a future iteration that is being planned and still not written in stone yet (and why it's tagged as beta in the warning).
This part isn't conjecture.
If you add this to your code before you connect to the cluster:
cass_cluster_set_protocol_version(cluster, CASS_PROTOCOL_VERSION_V3);
All the warnings about downgrading to different protocols should go away.

IE WebDriver Not Working Consistently On Azure DevOps

Here is the query from one of my developers who is trying his best to setup:
I could install the IE webdriver to the build agent and make some setting adjustments. Unfortunately I can’t get it to work all the time, randomly at some points it works and on others it doesn’t (with 0 change on either config or sourcecode). For some reason sometimes the driver can’t make the proper connection with IE and it times out. I’ve made all the required configurations on the server: https://github.com/SeleniumHQ/selenium/wiki/InternetExplorerDriver#required-configuration including the registry updated, but nothing solved the problem indefinitely. There are cases when I can run 4-5 times with success then on the next it fails for no reason – also reproducible on my local machine, so I do think there is a problem with the IEDriver.
This is the error we receive some times and if I increase the timeout it runs for longer, but dies with the same error.
[error]Error Message:
[error] Initialization method Selenium_Tests__DEV_.SiteTest.startBrowser threw exception. OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:60439/session timed out after 60 seconds. ---> System.Net.WebException: The operation has timed out.
[error]TestCleanup method Selenium_Tests__DEV_.SiteTest.closeBrowser threw exception. System.NullReferenceException: System.NullReferenceException: Object reference not set to an instance of an object..
[error]Stack Trace:
[error] at System.Net.HttpWebRequest.GetResponse()
[error] at OpenQA.Selenium.Remote.HttpCommandExecutor.MakeHttpRequest(HttpRequestInfo requestInfo)
[error]--- End of inner exception stack trace ---
[error] at OpenQA.Selenium.Remote.HttpCommandExecutor.MakeHttpRequest(HttpRequestInfo requestInfo)
[error] at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
[error] at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
[error] at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
[error] at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
[error] at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
[error] at Selenium_Tests__DEV_.SiteTest.startBrowser() in C:\agent_QA_work\1\s\Selenium Tests (DEV)\SiteTest.cs:line 35
[error]TestCleanup Stack Trace
[error] at Selenium_Tests__DEV_.SiteTest.closeBrowser() in C:\agent_QA_work\1\s\Selenium Tests (DEV)\SiteTest.cs:line 53
So this is the state currently, if anyone has any idea on how to continue feel free to advise.
Please help,
Alok

Google App Engine deployment failure: "The request is invalid for an unspecified reason." How to fix?

Our deployments for the default module of a particular app are failing, seemingly at random, at least 50% of the time, which is constantly disrupting our workflow.
With verbose logging turned on via appcfg.py update app.yaml --verbose, this error appears on the terminal:
03:43 PM Uploaded 4 files and blobs.
03:43 PM Compilation starting.
2015-09-23 15:43:51,886 INFO appcfg.py:1735 Send: /api/appversion/precompile, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
03:43 PM Compilation completed.
03:43 PM Starting deployment.
2015-09-23 15:43:54,215 INFO appcfg.py:1735 Send: /api/appversion/deploy, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
2015-09-23 15:43:56,341 INFO appcfg.py:2601 HTTP Error (HTTP Error 400: Bad Request Unexpected HTTP status 400)
03:43 PM Rolling back the update.
2015-09-23 15:43:56,341 INFO appcfg.py:1735 Send: /api/appversion/rollback, params={'version': 'myversion', 'app_id': 'myappid', 'module': 'default'}
Error 400: --- begin server output ---
Client Error (400)
The request is invalid for an unspecified reason.
--- end server output ---
The failure is extremely consistent, in that most of the time we try deploying the module after not having deployed for a few hours, the deployment attempt will fail with the above output.
Then, without changing any app code, retrying the deployment usually succeeds (but at times, the second attempt also fails, requiring subsequent deployment attempts).
This problem started happening earlier this year. Once the problem started occurring, it has not ceased. Before it occurred, we had no no issues with deployments.
The version of the module being deployed has no effect on the rate of deployment success. We are using the Python runtime for this module.
I have already emailed a Solutions Architect from Google about this, but apart from upgrading to a paid support plan to ensure someone looks into this, he suggested I post on here with the hope that the App Engine support team gets back to me.
App Engine support team - can you find out what is going on (and ideally provide a fix)? If you need more information (such as my app ID), please let me know.

Error while implementing Solr using solarium

I installed solr using the Bitnami installation in windows. When i ping the server using solarium.
If use var_dump($result->getResponse()); then everything works fine but if i use var_dump($result->getdata()); I get a error saying JSON could not be encoded.
Similarly when i try to index data into the solr server i get this error.
Fatal error: Uncaught exception 'Solarium\Exception\HttpException' with message 'Solr HTTP error: OK (405) Error 405 HTTP method POST is not supported by this URL<br> HTTP ERROR 405<br> Problem accessing /solr/admin.html. Reason: <br> HTTP method POST is not supported by this URL<br> Powered by Jetty<br> in C:\xampp\htdocs\trial\search\vendor\solarium\solarium\library\Solarium\Core\Query\Result\Result.php on line 104</p> <p>What can be the possible issue?</p>
Bitnami developer here
It seems to be an issue related to Solarium, and not with Bitnami Solr. You can see the issue here:
https://github.com/solariumphp/solarium/issues/101
You could ask there.
I hope it helps

Resources