MSSQL\Veeam Monitoring is not a valid login or you do ...

[xmk]

Hello,

I am installing Veeam Monitor on W2K3 connecting to a named instance on MS SQL 2005 Standard. I'm getting the following error:

04/16/09 23:18:11 00005240 0x00001478 "A database error (code:0x80040E14, ) has occured in context of EXEC master.dbo.sp_addsrvrolemember @loginame = N'MSSQL\Veeam Monitoring', @rolename = N'sysadmin'EXEC master.dbo.sp_grantlogin @loginame = N'MSSQL\Veeam Monitoring'. Error information follows"
04/16/09 23:18:11 00005240 0x00001478 "Error record 1 of 1: 'MSSQL\Veeam Monitoring' is not a valid login or you do not have permission."
04/16/09 23:18:11 00005240 0x00001478 "Throwing exception."

Any idea?

Thanks,

Michal

[Gostev]

Hello, are you trying to use remote SQL and either Veeam Monitor server or SQL server are not part of a domain?

[xmk]

Hi,
Both servers are part of the same domain.

[Gostev]

Do you specify domain account for SQL connection?
Does this account have rights to add logins to SQL server?
Also, do you have your SQL configured to accept Windows authentication?

Also, just to make sure, you are not installing Veeam Monitor server on Domain Controller here, right?

[xmk]

> Do you specify domain account for SQL connection?
> Does this account have rights to add logins to SQL server?
> Also, do you have your SQL configured to accept Windows authentication?
Looking into the Database tab in Veeam Monitor Settings application I'm using the "current user" setting which is a domain user and is an administrator on both the SQL server and local server. The database is in the mixed mode.

> Also, just to make sure, you are not installing Veeam Monitor server on Domain Controller here, right?
right -- no domain controllers here.

[Gostev]

OK, let me get further troubleshooting instructions from developers... myself or my colleagues from support will update this thread later.

[NShatsky]

Hello Michal,

Can you please create a support case and provide us with contact information. I would recommend a quick meeting to take a look at your environment in order to resolve this issue.

[xmk]

I'd be happy to...

[Luckas]

Hi,

Why is it a non supported configuration to setup veeam monitor in an existing sql 2005 Server, hosted on a Domain controller?
There are many SQL Installations that runs on a DC. I was able to setup monitor 3.x in this way

And, we have also our Veeam Backup DB, VC Database, View DB and mutch more DB´s on a common SQL Server (running on a DC including a working Backup and Disaster Recovery scenario).

I dont like to break this solution with a local Express DB on the VC Host!

Please give me a work around or working setup file, or must i setup a call to support team?

Thanks to all,
Helmut

[Gostev]

Why is it a non supported configuration to setup veeam monitor in an existing sql 2005 Server, hosted on a Domain controller?

Hi Helmut, this is because Veeam Monitor 4.0 creates local groups on SQL server computer, and local groups behave differently on domain controllers.

[Luckas]

Gostev,

ok, but is this the right way for our customers and myself? I guess they should think about the design of "local groups" and sql db servers...

What can i do now? This situation needs local Express Server on my virtual center host... (which is a VM itself!!!)

Helmut

[Gostev]

Helmut, typically many customers avoid installing any application on domain controllers, thus we expected this to be a rare case and do not support it yet. As a workaround, can you simply install Veeam Monitor on a separate VM? Veeam Monitor does not need to be installed on vCenter server...

[Luckas]

Gostev,

ok. I did a setup in the vm. But in deed, its no a rare case in small environments

thanks for your fast reply.

Helmuz

[Gostev]

No problems. You can setup Veeam Monitor server in a VM, and install client-only setup on your admin workstation, then connect the client to Veeam Monitor server.

[fd99tpr]

Has there been a resolution to the original issue? I am having the same problem ( MSSQL\Veeam Monitoring is not a valid login or you do ...) Seems this forum got off topic talking about installing on a domain controller. I am not installing on a domain controller and I am using a valid SQL admin account that is also part of the domain admin group. I am attempting to connect to a SQL 2005 cluster. Can anyone shed some light? Thanks!

[Gostev]

Phil, can you please provide more details on the error (log snippet).
Also, which version are you using - this thread is quite old and is about version 3.0.

[fd99tpr]

07/31/09 09:34:33 00003428 0x00000D64 "----------------------------------- New session -----------------------------------"
07/31/09 09:34:33 00003428 0x00000D64 "WinVer=Microsoft Windows Server 2003 Enterprise Edition; Platfrom=32"
07/31/09 09:34:33 00003428 0x00000D64 "UserIsAdmin=true; UserIsPowerUser=false"
07/31/09 09:34:33 00003428 0x00000D64 "A database error (code:0x80040E14, ) has occured in context of EXEC master.dbo.sp_addsrvrolemember @loginame = N'FEPSQLVS2\Veeam Monitoring', @rolename = N'sysadmin'EXEC master.dbo.sp_grantlogin @loginame = N'FEPSQLVS2\Veeam Monitoring'. Error information follows"
07/31/09 09:34:33 00003428 0x00000D64 "Error record 1 of 1: 'FEPSQLVS2\Veeam Monitoring' is not a valid login or you do not have permission."
07/31/09 09:34:33 00003428 0x00000D64 "Throwing exception."


We are attempting to run version 3.0. Going through setup for the first time. At the end of running setup it throws the exception. Please let me know if you need anything else. Thanks!

[Gostev]

Phil, could you please download and install the current version (4.0.1) and see if it fixes the issue?

[fd99tpr]

Gustev,

I have downloaded the latest version of the monitor and I am still having the issue. Funny thing, the old version started working before I uninstalled it. I wanted the latest version installed. Now it doesn't matter what I try I get the same error. It trys to upgrade the DB and fails because it can't connect with the sql id I am using. This is the same SQL id that started working in the old version. Any ideas?

[Gostev]

Phil, if both Monitor client and server are in the same domain and you are not installing on domain controller, then I am not sure what this might be and what are you doing wrong. If you are using licensed Veeam Monitor, feel free to contact our support to setup a live webex and they will help you to make this work.

[glen.rhea]

I can replicate the issue as well. I am using the default instance of SQL Server 2005 in a cluster too. The logs are below. It looks like it is trying to put hostname\localusername for the username when it calls master.dbo.sp_addsrvrolemember. Obviously that wont work on a clustered instance of SQL Server and I would prefer to use my domain service account for this service anyway. I would like to test this product and if it fits our needs we will purchase it, however it is difficult to justify the purchase for something that wont even install.

08/24/09 13:18:43 Generic 0x1188 main "Instance=geostorsql; DB=veeammonitor; Username=HDS\grhea"
08/24/09 13:18:43 Inform 0x1188 main "A database error (code:0x80040E14, ) has occured in context of EXEC master.dbo.sp_addsrvrolemember @loginame = N'GEOSTORSQL\Veeam Monitoring', @rolename = N'sysadmin'EXEC master.dbo.sp_grantlogin @loginame = N'GEOSTORSQL\Veeam Monitoring'. Error information follows"
08/24/09 13:18:43 Inform 0x1188 main "Error record 1 of 1: 'GEOSTORSQL\Veeam Monitoring' is not a valid login or you do not have permission."
08/24/09 13:18:43 Inform 0x1188 main "Throwing exception."
08/24/09 13:18:43 Inform 0x1188 main "Impersonate: Reverting to self..."
08/24/09 13:18:43 Inform 0x1188 main "Impersonate: OK"
08/24/09 13:18:43 Error 0x1188 main "IDispatch error #3092 (Code: 0x80040E14, Source: Microsoft SQL Native Client, Description: 'GEOSTORSQL\Veeam Monitoring' is not a valid login or you do not have permission.)"

[Gostev]

Hello Glen, unfortunately right now we do not support clustered SQL server - but we are planning to add such support later.