SQL Server Instance on VM - Cloning to create a new box

Hi Guys,
I'm just wondering if there's a way to image the SQL Server instance to create a new box?
We're planning to upgrade to SQL Server 2005 to 2012 and we're currently testing the 2012 DEV box if all necessary server configurations, settings, linked sever at etc are in place. I'm not sure if the DBA have these scripted but we have or own checklist
to verify.
Given that, if we create a new 2012 UAT Box, we don't want to repeat the whole checking process, we want to clone/migrate/copy what was tested in the DEV BOX. is there a way to do it? or what's the best practice.
Thanks in advance.
Regards,
Marvin

Yes - SQL Server 2012 can be SYSPREP'd to create a deployable image file.
There is a little gotcha though :
http://blogs.msdn.com/b/virtual_pc_guy/archive/2006/11/13/running-sysprep-on-a-virtual-machine-with-sql-server-installed.aspx

Similar Messages

  • DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

    I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem.  In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total).  All of the SQL
    environment is backing up fine except for a SQL Cluster Application.  This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them.  The other 5 SQL instances in the cluster are backing
    up fine; only one instance is failing.  The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
    Affected area: KEN-PROD-VDB001\POSREPL1\master
    Occurred since: 6/11/2011 11:00:56 PM
    Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
    4.
     If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
     The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
    Internal error code: 0x80990F85)
     More information
    Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
     Create a recovery point...
    Resolution: To dismiss the alert, click below
     Inactivate alert
    I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
    receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine).  The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
    to when the failures started to occur.  However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem.  We are running SQL 2008 SP2 (version 10.0.4000.0)
    on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
    One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
    Log Name:      Application
    Source:        MSDPM
    Date:          6/13/2011 1:09:12 AM
    Event ID:      4223
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      KEN-PROD-BS002.aarons.aaronrents.com
    Description:
    The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
    1) No valid recovery points present on the replica.
    2) Failure of the last express full backup job for the datasource.
    3) Failure while deleting the invalid incremental recovery points on the replica.
    Problem Details:
    <DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
    the message resource is present but the message is not found in the string/message table
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSDPM" />
        <EventID Qualifiers="0">4223</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
        <EventRecordID>68785</EventRecordID>
        <Channel>Application</Channel>
        <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
    1) No valid recovery points present on the replica.
    2) Failure of the last express full backup job for the datasource.
    3) Failure while deleting the invalid incremental recovery points on the replica.
    Problem Details:
    &lt;DpmWriterEvent&gt;&lt;__System&gt;&lt;ID&gt;30&lt;/ID&gt;&lt;Seq&gt;1833&lt;/Seq&gt;&lt;TimeCreated&gt;6/13/2011 5:09:12 AM&lt;/TimeCreated&gt;&lt;Source&gt;f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp&lt;/Source&gt;&lt;Line&gt;815&lt;/Line&gt;&lt;HasError&gt;True&lt;/HasError&gt;&lt;/__System&gt;&lt;DetailedCode&gt;-2147212300&lt;/DetailedCode&gt;&lt;/DpmWriterEvent&gt;
    </Data>
        <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
      </EventData>
    </Event>
    Any help would be greatly appreciated!

    Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem.  If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
    and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
    I would also like to add that the databases on this node that will not backup are running fine.  They run hundreds of transactions daily so we know SQL itself is OK.  Even though it is a busy SQL Server, there is plenty of available resources as
    the SQL buffer and memory counters show the node is not under durress.

  • Is it possible to have different authentication mode for SQL Server Database Engine and corresponding SQL Server instance?

    Hi,
    I have installed the x64 SQL Server 2008 R2 Express with default settings and run MBSA 2.3 (using default settings too). It shows three SQL Server instances: MSSQL10_50.SQLEXPRESS, SQLEXPRESS and SQLEXPRESS (32-bit). For the first, authentication
    mode is Windows, for the rest two - mixed. Here https://social.msdn.microsoft.com/Forums/sqlserver/en-US/03e470dc-874d-476d-849b-c805acf5b24d/sql-mbsa-question-on-folder-permission?forum=sqlsecurity question
    about such multiple instances was asked and the answer is that "MSSQL10.TEST_DB
    is the instance ID for the SQL Server Database Engine of the instance, TEST_DB", so in my case, it seems that MSSQL10_50.SQLEXPRESS is the instance ID for SQL Server Database Engine  of the SQLEXPRESS instance.
    I have two questions:
    1) How can it be that SQL Server DB Engine instance has different authentication mode than corresponding SQL Server Instance?
    2) Why 32-bit instance reported although I installed only 64-bit version?
    Also, this https://social.technet.microsoft.com/Forums/security/en-US/6b12c019-eaf0-402c-ab40-51d31dce968f/mbsa-23-reporting-sql-32bt-instance-is-running-in-mixed-mode-when-it-is-set-to-integrated?forum=MBSA question seems to be related to this
    issue, but there is no answer :(.
    Upd: Tried on clean Windows 8 installation and Windows 7 with the same result.

      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

  • SCOM 2012 Installation does not show the SQL Server Instance for reporting services

    I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
    In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
    Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
    Regards,
    Paul Mendoza.

    Hi Paul
    Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
    For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
    - run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
    - run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
    Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together. 
    Cheers
    Graham
    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at
    http://systemcentersolutions.wordpress.com/

  • Entity Framework doesn't create the database in SQL Server Management 2012, instead it just creates in (localdb)\v11.0 How to fix it?

    Hi, I'm Begginer in Entity Framework. Then I'm having some problems.
    I created my entities and I give Save Changes. (Ok)
    Then, I Tried to Connect with the database through Server Explorer, if I use the instance of the SQL Server Management Studio 2012(PC-PAULO\INSTANCIAPJ) as Server Name, the database doesn't appears but, if I use the the instance (localdb)\v11.0 the dabase
    appears.
    How to change the save to the SQL Server Management Studio 2012, I don't know where this (localDB)\v11.0 saves.
    Help-me Thank you :D

    Hello PauloJos,
    The code should be ok and it is really strange that the database is only created into the local database in your machine. I am wondering if it is related with the machine environment, could you please have a try with below demo on your machine which works
    on my side and if it is possible, please have a try to run your application on other machines to see if it works:
    class Program
    static void Main(string[] args)
    #region https://social.msdn.microsoft.com/Forums/en-US/00eff3c4-2336-4807-9212-e6f2a6c8812e/entity-framework-doesnt-create-the-database-in-sql-server-management-2012-instead-it-just-creates?forum=adodotnetentityframework
    using (CFDbContext db = new CFDbContext())
    db.Database.CreateIfNotExists();
    #endregion
    public class CFDbContext : DbContext
    public CFDbContext() : base("UltraFoda3") { }
    public DbSet<TestOne> TestOnes { get; set; }
    public class TestOne
    public int ID { get; set; }
    public string Name { get; set; }
    Config file is similar:
    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
    <configSections>
    <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
    <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
    </configSections>
    <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework">
    <parameters>
    <parameter value="v11.0" />
    </parameters>
    </defaultConnectionFactory>
    <providers>
    <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
    </providers>
    </entityFramework>
    <connectionStrings>
    <add name="UltraFoda3" connectionString="Data Source=YourServer;Initial Catalog=UltraFoda3;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
    </connectionStrings>
    </configuration>
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Cannot connect to the specified SQL Server instance

    I am trying to install Microsoft System Center 2012 R2 Virtual Machine Management.
    I am getting the following error:
    Setup cannot connect to the specified SQL Server instance.
    Ensure that the server name, isntance name, and, if speceified, port number are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then try Setup again.
    I have installed the 
    Microsoft® SQL Server® 2008 R2 Command Line Utilities
    but have not set up any SQL Server instances. 
    how should i proceed?
    Edit:
    The followign fields are configured:
    Server Name: The name of the machine i am using
    Port: <empty>
    Use the following credentials <NOT ticked>
    Instance name <empty> (the drop down is empty)
    New Database <Ticked> :  VirtualManagerDB

    Is SQL server is properly installed on the system?
    Are you able to connect with SQL server instance?
    As per the given details looks, only client utilities installed and trying to create the database which needs SQL server.
    Make sure you are able to connect with the "ServerName\InstanceName,PortNumber" and hope installing the system as per below article:
    http://technet.microsoft.com/en-us/library/gg610656.aspx
    Hope it help!
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • Connecting to a specific SQL Server instance?

    Hi all,
    I create a new connection for SQL Server, specify the host and the port number that SQL Browser is listening on (my servers have dynamic ports, not static), and I can connect succesfully to the local SQL Server Instance on that machine, which is SQL Server 2000. However, I also have a SQL Server 2005 and 2008 running on that machine as well, and wish to connect to them.
    The SQL Server tab doesn't ask for an instance name at all, so I don't know how to do that. I suppose I could make my ports static for each instance, but the point of using SQL Browser is that you don't need to do that. SQL Browser acts almost like a DNS server for any sql requests coming to that machine.
    Is there any way to specify which instance name you want to connect to rather than a port #?

    Ok, that worked. Now for another question, why isn't the connection retreiving the database I selected in the SQL Server tab? It's only retrieving the master database if I connect as sa (master is the default database for SA). How do I set it up to use a different database, or do cross database queries? I suppose I could make a user for each database, but that doesn't fix the second issue.
    I think I might just be stuck using two different tools for these two very different products.

  • Connect from SQL Developer to several SQL Server instances

    Our SQL Server has more than one instance, but I see only one instance of them trying to connect from SQL Developer 1.2 to SQL Server. How I should define the connection information? Usually we connect to SQL Server by <hostname>/<instancename> and then the database name as CatalogName (Initial Catalog). In the Oracle world you can give only the hostname, a port number and the database name. How I can convince the SQL Developer to choose one of our SQL Server instances?

    Hi user627927,
    Bug/Enhancement request already logged.
    We have not got this configuration in house, two people have suggested workarounds but we are unable to test them for now. The last person was unable to get these workarounds working, and we have not confirmed them in house.
    Can you get the instances connected through two different ports?
    It would be great if you could confirm either workaround.
    -Turloch
    *1/Suggestion 1 change the URL through SQLDevelopers xml connection store.
    *2/Overload the port field to have instance in the eventual url
    *1/Suggestion 1 change the url through SQLDevelopers xml connection store.
    [Note it is probably simpler to connect a dummy connection through the connection dialog as usual save it (you cannot connect) and then add the instance information rather than having to enter all the information in an unmanaged way.]
    Hi Naveen,
    I had same problem as you and user579801. I managed to resolve it by doing the following.
    1. Locate the file called IDEConnections.xml in the folder where you have installed SQL Developer (eg. c:\sql developer\sqldeveloper\system\oracle.jdeveloper.db.connection.11.1.1.0.11.42.62).
    2. Create the following entries under <connections> tag.
    <connection>
    <URL>jdbc:jtds:sqlserver://\\.\;namedPipe=true;instance=SQLDBNam;</URL>
    <ConnectionName>SQLServer</ConnectionName>
    <user>SQLUser</user>
    <ConnectionType>JDBC</ConnectionType>
    <DeployPassword>false</DeployPassword>
    <JdbcDriver>net.sourceforge.jtds.jdbc.Driver</JdbcDriver>
    <RaptorConnectionType>Microsoft SQL Server</RaptorConnectionType>
    </connection>
    3. Save the file; Close and re-open the SQL Developer and try connecting.
    Hope this will solve your problem. Good luck.
    Regards
    Raja
    *2/Overload the port field to have instance in the eventual url
    This took some figuring out but I cracked it in the end....
    SQLServer tab:
    Hostname: <servername>
    Port: <portnumber>/<databasename>;instance=<instancename>
    so for me the Port field looks like this: 1433/Gaffa;instance=SQL01
    That should now connect to a named instance SQL Server.
    Paul Fairhurst

  • Problem using DG4ODBC with named SQL Server instance

    I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
    ORA-02063: preceding 2 lines from DEVMISC
    odbc.ini
    [GENERALI_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = CLTDMJCWBYZ.eu.scor.local
    User                    = everest
    Password                = everest
    Database                = Everest_Generali
    [DEVMISC_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = [USVCLTDEVSQL02\DEVMISC]
    User                    = link_user
    Password                = password1
    Database                = DBA
    initDG4ODBC2.ora
    # HS init parameters
    HS_FDS_CONNECT_INFO = DEVMISC_DSN
    HS_FDS_TRACE_LEVEL = DEBUG
    HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/home/oracle/.odbc.ini
    listener.ora
    SID_LIST_LISTENER_GW =
       (SID_LIST =
          (SID_DESC =
           (SID_NAME=DG4ODBC)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
    soft/sqlncli/lib)
          (PROGRAM=dg4odbc)
          (SID_DESC =
           (SID_NAME=DG4ODBC2)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
    osoft/sqlncli/lib)
          (PROGRAM=dg4odbc)
    LISTENER_GW =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
    tnsnames.ora
    DG4ODBC =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC))
          (HS=OK)
    DG4ODBC2 =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC2))
          (HS=OK)
    I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

    Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
    Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
    who states that named instance connections are not supported using that driver.
    - Klaus

  • [Forum FAQ] Troubleshooting error "The specified SQL server instance is not valid" when installing SCOM reporting service

    Symptom
    If you have failed to install SCOM reporting service, you may encounter below error when you reinstall it:
    “The specified SQL server instance is not valid”.
    (Figure 1)
    Figure 1.
    Reason
    This issue may be caused by multiple reasons, for example the reasons in Figure 1.
    However, you may find that SSRS and Report Server website are configured correctly and no SSL or proxy Server is used. In these scenario, you can open the log file under path
    to find the root reason:
    C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
    Later, you will find the error as below:
    ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDisabledException: , Microsoft.ReportingServices.Library.ReportServerDisabledException:
    The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException
    (0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at RSManagedCrypto.RSCrypto.ReencryptSymmetricKey(Byte[] symKeyBlob, Byte[] pPublicKeyBlob)
    at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
    --- End of inner exception stack trace ---;
    Solution
    According to the error message, you can delete encrypted content by following the steps below:
    Open SQL Reporting Services Configuration Manager.
    Select “Encryption Keys”.
    Click “Delete” to delete all encrypted content. (Figure 2)
    Figure 2.
    After that, we can install SCOM reporting service again, after successfully install reporting service, we should see the SCOM operation console as below:
    Figure 3.
    In addition, you may also encounter other errors when installing SCOM reporting service, and the troubleshooting steps may be different. However, we can also check SQL reporting
    service logs to find the root reason.
    Here are some articles that would be helpful for SCOM reporting service installation and troubleshooting:
    How to Install the Operations Manager Reporting Server
    http://technet.microsoft.com/en-us/library/hh298611.aspx
    Unable to install SCOM 2012 Reporting Services
    http://blogs.technet.com/b/mdegre/archive/2013/05/27/unable-to-install-scom-2012-reporting-services.aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hello,
    I'm afraid you must use a dedicated instance of SQL Server for each site(SCOM/SCCM). Some similar issues were disscussed on this forum:
    SCCM and SCOM - SQL Server 
    http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/bfa14da9-4692-4c64-a107-e085c967d259
    SCOM, SCCM, SQL on same server?
    http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/b5373aa7-5233-4b1f-9b39-b86e481e04d5
    Thanks,
    Yog Li
    TechNet Community Support

  • Data modeler cannot connect to non-default sql server instance

    I've just started using DM, it installed and loaded fine, I got the jdbc drivers v2.0 from MS so that I can reverse engineer a couple of SQL-Server 2005 DB's.
    All worked just fine until I tried to connect to a machine with a named-sql-server instance.
    Normal way of doing this for sql-server is to add instance name to end of hostname in the hostname field, like this: "server10\inst01"
    but this gives me a cannot-connect-to-server10 error.
    I copied database over to a different server that has just a default sql-server instance and it worked fine. (both sql-server2005 and 2000!)
    I also tried the older 1.2 jdbc driver from MS against the sql-server 2005 named instance, no luck!
    I tried putting the instance name in front of the port number, that didn't work either.
    Am I just doing something wrong? or does DM need a special way of specifying the instance name on the sql-server host?

    Hello,
    you don't need instance name in order to connect. It's only host and port - probably named instance is not listening on default port. It'll be unfortunate if dynamic port assignment is used - but probably that won't be the case.
    I hope someone can tell you the port number.
    Philip

  • I want make use of SQL Server Instance, while connecting

    hi,
    i have developed Code using normal conditions,Like i have not checked for SQL Server Instances, my client need to b use Instances of the SQL Server, so i need to change the code.
    can any one help Regarding SQL Server Instances Connection coding.
    Ex: jdbc:JSQLConnect://servername\Instance_Name
    can any one help out me, it would be grate help for me,
    thanks.

    Read the JDBC tutorial and read the SQL Server JDBC driver documentation.
    http://www.google.com/search?q=jdbc+tutorial+site:sun.com
    http://www.google.com/search?q=sql+server+jdbc+driver+site:microsoft.com

  • Setup cannot connect to the specified SQL Server instance

    On a clean install domain member (Windows 2012), I am trying to setup System center 2012 VMM:
    1. I installed the prerequisites as instructed during the pre-setup phase of the installation then rebooted the server (SQL Server 2012 was installed and services seem to be all started properly and SQL Configuration Manager starts as well).
    2. After reboot, logged again with domain admin account and Windows update installed right away SP1 for SQL server 2012. Then I rebooted again.
    3. Restarted the installation process and left default values. At the "Database configuration" step, I am leaving everything by default as well and I am getting error: "Setup cannot connect to the specified SQL Server instance. Ensure that
    the server name..."
    4. Tried different credentials, tried using port 1433 with no effect.
    Am I missing something????
    Thanks.
    Benjilafouine

    Definitely be sure to connect with the "ServerName\InstanceName,PortNumber". If you don't reference a port number it will try 1433 and then will connect via a dynamic port number. It is best in my opinion to always specify a specific port for each instance
    to listen on in the SQL Server Configuration Manager so that you can open the fewest number of ports in the Windows firewall.

  • Cannot not connect to SQL Server instance.

    Hello,
    I have SQL Server 2012 installed and when I run this command:
    sc query mssql$MSSQLSERVER
    I get this error:
    [SC] EnumQueryServicesStatus:OpenService FAILED 1060:
    The specified service does not exist as an installed service.
    I run this command on the same server where SQL Server is installed.  Databases are on the same server too.  TCP/IP is enabled for the instance and port 1433 is open on the server's firewall. SQL Server Browser is running.
    Many errors in the SQL Server error logs like:
    SQLServer Error: 11001, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct.
    SQLServer Error: 11001, TCP Provider: No such host is known. [SQLSTATE 08001]
    Any ideas what could  have gone wrong?
    Thanks,
    Paul
    Paul

    Hi Paul,
    According to your description, you fail to connect to SQL Server 2012 instance. According to the SQL Server error log, based on my research, your issue could be due to that
    the client cannot resolve the name of the SQL Server instance.
    Are the errors from the SQL Server error log solved? If the errors are not solved, please follow the steps below to troubleshoot the issue.
    1. Make sure you are able to ping the physical server where SQL Server is installed from the client machine. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Name
    for a named instance.
    2. Make sure you are using the correct instance name. When you connect to a default instance, machine name is the best representative for the instance name and when you connect to a named instance such as sqlexpress, you should
    specify machinename\instancename according to
    Niting123’s post. And you could verify if you use the right instance name in SQL Server configuration manager according to
    Niting123’s post.
    3. Check that SQL Server is in the network. You can use the SQLCMD -L command to retrieve the list of SQL Server installed in the network. Note that this will only return SQL Servers if the SQL Server Browser service is running.
    4. Make sure that you enable Named Pipes besides TCP/IP protocol.
    5. Check to see if remote connections is enabled. Right click on the server name in SSMS and select Properties. Go to the Connections tab and make sure Allow remote connection to this server is checked.
    6. Locally connect to SQL Server and check the error log for the port entry.
    7. To connect to SQL Server instance using TCP/IP from another computer, on the SQL Server computer, you must configure the firewall to allow connections to the TCP port used by the Database Engine. If you are connecting to a named
    instance or a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service according to pasquale’s post.
    For step by step instruction on opening a port in the Windows firewall, see
    How to: Configure a Windows Firewall for Database Engine Access
    For more information about the process, please refer to the article:
    http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
    In addition, you mention that there are many other errors, so please provide the SQL Server error log for analysis.
    Regards,
    Michelle Li

  • SQL 2012 SP2 There are no SQL Server instances or shared features that can be updated on this computer

    Hi, 
    I have a SQL Server instance:
    Microsoft SQL Server 2012 - 11.0.5058.0 (X64) 
    May 14 2014 18:34:29 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
    I am trying to install:
    SQLServer2012SP2-KB2958429-x64-ENU
    On the "Select Features" screen of the setup I get an error message when I try to click next:
    "There are no SQL Server Instances or shared features that can be updated on this computer."
    I've checked and re-checked the release notes - pretty sure I have the right versions of everything:
    https://msdn.microsoft.com/en-us/library/67cb8b3e-3d82-47f4-840d-0f12a3bff565?f=255&MSPPError=-2147217396
    Any help appreciated!
    Cheers
    Lucas
    LucasF

    Hi, 
    I have a SQL Server instance:
    Microsoft SQL Server 2012 - 11.0.5058.0 (X64) 
    May 14 2014 18:34:29 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
    I am trying to i
    LucasF
    Your SQL Server 2012 is already at SP2 see version number 11.0.5058 this corresponds to SP2. So when you run the setup it says there is nothing to upgrade
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

Maybe you are looking for