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

Enterprise Console 4.5 Upgrade Failure [Topic title changed]

Blood

Hi

I tried to upgrade from 4 to 4.5 but the installer displayed an error message:

Script Execution has failed. For more detail, see c:\..\installdb.log

Which contains:

InstallDB TITAN\SOPHOS HTLINCS SOPHOS45 InstallDB.log
Started
24/07/2010
09:44
==========
Login failed for user 'HTLINCS\Administrator'.
Cannot open database "SOPHOS45" requested by the login. The login failed.

This is the domain administrator account. Anyone have any suggestions on how to fix this, please?

Thanks

:4118


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

    Hi, Christian

    I made a backup of the Sophos database before upgrading as per the instructions in the Upgrade Advisor.

    I think that despite the fact that SAV worked beforehand, the Support Technician I was working with yesterday was literally flabbergasted at the size of the database files. The mdf was 23MB and the ldf was 1.62GB. There are only 34 clients on the network...

    When I sent the DB to Sophos several months ago the files were even larger, and when returned were 20MB and 40MB respectively. I have to admit that because of my lack of SQL knowledge I never thought to check the size of the files, and even then I would not know what was too large etc

    So, at the end of the day, I learnt some more things about how it all works. The other benefit, of course, is that the previous installation had been in place since 2006 with several upgrades, so a new installation and setting the configuration from scratch is a good thing. I don't want to restore the DB in case I introduce a problem. The main issue the Support Technician had yesterday was trying to remove all references to the previous Sophos4 instance in SQL. I wonder if the instance was 'healthy'.

    Thanks for your comments. I will schedule the backupdb batch file to copy the database to a remote machine from where it can be backed up to tape each night.

    Cheers!

    :4165
Reply
  • 0

    Hi, Christian

    I made a backup of the Sophos database before upgrading as per the instructions in the Upgrade Advisor.

    I think that despite the fact that SAV worked beforehand, the Support Technician I was working with yesterday was literally flabbergasted at the size of the database files. The mdf was 23MB and the ldf was 1.62GB. There are only 34 clients on the network...

    When I sent the DB to Sophos several months ago the files were even larger, and when returned were 20MB and 40MB respectively. I have to admit that because of my lack of SQL knowledge I never thought to check the size of the files, and even then I would not know what was too large etc

    So, at the end of the day, I learnt some more things about how it all works. The other benefit, of course, is that the previous installation had been in place since 2006 with several upgrades, so a new installation and setting the configuration from scratch is a good thing. I don't want to restore the DB in case I introduce a problem. The main issue the Support Technician had yesterday was trying to remove all references to the previous Sophos4 instance in SQL. I wonder if the instance was 'healthy'.

    Thanks for your comments. I will schedule the backupdb batch file to copy the database to a remote machine from where it can be backed up to tape each night.

    Cheers!

    :4165
Children
No Data
Unfiltered HTML