Adding instance to SQL Server 2008 R2 on SBS 2011 Standard

I need to add an instance to my SQL Server 2008 R2 that is part of Small Business Server 2011 Standard operating system. When I click on "New SQL Server stand-alone installation or add features to an existing installation" I get another pop up
window asking for SQL Server 2008 Installation Media. Where can I find this installation media?

Hi BruceR80,
According to your description, SQL Server installation center asks for SQL Server 2008 installation media and you don't know where to find it. This could happen when the temporary folder to which the installation file is extracted doesn't exist. You could
follow the steps below to troubleshoot the issue.
1.In Microsoft Download Center, download the SQL Server 2008 installation file to your local drive and click the file, you will see that the file will be extracted to a temporary folder. Please make a note of what directory it is extracted to. For example,
it could be in c:\ followed by a folder name which will be a set of random letters and numbers "fd7667bgbb33gg2g".
2.Copy that temporary folder to your desktop and close the SQL Server Installation Center window.
3.Reopen SQL Server Installation Center. Click on the installation tab and install. When it asks for SQL Server 2008 installation media, browse to the instillation media folder(that temporary folder) which is copied to your desktop and continue the installation
process.
There are two similar articles for your reference:
http://forum.winhost.com/threads/ms-server-management-studio-cant-find-installation-media.3432/
https://coastalcoder.wordpress.com/2012/12/03/browse-for-sql-server-2008-r2-installation-media/
Regards,
Michelle Li

Similar Messages

Is it possible to have two or more virtual machines point to a shared instance of SQL Server 2008 R2 for systems administration?

Hello All,
I am the Systems Admin for a production box running SQL Server 2008 R2. I have been ask to do the following and and trying to figure out if it's even possible.
1. The Production Server is named ProductionA
2. Create 3 Administrator accounts on ProductionA each with access to the SQL Server instance on ProductionA. Use Standard SQL Server login for credentials. i.e. Username/Password and assign the role sysadmin.
3. Install 3 Virtual Machines on ProductionA each with Windows 2008 R2 64 bit operating system.
4. For each Virtual Machine, Install SQL Management Studio and write down the IP Address assigned to each VM.
5. Using Remote Desktop Connection, connect to each virtual machine to be able to manage the SQL Server.
Is this possible? And, why am i doing it? Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box
to manage the SQL Server, I figure why not create a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sudden Server Infrastructure Licensing errors SBS 2011 Standard install (10 months old)

The following errors began about a month ago and I can't figure out how to fix it. I especially don't like that it states the server will be shut down in 22 days. When I rebooted the server last week the problem went away for exactly 24 hours
then came back and seems to report every 4 hours.
Background:
Fresh SBS 2011 install last Dec. 7th (2012).
We did have an SBS 2003 server but it was never on the same network. We simply backed up the data off of its data drive. Exchange was backed up via OST to PST conversion then imported in. Only 10 - 12 users.
HP ProLiant server and the SBS 2011 DVDs were OEM supplied by HP but we installed NOT pre-installed.
Thx,
D
Server Infrastructure Licensing
38 10/8/2013 2:47:03 AM
18
Event Details:
The Root Domain Check detected a condition in your environment that is out of compliance with the licensing policy. This server will be automatically shut down if the issue is not corrected in 22 day(s) 8 hour(s) 0 minute(s). Please look for additional events
for Root Domain Check to troubleshoot.
Server Infrastructure Licensing 2
10/8/2013 2:47:03 AM 12
Event Details:
The Forest Trust Check in the Licensing component did not pass because error 0x80070008 occurred in function fe1 [RKIQ]. Not enough storage is available to process this command. Make sure that each primary domain controller in your Active Directory forest can
be contacted and the following services are running on it: Active Directory Domain Services (NTDS), DNS Server (DNS) and Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected.
Server Infrastructure Licensing 3
10/8/2013 2:47:03 AM 12
Event Details:
The FSMO Role Check in the Licensing component did not pass because error 0x80070008 occurred in function f2 [KRTC]. Not enough storage is available to process this command. Make sure that your DNS server can be contacted and the following services are running:
Active Directory Domain Services (NTDS), DNS Server (DNS), Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected.
Server Infrastructure Licensing 50
10/8/2013 2:47:03 AM 6
Event Details:
Root domain check did not pass because error 0x80070008 occurred in function f1980 [QJTA]. Not enough storage is available to process this command. Make sure that the domain that this computer is joined is reachable. This server will automatically shut down
if the issue cannot be corrected.

Not sure if it helps but I just wanted to add the following alerts emailed to me:An alert was detected on your network. Further investigation into the issue is recommended.
Computer: NESRV
Date/Time generated: 10/8/2013 2:47:03 PM
Title: Forest trust licensing error
Source: License Compliance service
Description:
The Forest Trust Check in the Licensing component did not pass because error 0x80070583 occurred in function fe1 [ZHUS].
Class does not exist.
Make sure that each primary domain controller in your Active Directory forest can be contacted and the following services are running on it: Active Directory Domain Services (NTDS), DNS Server (DNS) and Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected.
Computer: NESRV
Date/Time generated: 10/8/2013 2:47:03 PM
Title: FSMO roles licensing error
Source: License Compliance service
Description:
The FSMO Role Check in the Licensing component did not pass because error 0x80070583 occurred in function f2 [OKDF].
Class does not exist.
Make sure that your DNS server can be contacted and the following services are running: Active Directory Domain Services (NTDS), DNS Server (DNS), Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected.

"a network related or instance specific error in sql server 2008..." error in sbs 2011 standard.

Hi All,
When we try to open "Sql Server 2008 R2" in SBS 2011.......... we are getting the error message" “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. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) ”
How can we resolve the issue?
Thanks in advance.
Ram.
Ramakrishna

Hi Ram, you can check the solutions in the following links and see if that helps:
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.technet.microsoft.com/wiki/contents/articles/a-network-related-or-instance-specific-error-occurred-while-establishing-a-connection-to-sql-server.aspx
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/3a1c4d72-300c-4f9b-a0ac-23027ce04d1c/
Also, rather than a SBS specific issue, it seems only relate to SQL server, you can also post it to SQL server forum so that SQL server experts there can provide more accurate solutions:
http://social.technet.microsoft.com/Forums/en-US/category/sqlserver
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SQL Server 2008 R2 - Adding Replication Components to an Existing Installation

Hi All
I have a SQL Server 2008 R2 instance that I need to install Replication components on.
I've been going through the appropriate wizard and selecting to upgrade an existing instance, the wizard recognizes the SQL Server that we have installed so that one is selected. On the next screen, I'd expect to see the feature selector with everything
we currently have installed selected and greyed out, however nothing is selected (except for BOL).
So in order to select Replication Components, I'd have to also select Database Engine, suggesting that a new SQL Instance would be installed. Not wanting to do this, I'm having to abort.
I've tried a number of different ISOs now (one I found lying around on the server), but I haven't had any luck. My only option now seems to be to recreate the instance entirely, but that being a last resort, I was wondering if anyone may have had some experience
with this problem?
I am running the installer with the highest level of Windows and SQL access, if that helps.
Thank you

Just to confirm when you try to install you select the option "Add features to an existing Instance of SQL" and below you see the instance name and you *Dont* see replication.
Now when you click next in the feature selection page you see replication as greyed out is that correct?
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com
To confirm, the steps I'm taking are as follows:
Once all the Setup Support files have been installed, and the Setup Support rules have been checked (with no errors)
- At the Installation Type screen I select Add features to an existing instance of SQL Server 2008 R2. My server appears in the drop down as the only instance on this server. I see the list of installed instances too, and can confirm that Replication does
not appear in the Features column. I click next.
- At the Feature selection screen, the only items that are selected are Books Online, SQL Client Connectivity and Microsoft Sync Framework. No other features are selected and greyed out, where I would expect Database Engine Services, Analysis Services and
Reporting Services (among others) to be selected. Selecting SQL Server Replication at this stage results in Database Engine Services also being ticked, suggesting the wizard will add a new instance on this machine.
The only peculiarity that I've noticed is with the version number reported on the Installation Type screen, which shows 10.51.2500. Not the same as the version that is reported if I inspect object browser or I user the @@Version command. In fact, I believe
this version relates to MDS instead? This being said, our other production server reports the same version here, and I was able to install replication components here with no problem.
I hope this helps, I don't know if I can attach some images to my post to make it more clear? It's quite a difficult and unusual problem to explain!

Cannot find SQL Server 2008 instance

I have installed SQL server 2008 Developer edition on my laptop. When I open SSMS I cannot find the installed instance under the Server Name group and When I choose the Browse More option and go to Database engine, the instance name does not show up. Will
appreciate any suggestions.
Thanks
akoranteng

>>I see two instances of SQL Server 2008 when i issue the commands you suggested to me
I don't why you have two instances, may be you installed two different instances.
I think local servers list is obtained by reading the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL
Sometimes (don't know why may it is SQL browser service or something else messed up) you don't see a locally installed instance on the drop down list. Just
type in the instance name manually inside the textbox for server name and you should be able to connect

Issues installing SQL Server 2008 instance - Install fails

Hi there,
I have a server windows server 2008 R2 standard.
While doing an Enterprise to Standard downgrade, I have removed enterprise edition of SQL Server 2008, rebooted and while installing standard edition, I get the below error saying "You
SQL server 2008 installation completed with failures. Some or all identity references could not be translated"
Bit of background. This server has another express instance of SQL Server 2008. I have used local system account, network service as well as our general SQL service account, but I get the error
towards the end of the installation and it fails saying “Some or all identity references could not be translated.”
I am installing a named instance with the same name as before but fails. I have tried creating a test instance that fails too. Any ideas? I have also run the clean up utility but no joy.
Cheers
Faltaf

Hi FAltafB,
According to your description, you come across the error that some or all identity references could not be translated. Please help to post SQL Server setup error log for analysis. By default, SQL Server setup summary and detail logs located in C:\Program
Files\Microsoft SQL Server\100\Setup Bootstrap\Log.
Based on my research, this issue could be due to the incomplete uninstallation for previous installation. Another cause could be that you are installing SQL Server after your machine becomes a domain controller.
To troubleshoot the issue, please pay attention to the points below.
1. Make sure you have administrative rights on the computer, uninstall all the components related with SQL Server 2008 enterprise from the control panel and delete registry keys mentioned in the article:
http://blogs.msdn.com/b/sreekarm/archive/2010/03/15/sql-express-is-not-installed-properly-steps-to-be-taken-before-reinstall-again.aspx
2. Use
SQL Server 2008 R2 Best Practice Analyzer to detect if SQL Server is installed on a domain controller. If SQL Server is installed on a domain controller, please demote your machine from being a domain controller and install the SQL Server again since it
is not recommended to install SQL Server on a domain controller.
Regards,
Michelle Li

Service Account for SQL Server Agent on SQL Server 2008 R2

This SQL Server instance is SQL Server 2008 R2 (10.50.4000). We had Active Domain Service accounts created to run the service accounts for SQL Server and SQL Server Agent.
It has become company policy to alter the service accounts that run SQL Server and SQL Server Agent. Currently, both were running under the Local System Accounts. We have altered the SQL Server but we are having issues with the SQL Server Agent.
I am told by another DBA that
"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
So I was wondering if anyone has come across this issue and how did they resolve it.
lcerni

"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
This is completely not true. It is indeed possible to run agent as a domain account without giving it local admin. Chances are you'll need to update the local acls by adding the account to the local security groups. Please see this article for more information:
http://technet.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
Edit: In addition, it'll need rights to SQL server for that account to connect and do its work. It will need to be given sysadmin:
http://technet.microsoft.com/en-us/library/ms191543.aspx
Sean Gallardy | Blog |
Twitter

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

How to attached a sql server 2008 database on sql server 2005

Hi,
I have a backup of database designed over sql server 2008. I need to attacched this on a machine where sql server 2005 is installed and I am getting the message while attaching the database.
"The database can not be opened because it is version 661.
the server supports version 611 and earlier"

You need to install/have another instance of SQL Server 2008, restore over there the database and perhaps create a SSIS package to move objects and data into SQL Server 2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Error installing sql server 2008 management studio express

Hello,
I need to install sql server 2008 management studio express on a sql server 2k8 R2 instance.
First of all, I've downloaded this one from this link: http://www.microsoft.com/en-us/download/details.aspx?id=7593 (for 32 bits).
Once I've the downloaded file I run this file and choose the first option (New sql server stand-alone...) in the installation part. Finally, in the installation type I choose the option 'Add features to an existing instance of SQL Server 2008' with the instance
selected. I push Next and then I get the following error: 'The instance ID is required but it is missing'.
Can anybody help me?
Thanks a lot.
Regards.

Hello,
What’s the edition of the SQL Server 2008 R2? If you had installed SQL Server 2008 R2 Developer edition, you should install “SQL Server 2008 Express with Tools” edition or “SQL Server 2008 Express with Advanced Services” edition.
Please refer to the following article for more information:
http://www.benlittler.com/2009/06/how-to-install-sql-management-studio-express-2008/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Can't login SQL Server 2008 R2 Express management studio

Hi i recently installed SQL Server 2008 R2 management studio. When I try to login i select 'Database engine' as the server type, I'm not sure what server name I'm
supposed to be using but I tried .\SQLEXPRESS and authentication is 'SQL server Authentication'. But as for login and password I don't have one. During the installation I was not prompted to provide a login/password. As with the 2005 server installation I
could by selecting 'mixed'. So how do i login for the first time on SQL server 2008 if i dont know/have my login/password?

Hi,
Try below links :
http://blogs.msdn.com/b/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx
http://stackoverflow.com/questions/360141/how-to-connect-to-local-instance-of-sql-server-2008-express
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/e880c3be-a874-4979-8874-7044c087318d/sql-server-express-default-username-and-password
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

SQL Server 2008 + 2008r2 install

Hello,
I have SQL Server 2005 express installed on my Windows 2008 server
I installed SQL Server 2008 express on my machine.
I didn't add the tools - so I donwloaded and installed the tools afterwards.
I accidentally downloaded and installed the SQL express 2008 R2 tools. I realised my mistake so tried to uninstall 2008 R2 (which also seems to have installed 2008 r2 server as well - even though it was just the tools download)
2008 r2 failed to uninstall. So, I tried to uninstall 2008 as well and start from scratch. But the install fails to 2008 as well. The binary files are still there and both still appear in the add/remove programs list.
Should I just re-install 2008 with tools?
Will there be any conflicts if 2008 r2 is still "hanging around"
Thanks
Ronnie

As Olaf mentioned, you can run multiple versions of SQL Server on the same machine without any issues. The SSMS client tools support down-level connections and will "light up" functionality based on the version you connect to. Ex: If you have 2008
R2 SSMS and connect to an instance of SQL Server 2000 versus an instance of SQL Server 2008 R2, you will see a much different set of functionality. As a general rule, I typically stick to always running the client tools from the highest version of the
database engine that I have on that particular machine.
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

SP3 cannot be installed on SQL Server 2008 standard edition 64 bit

I am getting error during the running of setup of SP3 for SQL Server 2008 Standard edition on windows 2008 R2 enterprise ed.
Description:
SQL Server 2008 Setup has encountered an error.
Problem signature:
Problem Event Name: SQL100Exception
Problem Signature 01: SQL2008@RTM@KB2546951
Problem Signature 02: 0xFE9E43A7
Problem Signature 03: 0xFE9E43A7
Problem Signature 04: 0xDC80C325
Problem Signature 05: 0xDC80C325
Problem Signature 06: InitializeUIDataAction
Problem Signature 07: Unknown
Problem Signature 08: Unknown
Problem Signature 09: Unknown
Problem Signature 10: Unknown
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hi,
I found the log file but I am not able to find any upload file button. It is very big file how can I upload it here?
Overall summary:
Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal):           -74274373
Exit facility code:            914
Exit error code:               43451
Exit message:                  The system cannot open the device or file specified.
Start time:                    2014-04-10 08:03:59
End time:                      2014-04-10 08:05:15
Requested action:              Patch
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140410_080359\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.5500.0%26EvtType%3d0xFE9E43A7%400xDC80C325
Machine Properties:
Machine name:                  AD-ITD-SW-SQLDB
Machine processor count:       16
OS version:                    Windows Server 2008
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      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services
1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          Database Engine Services
1033                                      10.0.1600.22
No
Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          SQL Server Replication
1033                                      10.0.1600.22
No
Sql Server 2008
Management Tools - Basic                 1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008
Management Tools - Complete              1033                 Standard Edition     10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity                1033                 Standard Edition
10.0.1600.22    No
Sql Server 2008
Client Tools Backwards Compatibility     1033                 Standard Edition     10.0.1600.22    No
Sql Server 2008
Client Tools SDK                         1033
Standard Edition     10.0.1600.22    No
Sql Server 2008
Integration Services                     1033                 Standard Edition
10.0.1600.22    No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       3
KBArticle:                     KB2546951
KBArticleHyperlink:
PatchType:                     SP
AssociatedHotfixBuild:         0
Platform:                      x64
PatchLevel:                    10.3.5500.0
ProductVersion:                10.0.1600.22
GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0
PackageName:                   SQLServer2008-KB2546951-x64.exe
Installation location:         d:\c8811b7ec810308deb\x64\setup\
User Input Settings:
ACTION:                        Patch
ALLINSTANCES:                  False
CLUSTERPASSIVE:                False
CONFIGURATIONFILE:
HELP:                          False
INDICATEPROGRESS:              False
INSTANCENAME:                  <empty>
QUIET:                         False
QUIETSIMPLE:                   False
X86:                           False
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.ComponentModel.Win32Exception
    Message:
        The system cannot open the device or file specified.
    Data:
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetDBProperty(ServiceContainer context, String pathToMsi, String propertyName)
        at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.GetMsiRtmVersion(PackageInstallProperty targetPackage)
        at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.IsApplicablePatch(PatchProperty currentPatch, PackageInstallProperty targetPackage)
        at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.GetInstalledPackages(String instanceName, List`1& installedInstancePackages, List`1& installedSharedPackages, String& returnedErrorMessage)
        at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CollectProductData()
        at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinitionAllInstances()
        at Microsoft.SqlServer.Configuration.PatchFeatureTree.InitializePatchFeatureTree(ServiceContainer context)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

Incompatible SQL backup on SQL Server 2008 R2

I installed SQL Server 2008 R2 from MSDN download for testing on a development server. I copied a backup from a live SQL Server 2008 R2 server and when I tried to restore the database on the MSDN downloaded copy of SQL the following error was generated...
"The database was backed up on server version 10.50.4033. That version is incompatible with this server, which is running version 10.00.2531....."
Any suggestions on a solution?

NO possibilities of backing up from higher to lower version.
only lower to higher is possible.
you can do this
upgrade this instance to SQL Server 2008 R2 or
restore the backup you have on a SQL Server 2008 R2 instance, export all the data and import it on a SQL Server 2008 database.
Mark as answer if it is useful

Adding instance to SQL Server 2008 R2 on SBS 2011 Standard

Similar Messages

Maybe you are looking for