I'm running Moodle 2.4.3. Seems like I have issues with my Scorm API. It throws an error at the end of last slide.
"Trying to set value but API not available."
What could be the reason?
BTW, I'm using Google Chrome 44.
The fact that this is happening at the end of the package suggests to me that the package is closing the connection and then trying to send more data.
Have you tried running the course on SCORM Cloud in debug mode to see what's going on?
Related
We have SugarCRM Enterprise, Version 7.10.2.0 (On-Demand) and tried to install latest version (v1.5.62) of DocuSign plugin (https://sugarexchange.sugarcrm.com/apps/188/sugar-connector-to-docusign) on SugarCRM.
We followed the installation documentation (https://help.upcurvecloud.com/sugardocusign/Sugar_Connector_to_DocuSign.pdf)
Issue: Once we try to login then Error popups "DocuSign Error!" (Screenshot attached)
Any help will be highly appreciable.
Regards
In your Sugar instance go to Administration -> System Settings -> View Log and check the log for FATAL messages during the attempted login time.
E.g. a possible fatal message could be [FATAL] Platform name violation: unknown platform (<used platform name of connector goes here>).
Since Sugar 7.10 the platform parameter during authorization is limited to platforms known by your instance. Unknown platforms will be rejected and authorization will fail.
This could be the problem if the connector has yet to be updated for this new behavior.
If so either the provider of the connector or you should add the platform to the instance. E.g. by adding the file custom/Extension/application/Ext/Platforms/docusign_connector.php with contents:
<?php
$platforms[] = '<used platform name of connector goes here>';
However this is just a guess of what the problem could be as I have not seen your Sugar's log.
If your have any other fatal error messages, feel free to share.
Edit: Actually the platform enforcing seems to be a 7.11 thing rather than a 7.10 thing. So even if you do see an error as described above, it could only to be a warning (for future version compatibility reasons), rather than the actual source of the problem experienced by you.
So make sure to look for other errors as well.
This is an informational post about a recent problem I encountered when installing PCFDEV for use in development and testing.
On Ubuntu-16.04 server core, when I was starting PCFDEV as follows ...
cf dev start
... I was getting the error "Pivotal Network returned: 451 Unavailable For Legal Reasons".
I was using this within the proper terms and conditions (local development and/or integration testing) and my email and password are correct. Why was I getting this error?
Possible Reasons and/or Solutions:
Make Sure to Download the most recent version of PCFDEV (https://stackoverflow.com/a/44029486/1669464).
Logging into the Pivotal.io website with the credentials being used may resolve the issue (https://stackoverflow.com/a/44094847/1669464).
I had exactly the same problem just recently. I logged in at pivotal's network and the issue was resolved.
For me, this problem was caused by an outdated version of PCFDEV I had downloaded a month ago.
Downloading a fresh copy and running the plugin installer will upgrade the plugin to the most recent version. The error went away after this.
I am using apiary service to generate the offline documentation using below command
apiary preview --path=docs/tmpApi.apib
It was working so far, but noticed today that it is giving error "apiary service responded with an error: 410 Gone".
Any idea, what has gone wrong with the service?
Try updating the apiaryio gem please. I was able to make it work on my side.
It sounds like the older gem is pointing to an old version of the service - we'll improve that error message.
Emmanuel
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.
When I go Add Google API's and click on any API I want to download I
get the following error
"There was a problem downloading the API bundles, See Error log for
more details" Can any one help me figure out what might be going wrong
and where is this logs location ?
The Error Log can be accessed by clicking on Window - Error Log.
The server is currently malfunctioning and returning HTTP Error 502 (Bad Gateway). It should be a transient issue, though, and everything should be back to normal soon.