Thanks, Jakub.
I would expect to see further details in another log regarding the root cause... Can you check if there is any other log in logs\install or %TEMP\casm folders which contains more information about the error message shown in view.log/install.log?
Thanks!
------------------------------
Senior Support Engineer
------------------------------
Original Message:
Sent: 06-22-2020 01:45 PM
From: Jakub Kolacny
Subject: installation of second catalog server
Hi Pablo,
there are no errors in the seeddata.log file. In the view.log there is only one thing I found interesting about the mdb deployment - see the screenshot below...
Original Message:
Sent: 06-22-2020 10:58 AM
From: Pablo Oyarzo
Subject: installation of second catalog server
Hi Jakub,
Is there any error in the seeddata.log and view.log in the exact moment you get the -3 error code in the install.log file?
Regards,
Pablo
------------------------------
Senior Support Engineer
Original Message:
Sent: 06-16-2020 11:19 AM
From: Jakub Kolacny
Subject: installation of second catalog server
I've found that even for the successful Catalog installation on the first server, there are some error messages in the install.log (EEM integration step). Despite these messages, the Catalog on the first server works fine.
Original Message:
Sent: 06-16-2020 08:54 AM
From: Jakub Kolacny
Subject: installation of second catalog server
Team,
we have some troubles while installing the second catalog server (17.3). We always get an error message at the very beginning of the "Configuring CA Service Catalog - Components" installation step.
The first server is always installed without any issues. The problem is not with the server itself - is doesn't matter which server is installed first. The second installation always fails.
I can't upload the log file (some weird security rules) so here are some screenshots...