April 15, 2011 at 3:35 am
Hello, I'm a new user and now I'm slowly switching to Vb.NET, although I have many customers who still have projects in VB6.
I need to install on my notebook with Windows 7 64bit Home Premium on Sql Server 2008 R2 Enterprise.
When I install I get the following error:
"Hive of the registry on the performance counter damaged. To continue, you must restore the hive. For more information, see http://support.microsoft.com/kb/300956.
I already tried to follow Microsoft's help, but nothing.
I tried to run it through "C: \ Users \ SAMSUNG \ Desktop \ SQLServer08/setup.exe / ACTION = install / SKIPRULES PerfMonCounterNotCorruptedCheck =" (found at other links) (bypassing the role that practically running it by mistake), but nothing done even with that. The installation part of me and then I go ahead but by a series of mistakes and not everything m'installa.
Can someone help me if maybe he has already installed on Win7 ?....
Thanks,
ptcom
April 15, 2011 at 3:40 am
Why are you installing Enterprise edition? Are you aware that you will have to license that, as per the enterprise edition costs (and they are not cheap)?
Developer edition installs fine on Win 7 Ultimate, not sure about Home Premium
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2011 at 3:46 am
I seem to remember most of the 6 month trial's of SQL Server are the Enterprise Edition.
Not sure if this link may help:
April 15, 2011 at 3:50 am
HowardW (4/15/2011)
I seem to remember most of the 6 month trial's of SQL Server are the Enterprise Edition.
Under the covers, yes, but they are called Evaluation Edition. Evaluation edition should install on Win 7 as well. Enterprise normally requires server operating systems.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2011 at 3:54 am
Sorry, just realised that you've already looked at the KB I posted. It's actually not applicable to Windows 7 - there's an MS blog here detailing how to repair these for Windows 7:
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply