ERAS Advanced Installation

Discussion in 'ESET Server & Remote Administrator' started by feryo, Apr 9, 2012.

Thread Status:
Not open for further replies.
  1. feryo
    Offline

    feryo Registered Member

    Hi guys. I need some help here.
    I'm getting crazy trying to create the connection to an SQL server for hosting ERAS db.

    I'm freeze with Connection String window. Even I've left the options as default (only changing Server=<mysqlserver>), set the user account with logins rights, I get a message with "Login failed for user domain\service_account". If I use SA user I got that message too.

    Following ERA PDF for setting things up, I found an ODBC connection should be created prior to test the connection. I did and also have changed connection string to DSN instead of SERVER but I'm not able to sucess.


    References:
    Operating system: Windows 2008 R2
    SQL Server: SQL Server 2010 SP1 (RTM)

    Any clue that can help me?
  2. feryo
    Offline

    feryo Registered Member

    I got fixed this connection error now by just using SCHEMA text box (instad of a user account) and connection is successful.

    Now I'm facing another issue after set all properties asked by the installer.
    When it start running I can see a RollBack action and can see a temp. log that shows the following at the end:

    <2012-04-10 00:39:18> MigrateData: Entered
    <2012-04-10 00:39:18> Updating database flags...
    <2012-04-10 00:39:19> LoadUserProfile failed (code=1314)
    <2012-04-10 00:39:19> Current session impersonated to account "HQ\svc_ESET"
    <2012-04-10 00:39:19> User session reverted
    <2012-04-10 00:39:19> Cannot update database flags
    <2012-04-10 00:39:19> Last DB error: Operation: {Execute} Native: {0xA43} State: {23000} [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_DBProperty'. Cannot insert duplicate key in object 'dbo.DBProperty'. The duplicate key value is (setup_guid). QUERY: INSERT INTO dbo.DBProperty (Name, ValueStr) VALUES (N'setup_guid',N'58C0D993FF47C9D5301350D7E8D5B88C9C16CCB3')
    <2012-04-10 00:39:19> InstallAbort: Entered
    <2012-04-10 00:39:19> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\license\EAV-19336069.lic" was deleted
    <2012-04-10 00:39:19> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era.xml" was deleted
    <2012-04-10 00:39:19> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era_private.xml" was deleted

    Any clue about what this means?

    Thanks in advance.
  3. DrewD
    Offline

    DrewD Eset Staff Account

    For MS SQL you will need to provide a database user name, database username password, and schema name.

    The Schema name is usually the same as the database username.

    You will need to reinstall ESET RA if you are still experiencing the connectivity issues with the database.

    Perhaps start over by creating a new empty database on the MS SQL server.

    Accept the default settings for the connection string, only updating the servername.

    Be sure to set the installer to create tables automatically.
  4. feryo
    Offline

    feryo Registered Member

    DrewD.

    It is the 1st installation within my server as I don't have any other previous version installed. However I did what you told me: create a new DB and let the installer to create the tables within.

    So... it did create the tables but again I was presented with a Rollback action:

    <2012-05-02 20:33:47> Product: ESET Remote Administrator
    <2012-05-02 20:33:47> Customer: <removed for security purposes>
    <2012-05-02 20:33:47> Valid to: <removed for security purposes>
    <2012-05-02 20:33:47> CreateCfgFiles: Entered
    <2012-05-02 20:33:47> CreateXmlCfg: C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era.xml
    <2012-05-02 20:33:47> CreateXmlCfg: C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era_private.xml
    <2012-05-02 20:33:47> CreateCfgFiles: Configuration successfully saved
    <2012-05-02 20:33:47> MigrateData: Entered
    <2012-05-02 20:33:47> Updating database flags...
    <2012-05-02 20:33:47> LoadUserProfile failed (code=1314)
    <2012-05-02 20:33:47> Current session impersonated to account "hq\svc_eset"
    <2012-05-02 20:33:47> User session reverted
    <2012-05-02 20:33:47> Cannot update database flags
    <2012-05-02 20:33:48> Last DB error: Operation: {Execute} Native: {0xA43} State: {23000} [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_DBProperty'. Cannot insert duplicate key in object 'dbo.DBProperty'. The duplicate key value is (version). QUERY: INSERT INTO dbo.DBProperty (Name, ValueStr) VALUES (N'version',N'4.0.138')
    <2012-05-02 20:33:48> InstallAbort: Entered
    <2012-05-02 20:33:48> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\license\EAV-19336069.lic" was deleted
    <2012-05-02 20:33:48> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era.xml" was deleted
    <2012-05-02 20:33:48> Installed file "C:\ProgramData\ESET\ESET Remote Administrator\Server\configuration\era_private.xml" was deleted
  5. rockshox
    Offline

    rockshox Registered Member

    Are you sure that the database was completely empty? The error is stating that a duplicate key is being entered. The PK in that table is the "Name", so it is trying to insert a key that already exists.

    Violation of PRIMARY KEY constraint 'PK_DBProperty'. Cannot insert duplicate key in object 'dbo.DBProperty'. The duplicate key value is (version).

    QUERY: INSERT INTO dbo.DBProperty (Name, ValueStr) VALUES (N'version',N'4.0.138')

    From Management Studio, I would do a "select * from dbproperty" and see if the table is in fact empty. If the table is in fact empty, then try running the insert command manually from Management Studio and see if you get errors:

    Code:
    INSERT INTO dbo.DBProperty (Name, ValueStr) VALUES (N'version',N'4.0.138')
Thread Status:
Not open for further replies.