Hi all,
Environment :
Windows Server 2012 r2 (SRM server for both production and dr site)
vCenter virtual appliance 5.5 (both production and dr site)
Site Recovery Manager 5.5 (Success installed on dr site but failed in production site)
MSSQL 2008 r2 express (installed on the same servers of SRM)
I have success to install the SRM on DR site but failed in production, and below are the SRM installation logs from production site, it seems the SRM cannot get the VC version from the SQL statement and the ODBC source already tested and success. The SRM installation will rollback when almost done. Any advices for this? Thanks
Section for VMware vCenter Site Recovery Manager, pid=2016, version=5.5.0, build=1315893, option=Release
2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Logging uses fast path: false
2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Handling bora/lib logs with VmaCore facilities
2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Initialized channel manager
2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] Current working directory: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin
2015-01-22T10:38:45.160+08:00 [02168 verbose 'Default'] Setting COM threading model to MTA
2015-01-22T10:38:45.160+08:00 [02168 info 'Default'] ThreadPool windowsStackImmediateCommit = true
2015-01-22T10:38:45.160+08:00 [02168 info 'ThreadPool'] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 401, 2, 200, 2147483647
2015-01-22T10:38:45.160+08:00 [02168 info 'ThreadPool'] Thread enlisted
2015-01-22T10:38:45.176+08:00 [01836 info 'ThreadPool'] Thread enlisted
2015-01-22T10:38:45.191+08:00 [02476 info 'ThreadPool'] Thread enlisted
2015-01-22T10:38:45.191+08:00 [01956 info 'ThreadPool'] Thread enlisted
2015-01-22T10:38:45.191+08:00 [00620 info 'ThreadPool'] Thread enlisted
2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute - SQL execution failed: SELECT * FROM VPX_VERSION
2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute - Bind parameters:
2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Execute - ODBC Error: "ODBC error: (42S02) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'VPX_VERSION'." is returned when executing SQL statement "SELECT * FROM VPX_VERSION"
2015-01-22T10:38:45.238+08:00 [02168 warning 'Vdb'] Backtrace:
--> backtrace[00] rip 00007fff4b5aa04a
--> backtrace[01] rip 00007fff4b46f51f
--> backtrace[02] rip 00007fff4b4706be
--> backtrace[03] rip 0000000000187140
--> backtrace[04] rip 000000000018733c
--> backtrace[05] rip 0000000140005d6d
--> backtrace[06] rip 0000000140007a3c
--> backtrace[07] rip 0000000140008019
--> backtrace[08] rip 000000014000f322
--> backtrace[09] rip 00007fff608113d2
--> backtrace[10] rip 00007fff60f903c4
-->
2015-01-22T10:38:45.238+08:00 [02168 error 'Vdb'] VdbStatement::Execute(): Failed: "ODBC error: (42S02) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'VPX_VERSION'." is returned when executing SQL statement "SELECT * FROM VPX_VERSION"
2015-01-22T10:38:45.254+08:00 [00620 info 'ThreadPool'] Thread delisted
2015-01-22T10:38:45.254+08:00 [01956 info 'ThreadPool'] Thread delisted
2015-01-22T10:38:45.254+08:00 [02476 info 'ThreadPool'] Thread delisted
2015-01-22T10:38:45.269+08:00 [01836 info 'ThreadPool'] Thread delisted