We have been using Microsofts LiveSearchService successfully for a number of years but just over a week ago it stopped working. It now returns the error
System.Web.Services.Protocols.SoapException: Client error
This happens on line 79 of the Reference.cs file provided by Microsoft:
object[] results = this.Invoke("Search", new object[] {parameters});
I build a SearchRequest object before calling LiveSearchService.Search() and everything looks fine in here, it has the correct appID and is passing a simple query string to the correct site address.
My network administrator assures me that there are no issues with our firewall which would stop any traffic trying to reach the api.search.live.net site and I can access this URL with our appID fine which returns the expected XML.
I have also tried changing the offset to 10 in case the search term was returning a ridiculous amount of results but this made no difference.
We have IIS7 on a Windows Server 2008 R2 machine and the website is written in C#.NET 3.5 using VS 2008.
I am at a loss as to what to try next so any advice would be much appreciated.
According to Bing.com,
...Bing Search API 2.0 AppIDs are decommissioned on August 1, 2012. On and after this date, AppIDs will no longer return results. Developers can continue using the API by signing up for the Windows Azure Marketplace or by submitting a request if greater query volume is needed.
There are pricing plans and a migration guide here.
Related
I'm experiencing an issue using Sophos Labs Intelix Dynamic file analysis: https://api.labs.sophos.com/doc/analysis/file/dynamic.html
For some files submitted, the API returns 202 for several minutes, then returns 404, as if the job is suddenly lost. There is no explanation or report provided. I did not experience this issue until this morning when suddenly it happened for 7 different files, although we have not made any code changes.
Why is this happening and what are we supposed to do to handle it?
Some example dynamic analysis jobIDs which now return 404: 10c37c488e86b6871c3f6224ff5273e1, bc900e7bfb8bb25e1f8f127dc25ab8fe, 48cda26c2e3cb54d0b3f4b79ac1ddb7e
Also, is this the correct forum for support requests? I am also trying to go through https://support.sophos.com/support/s/sophos-technical-support but they don't seem to have any knowledge or understanding about Intelix API. My credentials for the API don't appear to be linked to any kind of support portal?
Thanks!
This has been an issue every now and then for the last year but now since last Friday it's dramatic.
None of our queries are refreshing like they were before.
Message:
Error interacting with REST API: Couldn't connect to server ERROR
[HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with
REST API: Couldn't connect to server Table:
Notes:
PowerBI - Desktop refresh works
The table or view triggering the error differs, it's not always the same table or view.
It seems to be related to running parallel queries, loading from the same table simultaneously.
Dataflow jobs are reported to be working, since the load sequentially
Can Microsoft and Google talk to each other? On both sides they are pointing to each other.
It seems that this has affected several users in the last days.
I found this Public Issue Tracker where it's said that the BigQuery Eng team is working on this. I could also see that there are no workarounds available for now.
Feel free to ask for updates or add additional questions on it.
We have a SaaS application running with an AngularJS front end and Jasper Reports integrated using the Visualize.js framework. We are seeing an issue where after the Jasper server has been running for a while, the call to get the input controls will stall in the browser. The strange thing is that all the other calls proceeding it (auth, resourcessearch, etc.) return just fine. It seems to be only the inputcontrols that stalls. When this happens, we see no errors in the logs, memory & CPU on the Jasper server are fine, etc. To fix the problem, we are generally forced to bounce the Jasper server.
Has anyone experienced this problem? Any advice?
A little more info:
Jasper Professional version 6.1.1
Seeing the problem in all supported browsers (IE, Firefox, Chrome)
Problem happens both with a single user and with concurrent users
Input controls will sometimes return after 8-10 MINUTES if we wait
long enough (with Apache timeout cranked to 15 minutes)
I have an application hosted on a dedicated Win Server 2008 R2.
The customer need past 3 months data to be entered into the application.We have only one method and that is setting the Server System Date to 3 months back data, till all the users completes updating the past data.
So my question is does setting the System Date to past date have any kind of impact in normal functioning of server or the network it's part of.
Please advice...
The server might automatically try to correct its time back to current time. If this server is apart of AD then there could be some issues. If it is apart of AD and is a GC then users might not be able to authenticate do to a time discrepancy. Updates via Windows Updates will also not work until the time is corrected. If this is the only way I would suggest getting it done as quickly as possible and setting the time back.
Background:
I have a Windows 2008 R2 box set up with SQL 2008 R2 both the Data Engine and Reporting Services.
I have configured Reporting Services to use custom authentication (FormsAuthentication) that I wrote.
The custom authentication gets passed the name of a user to treat as the admininistrator assuming they login correctly in the Reporting Services configuration files.
The custom authentication when queried by Reporting Services about the current users permissions will always return true when logged in as the user configured as the administrator.
I have uploaded a Data Model to Reporting Services (using the built in Report Manager app) which uses a Data Source I added (also using built in Report Manager app) which connects to a database on the same box.
I have a ASP.NET MVC3 web app (also on same box) that is configured to use the Reporting Services web service to do things like list existing reports, run existing reports and a link to start Report Builder 3.
The ASP.NET MVC3 web app shares it user logins with Reporting Services, i.e. the custom authentication used by Reporting Services verifies user details by looking at the same data as the web app.
The ASP.NET MVC3 web app is available externally.
Problem:
If I log into the web app remotely, start Report Builder 3 via link, login as UserA, use the Report Wizard with options >> Create dataset >> select Data Model (see above) as the source of data >> choose 1 table of data (e.g. Organisations) >> click button to preview data >> click next -- BANG - REPORT BUILDER 3 HANGS.
If I log into the web app locally on the server hosting everything, start Report Builder 3 via link, login as UserA, use the Report Wizard with options >> Create dataset >> select Data Model (see above) as the source of data >> choose 1 table of data (e.g. Organisations) >> click button to preview data >> click next >> choose row/column groups and values, report style and click finish. I can then run the report and save it. -- EVERYTHING WORKS!
Things I looked at:
If I do a SQL Profiler Trace against
the both the Reporting Services
database and the database that the
Data Model is using in the case where
it hangs it appears Reporting
Services is getting into some kind of
loop continuously asking the
Reporting Services databases if there
are any running jobs. When it works
it never asks the Reporting Services
about Running jobs at this point.
If I use the Data Source the Data Model uses in Report Builder 3 as the data source then it does work. HOWEVER this then prompts for a SQL Server login and requires the you open the SQL Server port on both the server and the remote machine! Not good.
This is driving me crazy. Any body with elite skills in the black magic of using Reporting Services 2008 R2 and Report Builder 3 that can help be figure this out will be deserving of everying computing award going.
EDIT: I found this while Googling again (Forum post, Google Cache) and got really excited but couldn't quite make sense of what the poster was saying and changes I made trying to follow it just broke all Reporting Services access so I rolled back the changes. Unfortunately the forum is archieved (and a bit rubbish) so I can't contact or leave a message for the poster.
Peter, my experience with Reporting Services is extremely limited; I've been building reports for SQL Azure Reporting Services using BIDS.
I had a problem whereby BIDS was crashing when I attempted to preview a report and it took me hours to work out that my reports weren't checked out of version control and BIDS couldn't save them. Rather than giving me any kind of meaningful error message, Visual Studio simply crashed on me.
Maybe, just maybe, your issue is that Report Builder can't save the report and is crashing for a similar reason. However, from your description, I'd suggest that if it is the case, it's likely to be a permissions issue rather than a read-only one. I'd check that the security context for the access of data is as you expect when logging in remotely.
Sorry that I can't give you a definitive answer, but maybe it will suggest somewhere new to look.
It turns out that this is caused by a school boy error by Microsoft of using one connection and not opening/closing it appropriately. MS were able to give us this workaround when we called them:
Basically after you've got the Report Builder 3 clickOnce app installed, locate it on your computer and then inside the system.net tag of the app.config file add the tags below.
<connectionManagement>
<add address="*" maxconnection="1024"/>
</connectionManagement>