This content has been marked as final. Show 6 replies
I'm also having that error with the newest patch 3.
And its not related with SQL tcp/ip settings (like stated on a few mcafee kb articles).
Going to try to check for more solutions.
Hi guys this is my first post but I found that because my SQL user account had a complex password it gave an error and would not install. So keep the password short and simple for the installation and then change it to a complex password afterwards. I also found that the log files didn't really say anything much regarding SQL being the problem.
Let me know if you fix the problem.
On thing that I had to do and resolved the patch installation problem (2 & 3) was to set the ePO DB connection account to SA (SQL Admin), with no domain, and simple SA password (also set on the SQL server). This is configurable on the ePO config page.
After successful patch install, I revert back to AD authentication with a stronger password, etc.
How did you do this? I'm getting the same error trying to apply patch 2. I noticed in the installation instructions that it said to logon the server as a local administrator but that made no difference.
You will have to go to
from there, you can change the database login credentials. For patching, I need to use SA as the username, leave domain empty and of course supply the SA password.
Thanks happy I'll give it a go in the morning grin