Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 4203 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

error code 0x80040603

raincute

I updated the Sophos server and below is the error message after reboot of
> the server.  Please help ASAP.  TY



 Failed to open connection.
 ----- [outer exception] -----
   -- error: 0x80040603
   -- facility: Custom (Defined by the interface)

   at class ATL::CComPtr<struct IDispatch> __thiscall
 bl::CReusingManagementServiceClientBroker::logIn(void)
   at int __cdecl Run(int,enum bl::ConsoleType::Type)
   at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__
 *,wchar_t *,int)

please can anyone help me thanks..

:380


This thread was automatically locked due to age.
  • 0

    Check status of Sophos services, specially Sophos Management Service.

    Also check if TCP/IP protocol is active on SQL server and you have sufficient rights to access SQL server instance.

    :382
  • 0

    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

    :390
  • 0

    I'm gonna try that guys and hope it will works, coz my boss are in panic mode so I need a tranquilizer for that.;)

    I'll give an update regarding that matter.

    :402
  • 0

    Here's the update to my problem. The migration is failed so thats why it say failed to connect.

    What I did is to uncheck the legacy updating. so I upgraded the workstations and now its ok never prompt that error.

    Thanks for the help.

    Kudos to all of you!!!:)

    :418
Unfiltered HTML