Neo4j 2.0.0 was released. so I update neo4j version 2.0.0.M6 to 2.0.0.RELEASE.
And try to update Model in my webSite but exception is occured.
org.springframework.dao.DataIntegrityViolationException: Unique
property class java.lang.String rankStatId rel: false idx: true was to
be set to duplicate value 3073631_99
MY SDN version is 2.3.2.
SDN 2.3.2 cann't support Neo4j 2.0?
Check the comment way at the bottom of this post: http://blog.neo4j.org/2013/12/neo4j-20-ga-graphs-for-everyone.html
Michael Hunger states that SDN 3.0.0-M2 will support neo4j 2.0, so we need to be a bit more patient I'm afraid.
Related
I have installed Sitecore Commerce Server(ver. 11.3) and I need to migrate all data from the previous version of Commerce Server(it is 11.2). Just back up and restore doesn't work, I got following error message:
"Application is not compatible with '11.200' version of 'Product Catalog' resource. Expected resource version is '11.300'"
Also, I tried to follow section "Breaking Changes" from this manual: http://commercesdn.sitecore.net/SCpbCS81/releasenotes/en-us/index.html , but it doesn't help, too.
What are the best practices of upgrading Sitecore Commerce Server?
Any help will be appreciated.
WSO2 EMM version: 2.0.1
Database: MySQL
Scenario: BYOD (Non-supervised)
WSO2 EMM is not working after use upgrade iOS version. This happens when I upgrade the iOS version from iOS 9.2 to 9.3.
Exception on Server: "Data too long for column UNLOCK_TOKEN"
Class:org.wso2.carbon.device.mgt.mobile.impl.ios.dao.impl.IOSDeviceDAOImpl
I accidently deleted server log. I can't downgrade my iOS device & then try again.
Please help me. It's not WSO2's open-source class, so I can't compile & reuse it.
Please note that the EMM version 2.0.1 has not been tested on iOS 9.3.x (1) since the product relases was done prior to the iOS release 9.3.x release.
However the issue seems to be caused by column length of the column UNLOCK_TOKEN, that is too small to hold the token sent by iOS 9.3.x devices. As a solution, you can increase the column length of UNLOCK_TOKEN column in IOS_DEVICE table of the iOS related database.
(1). https://docs.wso2.com/display/EMM201/Prerequisites
I installed SBOS accelerators version 1.2 to have click-through reporting for Multi variant testing.
I use Sitecore 7.0 Mvc and the clicks are not registered on the report.
Is Mvc not supported in version 1.2?
Does anyone know what I can do to make it work?
Thanks for your help.
SBOS 1.2 does not support MVC. This is mentioned in the comments on the Sitecore Marketplace. It's supported by 2.0 only.
https://marketplace.sitecore.net/Modules/SBOS_Accelerators.aspx
Have a nice day!
Gert.
Hi I am getting this error when I am trying to install Social Connected 2.1 in sitecore 7.2
Could not find configuration node:
contentSearch/configuration/defaultIndexConfiguration/analyzer
Could not find solution.
Can anyone help me out with this.
Thanks in advance!
Sitecore does have a workaround in place for the known issues:
Using Social Connected 2.1 with Sitecore CMS 7.2 Reference number:
408378
Social Connected 2.1 isn’t compatible with Sitecore CMS 7.2.
Workaround:
Install Social Connected module on Sitecore 7.2 rev. 140228.
Install Social Connected 2.1 rev. 140113 using the Installation Wizard. During
installation, you'll get the following error message: "Could not find
configuration node: content Search/configuration/defaultIndex
Configuration/analyzer". Close the message. Make required changes* to
configuration files. Open the Installation Wizard and install the
module package again. Use the Skip option for items and files
conflicts. Fix Social Connected module that is already installed on
Sitecore 7.2 rev. 140228 Make required changes* to configuration
files.
* Required changes to the Sitecore.Social.config file:
Change the analyzer tag from
<analyzer ref="contentSearch/configuration/defaultIndexConfiguration/analyzer" />
to the following...
<analyzer ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/analyzer" />
Add the "true" tag to the
"socialSearch/configuration" section.
* You can find the official Sitecore workaround / KB article here *
So you can use Social Connected 2.1 with this fix.
I don't have any good news for you. Social Connected module doesn't have any version which is compatible with Sitecore 7.2 version.
Here is the full table of the modules compatibility: http://sdn.sitecore.net/products/sitecore%20v5/sitecore%20cms%206/installation/modules%20compatibility.aspx.
The answer I've got from Sitecore Support is
There is currently no supported by CMS 7.2 Social Connected. Reasons are - many breaking changes.
EDIT:
According to the latest news, there are now versions of Social Connected supporting Sitecore up to 7.5:
https://kb.sitecore.net/articles/541788
I'm currently migrating an axis2 1.5.1 installation to 1.6.1. currentyl I'm facing several issues.
e.g.: where's the
ListenerManager.defaultConfigurationContext
field gone?
where do I get the current configuration context?
regards
that method is no longer supported. you can use MessageContext.getCurrentMessageContext().getConfigurationContext() if you want to access the configuration context at the service.