I migrated RMS to AD RMS step by step as Microsoft explained the migration inĪfter joining the Windows Server 2008 R2 with AD RMS to the RMS cluster a second DB appears in the SQL Server. The databases on SQL Server 2000 are offline and logging works too. The only thing I skipped is moving sysmessages from SQL Server 2000 to sysmessages on SQL Server 2008 R2. All Clients can contact the cluster.įirst I moved the databases from SQL Server 2000 to an SQL Server 2008 R2 using thisĭocumentation. Now I restored the old databases on my SQL Server 2000 before migration and restored the old Windows Server 2003 with RMS SP2 configured for using SQL Serve 2000r. The Active Directory Rights Management Services (AD RMS) logging service started successfully.
Source: Active Directory Rights Management Services Information 09:17:34 Active Directory Rights Management Services 65 Logging
Message: Could not find stored procedure 'sp_AddServiceRequest'. Logging stored procedure: sp_AddServiceRequestĮrror0.Message: Could not find stored procedure 'sp_AddServiceRequest'. All other messages will not be read from Message Queuing until the AD RMS logging database is available.Ĭontext: LoggingWriter.WriteToDatabaseTable It will try to write the last message to the AD RMS logging database. The Active Directory Rights Management Services (AD RMS) logging service could not write to the AD RMS logging database. Now AD RMS reports an error, because stored procedures are missing. we changed back through RMSCongEditor to DRMS_Logging_DRMCluster_80. We have been a little bit too fast and deleted DRMS_Logging_DRMCluster_80_01 (without Backup) which was a migrated version of the logging database. In addition to DRMS_Logging_DRMCluster_80 there was a database DRMS_Logging_DRMCluster_80_01. After the migration to AD RMS I was wondering about a newĭatabase.
First thing we had to do is moving the databases from a MS SQL Server 2000 to SQL Server 2008 R2. We migrated from Windows Server 2003 to AD RMS on a Windows Server 2008 R2.
0 kommentar(er)
