walleyeman 1 Posted November 13, 2020 Share Posted November 13, 2020 Hello: How can i correct this error? I currently moving the eset server management console to a new windows 2012 server from a Windows server 2008. this is a partial from log file 2020-11-13 18:33:08 Error: CReplicationModule [Thread 2a74]: CReplicationModuleBase: Peer uuid stored in database: '09864601-779e-4b48-92c5-9a32db077762' does not match peer uuid stored in install configuration: '0f5a8463-400a-4341-8aa5-bc9b150fc39d' 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CRemoteInstallModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CTagsModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CDynamicGroupsModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CSymbolsModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CCleanupModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: NetworkModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CNetworkGrpcModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CServerSecurityModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: SchedulerModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CDataMinersModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CDatabaseModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CUpdatesModule 2020-11-13 18:33:08 Information: Kernel [Thread 2a74]: Unloading module: CTranslatorModule 2020-11-13 18:33:08 Error: Service [Thread 2a74]: CReplicationModuleBase: Peer uuid stored in database does not match peer uuid stored in install configuration Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted November 13, 2020 ESET Staff Share Posted November 13, 2020 I would recommend to verify & review migration steps made as there was probably some step skipped or missed -> most probably, clean installation of ESMC was made, before database was migrated. Unfortunately I am not sure whether it will have any impact on functionality. In order to fix inconsistency in identifiers, you will have to modify value of ProductInstanceID in windows registries on path: HKEY_LOCAL_MACHINE\SOFTWARE\ESET\RemoteAdministrator\Server\CurrentVersion\Info where ProductInstanceID has to be set to value 09864601-779e-4b48-92c5-9a32db077762 seemingly stored in database (it should be the same value as was in this registry path on old server). Link to comment Share on other sites More sharing options...
Recommended Posts