I've tried installing and running from the Zip instead of EXE as other have mentioned.
Gives a 404 if authorization header is supplied, and 401 if not
GraphAware seems to have only a version for 2.2.2, whereas 2.2.3 is the latest on the neo4j site. Managed to track down 2.2.2 only to have it not work still. Any ideas?
It is correct the GraphAware modules are not compatible with Neo4j2.2.3 due to a bug in the Transaction data in neo4j itself (ref here https://github.com/neo4j/neo4j/issues/4910) which should be fixed in 2.2.4 or 2.3-RC1
If you installed via the zip, this should however work with 2.2.2, Please amend your question with the modules you use and their version, also all configuration you have set for the moduleS.
Related
I'm using Magento 2.3.1 with PHP 7.2, facing error while creating customers account at admin end.
Found some sources on the internet to degrade PHP version.
Is there any other option available without degrading PHP 7.2?
Log:
main.CRITICAL: Exception message: Deprecated Functionality: idn_to_ascii(): INTL_IDNA_VARIANT_2003 is deprecated in /public_html/vendor/zendframework/zend-validator/src/EmailAddress.php on line 560
idn_to_ascii() at Line 560:
return (idn_to_ascii($email) ?: $email);
I encountered this exact issue after upgrading the PHP version of the server to 7.3.
Initially, the issue was with the Zend framework like yourself, but after an upgrade to Magento 2.3.5 (in an attempt to correct the problem), an identical error was thrown for the newer Laminas.
I tried a number of solutions, including downgrading guzzle from 6.5.3 to 6.5.2, as suggested here: https://stackoverflow.com/a/61596343/9667652
It seems the only solution is to downgrade PHP to 7.1. The issue continues even with PHP 7.2. I downgraded to PHP 7.1 and emails are now sending.
EDIT: As per comment by #user125661, it's important to note that PHP 7.1 is no longer supported:
PHP 7.1 has reached End of Life. To maintain PCI compliance, Magento should not be run on unsupported software. Installing from GitHub will no longer work with Magento 2.3.4/PHP 7.1. The only way to install 2.3.4 with PHP 7.1.x is with Composer. Magento recommends using PHP 7.3
See: https://devdocs.magento.com/guides/v2.3/install-gde/system-requirements-tech.html#php
This issue has been encountered repeatedly but is not able to be reproduced reliably, as documented here: https://github.com/magento/magento2/issues/19795
Looks as though the most likely reason for the issue is servers running CentOS 6, where CentOS 7 is needed: https://github.com/magento/magento2/issues/19795#issuecomment-486432245
Best bet is to get your server onto CentOS 7, but where this is not possible, it seems the only workaround is downgrading to PHP 7.1.
I have installed the Anypoint Enterprise Security - http://anypoint-enterprise-security-update-site.s3.amazonaws.com/1.7.1 and been using the ability to Encrypt and Decrypt passwords. This was working fine for a while.
Today, my 'Secure Property Placeholder' is not working.
If I add it manually in XML I see the following in my 'Global Elemetns'
If I try to add a new 'Secure Property Placeholder' it does not give me that option:
But I have the package installed in my Anypoint.
I'm not sure what I did or what happened. I've tried:
1. Uninstalling the 'Secure Property Placeholder Module' and Reinstalling
2. Uninstall the entire Enterprise Package and Reinstalling
But Nothing is working.
Thanks for your help
A similar problem occured to me with another mule connector. In my case, I had a lower version Mule Server RunTime and the connector was of a higher version. In your case I see that you have both Mule ESB server 3.8.5 and Mule ESB server 3.9.0 EE. Your Enterprise Security is of version 3.9.0. Now when you add the security component to your project, make sure that you have it running on the Mule ESB server 3.9.0 and not on the 3.8.5 version. Hope this helps!
Try installing from anypoint exchange rather than Help/Install New Software, I was having a similar problem which seems to be resolved now.
Clean install:
Downloaded wso2iot 3.1.0 from GitHub
Downloaded yajsw-stable-12.09
Put them in one file (wso):
Pointed jdk1.7.0_75 for JAVA_HOME
Pointed CARBON_HOME to my wso/wso2iot 3.1.0
This is what I downloaded only.
Run iot-server in folder bin.
After that nothing the system don't give me localhost why?
Is this installation correct for running wso2iot?
If not please advise me. Do I need to install something else?
First, you need to have java 8 on your system in order to run the WSO2 IoT 3.1.0. Secondly, if you need to run the WSO2 IoT 3.1.0 as a windows services, you need to have jajws 11.03.
Please refer the following document for more information
You can download the latest release candidate for WSO2 IoT 3.1.0 from here unzip it and start the pack in the following order.
Navigate to <IOTS_HOME>/bin and run ./broker.sh
./iot-server.sh &
./analytics.sh
Then you can login to the console from - https://localhost:9443/devicemgt
Additionally, to the above reply by jdk7. Make sure that you have JAVA 8. WSO2 IoT Server needs JAVA 8.
[1] https://docs.wso2.com/display/IoTS310/System+Requirements
I am running jMeter via Taurus (bzt) on CentOS. My first call is a login that needs to get the access tokens from the returned JSON. When I run this test on my Mac everything works as expected. But when I run it on my CentOS server I get the following error every time I try to extract data from a JSON path. I have tried reinstalling the plugin. I have also tried running it directly via jMeter. In both cases I still have the same problem. Any idea what is causing this error?
2016/06/08 14:34:05 WARN - com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor: Extract failed com.jayway.jsonpath.PathNotFoundException: Extracted array is empty
at com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor.process(JSONPathExtractor.java:104)
at org.apache.jmeter.threads.JMeterThread.runPostProcessors(JMeterThread.java:776)
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:489)
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:410)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:241)
at java.lang.Thread.run(Unknown Source)
If you use Taurus for quite a while it might be the case it's using previously downloaded JMeter 2.13 which doesn't have JSON Path PostProcessor yet. So the following commands can help:
Upgrade Taurus to the most recent version:
sudo pip instal --upgrade bzt
Remove previous JMeter installation:
rm -rf ~/.bzt/jmeter-taurus
Run your test normally - Taurus should download JMeter 3.0
If you don't have possibility to upgrade JMeter and/or Taurus - use JSON Path Extractor plugin instead
It turns out my problem was a version mismatch. I downloaded the latest greatest (stable) jMeter when I started working with jMeter about a month ago. About a week after I downloaded jMeter they released 3.0. I didn’t start setting up my perf server until over a week later. When I installed jMeter on the sever it got 3.0, but my Mac had 2.13. So I was trying to run jmx files created with 2.13 on my 3.0 server. I never got any version mismatch errors just stuff like I shared above. After I upgraded my Mac and rewrote my jmx files via 3.0 everything worked fine.
Just installed latest version of Edine from nodeclipse, and in the console that is the only message outside of path information for the directory the project is stationed in. Also tried grabbing the latest default version and tried to install via New Software with similar results.
C:\Users\user\AppData\Local\Temp\express-work\1406755265579/test
Unexpected Exception
Anyone had this ever work? All methods I'm finding online seem to be broken.
This is on Windows 7 64 bit.
For anyone that arrives at this question and has the same issue.
I was under the mistaken understanding that when installing Nodeclipse, it also installed node.js, express, and mongodb. This is not the case. Installing node.js and express resolved this issue.