Share via

MIM/FIM Troubleshooting: Sync service terminated with service-specific error %%-2146234334 (Primary Server)

  • Article

 

Source 

MIM Forum Question: MIM Sync service start error   

Symptoms

After installing the secondary MIM Sync server, the Primary MIM Sync server service fails to start. 

Error message

The server encountered an unexpected error and stopped.

"BAIL: MMS(5084): ..\storeimp.cpp(4852): 0x8023060d (The computer_id in the database does not match this computer.)

BAIL: MMS(5084): ..\storeimp.cpp(460): 0x8023060d (The computer_id in the database does not match this computer.)

BAIL: MMS(5084): ..\server.cpp(416): 0x8023060d (The computer_id in the database does not match this computer.)

BAIL: MMS(5084): ..\server.cpp(3945): 0x8023060d (The computer_id in the database does not match this computer.)

BAIL: MMS(5084): ..\service.cpp(1585): 0x8023060d (The computer_id in the database does not match this computer.)

ERR_: MMS(5084): ..\service.cpp(1024): Error creating com objects. Error code: -2145188339. This is retry number 0.

BAIL: MMS(5084): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(259): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(3945): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\service.cpp(1585): 0x80131022 (unable to get error text)

ERR_: MMS(5084): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 1.

BAIL: MMS(5084): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(259): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(3945): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\service.cpp(1585): 0x80131022 (unable to get error text)

ERR_: MMS(5084): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 2.

BAIL: MMS(5084): ..\CLRHost.cpp(225): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\ScriptManagerImpl.cpp(7894): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(259): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\server.cpp(3945): 0x80131022 (unable to get error text)

BAIL: MMS(5084): ..\service.cpp(1585): 0x80131022 (unable to get error text)

ERR_: MMS(5084): ..\service.cpp(1024): Error creating com objects. Error code: -2146234334. This is retry number 3.

BAIL: MMS(5084): ..\service.cpp(1038): 0x80131022 (unable to get error text)

Forefront Identity Manager 4.4.1302.0"

 

Background

MIM Sync only allows 1 active server connection to the database, which is controlled by the encryption key.

When you install the server, the server takes control over the database with the encryption key.

The database owner is stored in the database.

When you install a new server, and connect it to the database (with the encryption key), that server becomes the owner.

 Also, when (re)activating the server with MIISActivate, that server takes over control.

Any other server, will lose control and will not be able to connect to the database.

Solution

Install Secondary server first, primary server last

The last MIM Sync server that is installed, will have final control.

So, you should install your backup- or secondary server first.

The primary server, that will run normal operations, must be installed (or activated) last.

Reactivate Primary Server

If you forget about this rule, and install the servers the other way around, you'll need to reactivate the primary server again.

There are some other cases, the primary server needs to be halted or fixed (eg restore, repair,hotfixing, ...), for which you fail over to the secondary server.

So reactivate the primary server run the MIISActivate tool, which will take control of the database connection.

More info:

Other troubleshooting (SQL Connection Failures)

References