I'm following an Install Guide to IBM Connections 4.0. This guide and many others point to the following Cumulative Release 2 Fix Pack:
4.0.0.0-IC-Multi-TDISOL-CR2-LO72170
All my online searches have failed me and keep referencing a different fix pack part of a later cumulative release.
This is the only fix pack I'm missing for the full IBM Connections 4 Installation.
Please can someone assist me in finding a download link to this Fix Pack.
Connections 4.0 CR4 is also available; this could be used instead of both CR2 and CR3
http://www-01.ibm.com/support/docview.wss?uid=swg21637538
CR3 is released. You should try that instead.
http://www-933.ibm.com/support/fixcentral/swg/doSelectFixes?options.selectedFixes=4.0.0.0-IC-Multi-TDISOL-CR3-LO73535&continue=1
TDISOL is just the method to load the users/sync users.
Note, I had issues with CR2, and used CR1 as a fix. CR3 is an option that should work in your case.
Related
I've used CTL in ExecuteGroovyScript processor to connect to database which is selected by database.name due to this problem DBCPConnectionPoolLookup problem in ExecuteGroovyScript. after upgrading NiFi to new version (1.10.0), the processors show this error:
and this is my processor configuration:
Please let me know the problem.
I started testing version 1.10.0 myself recently and that was one of the things I ran in to as well. Try using SQL.* (ex: SQL.db) for your property name as that is used specifically for DBCP services. If you need to access other services that still can be done by looking up the service by name in your Groovy script as a workaround but based on Jira activity, I see this bug is already being worked on and hopefully will be fixed in next release. I hope this helps.
we are using MPP14Reader to read tasks from Microsoft Project, and recently for some of the projects, we are seeing that getOutlineNumber is giving wrong value. (ex: in Microsoft Project OutlineNumber is 1.2 ,
where as task.getOutlineNumber() is resulting in 2.4).
going through MPXJ code, found that this has been fixed in latest release via commit https://github.com/joniles/mpxj/commit/628df2b4a9dc4f00f59c5d8ad1c54648292a5c41
looking at commit description, seems this is happening after Microsoft June Update !!
do we have any workaround here ? can some one please help
Not all projects have this issue, seems to be issue with some of the projects
This issue with MPXJ was recently fixed, as discussed here: https://github.com/joniles/mpxj/issues/107
my PC changed but I would like to continue with SPSS test version on my new one. HOw can I deactivate the test Version on the old one? It is already deinstalled.
Thanks a lot.
Best regards
Henriette
Have you tried to simply install your test version on the new machine and to see if that works out?
According to this IBM support page,
A valid Authorized User product authorization code can be used to license up to two (2) product installations used by the same individual.
That might hold true for test versions as well, so maybe you can just reinstall it and carry on.
Otherwise, it never does any harm to write IBM support a quick e-mail describing your problem, as license transfer should be a routine situation for most software developers.
Does anyone have a guide on setting up AHBot in an AzerothCore 3.3.5 server? I can find no mention of ahbot in the world.conf and no DB tables like auctionhousebot in the database or any references. It is included in TrinityCore so all the google references that I find point me back there.
Our server is just two of us and it would be nice to have some items on the auction house. At the moment, if you need a silver bar you have to go out in the world and find it. That was exciting the first couple of times... but gets old.
I followed the guide to install off github: https://www.azerothcore.org/wiki/Installation and am using the latest release under Ubuntu linux.
Thank you for any help. You are my last hope...
AHBot is not currently an 'official' supported module of AzerothCore (which would be why you aren't finding any settings in the worldserver or anywhere else regarding it).
There is a module in development that isn't currently part of the AC list, but I've gotten it working on my personal server: https://github.com/AyaseCore/mod-ahbot Note that this is a bit different than a normal module as there is also a git patch that needs to be applied manually.
Theres a module in azerothCore repository you have to apply patch manually but it wont compile on Win x64 and unix x64 comes up with an error about 9 arguments, but seems to compile for some
I want to know how to apply the issue changes done in the Liferay Issues can be applied in our portal.
For example my issues are cleared in the following links,
https://issues.liferay.com/browse/LPS-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
https://issues.liferay.com/browse/LPS-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
I want to apply the issue changed in the above links in my portal.
Please some one help me to achieve this.
Thanks in Advance.
Regards,
Dinesh M K
You have to see the resolution and fix version stated.
the second issue says :
Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
and that means that the issue was solved in all Portals after version 6.1.0 CE.
the first issue , is no longer reproducible, and duplicate of https://issues.liferay.com/browse/LPS-14220 which is again solved in 6.1.0 CE RC1
In other words, If your portal is older than this version, you can't do anything. You'll have to upgrade to version 6.1.0 RC1 or later
It seems that the fixed-in version is a bit weirdly set in those issues - e.g. LPS-14220 is a subtask of a story in LPS-14414, which is stated as completed for 6.2.0. Careful: I did not fully read through all of the issue's descriptions, links and mix what I read with the answer (and comment to) #yannicuLar gave
Basically, this seems to be a new feature. The way to backport it to your installation is to identify the relevant commits (e.g. download the repository from https://github.com/liferay/liferay-portal or https://github.com/liferay/liferay-plugins, identify the relevant commits (they all contain the LPS number), "backport" them (e.g. see if they can just be applied to your codebase or if they need manual adaptation because the whole code changed.
Some features are easier to backport than others, I can't tell about the complexity for this one.
In order to separate your changes from Liferay's core changes, you should try to implement this in plugins (or patched plugins) rather than changing the original code and recompile. Most likely it's only the kaleo-web plugin that's effected, but if there are core changes, you'd be better of having them isolated in plugins.
The simplest (and most futureproof) possibility is to wait a bit for 6.2 (RCs are already out) and upgrade your portal to this version. If you want to stay on a version that gets updates, you should do this soon anyway.