Monitor - Can't connect to local machine (server)

[tcpjsm]

Have install version 3, full installation. When I launch the executable, Monitor can't connection error below:

Could not connect to Veeam Monitor Server. Please check "Options" -> "General" -> "Veeam Monitor Server"

The local machine name is correct in location mentioned above.

Thanks in advance for any input/help.

[Gostev]

Hello,

First, I would check if Veeam Monitor service is running on your computer. If it is, please send all logs to our support along with the link to this topic, and we should be able to tell the reason from those. You can get to the logs using the Monitor Settings program in Start menu.

[tcpjsm]

Now, after a little further investigation. I get this error:

02/21/09 16:25:08 00000984 0x000003D8 "----------------------------------- New session -----------------------------------"
02/21/09 16:25:08 00000984 0x000003D8 "WinVer=Microsoft Windows Vista; Platfrom=32"
02/21/09 16:25:08 00000984 0x000003D8 "UserIsAdmin=true; UserIsPowerUser=false"
02/21/09 16:25:23 00000984 0x000003D8 "A database error (code:0x80004005, Unspecified error ) has occured in context of Connecting to DB. Error information follows"
02/21/09 16:25:23 00000984 0x000003D8 "Error record 1 of 3: Login timeout expired"
02/21/09 16:25:23 00000984 0x000003D8 "Error record 2 of 3: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections."
02/21/09 16:25:23 00000984 0x000003D8 "Error record 3 of 3: SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. "
02/21/09 16:25:23 00000984 0x000003D8 "Throwing exception."

Resolution?

[Gostev]

Did you also send all log files to our support? We really need to investigate all logs, not just the pieces that you think could be relevant to the issue. The log part you have provided is related to SQL connection, whereas the original issue reported is due to failure to establish connection to Monitor server.

[tcpjsm]

Yes, I have submitted log files to support and received a case number. The Veeam service is running. The database checks out just fine. (via Veeam Monitor Settings). However, when I launch the UI the service says running but disconnected. Also, the database of course says disconnected.

[Ben Milligan]

It is likely that enabling TCP/IP and named pipes under the SQL Surface Area Configuration for this instance will resolve the problem.

[jonatj]

I had the same problem and I already showed TCP/IP and named pipes enabled in Surface Area Configuration. What seemed to fix the problem for me was using the Add Administrator link on the Surface Area Configuration page. It explains:

"Users with administrative privileges on Microsoft Windows Vista or later version will no longer have administrative privileges on this SQL Server installation by default. To explicitly add yourself as a SQL Server administrator, click on the below link:

Add New Administrator"

I clicked the link and added the available privileges for the VEEAM instance to my user id on the right side and restarted my computer for good measure. You probably can just stop and start the SQL service.

I think the new SQL Server SP3 patch that just came out also defaults to no admin privileges too even in Windows XP.

Jonathan

[tcpjsm]

That is one of the first things I tried days ago. It's still set on tcp/ip and named pipes. Still no connection.

[Gostev]

Please also review the suggestion above from jonatj - it was pending approval (first post) when you replied to Ben so you could not see it.

[Gostev]

Also, please let me know the support case number.
[Edited] NVM someone has pointed me to it (504264).

[tcpjsm]

Tried jonatj's suggestion above. Still no connection. Ticket # 504264...