I have been following the directions https://kc.mcafee.com/corporate/index?page=content&id=KB68427, but it is not working.
I need to move the current ePO 4.5 SQL Express DB to a remote SQL 2005 Enterprise Edition server.
Any ideas or suggestions?
Thanks in advance.
First when I test the connection it fails.
Second the directions in the KB article are not correct, because in step 6 it is not possible because step 1 has you turn off all the services for ePO:
Step 6 - Open the Configure Database Settings page and change the servername entry to the new SQL server
It should be pretty straight forward, we are using all the default ports.
Does the SQL service need to be stopped/disabled since we will no longer be using it on the ePO server?
Do I need to copy the ePO_<Servername>.mdf over to the new SQL server or just restore the backup to the new SQL server?
Message was edited by: jtemple on 4/8/10 6:10:17 PM CDTMessage was edited by: jtemple on 4/8/10 6:10:37 PM CDT
Thanks for that - I'll get the article modified.
You don't need to copy the mdf over - all that should be necessary is to restore the backup to the new server. Then start the ePO services again - at this point ePO is still running on the original DB - and then use the config page as described in the article to point to the new server.
Thanks for the information, but I am still getting "Test filed: Unable to get the information from SQL Server: <Database server name>.
This is from the database connection test.
We are using the default SQL TCP port 1433.
I'm not near my test systems at the moment so this is all off the top of my head...
Check cliconfig on the ePO server and ensure that TCP/IP is enabled and that the port is correct
Is the new SQL server a named instance? If so make sure that the details in ePO's config window are specified as <SQLservername>\<instancename>
Can you log in to the new SQL server from the ePO server via OSQL or the SQL management studio?
This is going to be difficult for us to determine because we don't know what the correct connection information for your SQL server should be.
Here are some common reaons for this to fail:
* DNS is not working from the ePO server to whatever the new SQL server is
* The instance name has changed an you need to specifiy the new instance name
* SQL is not listening on the port you think it is. Run "netstat -anb > output.txt" on your sql server and confirm SQL is listening on the right port
* The account you are specifying does not have the required permissions on the new SQL server or the password has changed
* The required protocols for EPO are not enabled on the SQL server (Must have TCP/IP and Shared Memory protocols enabled)
You can try testing the connection outside of EPO to verify the information you are providing ePO is accurate. For example try to make an OSQL connection to the DB:
OSQL -E -S<Server name>\<Instance name>,<Port> -d<Database name>
or if you are using SQL authentication:
OSQL -U <account name> -S<Server name>\<Instance name>,<Port> -d<Database name>
From the above lets suppose you have the following information:
Instance name: Instance
Database name: ePO4_Server
Account name: sa
Then the correct OSQL connection for SQL authentication would be:
OSQL -U sa -SServer\Instance,1433 -dePO4_Server
The correct OSQL connection with the same info for NT Authentication would be:
OSQL -E -SServer\Instance,1433 -dePO4_Server
* note the above switches are case sensitive so "-D" is not the same as "-d"
* for NT authentication "-E" assumes the account you are currently logged on with has the required permissions.