Im installing a new environment with CAEEM and CA SDM pointing to a remote SQL Server, but for some reason the installation stop after "Installing CA Service Desk Manager Database Schema remotely" step.
I ran the installation of mdb (CASM install media \ products \ sdm \ setup.exe) on the DB server before running the Service Management installer on the application server and I'm using the SQL Server ServiceDesk user, which has sysadmin privilegies.
I'm using a named instance and I see no connection problems with the database server through port 56625.
The install file at C:\Users\albinosv\AppData\Local\Temp\casm show this error messages:
2017/09/26 126.96.36.1990 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [DatabasePersister] SQLException: Invalid object name 'al_cdb_componentinstallstate'.
2017/09/26 188.8.131.529 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] Setup MDB returns code 8012017/09/26 184.108.40.2068 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] MDB RC : 8012017/09/26 220.127.116.118 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] MDB Error: Unexpected error. Check logs at D:\CA\SDM\temp\mdb_sql.2017/09/26 18.104.22.1688 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] Check mdb logs at D:\CA\SDM\temp\mdb_sql.2017/09/26 22.214.171.1248 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [InstallSDMRemoteMDB] SetupMDB returns code 801
2017/09/26 14.03.57.942 ERROR [DeployThread: Configuring CA Service Desk Manager] [ConfigureSDM] SDM configuration failed with message : 09/26 13:54:39.829 WARN ConfigThread.java 582 Configuration task (Configure MS SQL Server) is failed in step : 11
The install_mdb_msg file D:\CA\SDM\temp\mdb_sql shows only this:
09-26,13:54:39 Unable to determine the Common Component Directory for the MDB.
Can anyone help?
In addition to this
I have already tried to install Service Desk without first creating mdb on the remote server or generating it manually, but the installation fails with other error messages.
There should be another file called %TEMP%\casm\install_mdb.log (or the parent directory of %temp%\casm has another casm folder with that file)
Can you provide that file?
I think the issue is with the database instance / firewall of some sort that's preventing us to create the Common schema.
On the application server, in the TEMP folder there is no file other than install.txt.
In the TEMP folder on the database server, I found the files I'm attaching now.
Unfortunately the architecture is a bit confusing to me, apologies in advance. Since 14.x release, SM installer is able to setup the database remotely, install common tables remotely as well as install SDM database remotely. So normally we don't need to run the SDM database installer on the db server (like we used to in 12.x releases).
My best guess at this time is that, the database that was created from the DB server itself, is not lettting you add enough data from the SDM server. The logs are not very clear on this yet, but that's the best thing that I can think of at this time.
My recommendation is to raise support case for this for our team to look into remotely.
One option you can try is, to delete the mdb database that was created, delete the mdbadmin account and then try to get the SM installer (from SDM node) create it for you.
I raised a case on the support site.
I also tried to run according to your suggestion.1-Uninstalled SDM2-Removed the mdb from the db instance3-Removed user mdbadmin4-Tried a new installation
Installation failed with this message:
In the "%temp%\casm\install" file we can check for multiple database connection failure messages.
However, both servers are in the same VLAN 172.16.3 ..., this traffic does not pass through a firewall according to my infrastructure team.
I can validate this communication through an udl file that I created.
I think we're on the right track. Thank you for confirming about firewall.
There's either some left over entry of previous mdb or some additional missing permission that's causing the creation of MDB / mdbadmin to fail now
I've started a trace log at SQL Server to investigate this issue and got this errors:
The installation wizard try to log on mdb database before it is created.
It is expected?
I believe its part of our logic where we try to check if mdb exists and try to login/query for mdbadmin user too
I found an unexpected behavior of the virtual machine, it was consuming too much memory without any process presenting this high consumption. My co-worker created a nnew VM from another template and after that the installation worked perfectly.
How can I end this topic?
Thanks for helping!
Thanks for the update - that is good news.
Please mark one of the answers/comments as correct (either yours or someone else's) and this topic/thread will get closed.
Thank you for the update Albino. I have marked your suggestion as correct for now)