I get the error "Failed to Create Database" when I attempt to create the database after installing SEP 12. I am running Windows Server 2003 R2. I suspect that this is an issue with the program wanting to create the database on the C: drive. The Server's root drive is F:. I have found a previous article that mentions this, but does not mention the work around
https://www-secure.symantec.com/connect/forums/failed-save-database-error-when-runnning-management-server-configuration-wizard
If anyone knows the workaround I would be grateful.
Thanks.
Check the reg key modification in this KB to change the DB to point to a different partition.
How to move Symantec Endpoint Protection Manager embedded database file to another folder?
http://bit.ly/jhEOgH
Moving this thread to the SEP 12 SBE forum.
That key does point to a valid location on the F: drive. Is there another area to look?
Hello,
What version of SEP 12 are you trying to install?
Is that version SEP 12.0.1 or 12.1?
Could you upload a screenshot of the Error you are receiving?
I don't think that the System drive or Root drive has something to do with this.
It is 12.0.1. I will get a screenshot shortly.
Attached is the image of the error. The odd thing, is that when it begins to prepare the database it says that Sem5 is already there and would I like to overwrite it, so it seems that a file is created, it is simply never finished.
Check this -
Error "failed to save database" while Symantec Endpoint Protection Manager's Management Server Configuration Wizard is creating a new database.
http://bit.ly/lSGxoZ
The file mentioned in the document was found in the proper directory, but replaced it with the one from the CD anyway, unfortuantley it did not fix the issue.
Is there any solution to this? Can I build the Database manually, what can I do here? This is a fresh install of Windows Server 2003 R2, I have installed SEP many times before and this is the first time I am getting this error. This is also the first time my root drive has been F: which is why I believe it is part of the problem. In the post I linked to in my opening comment a Symantec Employee infered there was some sort of work around for this. The Entry in the Registry and the Sav file have been setup properly by the program itself, so neither of those KBs solved the issue. Is there nothing else I can try?
It may be time to open a case with Support to get the engineers looking at your issue.
Online Portal - https://mysupport.symantec.com/
Phone - http://www.symantec.com/business/support/contact_techsupp_static.jsp