Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 670 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

installation 4.5

fdsafdsfds

installation of sophos enterpirse console got an error

[ODBC Driver Manager] Data source name not found and no default driver
specified

can someone help me guys :D

thanks in advance...

:18407


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    I assume that the installation rolled back and there is nothing on the machine left to fix?  So the machine needs to be fixed up in some way before the next reinstall attempt?  Does the Microsoft SQL Server instance remain on the machine?  Did it get that far?

    It would be nice to see where in the sequence this error was thrown, Im not sure if this is thrown from a pre-check earlyy on or when the Sophos Management service first tries to connect to the database later on.  The full msi log for the install as found in %temp% would be useful if you could make it available to view somewhere.

    I would suggest ensuring that you can do the following thought: as it will test some of the system components Sophos requires

    Create a file called: "DBConnTest.udl".

    Double click on it.

    There should be a number of data providers on the "Provider" tab, choose: "Microsoft OLEDB Provier for SQL Server".

    On the "Connection" tab, Enter the location and instance name of the SQL instance the Sophos database is going to reside in.

    .\sophos

    Would be the default, i.e. a local instance called Sophos.  

    Choose "Use Windows NT Intergrated security".

    Then, on step 3 you should see the databases hosted in the instance you can select one and then choose "Test Connection"

    Does this all work?

    Do you know if the SOPHOS instance remains on the machine?  You can use the above test to see if a SOPHOS45 database exists as well.

    Sorry, it's hard to tell the state of the machine.

    Regards,

    Jak

    :18415
Reply
  • 0

    Hi,

    I assume that the installation rolled back and there is nothing on the machine left to fix?  So the machine needs to be fixed up in some way before the next reinstall attempt?  Does the Microsoft SQL Server instance remain on the machine?  Did it get that far?

    It would be nice to see where in the sequence this error was thrown, Im not sure if this is thrown from a pre-check earlyy on or when the Sophos Management service first tries to connect to the database later on.  The full msi log for the install as found in %temp% would be useful if you could make it available to view somewhere.

    I would suggest ensuring that you can do the following thought: as it will test some of the system components Sophos requires

    Create a file called: "DBConnTest.udl".

    Double click on it.

    There should be a number of data providers on the "Provider" tab, choose: "Microsoft OLEDB Provier for SQL Server".

    On the "Connection" tab, Enter the location and instance name of the SQL instance the Sophos database is going to reside in.

    .\sophos

    Would be the default, i.e. a local instance called Sophos.  

    Choose "Use Windows NT Intergrated security".

    Then, on step 3 you should see the databases hosted in the instance you can select one and then choose "Test Connection"

    Does this all work?

    Do you know if the SOPHOS instance remains on the machine?  You can use the above test to see if a SOPHOS45 database exists as well.

    Sorry, it's hard to tell the state of the machine.

    Regards,

    Jak

    :18415
Children
No Data