Endpoint Protection

 View Only
  • 1.  Symantec Endpoint Protection upgrade woes

    Posted Dec 15, 2009 03:00 PM

    We've been on Symantec Endpoint Protection version 11.0.1  for a while now, and it has been working fine. Except that recently I noticed that the sem5.db file (which resides on my C:) on my server has grown to be over 60GB! We only have 10 users.

    I saw some posts around here and articles that says to upgrade to 11.0.5. Well I couldn't easily do that as because that file has gotten so big, it let me with only a few megabytes of disk space. So I ended up following instructions found at: https://www-secure.symantec.com/connect/forums/move-sem5db-sep-11 to move that giant file/folder to my D: drive.

    So after this, I was able to use my 11.0.5 CD to install the new Enpoint Protection Manager. When it was done, the 'Management Server Upgrade Wizard' ran, and right after clicking on 'Next', I got the following error:

    Unable to get the database schema version. You must ensure that the database server is working and can be connected to from the Management Server.

    So I looked into this and I found out that upgrading seemed to reset the registry setting and the Data Source setting back to the default location on C:. So I changed it back, and tested the data source, and it gives me the whole 'Test Connection Successful' message or whatever. This got me 1 step further.  Now at the first screen, I click 'Next', and it pops up an information window that tells me that I 'must stop all management servers connecting to this site...', I click 'Continue', and it changes screens to a 'Server upgrade status' window. It gets to 5% very quickly, and at that point in the little window below it just says:

    Initializing...
    Error occurred

    I click 'Next', and the next screen says 'Upgraded failed; check the log for details', and 'Launch log file' is checked, so after I click 'Finish', I get the log that I have posted below:

    http://pastebin.com/f1898a6f3

    This is where I get stuck and need help. I don't know how to decipher that log.



  • 2.  RE: Symantec Endpoint Protection upgrade woes
    Best Answer

    Posted Dec 15, 2009 03:37 PM
     Why even carrying that 60 gb garbage when you have just 10 clients.

    Un-install SEPM. Do a fresh install of SEPM MR5. Deploy MR5 clients with this package
    http://service1.symantec.com/support/ent-security.nsf/docid/2009042408004148


  • 3.  RE: Symantec Endpoint Protection upgrade woes

    Posted Dec 15, 2009 03:43 PM
     Agreed.  With only 10 clients, we're talking less than a few hours of work to export your policies, uninstall, reinstall, import policies, and deploy packages...  All using the new RU5 build.




  • 4.  RE: Symantec Endpoint Protection upgrade woes

    Posted Dec 15, 2009 04:18 PM
    Thanks guys. I guess I'll get uninstalling...


  • 5.  RE: Symantec Endpoint Protection upgrade woes

    Posted Dec 15, 2009 05:31 PM
     I am sorry I didn't see this post earlier. I don't know if this can help at this point but the version of SEP that you were using had the issue of the embedded database growing very large (as you know). A fix was released in the next version, but symantec has a tool to decrease that size for people in exactly you situation, it is called  Dbunload. Anyway I am sorry that you went through that trouble of moving around the database file when you could have shrunk it and then done the upgrade. But I think vikram and teiva are right, it is probably just easier starting fresh. If you have any troubles with the install please let us know.

    For anyone else who reads this post in the future please visit http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008022616103648 for more information on the Dbunload tool.

    Thanks
    Grant