error code 0x80040603

Hi

I would be interested to see the results of the following tests:

1.    What is held in the connection string registry key the management service uses to locate the SQL instance?
        HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\DatabaseConnectionMS
        It should take the form:
        Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS4;Data Source=<SERVERNAME>\<INSTANCE>;

        Where the Data Source value is the location of the instance which contains the SOPHOS4 database.

2.    The name of the Sophos Management Server, just to ensure the management service is looking in the right location. 

       You say you updated the Sophos server.  I assume the database and management service are on the same machine?
 
3.    Does the following return the name of the server?
       OSQL –E –S .\sophos –d SOPHOS4 –Q “SELECT NAME FROM ComputersAndDeletedComputers WHERE ID=1”
        I assume you have a SOPHOS named instance on the same machine, hence the .\sophos parameter.

4.    If you create a UDL file to test the connection, does this connect ok?  To do so:
    1. Create a new file called “test.udl”.
    2. Double click on it, it should launch a “Data Link Properties” dialog.
    3. From the “Provider” tab, choose: “Microsoft OLE DB Provider for SQL Server”
    4. On the “Connection” tab, enter the name of the server and instance, in the format: <server>\<instace>. 

         By default you could put in .\SOPHOS to represent the local SOPHOS instance of SQL.

    5. “Use Windows NT integrated security” as the authentication method.
    6. You should then be able to Select the SOPHOS4 database from the select box.
    7. Does clicking on “Test Connection” succeed?

5.  As mentioned before, checking the protocols configured for SQL are correct. 

     This certainly applies if the database is remote to the management server.

These tests should help to understand the problem.

Thanks

Hi

I would be interested to see the results of the following tests:

1.    What is held in the connection string registry key the management service uses to locate the SQL instance?
        HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\DatabaseConnectionMS
        It should take the form:
        Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS4;Data Source=<SERVERNAME>\<INSTANCE>;

        Where the Data Source value is the location of the instance which contains the SOPHOS4 database.

2.    The name of the Sophos Management Server, just to ensure the management service is looking in the right location. 

       You say you updated the Sophos server.  I assume the database and management service are on the same machine?
 
3.    Does the following return the name of the server?
       OSQL –E –S .\sophos –d SOPHOS4 –Q “SELECT NAME FROM ComputersAndDeletedComputers WHERE ID=1”
        I assume you have a SOPHOS named instance on the same machine, hence the .\sophos parameter.

4.    If you create a UDL file to test the connection, does this connect ok?  To do so:
    1. Create a new file called “test.udl”.
    2. Double click on it, it should launch a “Data Link Properties” dialog.
    3. From the “Provider” tab, choose: “Microsoft OLE DB Provider for SQL Server”
    4. On the “Connection” tab, enter the name of the server and instance, in the format: <server>\<instace>. 

         By default you could put in .\SOPHOS to represent the local SOPHOS instance of SQL.

    5. “Use Windows NT integrated security” as the authentication method.
    6. You should then be able to Select the SOPHOS4 database from the select box.
    7. Does clicking on “Test Connection” succeed?

5.  As mentioned before, checking the protocols configured for SQL are correct. 

     This certainly applies if the database is remote to the management server.

These tests should help to understand the problem.

Thanks