error upgrading SQL server from 2005  -- 2012

SiemensSEN
SiemensSEN used Ask the Experts™
on
Hello,
  I get the following error when I tried to upgrade my SQLserver . Please let me know how i can fix this issue.

=== Error 1 ==
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------

The following error has occurred:

The specified local group already exists. (Exception from HRESULT: 0x80070563)

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------

The following error has occurred:

The directory property cannot be found in the cache.


Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xED20C17F%25400x02C5AE77

--ERROR 2 -- I selected retry after error 1

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xED20C17F%25400x02C5AE77

---------------------------------------------------------------
After pressing cancel button I see a dialog that with fail status for the database

I attach the log. Please have a look . The link provided in message does not work..

Thanks
msssql.err.txt
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017

Commented:
Why not install it as a new instance (if you require it to be the default instance, an option is to add another IP to the system and bind the 2012 instance to this IP.
Once the DB is installed, you can use login transfer scripts that exist on MS and then backup/restore the DBs one application at a time, while transitioning the applications to point to the new sql 2012.

The issue will provide for a controlled transition as well as provide for a way to revert if some incompatibilities are encountered.

Presumably you used this prior to initiating the upgrade attempt.
http://technet.microsoft.com/en-us/library/ms144256.aspx

Yes, you would need to have adequate space to handle both for a time.

Once the DB/application transition is done, you can rescind the binding of sql 2012 to the single IP.
....

Author

Commented:
Sorry but I cannot do an in-plae upgrade. Do you know what the error means or how to fix it. The link on how to resolve the issue that is displayed by the installation is not valid.

Thanks for your help
Arnold is right, if you don't want to do an in-place upgrade, then you have to install the new SQL Server as a "named instance".
The error message is telling you exactly the same; you can't have two default instances running on the same server.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Sorry again..

I have SqlServer 2005 install in thia machine  and I want to upgrade it . So, I am doing an in-place upgrade  and then I get the error.
I ran the upgrade advisior and it gave no error.

Thanks
Ah I see. There are a number of different reasons that may cause the error message you're getting. To further investigate go to the registry
"HKEY_LOCAL_MACHINE > Software > Microsoft > Windows > Currentversion > Run" to find which file is the error message referring to. You can then decide on the action that you need to take based on that info.

Author

Commented:
Thanks for your help

no value  is set in registry.


I de-install using the information in the help text

C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012>setup /q
 /action=uninstall /instanceid=CQ2005 /features=SQLENGINE,FULLTEXT,REPLICATION,A
S


And re-install and got this error below..

Also, Although  i remove the installation the information for SQLserver 2012 is still in add/remove dialog


TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------

The following error has occurred:

The directory property cannot be found in the cache.


Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xED20C17F%25400x02C5AE77

------------------------------
BUTTONS:

&Retry
Cancel
------------------------------
I can't be sure without actually looking at the server but it looks like the installation process has bumped into some missing packages or modules and is trying to add them back from the original source media, which obviously may not be accessible anymore...
but you can fix it and it's not as daunting as it may sound.

First locate the directory containing FindSQLInstalls.vbs and open up an elevated command prompt to that directory and run the following command:
Cscript FindSQLInstalls.vbs %computername%_sql_install_details.txt

Then open up the text file that you've just created and search for "!!!" and "do not".
Based on the info you have to take corrective action to resolve all items found in the previous step, one issue at a time. You have to repeat the process until there are no "!!!" or "do not" in that file.

Author

Commented:
Sorry but I could not get it to  work.  I may have remove entries from the registry that cause this issue.

So, I reinstall the server and SQL server 2005 then upgraded to 2012 .  I saw no error . However,  in windows add/remove dialog I still see an entry for "Microsoft SQL server 2005(64) with no size or version associated with it.  Is this normal? . How do I remove it.
I wouldn't worry about that residual entry; SQL Server 2005 setup had some issues preventing users from a clean uninstall. If you want you can get rid of it hy tidying up the registry manually - not recommended though, because it's not worth the time and effort required, let alone the potential risks involved. The important thing is you're on 2012 now! With all the new features and the enhanced stabilityand productivity of the SQL Server 2012 there so much more you can achieve rather than spending your time cleaning up old registry entries.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial