after upgrading from EPOS v4 to EPOS v4.5 am getting the following error when i lunch the ePolicy Orchestrator 4.5.0 Console:
"" The license for ePolicy Orchestrator is invalid ""
license is valid am sure.
This can be caused by ePO being unable to communicate with the database. If you check the epoapsrv.log and orion.log, are there any relevant errors?
I have checked the orion.log there is nothing related to the SQL Server DB, then the SQL server is UP.
mainly there is one error only:
[http-8443-Processor25] realm.JAASRealm - Login exception authenticating username "admin"
javax.security.auth.login.LoginException: Product "ePolicy Orchestrator" does not have a valid license!
Can you restart the three ePO services, wait until you can try and log in again, and (assuming it fails again) post the epoapsrv and orion logs?
I ran into the same problem during a fresh install with a new DB and was also told that the error message is a sign of the ePO being unable to authenticate the database. My issue was a combination of problems but I couldn't get myself out of the corner I was painted into. I finally gave up and performed a complete uninstall/reinstall of the ePO using a different set of credentials for the DB which fixed it. My understanding was that McAfee was working to make the error message more intuitive in the future. Are you running v4.5 or v4.5 Patch 1? If you have patch 1, it will be disappointing to learn that the error message hasn't been changed to something that makes a bit more sense. I apologize that I'm probably not being much help... Since you upgraded, playing with credentials and uninstalling/reinstalling probably isn't much of an option. Here is the thread I worked from when attempting to resolve the issue I encountered:
what do you think if i uninstalled the EPO, reinsall it as Evaluation and later on i added the License key?
I'm far from an ePO expert, so it's difficult for me to say. If your ePO v4.5 install is an upgrade from v4, my concern would be what effect the uninstall of v4.5 would have upon your DB. I don't know what DB differences there are between v4 and v4.5. If the ePO at v4.5 is truly unable to connect to the DB at this point, then maybe it doesn't matter because no changes have been made. ...That's where our installation roads are different... I performed a parallel "upgrade" from v3.5 to v4.5 with a new ePO server and a fresh DB. Again, I'm sorry I'm not being much help. If you're confident in your DB backup and ability to piece ePO v4 back together, then go for it. If not, and if I were in your shoes, I'd open a case with support.
I already opened a case with support, they asked to check if the SQL server service is Up .
there is somthing wrong with the link : C:\WINDOWS\explorer.exe https://localhost:8443/core
(Launch McAfee ePolicy Orchestrator 4.5.0 Console)
it fails to reach to the SQL DB.
Message was edited by: Yasin Yasin on 1/13/10 12:34:28 AM CST
Okay, this error:
2010-01-12 07:42:46,375 ERROR [http-8443-Processor24] auth.OrionUser - OrionUser: invalid auth type:pwd
means that ePO doesn't know how to authenticate the user, which is comparatively serious. You have a case open already, which is good - I would imagine that the technician handling the case will need to see a copy of your database.