vRanger “cannot connect to service” error; API service will not start. (4044350)

When attempting to launch the vRanger GUI, the application fails to launch with the above error. Upon inspection in “services.msc”, the vRanger API service is stopped and cannot be started. The other two vRanger services (vRanger and vRanger FLR) show as being running normally.

The vRanger Database initially was installed on a remote SQL Server manually, instead of using the automatic installation of SQL Express that is packaged with the product. Because the SQL Database was setup manually, the default settings for maximum transaction log size were manually entered rather than automatically created. Upon examination of the remote SQL database via the Microsoft Management Studio, the database could be taken offline, but not brought back online. Trying to bring the vRanger database online yields the result:

ERROR: 9002 The database transaction log is full

So, the space allocated for the transaction logs has completely filled, and no new transactions can be written. When the database was created either the transaction log size limit was under-sized, or circular logging (this allows the logfiles to be overwritten as needed) was not enabled. This prohibits the vRanger API service from starting, since it needs to synchronize with the database in order to run. The failure of the API service, in turn, prohibits the vRanger GUI from launching.

The transaction log maximum size must be reconfigured, or other modifications to the SQL Server logging must be done. Consult the Microsoft article below for more information.

http://msdn.microsoft.com/en-us/library/ms175495.aspx