FIM hotfix installation fails with event id 1023 and FIM Service crashes when installation is run without SQL Sysadmin rights

Last week, a customer was trying to upgrade his FIM environment in production to the latest hotfix.

In test and acceptance environment the FIM engineer was able to update both FIM Sync and FIM Service + Portal.

But when executing the update (Build 4.1.3496.0 (for R2): KB 2906832 ) on the production servers, only the FIM Sync update succeeded.

When trying to install the previous version, the update didn’t work neither.

The installation wizard throws an error: “Cannot connect to the SQL Server <SQL Server> with service account <FIMService Account>”.

error2

The event viewer shows an error with event ID 1023.

“Product: Forefront Identity Manager Service And Portal – Update ‘FIM Service & Portal Hotfix KB 2906832’ could not be installed.  Error code 1603. Additional information is available in the logfile …”

error

When you try to run an import from the FIM MA on the FIM Sync server, then you get the error below

Log Name:      Application
Source:        FIMSynchronizationService
Date:          1/29/2014 6:04:43 PM
Event ID:      6309
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVERNAME.ENVIRONMENT.DOMAIN.ROOT
Description:
The server encountered an unexpected error while performing an operation for a management agent.
“BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\manhost\manhost.cpp(784): 0x80230709 (The extension operation aborted due to an internal error in FIM Synchronization Service.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\nathost\nathost.cpp(203): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\cntrler\cntrler.cpp(535): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\server\server\ma.cpp(3791): 0x80230804 (The management agent run could not start as there were connection errors.)
Forefront Identity Manager 4.1.3441.0″
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”FIMSynchronizationService” />
<EventID Qualifiers=”49152″>6309</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2014-01-29T17:04:43.000000000Z” />
<EventRecordID>935455</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVERNAME.ENVIRONMENT.DOMAIN.ROOT</Computer>
<Security />
</System>
<EventData>
<Data>BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\manhost\manhost.cpp(784): 0x80230709 (The extension operation aborted due to an internal error in FIM Synchronization Service.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\nathost\nathost.cpp(203): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\cntrler\cntrler.cpp(535): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\server\server\ma.cpp(3791): 0x80230804 (The management agent run could not start as there were connection errors.)
Forefront Identity Manager 4.1.3441.0</Data>
</EventData>
</Event>
The server encountered an unexpected error while performing an operation for a management agent.
“BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\manhost\manhost.cpp(784): 0x80230709 (The extension operation aborted due to an internal error in FIM Synchronization Service.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\ma\managed\nathost\nathost.cpp(203): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\cntrler\cntrler.cpp(535): 0x80230804 (The management agent run could not start as there were connection errors.)
BAIL: MMS(8044): d:\bt\5414\private\source\miis\server\server\ma.cpp(3791): 0x80230804 (The management agent run could not start as there were connection errors.)
Forefront Identity Manager 4.1.3441.0”

While researching these errors and events, I got another hint / sample error message that can show up because of the same root cause. (Thanks, Paul!)

“Error 25070: Error connecting to database <name>. These workstations have sessions with open files to this server:”

This error is documented here: Troubleshooting FIM 2010 Hotfix Installation: Error 25070 These workstations have sessions with open files on this server

Resolution

Initiate the installation with an account that has SQL SysAdmin rights on your SQL Server hosting the FIM Databases (rights only needed during installation).

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s