Video Screencast Help

Symantec Endpoint Protection Prevents me from installing a Postgresql database server

Created: 16 Aug 2012 • Updated: 16 Aug 2012 | 14 comments

I was trying to install a Postgresql database server in my Windows 2003 R2 server, but always got a some error messages.  After installation, I could not start my Postgresql server at all.  It looks like Symantec Endpoint Protection has something to do with it.  Because after I uninstalled Symantec, I could install my Postgresql database server.  Can anyone with the knowledge please tell me what is going on?  I really need to run both Symantec Endpoint and Postgresql database together.

Comments 14 CommentsJump to latest comment

Simpson Homer's picture

What version of SEP are u using?

Are you using SEP with full protection or basic protection>?

pete_4u2002's picture

what compoenents of SEP is installed?

are there anything in the SEP logs or application event logs?

Postgresql's picture

This is our customer's server.  For what I can see they have SEP manager installed and they also have an embedded database service running for SEP.  I will ask them for what components they have installed.

mitcheljh's picture

I would also like some information on this issue.

I have a software product which uses postgres for it's database.  The software can initialize the database cluster fine, and seems to be able to start the database, but is not able to communicate with the database via port 5433.  From what I read, SEP does not use this port, and I suspect it's blocking this port.  

Postgres is an established database server.  Shouldn't SEP be able to recognize that this port is being used by postgres, and allow it's use?

sandra.g's picture

So if you (or they) are using the SEP client only, I would definitely have a look at the Network Threat Protection logs.

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

mitcheljh's picture

Thanks Sandra,

I'll ask my customer to check those logs.

I'm also trying to setup a trial version of SEP on a VM, so I can replicate the issue.

.Brian's picture

What's showing in the traffic logs?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

mitcheljh's picture

Thanks for the suggestion, Brian.

I'll ask my customer if he can check them, and I'll post them below.

mitcheljh's picture

Thanks for your reply.

This is on a clients machine, so I'll try to get the logs.

Also, I've downloaded the trial version of SEP, to try to replicate the issue.  I have a VM setup for Windows 7 Home Premium.  When I try to install SEP on this VM, I get the message "Installation of Symantec Endpoint Protections Manager is not allowed on Windows XP Home Edition", which is a little odd, because it's actually Windows 7 Home Premium.

Thanks again for your help.

.Brian's picture

You won't be able to install SEPM on Win7 Home, 11.x or 12.1:

System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1

http://www.symantec.com/business/support/index?pag...

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

mitcheljh's picture

Thanks Brian,

I didn't realize those requirements.

I'll try installing on Win7 Pro.

sandra.g's picture

It's possible that PostgreSQL and the embedded database (SQL Anywhere), which is a component of the SEPM (the management console), are in conflict. What do the PostgreSQL logs indicate is happening, if anything? (What's odd to me is is that while it's not recommended to do so because of potential resource issues, the SEPM and LiveUpdate Administrator, which (I believe) uses a PostgreSQL database, can both be installed on the same machine. Granted, it's been a while since I tested such a setup, but...)

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

mitcheljh's picture

 

Thanks for the input, Sandra.

I get a generic connection error from Postgres: 

"Could not connect to server: Connection refused (0x000027AD/10061)  Is the server running on host "localhost" and accepting TCP/IP connections on port 5433?"

I do know that the server starts up fine.  The application just can't connect to the database.  It works find when SEP isn't running.

I could ask my customer(s) to put in a rule for this port, but I hate to ask all customers that are using SEP to do this.

I don't think it's an issue if there's another instance of postgres installed, or even another instance running.  I make sure to install the cluster in a different location, and don't start it from a service, and make sure I use a different port.  I've tested it on other machines which already have postgres installed, even when it's a different version.

It seems like the port is being blocked, but I may have to ask my customer to unblock the port in SEP to know for sure.

Thanks again

 
mitcheljh's picture

I just installed the latest version of SEP (12.1.1) on Win7 Pro x64, and it does not seem to cause any issues with our application connecting to the postgres database.  Our customer is running version 11.0.5, however, so there may be something with that older version that's different than the latest version.  It's possible that they may also have something configured differently in SEP that would cause the communication issue.

Thanks for everyone's help, and if I find the reason for the issue that our customer's issue with postgres, I'll report back.