cancel
Showing results for 
Search instead for 
Did you mean: 

I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

A server has been running Protection Pilot 1.5.0 for ages. Last week, I was given the task to install the current ePolicy Orchestrator. After reading the manual, and seeing that there was no upgrade path to 4.5.0 from Protection Pilot, I opted for a 2 stage upgrade.

I first of all upgraded to ePolicy Orchestrator 3.6.1 - that went through without any hitches.

Now however, I cannot seem to upgrade to 4.5.0. Initially, the problem was that I needed a newer version of SQL/MSDE than was already installed, so I installed SQL Server 2008 Express. The 4.5.0 installer now sees that all required components are installed.

However, the installer seems to be trying to upgrade the old Protection Pilot database, and I get the following error, which I am hoping someone can help me get past?

SERVERNAME\PROTECTIONPILOT (is the shown in the"Database Server" dropdown - but the dropdown is greyed out and nothing can be selected)

The database instance you specified does not meet the minimum requirements.

The minimum requirements are as follows:

-MSDE 2005 or later

-SQL Server 2005 Standard or Enterprise or later

1 Solution

Accepted Solutions
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 8

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

I'm guessing that the old PP database (which is now the ePO 3.6.1 db, after the upgrade) is running on an instance of MSDE, which is effectively SQL 2000 which ePO 4.5 does not support.

I'd recommend the following:

1) Remove the SQL2008 Express instance and install an instance of SQL2005 Express

2) Move the ePO 3.6.1 database from the MSDE to the 2005 Express instance - ensure that ePO 361 works correctly before proceeding

3) The 4.5 upgrade should now be successful as 4.5 supports SQL2005 Express.

Regards -

Joe

7 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 8

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

I'm guessing that the old PP database (which is now the ePO 3.6.1 db, after the upgrade) is running on an instance of MSDE, which is effectively SQL 2000 which ePO 4.5 does not support.

I'd recommend the following:

1) Remove the SQL2008 Express instance and install an instance of SQL2005 Express

2) Move the ePO 3.6.1 database from the MSDE to the 2005 Express instance - ensure that ePO 361 works correctly before proceeding

3) The 4.5 upgrade should now be successful as 4.5 supports SQL2005 Express.

Regards -

Joe

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

Hi Joe,

Thanks for your reply. Can I just ask though if you could possibly point me in the right direction for migrating from MSDE to SQL? It's not something that I have done before.

Many thanks

Chris

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 8

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

As you've most likely got MSDE, you won't have access to the GUI tools that make life easier   Therefore I'd recommend you proceed as follows:

1) Create a backup of the epo 361 db, using the instructions in KB 59562

2) Install SQL2005 Express

3) Download and install the SQL 2005 Management Studio Express from here  - this makes life easier

4) Use the management studio to restore the backup to the new instance - this is all in the management studio docs

5) Then use cfgnaims.exe (in the ePO 261 folder) to point the ePO 361 server to the new SQL2005 express instance

HTH -

Regards,

Joe

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

Joe,

I'm getting very close now thanks - the final hurdle now, is when I try to install ePO 4.5.0, I get an error saying "The SQL server TCP port does not match the selected Database Server. Correct the problem and try again."

Right enough, the server that I created TUC\EPOLICY didn't have TCP enabled - so I have enabled this in SQL Server Configuration Manager. This has not however, cured the problem.

Thanks

Chris

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 8

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

I think I know what's happening here - let me have a play with it and I'll get back to you.

Regards -

Joe

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

Hi Joe

I found the final answer lied with the "DataSource" line of the server.ini file in the DB folder of the old ePO 3.6.1. Since I have modified that, and restarted the 4.5.0 install, it has installed fully this time.

I can't thank you enough for your help :-)

Chris

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 8 of 8

Re: I am having trouble upgrading to ePolicy Orchestrator 4.5.0

Jump to solution

You beat me to it

Glad it's all OK now -

Regards,

Joe