Again, I believe it has to do with the missing status of ESMC services on the new server.Īll of the other clients and two other servers running File Security connect just fine with the new ESMC server.
I have sent off a software install task and it gets started but doesn't complete. Third issue: this one is similar to the second issue. I believe this has to do with the first issue listed above. The task is shown as been executed and has been this way for the past 22 hours. From the ESMC console, I have fired off a software install task to install File Security 8 on the new ESMC server. Second issue: I have reinstalled File Security on the new server but the change is not reflected in the ESMC. Do I need to reinstall it (is there a repair function within the installer routine?)
Regarding the first issue, I am unsure as to what the best way is to have the new server recognized as running ESMC functions by the very same server. I fear though that there may have been some actions taken that are reflected in the db that has since then been overwritten by the era_db from the old server.Įver since then I have discovered these three issues and no matter what I do I cannot resolve these. I checked the About dialog box to ensure that it was connected to era_db on the correct server. Immediately I stopped SQL Server services on the old server, backed up era_db, restored era_db to the new server, and reinstalled ESMC on the new server taking care to ensure that it was connecting to the era_db on the new server. While I had thought that I was following instructions to the dot, I subsequently discovered that the new server was still connecting to the era_db on the old SQL server. I followed the instructions for migrating to a different server (). I needed to migrate to a newer SQL server due to the fact ESMC 7.1.717 requires a SQL Server newer than SQL Server 2008R2. These arose as part of the migration of ESMC from a Windows Server 2012 running SQL Server 2008R2 to a Windows Server 2019 running SQL Server 2017. * ESMC thinks the same ESMC server is running Management Agent 7.0.577.0 when it is actually running 7.1.717.0. * ESMC thinks the ESMC server is running File Security 6 when it actually runs 8 The ESMC icon is missing from the new server entry * The new ESMC server is not being recognized as having ESMC installed and running even though I can connect to the ESMC services on it using my web browser and manage it.
I have one apparently serious issue and two small issues that I cannot seem to resolve in the aftermath of a migration of SMC from one server to another.
0 kommentar(er)
