Data Loss Prevention

 View Only
  • 1.  Apache 404 , resource not found error

    Posted Apr 07, 2015 12:09 AM

    Hello all,

    Need your assistance on the below error

    There is an issue Enforce server connecting to DB after DB migration. Prior to this the new Db connection was tested and it was running fine.

    After the migration , We have connection failure error “apache 404 , resource not found error”. We followed up with DBA team to check the server connectivity , but the connection is fine and Database is up.

    One of the reasons might be  that , The account id: protect  password was changed on the DB , not on the enforce server,this happened before the migration.

    Advise how to resolve this connection error , Is it possible to change the database password .properties file on the enforce server ?

    I have checked the below threads already- 

    https://www-secure.symantec.com/connect/forums/symantec-dlp-enforce-web-console-fails-start

    https://www-secure.symantec.com/connect/forums/while-accessing-dlps-web-console-error-http-status-404-displayed



  • 2.  RE: Apache 404 , resource not found error

    Posted Apr 07, 2015 01:06 AM


  • 3.  RE: Apache 404 , resource not found error

    Posted Apr 07, 2015 09:49 PM

    Its been 20+ hours since you have posted.  DId you solve the problem?  IF so what was the solution?

     

    Have you reached out to Symantec support yet? If not thats what I would do.



  • 4.  RE: Apache 404 , resource not found error
    Best Answer

    Trusted Advisor
    Posted Apr 08, 2015 12:35 AM

    Hello,

    I agree with jjesse. It's been long. Have you contacted Symantec?

    Again, looking at the issue - it surely seems you have done some research.

    I am pretty sure there is something wrong with your database authentication.

    Please check with your DB admin.

    Regards,



  • 5.  RE: Apache 404 , resource not found error

    Posted Apr 09, 2015 09:51 AM

    The issue resolved,

    I had to change the DB password on the application server Using a Tool called DBpasswordchanger in Command prompt

    And a services restart started the connection.