this error rised when I tried to submit an assignment :
Submission failed: unexpected error: support for url transfers was disabled when Octave was built.
How can I enable this support for url transfer now?
ok, this is just a guess since you provided very little information about your system. Are you the administrator of the system running Octave? Or are you running on octave-online.net, or a user account on a laboratory computer, or similar?
The version of Octave you're using was likely built with the --without-curl switch enabled. I do not believe the functionality is present to just 'turn it back on'.
You would need to recompile Octave with URL transfers enabled. Or reinstall from a binary implementation with URL transfers enabled. Or switch to a different system where you have the system rights to do so.
Related
When I try to install google cloud SDK, I was getting the following error:
ERROR:
(gcloud.components.update) Failed to fetch component listing from
server. Check your network settings and try again. This will install
all the core command line tools necessary for working with the Google
Cloud Platform. Failed to install.
After reinstalling python (v3.7.0), I added the path and also added CLOUDSDK_PYTHON environment variable to make sure. Now when I attempt the installation, the installation simply hangs:
If I attempt the installation trough terminal by executing install.bat, it also gets stuck after requesting to send diagnostics to google:
Welcome to the Google Cloud SDK!
Active code page: 65001
To help improve the quality of this product, we collect anonymized usage data
and anonymized stacktraces when crashes are encountered; additional information
is available at <https://cloud.google.com/sdk/usage-statistics>. This data is
handled in accordance with our privacy policy
<https://policies.google.com/privacy>. You may choose to opt in this
collection now (by choosing 'Y' at the below prompt), or at any time in the
future by running the following command:
gcloud config set disable_usage_reporting false
Do you want to help improve the Google Cloud SDK (y/N)? n
Nothing gets printed after that.
it seems that the "(gcloud.components.update) Failed to fetch component listing from server" error might be caused by some proxies or antivirus in your environment, I'd recommend you to try a clean installation in a vm or using another network.
Also, I was able to find soem similar errors for this on issue tracker and the team gave a soltion at comment10, also, as you can see on the issue tracker, sometimes this behavior is because the Python SDK is installed on default "Program Files" location, you could give it a try by changing the location of the python SDK
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.
I am in the process of adapting the security configurations to LDAP on the Pentaho BI-server. I made the modifications a while back (simply to direct Pentaho where the LDAP references were), and the login process worked just fine. No other modifications have been made to the configuration.
However, the free month trial that I had been using ran out, and I had to switch to an Enterprise license. Ever since then, I have been having problems with the login. I am using a Firefox browser on a Linux VM.
When I enter my LDAP login credentials (that I am sure are correct and working) (Screenshot 1: Normal-appearing login screen hosted at localhost:8080/pentaho/Login)
I am redirected to the page I first saw when my free trial ran out (Screenshot 2). I see the error
Missing or expired license. To continue you must update your Pentaho BI Platform license. If you are not ready now you may log out and come back later.
but it shows all my licenses as up-to-date and valid.
I would think that this is maybe some sort of glitch, except that if I modify the web address it redirected me to
http://localhost:8080/pentaho/api/repos/admin-plugin/resources/licenseManagerModule/licenseManagerAdmin.html
and change it to
http://localhost:8080/pentaho/
after putting in my credentials, I am taken to my User Console dashboard, and I am logged in.
I am not even sure what type of problem I am running into. Is it coding related, browser related, Pentaho server related, or something else altogether? I would appreciate some guidance into where I might look to fix it.
Your problem is indeed a missing license. You need Pentaho BI Platform Enterprise Edition license to run PUC.
So today, whenever I try to sign My Blackberry app using the WebWorks packager, I get this error...
"General failure. Please try again. Server may be unavailable".
My proxy settings have not changed and I have been using the same command line instruction with success before.
I've also checked the status of the Blackberry signing server using the following link...
http://isthesigningserverdown.com/chart/index.php?sigType=RBB or RCR or RRT
And everything appears to be online!
So, where could I be going wrong? Here's the command line instruction I've been using. First, I navigate to my Blackberry build folder and run the following instruction against it...
bbwp appname.zip –g <password> –o z:\projects\appname\signed
It goes through through parsing the various elements. The signing tool pops up and then the error is generated.
So, after a couple of days of banging my head against the wall-the answer finally came to me. I'm on a MAC but am also using a Windows virtual machine for Blackberry developement, which is running on another network altogether and this specific network is using a firewall, which, according to the network administrator, is currently experiencing a severe technical problem.
The way round it was to sign my Blackberry app using configured proxy settings to communicate with the signing server and viola! It worked!
I am trying several examples from the forum, most of the samples are not in my phone but are unable to be installed via the B4ABridge even it says it is connected. How can this be fixed?
this is what it says:
Installing file to device. 0.20
Installing with B4A-Bridge.
Installation will fail if the signing key is different than the previous used key.
In that case you will need to manually uninstall the existing application.
Completed successfully.
regards
First check if other features work. For example, can you see the logs?
Make sure that you allowed installation of non-market applications.