SQL Server Database and SEP

Navigate to

\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\Logs

and look in scm.server0.log
            install_log.err   

And see if there are any errors
Else post the logs  

Thanks for the quick reply.  The only files I have in that folder are:

install_log.err
install_log.out
smbinstall_log.err
smbinstall_log.out

The first 3 logs are completely empty, the last log has:

Has valid SAV license
Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
Saving welcome panel data ...
Saving welcome panel data...
Advanced option selected...
Saving company size panel data ...
Checking disk/memory size(Bytes) requirement...
Required disk/memory size(Bytes): 3113851289/536870912
Checking available disk/memory size(Bytes)...
Available disk/memory size(Bytes): 51733749760/2144530432
Saving companySize Panel user settings:
Company size: 0
Content revision number:30
DB backup number: 10
Starting db configuration process...

Also, this is running on Windows Server 2008 64-bit so the folder is Program Files (x86).  Dont' know if that makes a difference.

EDIT: Also, I'm using SQL Server 2005 with Service Pack 3

Please paste the logs for install_log.err. 64 bir OS will not make a diffrence

There is nothing in that log.  The file is 0 KB.  When I open the file in Notepad, there is nothing in it.

Is this a remote SQL or local SQL.?

If its remote then try to uninstall & reinstall the SQL native client.

Make sure if there is any firewall in between then the respective port is open on the firewall I think its 1433 port that symantec uses. you will see that  port in the installation wizard.

Kavin,

SQL and SEPM are on the same machine.

Best Practices guide for Installing the Symantec Endpoint Protection Manager with a SQL Server 2005 Database
 

http://service1.symantec.com/SUPPORT/ent-security....

Try to reinstall the SEPM & use a new database instance name i.e use SEM6 instead of SEM5 & see how it works also you said it just stays on creating database let it run dont cancle the wizard & see id it gives you any error or something automatically.

I've followed everything in that Best Practices guide already.  It says pretty much what the Installation manual for SEPM says.

Kavin,

I tried that too.  I even tried creating a database manually and then using the SEPM wizard to point to it, still sticks on the "initializing database" part.  The "creating database" step only takes about 2 minutes. I left it on "initializing database" for 2 hours and it never completed. The database itself gets created just fine.  If I open SQL Server Management Studio, I can see the database SEPM creates, for some reason the databases just won't initialize.  I'm sure I am probably missing a simple setting somewhere in SQL Server 2005.  I may just have to call Support tomorrow.

Just check this document & check if all the requirements are matched for SQL database

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007102121480648

@Tristan: The Initializing phase has been known to take time ranging from 1 hour, to almost 5 hours even on a SQL based SEPM.

Ditto if you're also trying out replication, it'd also take the same time.

Could you check if the SQL instance is configured to suspend active connections after a certain timeline from the Configuration manager?
Also, do check if you have the TCP/IP & Named Pipes setting checked and enabled on this particular instance.

HTH

HIII

Please telnet 1433 its defult DB port.......

good

tell me u r trying to install SQL on the same computer on which SEPM is installed..................?

@ Tristan: Named pipes should also be enabled for everything to work properly. Even after 8 hours you're not able to get the database initialised, I'll say there is a dead sure chance that something is wrong in the configuration for the SQL server.