SRM services fail to start with error 1067

by julio on

When both protected and recovery site of the SRM services fail to start with error 1067, it is due to either an IP change or SQL Database corruption.

In my case the database was corrupted and I could not fix it to retain my SRM configurations.

To fix this 1067 service error do the following steps:

  1. uninstalling DRS on both sites
  2. Create new database and ODBC connection
  3. Install SRM again
  4. Install the SRA of your storage
  5. Synchronize the sites
  6. And last but not least recreate the Protected and Recovery groups respectively
  7. One last piece, don’t forget to do a Test and a Real Failover of the Groups.


News Tags:

Bookmark and Share

No related posts.

Leave a Comment

Comment moderation is enabled. Your comment may take some time to appear.

Previous post:

Next post: