IV90194: Outlook add-in install fails on Program Files folder


If you attempt to install the Reserve Outlook add-in into a folder within C:\Program Files\… the information provided on the command line such as URL is NOT copied into the user’s outlook.properties file. However, if you select any other folder in the computer as an install location, then the details are updated into the outlook.properties file.

The problem with using any other location is that those locations are not trusted by Windows. As such, the application when invoked forces a popup which, due to the expired application signing certificate, is not pretty. This is quite scary and is likely to result in many of the users declining the installation.

Because the files are sent to the users’ computers silently, they will not be aware that the add-in has been deployed into their machine. Any popup around email is worrying, so it is easy to see people taking the Don’t Install option.

Continue reading

IV89933: TRIRIGA 3.5.1 install not running with WebSphere 8.5.5.10


The TRIRIGA 3.5.1 compatibility matrix says that WebSphere 8.5.5.9 is supported, but also that “Future fix packs for this version are also supported.” If you run the TRIRIGA 3.5.1 installer with the full version of WebSphere 8.5.5.9 in place, the install works. If you try running with the full version of WebSphere 8.5.5.10 in place, however, the following error occurs:

“WebSphere Problem: WebSphere version is too old. The version of WebSphere that was detected is too old. IBM TRIRIGA Application Platform requires WebSphere version 8.5.5.9 or newer.”

This problem was seen when performing the TRIRIGA 3.5.1 install on Windows. It may exist when running the installer on other operating systems, as well.

Continue reading

IV89177: Install issues on MS SQL Server with collation settings


TRIRIGA 3.5 installation has issues installing on Microsoft SQL Server when using collation settings “French_BIN” and “Case Sensitive”. The upgrade tasks (script) will fail at the first JVM or server startup with the following message…

YYYY-MM-DD HH:MM:SS,mmm ERROR [com.tririga.util.startup.upgrade.StartupUpgradeManager](SoapConnectorThreadPool : 3) Error executing upgrade
com.tririga.util.startup.upgrade.AgentManagementUpgrade org.springframework.jdbc.BadSqlGrammarException: CallableStatementCallback; bad SQL grammar [{call nextval_notran(?, ?, ?)}]; nested exception is java.sql.SQLException: Procedure stockee 'nextval_notran' introuvable...

Continue reading

How do you add the CI 12.1.4 menu with AutoCAD 2016?


I just installed CAD Integrator 12.1.4 and I use it with AutoCAD 2016. I can manually enter commands in the command line. But I don’t see the menu in the menu bar. I know that in the previous AutoCAD version, we have to use the classic workspace. What is the procedure to add the CAD Integrator menu in the menu bar? Do I create an AutoCAD classic workspace?

[Admin: This post is related to the 04.29.15 article by Autodesk Support. The AutoCAD classic workspace is not available in AutoCAD 2015 and later versions. But the classic workspace can still be added to the interface.]

Continue reading

IV88018: Eclipse BIRT Designer fails to connect with TRIRIGA 3.5.1


The BIRT plugin that comes with TRIRIGA 3.5.1.1 and 3.5.2 installs fine in Eclipse 4.3.1, but the connection to TRIRIGA fails. After installing BIRT Designer all-in-one with Eclipse Kepler version 4.3.1 as recommended in the Compatibility Matrix for 3.5.1, we went ahead and pointed to your TRIRIGA URL to install the 3.5.1 BIRT plugin version 1.0.1v201607281127: http:// <server>:<port>/<context>/eclipse. But when connecting to the /remote URL for 3.5.1, a connection error is thrown.

As a temporary fix, upgrade to the 2016 version of Eclipse (4.6) and the corresponding newer BIRT plugins, and you will able to use to the newer TRIRIGA 3.5.1 plugin. To render reports, a platform upgrade to 3.5.1 and later will need to be also upgraded to the 2016 version of Eclipse (4.6) and the corresponding newer BIRT plugins. This is a documentation APAR. We will update the Compatibility Matrix to reflect the use of the new correct version of Eclipse/BIRT.

Continue reading

Having an issue with installing TRIRIGA on WebLogic


I’m having an issue with an installation on WebLogic. The installer only works if TRIRIGA is installed on WebLogic’s AdminServer node. I’ve found on a forum, not regarding TRIRIGA but WebLogic, that the script used by the installer is not compatible with any node other than AdminServer.

Does anyone have any documentation or reference where TRIRIGA on WebLogic can only be installed on the AdminServer node? This is doing a clean installation of TRIRIGA 3.5.1 on Linux with WebLogic 12c.

Continue reading

Why is server synchronization failing after upgrade to 3.5.1?


In an attempt to run a TRIRIGA 3.5.1 upgrade, I have installed WebSphere and TRIRIGA successfully without errors. But when trying to load the application (start server), I get a slew of errors just as the server attempts to perform “Initializing Spring Application Context”. Ultimately, the typical webpage login page is available, but no BOs ever publish. The application process essentially completely stops at “Loading Startup Cache” after my log file is blown up to the tune of 45MB, so there is nothing to actually log into. I’m trying everything I can think of, but the Java messages aren’t exactly the most helpful. Does anyone have any ideas where to start? I get the same result whether I’m attempting WAS or Liberty.

So, to add to my own question, I finally traced back to the original log file and noticed that the “Server and Database Server Synchronization” began, and failed after applying the first 6 of 95 updates. It looks like it was because the database was locked mid-stream. Restarting the server does not let it “pick up where it left off”. I need to restart the sync (or trick it the server into thinking it hasn’t done it yet), and I think that to do so, I need to inform my DBA of some values or packages to delete or change to trigger this. Am I thinking along the right lines, or am I way off here?

Actually, the issue was that the build numbers were the same. With the build numbers the same, it wasn’t recognizing that there was more to upgrade. So I committed the old build number to the database, restarted, and the process picked up where it left off. I’m still doing a bit of housekeeping, but it seems that the upgrade was a complete success. Thank you for you input, I would have been spinning my wheels for a long time.

Continue reading