Hi i get this error on installing the SRM5 Recovery Site,during the "create tables procedure of the installation process":
odbc error 42S01 there is already an object named dr_table_catalog.
The server is Windows2008 R2 and the database is MSSQL 2008 R2 (both on SRM compatibility matrix) ,i've experienced the same issue on a MSSQL 2005.
i've created 2 DB(forrecovery site and primary site), SRM_R and SRM_P on the same MSSQL instance (is for testing pourpose obviously), and the fun part is that the primary site installation worked great.
after installing the SRM service stops, after the timeout period..
on the logs i've found;
i've increased the timeout from 300 to 900 as suggested in a KB article, but with no luck.
On the DB site all tables are created.
On vc vlient i get the error:
Connection Error: Lost connection t oSRM server ipofserver:8095
The server 'ipofserver' could not interpret the client's requests. (Remote server error:(503) Server not available.)
Yes i've solved it by using FQDN on each field requested,
The important thing is to use always or the IP Address or the FQDN..
for me worked
this is really strange, just a blank screen.
tomorrow morning at work, i'll review my documentation about SRM 5 setup and let you know.
Can you post some logs?
The parining is working? are u able to pair sites?
I am new with SRM, but I could not find a way to do pairing between the two site.
I have not install the SRA. I will try to find the log and post it on the site.
Do you know where and which log you need? TIA.
You don't need the SRA for now,
The on the summary page you should see a list of tasks, very strange that is blank,
i'll check tommorrw morning at work
I usually ignore this, but I think I did.
Every time I connect to Site Recovery, it ask me to install the certificate again.
Anyway to verify?
In addition, sometimes, when I change my vSphere client from Site Recovery to Host and VM and switch back to Site Recovery, I get “Lost connection to SRM server IP:8095”.
sorry i was really busy today,
glad to hear that now all is ok.
Don't hesitate if you need more help on SRM. 8expecially with Vsphere Replication
And if you find my answer helpfull please rate it
I'm out of the office until Thursday 13th September. If your message is urgent please call Alan on 07717 756500, or email firstname.lastname@example.org othwerwise I will get back to you when I return. Thanks
The problem in my case was I missed this line in the installation guide: "The SRM database schema must have the same name as the database user account."
When I renamed the schema to the same name as the user it worked.