The database team is moving the FIMSynchronizationService database to a new server. How can I make FIM see this new server without breaking anything? I made two registry changes to the server name, but now I'm getting errors when trying to start the program.Ryan

Hi Ryan, What are the errors you are seeing? I recently described the method I used to move the FIMSynchronization database in this thread: http://social.technet.microsoft.com/Forums/en/ilm2/thread/7e478122-afc2-41cd-b23c-20c0737dd21b Cheers, Mark

All of the settings are listed here http://technet.microsoft.com/en-us/library/ff800821(WS.10).aspx Generally when moving the FIM Sync DB Stop the service Move the database Change the registry settings SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters Registry value name Value type Class Created by Notes Server <string> HKLM Setup Name of the FIM Synchronization database server. SQLInstance <string> HKLM Setup Name of the FIM Synchronization database instance. DBName <string> HKLM Setup Name of the FIM Synchronization database. Restart the Synch service Then open the Synch service manager to confirm it works. So where is your error occurring -- is it on starting the FIM Synch Service or opening Sync Service Manager? What error are you receiving? Install SQL Management Studio on your Sync Server, if you haven't already. Then test making the connection to the database through your SQL Server Management Studio. David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

All of the settings are listed here http://technet.microsoft.com/en-us/library/ff800821(WS.10).aspx Generally when moving the FIM Sync DB Stop the service Move the database Change the registry settings SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters Registry value name Value type Class Created by Notes Server <string> HKLM Setup Name of the FIM Synchronization database server. SQLInstance <string> HKLM Setup Name of the FIM Synchronization database instance. DBName <string> HKLM Setup Name of the FIM Synchronization database. Restart the Synch service Then open the Synch service manager to confirm it works. So where is your error occurring -- is it on starting the FIM Synch Service or opening Sync Service Manager? What error are you receiving? Install SQL Management Studio on your Sync Server, if you haven't already. Then test making the connection to the database through your SQL Server Management Studio. David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

The error message is: Unable to connect to the Synchronziation Service. Some possible reasons are: 1) The service is not started 2) Your account is not a member of a required security group. See the Synchronization Service Documentation for details. The problem is that the service will not start. The only registry key that I changed was "Server" to the new name. The DBName field is the same and SQLInstance is empty.Ryan

The error message is: Unable to connect to the Synchronziation Service. Some possible reasons are: 1) The service is not started 2) Your account is not a member of a required security group. See the Synchronization Service Documentation for details. The problem is that the service will not start. The only registry key that I changed was "Server" to the new name. The DBName field is the same and SQLInstance is empty.Ryan

I can confirm that changing the regkeys normally works to move the Sync Service DB. As an alternative to installing the SQL mgmt studio you can just use an ODBC connection as well to do a quick connectivity test...http://setspn.blogspot.com

I can confirm that changing the regkeys normally works to move the Sync Service DB. As an alternative to installing the SQL mgmt studio you can just use an ODBC connection as well to do a quick connectivity test...http://setspn.blogspot.com

Perhaps my issue is filling in the correct information. The instance name on the old server was just the server name. The new server is ServerName\DB. So filling out the registry keys, should I put ServerName\DB under Server and nothing under SQLInstance? How should I fill this out?Ryan

Can't check right now on a live system but Id say: Server: ServerName SQLInstance: DB DBName: FIMSynchronizationService SQLInstance is empty when a "default instance" is used I think.http://setspn.blogspot.com

This did not work. I'm still not able to get FIM to see the new DB location.Ryan

This did not work. I'm still not able to get FIM to see the new DB location. Here is what I have tried: DBName = FIMSynchronizationService Server = ServerName\ABC SQLInstance = (left blank) ---------------------------------------------------------------- Server = ServerName SQLInstance = ABC ---------------------------------------------------------------- Server = ServerName SQLInstance = ServerName\ABC Ryan

I checked the event log to see if there was an error, and there is. The server encountered an unexpected error and stopped. ERR: MMS(3540): sql.cpp(5583): Query (CSession::Open()) performed with error ERR: MMS(3540): sql.cpp(5604): Error retrieving error BAIL: MMS(3540): sql.cpp(571): 0x80230406 (An error has occurred at the store) BAIL: MMS(3540): sql.cpp(387): 0x80230406 (An error has occurred at the store) BAIL: MMS(3540): sql.cpp(259): 0x80230406 (An error has occurred at the store) BAIL: MMS(3540): storeimp.cpp(275): 0x80230406 (An error has occurred at the store) ERR: MMS(3540): server.cpp(297): Failed to connect to the database FIMSynchronizationService on ServerName\ABC BAIL: MMS(3540): server.cpp(298): 0x80230406 (An error has occurred at the store) BAIL: MMS(3540): server.cpp(3696): 0x80230406 (An error has occurred at the store) BAIL: MMS(3540): service.cpp(1531): 0x80230406 (An error has occurred at the store) ERR: MMS(3540): service.cpp(980): Error creating com objects. Error code: -2145188858. This is retry number 0. Forefront Identity Manager 4.0.2592.0 This repeats 3 times.Ryan

I just confirmed that I can connect to the new database with no issues. Created an ODBC connection to ServerName\ABC successfully. If I put the old SQL database name back in registry field, it connects fine and the service starts. Ryan

Have you re-created the login on SQL? The security is stored (and remains in place after a restore) in the database. But in SQL Server you have to create that same login again before it can be used to access the database. It should be below Security > Loginshttp://setspn.blogspot.com

I ended up backing up my MA's and uninstalling the application. Upon reinstall of the application it was determined that the new SQL database did not get all credentials moved over as the DBA said they did. When I tried to make a connection to the new DB in the install, it said I did not have permissions. The DBA looked again and saw the problem. Doah! I think the only problem I was having was permissions on the new DB.Ryan