Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Connecting to VMware vCenter Site Recovery Manager fails with the error: Unable to start Site Recovery Manager Service (1027973)

Last Updated: 11/1/2012Categories: Total Views: 16999Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You are unable to connect to Site Recovery Manager (SRM) through the vSphere Client

The SRM service is not running in Windows Services

You cannot start the SRM service or the SRM service starts then stops

In the vmware-dr-X.log file, you see a backtrace similar to:

warning 'Persistence'] Rolling back OPEN transaction context: txn_id=0
warning 'DrServiceInstance'] Initializing service content: std::exception 'class VdbError' "VdbError: Column db_id does not exist in table pd_localsite"
warning 'DrServiceInstance'] Backtrace:
backtrace[00] eip 0x007da6e0 ?AbortProcess@System@Vmacore@@YAXXZ
backtrace[01] eip 0x007dae57 ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref
@VBacktrace@System@Vmacore@@@3@@Z
backtrace[02] eip 0x00415a53 (no symbol)
backtrace[03] eip 0x02eb944b ?_Activate@EntityWithPermissionsLifetimeMixin
@Authorize@Dr@@UAEX_N@Z
backtrace[04] eip 0x0041407f (no symbol)
backtrace[05] eip 0x0040789e (no symbol)
backtrace[06] eip 0x0040c453 (no symbol)
backtrace[07] eip 0x0040e86b (no symbol)
backtrace[08] eip 0x0040edfa (no symbol)
backtrace[09] eip 0x034b2de8 ?InitServiceTable@Dr@@YAXPBDKKP6AXABV?$basic_string@DU?$char_traits
@D@std@@V?$allocator@D@2@@std@@@ZP6AXXZ333@Z
backtrace[10] eip 0x034b3e2c ?RegisterService@Dr@@YA_N_NPBD1ABV?$basic_string@DU?$char_traits
@D@std@@V?$allocator@D@2@@std@@@Z
backtrace[11] eip 0x74d02a47 _endthreadex
backtrace[12] eip 0x77339d42 RtlInitializeExceptionChain
backtrace[13] eip 0x77339d15 RtlInitializeExceptionChain
error 'App'] Application error: VdbError: Column db_id does not exist in table pd_localsite. Shutting down ...

[serviceWin32,421] vmware-dr service stopped

The SRM database is running on a Microsoft SQL database instance

Cause

This issue occurs if the SQL database user specified in the ODBC connection for SRM does not have the required SQL server role privileges. In most cases, this issue occurs when the SRM database user was assigned the SYSADMIN server role when SRM was installed, but the role or permission was changed after the installation.

Resolution

To resolve this issue, try one of these options:

Ensure that you have database administrator privileges.

Ensure that you have these permissions:

Bulk insert

Connect

Create table

Restore the SYSADMIN SQL server role for the SRM SQL database user. The SYSADMIN role includes all other server roles and is sufficient by itself.

Assign the BULK_ADMIN and DB_CREATOR privileges to the user. These are the minimum database privileges required by the SRM SQL database user.

For more information, see the Site Recovery Manager Administration Guide and the Configure Microsoft SQL Server for SRM section in the Site Recovery Manager Installation and Configuration documentation.

Related Information

This issue can also occur if the schema is not the same as database username.

A Microsoft SQL Server configuration must meet specific requirements to support SRM. SRM requires that the Microsoft SQL Server must have a 32-bit DSN. Microsoft SQL Server has these configuration requirements when used as the SRM database:

The database schema has three requirements:

It must be owned by the SRM database user (the database user name you supply when configuring the SRM database connection).

It must be the default schema for the SRM database user.

The database schema name must be the same as the database user name.

You must grant the SRM database user these permissions:

bulk insert

connect

create table

If you are using Windows authentication, the database user account must be the same user account that you use to run the SRM service.

If you are using SQL Authentication, you can leave the default local System user.

If the SRM server and database server run on different hosts, you must use mixed mode authentication.

If the SQL Server is installed locally, you might need to disable the Shared Memory network setting on the database server.

For more information, see the Microsoft SQL Server Configuration section in the Site Recovery Manager Administration Guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

Related Versions:

VMware vCenter Site Recovery Manager 4.1.x

VMware vCenter Site Recovery Manager 4.0.x

VMware vCenter Site Recovery Manager 1.0.x

Take Our Survey

Support Assistant