An Error Occurred Connecting To The Database Epo
Contents |
Support Home © 2003-2016 McAfee, Inc.
Support Home © 2003-2016 McAfee, Inc.
Focus — ProTips: More Product Info, More Frequently ePO Technical Briefs Troubleshooting Database Error While Getting ePO License Information When logging into the ePO web console, users http://www.mcafee.com/us/microsites/sns-jnl/2014-11-epo-jnl.html sometimes encounter a message reading: "A database error occurred while getting license information. https://answers.atlassian.com/questions/23561/getting-network-error-ioexception-connection-refused-during-jira-db-configuation Make sure your database server is currently running." Issues with verification, the server, or the environment could be the culprit. Verification issue. When ePO starts up, a licensing check is performed against the license entry in the database. If the license in the database can't be verified, users may need error occurred to manually enter a valid license. ePO server issue. An ePO registry configuration tells Tomcat where to read the database configuration file "db. properties." If this registry value is pointed to a file short name that is incorrect or does not exist, Tomcat will fail to find the database configuration file. This will cause a database connection failure resulting in a failure to retrieve to the database the license. See KB76582 — The license for ePolicy Orchestrator is invalid (When accessing the ePO 4.5/4.6 console page) for more information and specific steps on how to troubleshoot these issues. Environment issues. Several system settings or size restrictions could be causing connection issues. ● Network connection to database. Make sure your SQL Server (Instance Name) service is running. Can you telnet from ePO to the SQL server using the port configured by the Instance? A great way to test the connection outside of any McAfee process to determine if the issue is with the software itself or the environment is to use a UDL file per KB70929 — Steps for testing SQL database connectivity using test.udl file. ● Authentication to database. To test authentication to the database on the ePO server, open a browser and navigate to https://localhost:8443/core/config. Enter your credentials and hit the "Test Connection" button. If you feel an authentication error in core/config is incorrect, you can also use the UDL file per KB70929. Please note if you are using an NT account to authenticate to the database, you must be logged into the se
is Oct 10 - 13 in San Jose, CA – Register soon before tickets sell out. Linked ApplicationsLoading… Quick Search Help About Confluence Log in Sign up QuestionsTopicsLeaderboardRewardsGetting "Network error IOException: Connection refused" During Jira DB configuation10-1Ben SDec 02, 2011 · Trying to connect to mssql server 2008 database in Jira o Created new database o Created new login/user with db_owner permissions on new database o Used config.bat for config § Entered ‘localhost’ (no quotes) for hostname § Database, username & password § Port 1433 § Schema: blank o When i test connection I get ‘Could not connect to the DB: Network error IOException: Connection refused: connect’ o I’ve checked that the default port on sql server is 1433 and that it’s a static port. o Firewall: it is on (but i tried testing the connection w/the firewall down and still got this error message) I’ve checked the schema and collation type are correct, tcp/ip is enabled and mssql jtds driver is present and working. I also confirmed that the authorization is sql server and windows auth. Any suggestions as to what to try next?jirajira-configurationdatabase-connectionCommentCommentAdd your comment...3 answers432Thomas LennigerMay 12, 2014Its an issue of the dynamic port. Goto Windows-Start->Programs->Microsoft SQL Server 20xx->Configuration Tools->SQL-ServerConfiguration-Manager After starting this Configuration Tool go to SQL-Server-Network-config.-> protocols for [instance name] Open TCP/IP at right site Choose IP-Adresses above. Scroll down to IPAll Insert in the field for TCP-Port your port 1433 Restart SQL-Server service. u can check if your server is now listening on port 1433 with queries use master sp_ReadErrorLog --(sql server 2012) --or Xp_readerrorlog --(sql server 2008 and below) in the result you should read something like Server is listening on [ 'any'