Endpoint installation problems: embedded DB failed, failed to connect to the server

[Migration User]

I have been spending more than a day to install Endpoint.

I am installing on a SBS 2003. I first installed the manager, with an embedded DB, there I got an error message: failed to start the embedded DB. I did what is recommended here: http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/b1b907126956f3d5882573780072846a?OpenDocument

It then goes ok. I skipped the migration wizard for now. It then opened the management console. If I log in with the credentials I chose before, I got an error message, failed to connect to the server, check server name and port.

I changed the port, checked if it was not used... still not working

I read that java 1.6 had to be uninstalled and jave 1.5 installed instead.... still not working...

Now If I try to reinstall it again, I got an error message when creating the embedded DB, it says that the endpoint manager service is running, but it is not true. There is no endpoint manager serviceyet. I am not sure what to do anymore to make that product work.

[Migration User]

Hi Bartinla,

 

let me see if I understand this correctly

 

1 You installed SEP

2 You uninstallled SEP according the instranction of the knowledge base article (because you are running Ghost?)

3 You installed SEP according to the instruction of the knowledge base article using a different database port

 

Here you could not log on and got the errore "failed to connect to server"

 

Which port did you change now? The database, management or webser port?

 

4 You unistalled SEP again (?)

5 You try to install and get the message that the service is running. - right?

 

You have checked the Services and no Symantec Service is running? The service is called Symantec Endpoint Protection Manager service.

 

Carsten

 

[Migration User]

Hi Cartsen,

1. I installed SEPM on the server.
2. I first changed the port (see 3)
3. I am not using Ghost, but that is the only KB I found talking about the embedded DB error. And doing so worked.
there I changed the Database server port to 2639 instead of 2638
4. the installation was successful, then I could not connect to the console. I ran the wizard again and change the port to 8445, 8845 .... still not working
5. I uninstalled it...yes again
6. to overcome that error message, I had to change the port 8445 to something different again 8477
7. I still can't connect. I am assuming there is a conflict with something but I can't find what

8. I opened IE, and typed http://localhost:8477/Reporting/login/login.php that doesn't work, but if I typed
http://localhost/Reporting/login/login.php then I can access a login page, there I entered my credentials, but I now get an error message: can't access the server.


thanks in advance for your help

Gaetan

[Migration User]

Hi barinla,

 

http://localhost/Reporting/login/login.php is the normal way to access reporting from a browser. You don't have to specify a port. Is the Symantec Endpoint Protection service running? The reporting engine needs this service for authentication and it also has to run in order to log on to the managemen console?

 

Carsten

[Migration User]

Cartsen,

I did check that before, and I started it since it wasn't running, but today I pay more attention to it and I remarked that it stops after 5 seconds. It is set to start automatically.
Is there something that I need to change in the registry to make it run all the time?

thanks

Gaetan

[Migration User]

By any remote chance are you trying to install this on the same server that runs Altiris Notification Server? 

 

The reason I ask is that if you are doing this and don't have the SEP Integration Component installed in your Notification Server you will run into a port conflict for 9090.  To get around this you simply need to browse to HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Notification Server and change the RpcEndpoint to 9091.  After doing this simply restart the Altiris service, the Altiris NS Reciever service, the Symantec Endpoint service, and World Wide Web (or just run IISRESET to reset it).

 

Jeremy

Message Edited by JeremyDallas on 11-09-2007 06:13 AM

[Migration User]

In case you are not running Altiris (although everybody should :)  right Jeremy?) try the following KB article to isolate the cause

 

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/d87c5993a0a8b35f882573770063d834?OpenDocument

 

Carsten

[Migration User]

I am not running Altiris, and I have through the steps on the KB:

I have those 2 issues:

Symantec Endpoint Protection Manager service stops with a Java -1 error in the event log
Symantec Endpoint Protection Manager service (SemSrv) will not stay in a started state

I ran java 1.5
I adjusted the heap size to 1024

During the DB assessment, when I test the ODBC connection. it failed: Unable to start the DB server

I guess that is the issue

thanks again for your help

[Migration User]

hi bartinla,

i have the same issue you have. i have posted a message here describing my problem.

See the logs:

 

11/01 16:37:14. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page
11/01 16:38:33. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page
11/01 17:03:16. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page
11/01 17:14:36. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page

 

Event Type: Error
Event Source: semsrv
Event Category: None
Event ID: 4096
Date:  1/11/2007
Time:  17:15:48
User:  N/A
Computer: DCTA030
Description:
The Java Virtual Machine has exited with a code of -1, the service is being stopped.

 

Event Category: None
Event ID: 1
Date:  1/11/2007
Time:  17:14:36
User:  N/A
Computer: DCTA030
Description:
The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ASANYs_sem5; *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page.

 

Event Type: Error
Event Source: ASA 9.0
Event Category: None
Event ID: 1
Date:  1/11/2007
Time:  17:14:36
User:  N/A
Computer: DCTA030
Description:
The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ASANYs_sem5; Internal database error *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
Checkpoint log: invalid bitmap page -- transaction rolled back.

 

Event Type: Error
Event Source: ASA 9.0
Event Category: None
Event ID: 1
Date:  1/11/2007
Time:  17:14:38
User:  N/A
Computer: DCTA030
Description:
The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ASANYs_sem5; Could not start server.

 

I. 11/01 11:50:49. Running on Windows 2003 Build 3790 Service Pack 2
I. 11/01 11:50:49. 65536K of memory used for caching
I. 11/01 11:50:49. Minimum cache size: 65536K, maximum cache size: 65536K
I. 11/01 11:50:49. Using a maximum page size of 8192 bytes
I. 11/01 11:50:49. Starting database "sem5" (C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db) at Thu Nov 01 2007 11:50
I. 11/01 11:50:49. Database recovery in progress
I. 11/01 11:50:49.     Last checkpoint at Thu Nov 01 2007 10:03
I. 11/01 11:50:49.     Checkpoint log...
I. 11/01 11:50:49. Performance warning: Database file "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" consists of 6111 disk fragments
E. 11/01 11:50:49. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
E. 11/01 11:50:49. Checkpoint log: invalid bitmap page
I. 11/01 11:50:49. *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
I. 11/01 11:50:49. Checkpoint log: invalid bitmap page
I. 11/01 11:50:49.
I. 11/01 11:50:49. Attempting to save dump file at 'C:\WINDOWS\TEMP\sa_dump.dmp'
I. 11/01 11:50:50. Dump file saved
E. 11/01 11:50:50. Internal database error *** ERROR *** Assertion failed: 201819 (9.0.2.3347)
E. 11/01 11:50:50. Checkpoint log: invalid bitmap page -- transaction rolled back
I. 11/01 11:52:45. Adaptive Server Anywhere Network Server Version 9.0.2.3347

thanks in advance for help us.

[Migration User]

Hi,

 

---

I had these symptoms: