Error Encountered In Querying For Trusted Applications
to provision a UCMA 2.0 application for Office Communications Server 2007 R2 ★★★★★★★★★★★★★★★ Chris Mayo - MSFTJanuary 22, 20102 0 0 0 When developing with UCMA 2.0, there are a few steps you need to complete on your computer before you can develop and debug your code, including: Preparing your computer for trusted connections with OCS. Provisioning your application to be trusted by OCS. More often than not, when someone pings me with issues getting their UCMA 2.0 code up and running, the issue is with the environment rather than the actual UCMA 2.0 code. Provided you have Visual Studio 2008 and UCMA 2.0 installed and your development machine is in the same domain as your OCS server, here is what you need for a UCMA 2.0 dev environment: Prepare Your Computer – OCS and UCMA 2.0 applications communicate over trusted TLS/MTLS connections established using certificates. You need two certificates on your development machine in order to establish those TLS/MTLS connections: Local Machine Certificate: This is the cert you will use in UCMA 2.0 to connect to OCS. This certificate is located in Console Root\Certificates (Local Computer)\Personal Certificates. If you don’t have this certificate, request one from your domain controller. Trusted Certificate Authority Certificate: This is the certificate that both your development machine and the OCS server will have from joining the domain. This certificate is located in Console Root\Trusted Root Certification Authorities\Certificates. Provision Your Application – OCS will only accept secure TLS/MTLS connections from contacts or applications that are trusted. To create a trusted application (represented by the ApplicationEndpoint class) you can use the ApplicationProvisioner sample that ships with UCMA 2.0. See the topic “Using ApplicationProvisioner” in the UCMA 2.0 documentation. Once you have both of those environmental details taken care of your development machine will be able to create
administration BlackBerry Enterprise IM for BES12 Version: 12.2 Remove a trusted service record from Microsoft Active Directory If you upgrade BlackBerry Collaboration Service 12 version 12.1 to BlackBerry Collaboration Service 12 version 12.2 and you used automatic provisioning for the initial installation, you must remove the trusted service record that was created. Before you begin: Verify that the account that you use to complete this task is a member of the RTCUniversalServerAdmins group https://blogs.msdn.microsoft.com/cmayo/2010/01/22/how-to-provision-a-ucma-2-0-application-for-office-communications-server-2007-r2/ or a group with similar permissions. On the computer that hosts the BlackBerry Collaboration Service 12 version 12.1 that is upgraded to BlackBerry Collaboration Service 12 version 12.2, complete the following steps: Navigate to
This appendix describes common problems that you might encounter when using Discoverer and explains how to solve them. It contains the following topics: Section D.1, "Problems and Solutions" https://docs.oracle.com/cd/B14099_19/bi.1012/b13918/tshoot.htm Section D.2, "About Discoverer diagnostics and logging" Note: For information on troubleshooting https://support.klipfolio.com/hc/en-us/articles/216696817-Connecting-to-data-sources-error-messages Discoverer performance and scalability, see Section 12.3.13, "Troubleshooting Discoverer performance and scalability". D.1 Problems and Solutions This section describes common problems and solutions. It contains the following topics: Section D.1.1, "Discoverer Viewer reports errors when exporting using Microsoft Internet Explorer v6.0" Section D.1.2, "Discoverer and Oracle Applications certification" error encountered Section D.1.3, "Discoverer reports a network error" Section D.1.4, "Discoverer reports the error ORA-12154" Section D.1.5, "Pop-up stopper issues" Section D.1.6, "Netscape Navigator 4.x issues" Section D.1.7, "Discoverer Plus reports RMI error" Section D.1.8, "Discoverer memory issues" Section D.1.9, "Discoverer Plus Relational help issues" Section D.1.10, "Configuring a SMTP Server for Discoverer Viewer" Section D.1.11, "Problem With Microsoft Internet Explorer, HTTP error encountered in 1.1 Protocol and Compressed Data" Section D.1.12, "Error: Could Not Open Web Cache Connection (WWC-40019)" Section D.1.13, "Opening an exported Web Query file in Microsoft Excel containing non-ASCII dynamic parameter values" Section D.1.14, "List of values (LOV) is too long for a Discoverer portlet URL" Section D.1.15, "Specifying a parameter by index value in Microsoft Excel does not work for Web Query file" Section D.1.16, "Redirect conflicts with Single Sign-On (SSO) and Secure Sockets Layer (SSL)" Section D.1.17, "Worksheet customization issues" Section D.1.18, "Out of memory problems for the OC4J_BI_Forms JVM process" Section D.1.19, "Graphs do not display in Discoverer Viewer" Section D.1.20, "Discoverer Portlet Provider issue" Section D.1.21, "Availability of Discoverer connections" Section D.1.22, "Passwords not accepted as a URL parameter" Section D.1.23, "Customizing Discoverer Viewer" D.1.1 Discoverer Viewer reports errors when exporting using Microsoft Internet Explorer v6.0 When Discoverer Viewer users export data using Microsoft Internet Explorer v6.0, a bug in Microsoft Internet Explorer can lead to a number of errors being reported. Note: Discoverer supports data exported Microsoft Excel 97 or later. Problem 1 Microsoft I
Sources Connecting to data sources: error messages When you connect to a data source through Klipfolio's Web Accessible Resource connector, you may encounter an error message. To help find a solution to the problem, refer to this list of error codes and responses. Unexpected Error Error Message Possible Reason Oops! We encountered an unexpected error. Try again or contact support. You made a spelling mistake in the URL. Hey, the security certificate for this connection is not trusted. This means we can not rely on this certificate for identity information. Normally, sites will send trusted identification to prove that you are connecting to the right server. In this case, the site’s identity could not be verified. Check with our support team for help resolving this. Oh no, the connection to the service failed. This is known as a SSL handshake failure. It means we could not complete a secure connection with the specified server. Reach out to support@klipfolio.com for help with this problem. 404 Error You may have used an invalid API query in the URL field. There are two scenarios where you may encounter 404 error messages: When connecting to your data source. When you're reconfiguring or refreshing your data source. Check the API reference documentation associated with the service to which you want to connect. 403 Error There is an issue in the Query Parameters section. For example, you may have entered the wrong Application Key. Double check the information under Name, Value and Type and try again. 401 Error There is an issue in the Authentication section. For example, you entered the wrong Username and Password. Check your account details. Related Links Authentication method: OAuth Token Authentication for Web Accessible Data Source Authentication method: 2 Step Authentication Authentication method: Basic HTTP Authentication Authentication method: API Key Authentication Updated May 03, 2016 20:25 Was this article helpful? 0 out of 0 found this helpful Facebook Twitter LinkedIn Google+ Have more questions? Submit a request Klipfolio Feature Index Pricing Integrations Live Dashboard Examples About Us Blog Careers Clients Contact Us Resources Articles KPI Examples Dashboard Examples Webinars Case Studies Guides Other Press Support Security Free Trial Hosted on: Trusted by: Proudly designed and built in Canada, eh. Copyright © 2016 Klipfolio Inc. All Rights Reserved. Terms of use Questions? Feedback? powered by Olark live chat software ×