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

5.1 Console: "An exception has occurred: Unknown configuration."

AJ

SBS2003.  Upgrade from 4.1 to 5.1.  Upgrade went well.  All clients are up to date, and error free.

First run through of installation, console runs fine.  Shut down the console, and subsequent launces give the above referenced error and the console won't start.

Re-run .\ServerInstaller\Setup.exe and then the console loads fine again.  Close it and subsequent launches again give the error and won't start.

Obviously, this is not an acceptable work around to leave it in this state.

Any ideas on a fix?

:36451


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

    Hi,

    It would still be worth try installing the console only component on another computer just to prove the problem lies with just the console component on that server.

    To do so, just copy: C:\sec_51\ from the management server to a client, e.g. Win 7, or even another server.

    Run setup.exe from the serverinstaller directory and then just choose the console component.

    You will be asked for the address of the management server (could be name or IP) and if you're in a domain the account the Sophos Management Host service runs as on the management server.

    Can you open and close that console ok?

    If that works, at least you know the problem is just in the console component only.  

    When you run the installer again (to fix it) you are performing a modify.  So once you have confirmed the problem seems to be just with the console component, you could, go into add/remove programs (or Programs and features) and remove the console component only.  You can then run the installer again, just run setup.exe to add the console back.  This would at least perform a fresh install of the console component rather than a modify.

    Failing that, as it failed after deleting the key hkcu\software\sophos i'm not so sure the 'config' referenced in the error may not be registry but you could use ProcessMonitor from Sysinternals (http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx) to ensure that there are no problems reading/writing to registry keys in that area as you open and close the console.

    Hope it helps.  If not maybe worth a call to Support as they may have seen this error before and there is a simple fix.

    Regards,

    Jak

    :36475
Reply
  • 0

    Hi,

    It would still be worth try installing the console only component on another computer just to prove the problem lies with just the console component on that server.

    To do so, just copy: C:\sec_51\ from the management server to a client, e.g. Win 7, or even another server.

    Run setup.exe from the serverinstaller directory and then just choose the console component.

    You will be asked for the address of the management server (could be name or IP) and if you're in a domain the account the Sophos Management Host service runs as on the management server.

    Can you open and close that console ok?

    If that works, at least you know the problem is just in the console component only.  

    When you run the installer again (to fix it) you are performing a modify.  So once you have confirmed the problem seems to be just with the console component, you could, go into add/remove programs (or Programs and features) and remove the console component only.  You can then run the installer again, just run setup.exe to add the console back.  This would at least perform a fresh install of the console component rather than a modify.

    Failing that, as it failed after deleting the key hkcu\software\sophos i'm not so sure the 'config' referenced in the error may not be registry but you could use ProcessMonitor from Sysinternals (http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx) to ensure that there are no problems reading/writing to registry keys in that area as you open and close the console.

    Hope it helps.  If not maybe worth a call to Support as they may have seen this error before and there is a simple fix.

    Regards,

    Jak

    :36475
Children
No Data