You might have a named instance installed. You will need to launch the SQL Server Configuration manager to see if anything other than the default MSSQLSERVER instance is listed. If that is the case, you will need to point ePO to that instance (e.g. SERVERNAME\Instancename).
In SQL Server Configuration Manager, there are SQL Server 2005 Services, SQL Server 2005 Network Configuration, and a SQL Native Client Configuration. When I highlight the SQL Server 2005 Services.....there is a SQL Server(SQLEXPRESS) and a SQL Server Browser.
I do not believe there is any tie with the epo_EDISON in here....only in the SQL Server Management Studio Express....
Is that my problem?
It looks like you do have a named instance. When you specify the SQL server, try specifying it as EDISON\SQLEXPRESS.
I'm a real newbie here...sorry. Where(what folder) would I go to change the path to specify the SQL server? In the ePO console?
Actually this may be a mit more difficult than I anticipated. The problem is that it appears you may have installed SQL 2005 Express as a named instance, whil the ePO DB is still on the default instance of MSDE. The options you would have (if this truely is the case) are:
1. Backup the DB from MSDE and restore it to the SQL 2005 instance and point ePO 3.6.1 there and begin the upgrade.
2. Upgrade the default MSDE instance to SQL 2005 Express (make sure to backup the ePO DB before doing this just to be sure)
Here are some articles that may haelp with this:
Upgrading MSDE to SQL 2005 Express
Migrating ePO 3.6.1 and usage of CfgNaims.exe
Thanks for really looking into this Greg. I got it resolved now. =)
I had to detach the .mdf and copy it over to the new SQL 2005 folder and then add it to the new instance in Studio Express. Then open Cfgnaims.exe and change the settings there. Now I should be ready to upgrade to epo 4.5. Thanks for your inputs Greg. Much appreciated.