Upgrade From 3.2 to 3.4 Fails - Monitor Service Starts/Stops

Monitor, diagnose and receive alerts to problems across your SQL Servers.

Upgrade From 3.2 to 3.4 Fails - Monitor Service Starts/Stops

Postby TUellner » Thu Jul 11, 2013 8:23 pm

I am trying to upgrade from SQL Monitor 3.2 to 3.4. The install get close ti finishing and then gives the following error:

Service 'SQL Monitor 3 Base Monitor'
[MonitorBaseDeploymentService] failed to start. Verify
that you have sufficient priviledges to start system

The save login credentials work fine in 3.2. However, if I go to services and try to start the service at this point, the services starts briefly and then stops.

Windows 2008 R2 Datacenter SP1 (build 7601). The serice login is a domain user with priviledges to run a servers (run 3.2 fine).
SQL Server 2012 (11.0.3000) Enterprise Eval Edition.

Anyone else seeing this issue with 3.4?

Posts: 7
Joined: Thu Jul 11, 2013 8:03 pm

Postby priyasinha » Thu Jul 18, 2013 2:43 pm

Hi Tom,

We have not heard this issue from any other user. Also, as far as we are aware, there is no change in permission between v3.2 and v3.4 release. You may want to verify that Base monitor service account has these permissions.

Posts: 549
Joined: Wed Jan 03, 2007 4:02 pm

Return to SQL Monitor Previous Versions

Who is online

Users browsing this forum: No registered users and 1 guest