Installing First SEPM Mananagement Console on a remote SQL server.

[Migration User]

I have a SQL 2005 Server installed on a 32 bit Windows 2003 Server and created an instance named SEPM.  I have installed my first SEP Management Console on a 32bit Windows 2008 server and am using the Management Server Configuration Wizard to define my first site and database.  I have proceded past the form {Image 1 } where we defined the Database Server/Instance, User/Admin account info, and paths to the native sql client tools and the database.  I know the Management Server Configuration Wizard is able to access the SQL server because pushing the Default button for the Database path populates the Database Path field. 

The next form {Image 2} is where you define the SEPM admin account password and the E-mail address.  After completing the fields, I press the Next button and get a form with title Error and the message "Unexpected error."  I have tried multiple passwords and E-mail addresses and they all fail.  I have also tried a password and E-mail address that worked when using the embedded database option.  I don't beleive that is a invalid password or E-mail account issue but have no idea on what else might be wrong. 

Any help resolving this "Unexpected error" would be greately appreacited.

Bruce Singer
State of Missouri - OA - ITSD - DSS

[Migration User]

 Hi,

Just make sure that the setup file used for installation is unzipped properly and it is not blocked.

[Migration User]

Can you check the event viewer and let me know the event id's generated. This would be of help to us.

[Migration User]

It is the same set of files I used to install multiple management servers with the embedded database and one management server with an local SQL server.  It does not seem likely the setup files are corrupted.  However, if you give me the name of the files you think are corrupted, I will copy them from a working test installation.

Sincerely
Bruce Singer

[Migration User]

I looked at the Windows Application, Security, System, and Setup logs and then ran the configuration wizard again to get the error.  There were no entries in any of the logs that pertain to the error.  The only new entries in the logs were in the security logs that logged some successful logons.    I made copies of the logs but unfortunately I can not add them to this thread.  I can start a new thread with the logs if you want a copy of them.  .

Sincerely
Bruce Singer

[Rafeeq]

go to C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs
check scm-server 0.log as well catalina.out log you will find somethign.
make sure that the password what you are selecting is under password security for SQL.

[Migration User]

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\install_err.log

Check in that. 

[Migration User]

Note, I set the default program location to the D:.  In D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\ I found the following 4 files:  Install_log.err, Install_log.out, smbinstall_log.err, and smbinstall_log.out.  They were all empty except for smbinstall_log.out which I am listing the contents below:

Has valid SAV license
Info>> No SNAC license file in D:\Program Files\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): 52957622272/1072312320
Saving companySize Panel user settings:
Company size: 0
Content revision number:30
DB backup number: 10
Starting db configuration process...

Looks like it is aborting during the database configuration process.  On the server with SEP11 management server installed, Using the sa account, I can connect to the SQL instance using the SQL Server Management Studio program.  Not sure where to go next. 

Sincerely
Bruce Singer

[Rafeeq]

Try doing a repair  of SEP and try the configuration again..