Management Console Stopped Working Options

[Sebastian Schock...]

Hi

I have been running the Management Server component on my PDC with a dedicated SQL server for months now. Recently, it started giving me errors. After investigating the problem today, I discovered that the BitDefender Management Server service is starting, but it never starts accepting connections. I discovered via the log file that it is failing to connect to the database, but I can't figure out why.

I have tested via SQL Management Studio that I can log in with the specified uid/pwd combination, and that I can access the em3 database using that uid/pwd combination. Please advise what I can try. The service refuses to connect to the database.

I have attached my server.xml file and a cut down version of the bdemsrv.dbg file.

Attached File(s)

 server.xml ( 3.97K ) Number of downloads: 5
 bdemsrv.log ( 28.74K ) Number of downloads: 4

 

[Cristi Raducu]

Hello Sebastion and welcome to our forum.

From server.xml I noticed that the connection string is wrong.

<Database>
<ConnectionString><![CDATA[DRIVER={SQL Server};DATABASE=em3;SERVER=scepdc;uid=bitdefender;pwd=bitdefender;]]></ConnectionString>

A correct connection string should look like:

<Database>
<ConnectionString><![CDATA[DRIVER={SQL Server};DATABASE=em3;SERVER=127.0.0.1\BDMS;uid=sa;pwd=RG43G43W43RF43FF;]]></ConnectionString>

pwd=RG43G43W43RF43FF => this is a random hash based on the password you enter,so you will have a different hash.

Reset again the SA password by following these steps:

http://www.bitdefender.com/support/How-to-...xpress-787.html

[Sebastian Schock...]

Hello Sebastion and welcome to our forum.

From server.xml I noticed that the connection string is wrong.



A correct connection string should look like:




pwd=RG43G43W43RF43FF => this is a random hash based on the password you enter,so you will have a different hash.

Reset again the SA password by following these steps:

http://www.bitdefender.com/support/How-to-...xpress-787.html

Hi Cristi

As I mentioned in my OP, I am using a dedicated SQL server, not an SQL Express instance installed by BitDefender. I understand the connection string because I am both an SQL Server DB Admin and a .NET developer developing applications that run on SQL Server. And as I have said, it did work this way until recently.

Also, connecting from SQL Server Management Studio with the exact same settings I can access the database no problem. I have even written a small .NET application just to test it out, and I can connect from my application and query data out of the tables in the em3 database. It's just BitDefender Management Server that is refusing to connect with that connection string.

[Cristi Raducu]

There is no problem that you are using a dedicated SQL database but the password in the server.xml file is hashed,it is not in plain letters as you type it when you log in via SQL Management Studio.
You should enter the password in the Management Server from Tools-> Change SQL Connection Password and let me know if you have a different hash.

[Sebastian Schock...]

There is no problem that you are using a dedicated SQL database but the password in the server.xml file is hashed,it is not in plain letters as you type it when you log in via SQL Management Studio.
You should enter the password in the Management Server from Tools-> Change SQL Connection Password and let me know if you have a different hash.

I tried what you asked. I have used the Change SQL Connection Password option, and my connection string now looks like this:

CODE

<ConnectionString><![CDATA[DRIVER={SQL Server};DATABASE=em3;SERVER=scepdc;uid=bitdefender;pwd=CGMNKHLMOOBHHNECOOOANICGM
FDAEFHG;]]></ConnectionString>

I restarted the BitDefender Management Server service. However, I am still getting the same error :

CODE

[PID:00008020][TID:00007560][2013-02-26-14:56:15][~][EM3SERVER ][ERROR]:  CEnterpriseServer::InitAfterStart - connecting to database failed, error code: 5

[Cristi Raducu]

SERVER=scepdc

It is not enough to specify the server name,you must also enter the instance name.
The default value is SERVER=127.0.0.1\BDMS