aris architect does not connect with aris publisher after upgrade

Hi,

did you check that the correct Port for Publisher Server is configured for your abs Service?

D:\ARIS9.6\server\bin\work\work_abs_s\base\webapps\abs\config\defaultServerSettings.cfg

change Row: abs.bp.port=19990

to correct Port e.g. : abs.bp.port=80

Sometimes this is overwritten during update.

Bye

Alexander Hettrich

Hello Alexander(s),

I had the same issue while upgrading to 9.8 SR6. After the installation I renewed the entry in defaultServerSetting.cfg - but it was not sufficient. 

In addition I had to change the parameter abs.bp.port via set in the ARIS Server Administrator!!

Unfortunatelly I didn't find a hint in the release-letter or other docs 8o(( - so I had to call the support.

BR Gerald

Is your Publisher services running? Reboot publisher server/ start/ stop services.

thank you for the quick reply. We finally solved the issue here is our lessons learned...

Actually it was resolved by re-installation. The upgrades are just losing time.

In the Designer case the upgrade was in fact not done - the files (jars) named with the version in the name still were 9.8.5, though the upgrade reported success.

Both Designer and Publisher servers have to be upgraded twice the first run doesn't upgrade the Cloud controller properly (missing at least one file and the menu item is corrupted, missing icon and it doesn't find the program to run).

The https support is possible to install by the enhance command provided the certificate chain is done like: server + intermediate + root concatenation of the pem files. This should be better described in the docu. [The actual info is better explained in the Apache web server docu, what the load balancer actually is.]

The Publisher after the upgrade was not visible until reinstalled from scratch.

The original problem:

The server reported an exception like a missing class leading me to think the installation is corrupted. (Like a new antivirus update can find some false alarm and remove the file.) This class was actually an exception and had likely by the name to do something with some data exception. Since after re-installing from scratch in a new, clean database it works, probably the Publisher data was corrupted. There was several times reported an exception:

com.microsoft.sqlserver.jdbc.SQLServerException: Could not proceed with index DDL operation on table 'e1_cxndefattr' because it conflicts with another concurrent operation that is already in progress on the object.

The concurrent operation could be an online index operation on the same object or another concurrent operation that moves index pages like DBCC SHRINKFILE.

As even a database server restart and machine reboot didn't resolve it, the reinstallation after 3 years of intensive use is probably the best way how to clean the database. It was likely some corrupted index.

Now we have everything clean and up-to-date and I hope it will last some time.

BR

Alex