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

RESOLVED SEC 4.5.1 "Complete" install alongside SQL Server 2005 instance: will it break 2005?

Diewrecked

Hi guys

I am installing SEC 4.5.1 onto a Server 2003 box with SQL Server 2005 already installed running an instance for an unrelated application. I have installed a Server 2008 Express instance using the installer bundled in the SEC_451 executable and tried to point the Sophos database to it, it installs correctly but when you run it it fails with:

You cannot connect to the "management server" component on SERVERNAME, which provides data and services for Sophos Enterprise Console. This is because the management server is an earlier version or no management server exists. Click the Advanced button for information which you can send to Sophos Technical Support. This information can be used to diagnose and fix the problem.

The Advanced button provides:

Class not registered

----- [outer exception] -----
   -- error: 0x80040154
   -- facility: Custom (Defined by the interface)

   at struct IUnknown *__cdecl bl::SystemEnviroment::CreateInstanceOnServer(const struct _GUID &,const struct _GUID &,class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> >)
   at void __thiscall bl::CReusingManagementServiceClientBroker::CreateCoreServices(void)
   at __thiscall bl::CReusingManagementServiceClientBroker::CReusingManagementServiceClientBroker(const class bl::CReusingManagementServiceClientBroker &)
   at void __thiscall bl::CServerBrokerRegistrar::SetBroker(const class bl::CServerBrokerBase &) throw(...)
   at int __cdecl Run(int,enum bl::ConsoleType::Type)
   at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)

Two questions:

1. What does this failure mean? Has it not seen my SQL 2008 Express instance? How can I fix it?

2. If I uninstall and reinstall a "Complete" installation, which installs SQL Server 2008 Express itself, will it run alongside or instead of my SQL 2005 server? I absolutely DO NOT want to impact on the application/SQL server 2005 instance already running!

Many thanks in advance for any advice here.

Cheers

Jon

:10221


This thread was automatically locked due to age.
  • 0

    Hello Jon,

    Jak's the "SQL tinkerer" here :smileywink:. But meanwhile ... so you installed the 2008 Express "by hand" instead of letting the SEC installer do it? If so, what did you specify when the installer prompted you for the database details? You might want to check the registry key mentioned for example here for correct values.

    Different versions of SQL server can coexist, the only requirement is that the instances have a unique name. Can't say what's wrong with your SQL 2008 Express instance. A complete install should offer to install 2008 express alongside your existing instances I think (can't remember the details cause it's some time since I did it and I don't have an environment available to test it).

    Christian

    :10235
  • 0

    Thanks QC, although I'd like to think of it as more than "tinkering" :)

    From the error message it looks like the version of the console is out of whack with the version of the management server.

    There are 3 routes here typically:

    1. Let the installer create you a SOPHOS named instance as part of a "all in one" install.

    2. Create a SOPHOS named instance yourself and then run the install.  The SEC installer will pick up on the SOPHOS named instance and use it.

    3. Create your own named instance, e.g. SQLExpress.  If you go down this route you would install using the "Custom" option, choose all components, at the database page you should then be able to choose the custom instance.

    The various versions of SQL server will happily coexist.  The instance name is the unique factor.

    I hope this helps.

    Regards,

    Jak

    :10239
  • 0

    although I'd like to think of it as more than "tinkering"

    Strictly in the positive sense

    :10245
  • 0
    Thanks for the replies guys. I'm happy to uninstall and reinstall as "Complete" but can I confirm 100% it won't impact (ie try to upgrade) the SQL Server 2005 instance I have for my other application please? Thanks again all cheers
    :10265
  • 0

    Over the years I've done several installs and upgrades. Most of the time there were other instances of SQL Server (multiple MSDE/Express editions as well as full and Express alongside) on the machine. On one server the SOPHOS database resided in the default instance together with databases from another application (they guys didn't know what they were doing, eventually I moved it to its own instance before an upgrade). Never had any problems - and as long as the Sophos database has its own instance you shouldn't.

    Nevertheless - it's a good time to review your SQL backup restore process.

    Christian

    :10289
  • 0

    Sophos will not upgrade an instace that is not called "Sophos" so it will remain untouched.

    As QC says, taking a backup of the other database is worth doing and I assume it's being done anyway :)  Absolute worse case you can rip all SQL instances, install the same named instance and re-attach/restore the backup.

    It's always worth installing the SQL management tools on at least one machine.

    2005

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796

    2008
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=08e52ac2-1d62-45f6-9a4a-4b76a8564a2b

    They make it easy to connect to an instance, backup/restore the database.  I would think that the database probably has a maintenance plan, a part of which should be a backup.

    Regards,

    Jak

    :10295
  • 0

    Hi guys

    Many many thanks for all your replies and suggestions.

    I was unable to install a Complete installation of SEC 4.5.1 becuase there was already a SQL instance called SOPHOS and indeed it was an old legacy 2000SP3 (I think) instance. I tried the Custom install having created a new instance of 2008 Express but it failed with the errors described above. I tried it again and the same thing happened. However upon doing it a third time (I didn't do anything else) it worked!!

    So thanks again like I said, this issue is now resolved - although I have no idea why!!

    Cheers

    :10469
Unfiltered HTML