cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Installation of ePO 4.6 Patch3 failed

This is our db.properties

db.database.name=xxxxxxxxxx

db.jdbc.driver=jtds

db.param.ssl=off

db.param.USENTLMV2=true

db.instance.name=MSSQLSERVER

db.pool.connections.idle.max=400

db.pool.connections.max=400

db.user.domain=

db.port=1433

db.user.name=sa

db.pool.exhausted.action=grow

db.user.passwd.encrypted.ex=xxxxxxxxx

db.server.name=xxxxxxxxxx

seems to  be ok

Highlighted

Re: Installation of ePO 4.6 Patch3 failed

Hi,

does anybody have an idea.

All files have been proofed.

db.properties

server.ini

epo.properties

Could it be something wrong on the registry.

The sql server log has the following entrys

07/16/2012 08:18:50,spid53,Unknown,Starting up database 'ePOInstallerTestDB-{AF05AA5C-1B53-45DE-9FFD-8F37F329A4BC}'.

07/16/2012 07:59:14,spid90,Unknown,Starting up database 'ePOInstallerTestDB-{AF05AA5C-1B53-45DE-9FFD-8F37F329A4BC}'.

Should i do a fresh install?

Nachricht geändert durch Schnuecks on 16.07.12 01:27:13 CDT

Re: Installation of ePO 4.6 Patch3 failed

What information do you get when accessing the following URL:

https://<eposervername>:<consoleport>/core/config

Regards Tom

Re: Installation of ePO 4.6 Patch3 failed

The same as in db.properties defined.

Schnuecks

Re: Installation of ePO 4.6 Patch3 failed

Is "MSSQLSERVER" really your instance name ?

What if you configure https://<eposervername>:<consoleport>/core/config with an empty instance name - does the "Test connection" button work successfully ?

Regards Tom

Re: Installation of ePO 4.6 Patch3 failed

Yes its the instancename from the standard sql installation.

And thats it. Without the instancename the setup runs.

But why does the server works with that instancename, why it is working?

McAfee Employee JoeBidgood
McAfee Employee
Report Inappropriate Content
Message 17 of 17

Re: Installation of ePO 4.6 Patch3 failed

Ah - that makes sense now

When the instance name is specified, it tells the installer to try to dynamically determine the SQL port by querying the SQL browser service (which is probably not running, or is firewalled.) Most importantly this setting takes precedence over the port setting, so even if this is specified correctly, the install will still be unable to determine the port.

HTH -

Joe

More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community