I open information link in web browser i.e., Administration Console of Spotfire, it opens successfully. But, the same information link when I try to open in desktop version of Spotfire getting below error
Image of Error - Spotfire
Continuation of same error message - Spotfire
Note: The same information links are accessible from Web client but not from Desktop client of Spotfire.
Related
I want to get the data into the web query from url https://www.screener.in/screen.....all-stock/
This screen can be accessed with user is logged in
but when user is not logged in this screen cannot be accessed
I want to retrieve this data into the excel.
Added the following code in Advance Editor and authentication type as basic
Following error is thrown, attached in the xls
Any help in this regards is highly appreciated.
I am on the Demo platform trying to create a PowerForm. When I press "Create PowerForm" on a template I get the modal for creating the powerform. But when I press the Create button nothing happens.
I get the following error in the console though:
https://appdemo.docusign.com/api/accounts/{{UUID}}/powerforms
Failed to load resource: the server responded with a status of 400 (Bad Request)
I don't think this is a local error, as Docusign Live support tried to suggest.
Also the documentation for PowerForms shows a dropdown under the Use button. But my Use button is just a button, not a dropdown.
This issue is now resolved. PowerForms should work just fine on Demo.
I have deployed ssrs reports to sharepoint. When I browse the report first page is getting displayed but when i moved to next page i am getting below Error.
Error
Report Server has encountered a SharePoint error. (rsSharePointError)
Object reference not set to an instance of an object.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Also in the Report Page 1 for exporting the reports data when i click the Actions menu (to list the dropdown items) for type of export i am getting the error
**An Error Occured with the data fetch. Please refresh the page and try.**
Kindly let me know what cause this error. No application log was written in the sharepoint application.
Or kindly let me know what is the debug steps to find the underlaying error to find the root cause.
I am using sharepoint 2010 and ssrs 2008R2
I'm using MS Window server 2008 and is trying to import loads of options(picklist) using OptionSet Import wizard. When setup a new connection and tried to connect to the CRM on the server itself I'm getting an error message below
Have got the organization name as well input with the configuration information when clicked on load button. But when clicked on connect button (Do you want to connect now to this server) there is no luck. I'm not able to identify where I'm going wrong.
Screenshot is below
Please delete Live Device ID in your current system
start->select your user-> Live Device ID
and delete the LiveDevice.XML file and try again.
I'm attempting to create a filter using PerformancePoint's Dashboard Designer. After going through the wizard, however, the "Confirmation" page displays the following message:
No filter data retrieved
Warning 1: Filter was created but no
data was retrieved. To resolve the
problme, follow the step(s) below.
1. Verify that the data source for this filter is configured properly.
2. Check the server event log. Additional information about this
problem may have been recorded.
The data source is fine... I used the data source to build the report that the filter is supposed to be filtering... no problems with the report.
As for the logs, the only troubling spot is when the call is made from the PerformancePoint server (part of the SharePoint group) to the SQL Server -- the Event Viewer on the PerformancePoint server has a long message of which the important part is "An existing connection was forcibly closed by the remote host."
Has anyone else had trouble with Filters in PerformancePoint?
This was caused by a limitations in the checksum mechanism for Kerberos which would kill MDX queries. Microsoft released a hotfix for this issue: http://support.microsoft.com/kb/969083