cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

I am having an issue accessing my ePO server page, and the /core/config page from the ePO server itself. I took an export of my production ePO server image, and took a copy of my split config db, and placed them onto two separate machines. When I initially logged into the ePO server, I could at least hit the https://localhost:8443/core/config page. From there, I put in my SQL credentials (username, pwd), the private IP of the SQL server, and tested the connection. Tested successfully.

Once this was complete, I believe I rebooted, and now I cannot get to the https://localhost:8443/core, or the /core/config page. Is there any way to confirm why this is happening? I have checked the server.log and orion.log files, and there is nothing to lead me down any specific trail. Do I need a successful SQL connection to be able to get to these pages? Seems I would always need /core/config access, in the event a SQL connection had failed or needed configured.

1 Solution

Accepted Solutions

Re: HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

https://kc.mcafee.com/corporate/index?page=content&id=KB68427

Very bottom - did you update the DatabaseInstanceName and DatabaseServer entries in the registry?  I have run into weird issues with this before.  Usually when I want to check for DB connectivity errors, I check eventparser.log

4 Replies

Re: HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

https://kc.mcafee.com/corporate/index?page=content&id=KB68427

Very bottom - did you update the DatabaseInstanceName and DatabaseServer entries in the registry?  I have run into weird issues with this before.  Usually when I want to check for DB connectivity errors, I check eventparser.log

Re: HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

I checked in the registry, and the DatabaseServer name was incorrect, so I corrected it, and rebooted. I am still getting the 500 error though and cannot launch either page.

In the eventparser.log file, im getting the following:

COM Error 0x800004005, source=Microsoft OLE DB Provider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied., msg=Unspecified error

Re: HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

Some weirdness, especially as you checked the SQL connection before the reboot.  As from the sound of it you moved from a local SQL server to a remote SQL server, have you removed the DependOnService reg keys also (same KB)?  To be completely honest, I am grasping - the initial connection verification proves that network and port access is ok, so there is likely something under the hood that is causing an issue leading on to the current SQL Server connection issue (ie the connection issue isn't the root cause).

At this stage I would be mashing around in my lab environment :-\

Re: HTTP 500 Internal Server Error when starting ePO 5.1.2

Jump to solution

thanks for the response.

the production and test environments have always been split config, so there was never any local sql. i may try to take another copy of the production db, and import it. not sure if there is some hidden sql issue or not. it still doesnt make sense though, why i wouldnt be able to access /core/config. It seems this page should always be available.