Veeam Monitoring Free Installation issue

[synchronet]

I installed Veeam Monitoring Free product on a Server 2003 Standard. The installation errors with:

can't deploy database due to the following error: idispatch error 3092

I have removed and reinstalled the product, including the sql 2005 product twice the same result.

Does anyone have any ideas on this?
thanks
-pat

[Gostev]

I should check with devs on that - I have not seen this reported before.

[synchronet]

Here is my exact error message.

Can't deploy database due to the following error: IDispatch error #3092: "server\veeam Monitoring' is not a valid login or you do not have permission

[Vitaliy S.]

Hello Pat,

Can you tell me please whether you're trying to install Veeam Monitor to a Domain Controller by any chance or not?

[synchronet]

It's a standalone joined to a domain, however it used to be a domain controller and was demoted a while back.

[Vitaliy S.]

Pat,

Actually, installing Veeam Monitor on a DC is not supported, however as your DC was demoted you should have been successfull, so could you please send me the setup log, which can be found here:

C:\Documents and Settings\<USERNAME>\Local Settings\Application Data\Veeam\Veeam Monitor for Vmware\SetupHelper.log

Also, for now, please try installing Monitor on another machine.

[MarcWoN]

Hi,
I am having the exact same error. We are trying to install the application on a server with Windows Server 2003 (not a DC) and on a DB that is on another server.
Has a solution been found?
Thanks in advance.

[dimkaphantom]

I have same situation, but I can say more - Veeam Monitior was installed on Win2k3 R2 SP2 server which is not a domain controller, but SQL server, where database was located is DC and on DC we have no group named "SERVER\Veeam Monitoring", but we have group "DOMAIN\Veeam Monitoring" and Veeam fails.

Any ideas?

[Vitaliy S.]

Hello Dmitriy,

Installing Veeam Monitor on SQL DB which is located at DC machine is not supported, please use local SQL server or any other.

Thank you!

[Gostev]

BTW I would not suggest running additional applications on domain controllers anyhow (just common sense / best practices).

[dimkaphantom]

In fact, it's only one SQL server in out company and it installed on DC. Unfortunately, we have no free Microsoft Licenses for using a dedicated VM as DC.

And I think developers can (should) allow users to use any available SQL server.

[Vitaliy S.]

Dmitriy,

Yes, you're absolutely right, this limitation for SQL server relates only to DC machines, because there are no local groups, only domain ones. You may try to use local free SQL Express Server to run with Monitor.

[Gostev]

Yes, Vitaly is absolutely right - consider using default installation path that deploys free SQL Express backend.

[dimkaphantom]

Dmitriy,

Yes, you're absolutely right, this limitation for SQL server relates only to DC machines, because there are no local groups, only domain ones. You may try to use local free SQL Express Server to run with Monitor.

Yes, I'll use SQL Express, but in fact, can I hope that in future builds I'll be able to chose my primary SQL Server?

[Gostev]

Yes, we do plan to address this issue in the future releases.