Install Sql Server 2008 R2 In Windows 7

Virag nirmalkar 8-May-14 6:06 8-May-14 6:06 Any body can help me plz,While trying to install Sql Server 2008 in my windows 7 64-bit OS, it show Restart computer as failed. I have restarted my computer and still it shows the same error. I also refer the path 'HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Session Manager' but Can't see any 'PendingFileRenameOperation' in folder, nothing is present inside it,only default file is present. Please advice on how to shortout this problem to install SqlServer 2008. MiBeloved 27-Jun-12 13:53 27-Jun-12 13:53 I read your post about the installation of SQL server 2008. I just reinstalled the same but the R2 Developer disc.

I am always getting stuck at the point of connecting after installation and presently got the message below. I am new to this and would appreciate any help.

Install Sql Server 2008 R2 In Windows 7

I installed it as per instructions in the Microsoft SQL 2008 book by Mike Hotek. Could you look at the error message and give some advice on what to do. I disabled the firewall while installing it and has just turned it back on, Here is the error message: Cannot connect to MIBELOVED-PC SQLEXPRESS.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. I used mixed mode problem is that i am new at this, just got on to it after learning a little php so I am not expert at any of it I opened the server config manage and with the SQL Server Services highlighted on the left, everything on the right ( 7 items) all read running. I do not know if I connected the server to the management studio. I may have but I am not familiar with these processes.

Thanks for your interest I actually spend days following various suggestions on how to fix this on the internet but nothing seems to work, keep getting that message. This is the summary file after I ran the repair from the original software disc. I cannot send the detail file because it is a long file but I could send it by another means if you suppy an email address, because this box seems to freeze up when I copied and pasted the detailed file. Here is the summary file: Overall summary: Final result: Failed: see details below Exit code (Decimal): - Exit facility code: 1211 Exit error code: 1 Exit message: Failed: see details below Start time: 2012-06-29 20:50:03 End time: 2012-06-29 21:16:18 Requested action: Repair Log with failure: C: Program Files Microsoft SQL Server 100 Setup Bootstrap Log 20146 Detail. Txt Exception help link: http%3a%2f%2fgo. 1600.1%26EvtType%3d0x0AADD6DA%400xDC80C325 Machine Properties: Machine name: MIBELOVED-PC Machine processor count: 2 OS version: Windows 7 OS service pack: Service Pack 1 OS region: United States OS language: English (United States) OS architecture: x64 Process architecture: 64 Bit OS clustered: No Product features discovered: Product Instance Instance ID Feature Language Edition Version Clustered Sql Server 2008 R2 MSSQLSERVER MSSQL1050. MSSQLSERVER Database Engine Services 1033 Developer Edition 10.

0 No Sql Server 2008 R2 MSSQLSERVER MSSQL1050. MSSQLSERVER SQL Server Replication 1033 Developer Edition 10. 0 No Sql Server 2008 R2 MSSQLSERVER MSSQL1050. MSSQLSERVER Full-Text Search 1033 Developer Edition 10. 1 No Sql Server 2008 R2 MSSQLSERVER MSAS1050. MSSQLSERVER Analysis Services 1033 Developer Edition 10. 0 No Sql Server 2008 R2 MSSQLSERVER MSRS1050.

MSSQLSERVER Reporting Services 1033 Developer Edition 10. 0 No Sql Server 2008 R2 Management Tools - Basic 1033 Developer Edition 10. 0 No Sql Server 2008 R2 Management Tools - Complete 1033 Developer Edition 10.

0 No Sql Server 2008 R2 Client Tools Connectivity 1033 Developer Edition 10. 0 No Sql Server 2008 R2 Client Tools Backwards Compatibility 1033 Developer Edition 10. 0 No Sql Server 2008 R2 Client Tools SDK 1033 Developer Edition 10. 0 No Sql Server 2008 R2 Integration Services 1033 Developer Edition 10. 0 No Package properties: Description: SQL Server Database Services 2008 R2 ProductName: SQL Server 2008 R2 Type: RTM Version: 10 SPLevel: 0 Installation location: D: x64 setup Installation edition: DEVELOPER User Input Settings: ACTION: Repair AGTDOMAINGROUP: AGTSVCACCOUNT:. SQL2008SBSSQLAgent AGTSVCPASSWORD:.

AGTSVCSTARTUPTYPE: Automatic ASCONFIGDIR: Config ASDOMAINGROUP: ASSVCACCOUNT: ASSVCPASSWORD:. CONFIGURATIONFILE: C: Program Files Microsoft SQL Server 100 Setup Bootstrap Log 20146 ConfigurationFile.

Ini ENU: True FAILOVERCLUSTERGROUP: FAILOVERCLUSTERNETWORKNAME: FARMACCOUNT: FARMADMINPORT: 0 FARMPASSWORD:. FTSVCACCOUNT: NT AUTHORITY LOCAL SERVICE FTSVCPASSWORD:. HELP: False IACCEPTSQLSERVERLICENSETERMS: False INDICATEPROGRESS: False INSTANCENAME: MSSQLSERVER ISSVCACCOUNT: NT AUTHORITY NetworkService ISSVCPASSWORD:.

ISSVCSTARTUPTYPE: Automatic PASSPHRASE:. QUIET: False QUIETSIMPLE: False SQLDOMAINGROUP: SQLSVCACCOUNT: SQLSVCPASSWORD:.

UIMODE: Normal X86: False Configuration file: C: Program Files Microsoft SQL Server 100 Setup Bootstrap Log 20146 ConfigurationFile. Ini Detailed results: Feature: Database Engine Services Status: Failed: see logs for details MSI status: Passed Configuration status: Failed: see details below Configuration error code: 0xDC80C325 Configuration error description: The name has already been shared Configuration log: C: Program Files Microsoft SQL Server 100 Setup Bootstrap Log 20146 Detail. Txt Configuration status: Failed: see details below Configuration error code: 0x30E@1 Configuration error description: Service 'SQLSERVERAGENT' stop request failed. Configuration log: C: Program Files Microsoft SQL Server 100 Setup Bootstrap Log 20146 Detail.

It’s more common than you would expect to have SQL Server installed on your machine without knowing the exact version or edition. With tools and applications installing SQL Server behind the scenes, you may have unknowingly installed SQL Server. In this post, I’ll try to quickly explain some easy ways to investigate this question. This will include:. Using the Programs and Features control panel tool. Understanding and viewing SQL Server instances.

SELECT @@VERSION If you’d rather watch the techniques, here is a quick: Control Panel One well-known way of investigating installed versions is the Programs and Features control panel tool (which used to be Add/Remove Programs). In Windows 7, an easy way to get there is to type “Programs and Features” in the search box on the start menu like this: Your intent here is not necessarily to uninstall anything (although you could). Instead look through the list of installed programs for programs named “Microsoft SQL Server”. For example, in my list I see around ten items that start “Microsoft SQL Server 2008 R2”. Note that it is possible to have multiple versions of SQL Server installled at the same time, so you could also see “Microsoft SQL Server 2005” in the same list.

SQL Server Instances Even though the control panel is easy and well-known, it doesn’t really tell the whole story well. In order to really understand what versions of SQL Server are installed, you have to understand SQL Server Instances. Each instance of SQL Server operates independently and contains its own collection of databases and settings. There are two types of instances: Default Instance a single instance named MSSQLSERVER. You connect to this instance using only the server name (ex: localhost) Named Instance one or more instances. You connect to these instances uing the server name + instance name (ex: localhost SQLEXPRESS) It’s possible have only one instance installed on your machine. But it’s also possible to have many instances.

And each of those instances could be a different version of SQL Server! To understand your scenario, use the SQL Server Configuration Manager tool that installs with both SQL Server 2005 and 2008. On the start menu, expand the “Microsoft SQL Server YOURVERSION” menu, and then expand the “Configuration Tools” submenu. Launch the SQL Server Configuration Manager tool. Here is a screen shot to use as an example: In this example, I clicked on “SQL Server Services” in the left pane. The right pane shows the different services installed on my machine.

The ones that we’re interested in are the ones that have “SQL Server” in the Service Type column. You’ll notice that there are two rows with this distinction that are highlighted here. The instance name is listed in parantheses in the first column. In this case there are two instances:. MSSQLSERVER: the default instance. SQLEXPRESS: a named instance, which is the default name of the SQL Server Express instance. Each instance shows that it is running in its own process.

This is useful to know, but the important step is determining the version. To do this, right-click on the instance, and then click Properties. In the Properties dialog, select the Advanced tab. Scroll down to the Version row. Here is what it looks like for the MSSQLSERVER instance on my machine: The version number for this instance is.1. In order to translate this, you could search for that version number on the internet.

There are several resources that have compiled a list of SQL Server version numbers for you. Here is one example: Resources like this tell me that my default instance is SQL Server 2008 R2 RTM. The other great thing about a version database is that you might find that you’re not using the latest release. For example, I don’t have any of the post-RTM updates installed on my machine. One final note is that you can see the “Stock Keeping Unit Name” which is a strange way of calling out the edition. In this case my default instance is the “Developer Edition” of SQL Server 2008 R2. The SQLEXPRESS instance on my machine says “Express Edition with Advanced Services”.

Sometimes capabilities require a specific edition of SQL Server, so this is sometimes as important as the version information. SELECT @@VERSION I think looking at SQL Server Configuration Manager is the best way to truly understand what is on your machine. But there is an easier way if you already know your instances. You can run a simple query. Here’s how:. On the Start Menu, go to All Programs, Microsoft SQL Server YOURVERSION. Launch SQL Server Management Studio.

When the Connect to Server dialog appears, log onto the SQL Server Instance of interest. For example, if you’re on the local machine, you can use localhost or localhost SQLEXPRESS in the Server name text box. Instances were discussed in the previous section of this post. Make sure that the Server type is set to “Database Engine”. Click on the New Query button on the toolbar. In the query window, type the following query: SELECT @@VERSION. Press the Execute button to run the query.

Look at the version text in the Results window. On my machine, for the LOCALHOST SQLEXPRESS instance, this is the version information from this query: Microsoft SQL Server 2008 R2 (RTM) –.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Express Edition with Advanced Services (64-bit) on Windows NT 6.1 (Build 7600: ) (Hypervisor) This is perhaps the easiest way of detecting the version of whatever SQL Server instance you’re connected to. But you can see why I covered the control panel and instances first. If you don’t even know what instances are on your machine, you won’t know how to connect to them to run this query in SQL Server Management Studio! One final note, it is possible to have SQL Server installed on your machine without SQL Server Management Studio. If that is the case, you can still use the previous methods for determining your version, but you’d have to install the SQL Server Management Tools to run a query. This will most likely be covered in a later post.

Other resources on this topic:. (SQL Server Curry Blog). (SQLAuthority Blog). (Microsoft Support). (Transact-SQL MSDN Documentation).

The default instance is a selection on one of the setup pages. If you’re installing SQL Server Express, then “Named Instance” is automatically selected with a a named instance of “SQLEXPRESS”. But you can change this to a default instance, even for express. If you’re installing another edition, than the default instance radio button is the selection unless you already have a default instance installed. But note that SQL Server Configuration manager will tell you whether you have a default instance.

It will show a SQL Server service type with the name (MSSQLSERVER) next to it. Hope this helps. If that’s the case, then you can use the workaround at that link and you should be able to get your default instance up and running.

I had a free machine (Windows Server 2008 32bit), and I tested installing a default instance of EXPRESS (SQL Server 2008 R2 Express). It worked for me. I wonder if this has been fixed or if there are more variables going on to reproduce it. Regardless, I hope you can now either: a) Use the named SQLEXPRESS instance it installed for you, b) use the work around to create a new named instance named MSSQLSERVER as your link suggests to work around the problem and create the default instance explicitly. Usually when you’re asked to browse to the SQL Server “media”, it means that you installed once but now when you’re trying to add features (or remove), it can’t find the setup program to complete those actions. I think I’ve seen this before if I installed it over a network share.

I see your other comment too. I think that is the best route of trying to install it again from the internet download. Unfortunately, you seem to be having problems doing that too.

I’ve installed on Windows 7 many times. Did you make sure to pick the right platform (32bit or 64bit) for your machine? There is a service pack 1 for Windows 7 that you could make sure you’ve installed (I don’t think it is necessary though). From the Start menu, go to or search for “Run”, and from the Run dialog, type winver, and press enter. It should tell you whether you have SP1 installed or not.

Finally, if you’re installing the package with.just. management studio, I would suggest trying to install the package that has the Database Engine + Tools (i.e. Management Studio). Hopefully one of these suggestions helps. HI, my problem isi installed version of microsoft sql server 2008 enterprise edition on my pc.

Happily am working on that. But, when i am attaching sample data base, its giving the following error.

—————— An exception occurred while executing the T-sql statement or batch. The database ‘adventureworks’ cannot be opened beacuse it is a version 655.this server support version 654 or earlier. A downgrade path is not supported.

Could not oened new database ‘Adventureworks2008’.create database is aborted ——————————————————— I am new to SQL.Can any one pls give the solution. Good Afternoon, I am currently trying to silently install / package software. The software i am trying to install also installs SQL Express 2008 in the background and configures it for use with the software. I am now trying to break these installs down and package them individually. Is there anyway to capture the current SQL 2008 settings and deploy them as a configuration file? Just to make clear the current install of sql is packaged behind an install and i have no clue as to how its configuring it.

I can only go in to SQL after install and see its configuration. Hope you can help??? Hi, In my configuration manager i have mssqlserver instance,no more instances. When i installing sql server i gave server name ‘.’ and using sql server authentication. But when i connecting to my database it gives error Error:The TCP/IP connection to the host., port 1433 has failed. Error: “null. Verify the connection properties.

Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.”. Is this error because of missing another instance like ‘sqlexpress’?Help me pls.