Gracefully Shutdown Virtualized SQL 2012 Server on Battery (UPS) Power?

I have a VMWare ESXi 5.1 environment with a 2012 R2 SQL Server that hosts all of our databases and functions as the Report Server.  I am the only on-site IT person and as such am responsible for database administration.  I have done a lot of reading on database corruption and have determined that a hard shut down will very likely cause issues.  We have a UPS, but I wantto be prepared for the worst case scenario.  
We work with an MSP for high level networking issues and I have been requesting help with this for several weeks to no avail.  I have been told a hard shut down will not negatively effect my SQL Server (this individual has virtually no SQL experience).
Can anyone point me in the right direction?  This is keeping me awake at night!
This topic first appeared in the Spiceworks Community

Is this what you are talking about?
http://www.sophisticated.com/products/powerkey/pkp_650.html

Similar Messages

  • Multiple dev environments of CRM 2011 on one SQL 2012 server

    Hello,
    I have requirement to install multiple development servers of CRM 2011 which would use one SQL 2012 Server. 
    As you know, you need separate CRM 2011 Reporting Extensions, which means that Reporting Services (SSRS) should be installed not in SQL 2012 server but in the same server as CRM 2011. For SSRS (on CRM 2011 server) I want to use SQL 2008R2 Express (licensing
    issues).
    Is it possible to use SQL 2008R2 Express only for SSRS, while CRM 2011 is using SQL 2012 on different server?
    I get errors while creating organization:
    System.Web.Services.Protocols.SoapException: The feature: "Customizing security roles" is not supported in this edition of Reporting Services.
    Environment information:
    CRM 2011 on Windows Server 2008 R2. In the same server SSRS 2008 R2 on SQL 2008 R2 Express
    CRM database in different machine with SQL 2012 on Windows Server 2012.
    Regards, 
    Jonas

    SQL Express is not supported for Dynamics CRM.  Plus, the only way to have completely separate installations of Dynamics CRM pointing to one server for SQL is to used named instances of SQL Server on the Windows server you're installing SQL. 
    So you literally would have to install SQL multiple times on that one box.
    Instead of going through all that effort, why not just install Dynamics CRM once, and then make multiple CRM deployments using the CRM Deployment Manager? You can make as many CRM environments as you need with a single install of Dynamics CRM. This works
    great in dev environments where you need multiple instances for multiple devs. Plus, it gives you exactly one point of administration when it comes to the CRM install, and is a lot more supportable.
    The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions.

  • Migration of the database from Microsoft SQL 2014 Express to Microsoft SQL 2012 Server

    I posted a similar thread yesterday, and I realized that there was a serious typo.
    Link: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b3e201ea-6c7c-43a4-8908-842b714ea451/migration-of-the-database-from-microsoft-sql-2014-express-to-microsoft-sql-2012-server?forum=sqlservermigration
    Therefore, I made a decision to post another thread right now.
    I am
    writing to ask if there are any known issues when migration from MS SQL 2014 Express to MS SQL 2012 Server version. Are there any step-by-step instruction on how I can go about doing this?
    Looking forward to your response. Thank you for your time.
    Regards,
    Jeff Yoo 

    Hello,
    SQL Server 2012 setup program won’t allow you to perform a downgrade from SQL Server 2014 Express Edition. Backup/Restore
    and Detach/Attach won’t help you either.
    One option you have left is using SQL Server Import/Export Wizard as explained on the following article.
    http://www.mytechmantra.com/LearnSQLServer/Downgrade_SQL_Server_Database_P1.html
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Down grade SQL 2014 to SQL 2012 server

    Hi,
    I have purchased SQL 2014 paper license but I want to use SQL 2012 server can we use same licensing for SQL 2012. Can we downgrade the SQL 2014 to 2012.
    Thanks & Regards

    Hello,
    yes, you can downgarde you r SQL Server 2014 to 2012 Version. for Customers who have licensed software through a Microsoft Volume Licensing program are eligible to use prior versions of the software edition that they have licensed. This is known as
    a downgrade right.
    In general, the
    Volume Licensing Service Center (VLSC) provides download access only to the current (N) and the last (N-1) version of products(2014, 2012). however, as of December 2012, a limited set of N-2 and N-3 prior product versions remain available for download through
    the VLSC. for SQL Server you can also downgrade to 2012, 2008 R2 and 2008.
    Note: In addition to VLSC download software access, Volume Licensing customers can order physical media (CD/DVD) copies of their licensed software through the VLSC.
    if you purchase your SQL Server as FPP(BOX) product, you can also downgrade it to 2012 but you Need to have the media + key product of 2012 Version.
    thanks
    diramoh

  • Add login to sql 2012 server for a virtual account from another sql 2012 server

    I have two sql 2012 servers. 
    Server A has sql server agent running virtual account: NT Service\SQLSERVERAGENT
    Server B has some databases.
    Server A is running a scheduled SSIS package that needs access to Server B's databases via Windows Auth
    Thus I want to grant access by creating a login on Server B to the virtual account on server A: NT Service\SQLSERVERAGENT
    Q1 - Is this possible?
    Thanks beforehand.
    Paulino

    Raul,
    As a matter of a test and not with the actual intention to use it this way, I did try to add a login using the DOMAIN\MACHINE_NAME$
    concept but it did not work anyway. I will not find it.
    So I will use one of the approaches recommended by Mr. Gallardy
    Thanks!
    Paulino

  • Fulltext search of binary files outside of database in SQL 2012/Server 2012

    This may be more of a Windows Server 2012 question but I'm not sure.
    I have a system that holds large amounts of binary files (pdf, doc, etc.).  The files themselves are held outside the database in a folder and a SQL table holds the metadata.  I used the Indexing Service available through Windows Server 2008 to
    create a catalog called "EFCATALOG" to index the contents of the external folder, then created a linked server called MYIDXS which allowed me to query that external indexing catalog from within SQL with a query like this:
    EXEC sp_addlinkedserver MYIDXS, 'Internal App', 'MSIDXS', 'EFCATALOG'
    SELECT * FROM MYDOCS
    LEFT JOIN OPENQUERY(MYIDXS,'SELECT FILENAME FROM SCOPE() WHERE CONTAINS (''test'')') AS MYTBL
    ON MYDOC_FILE_NAME = MYTBL.[FILENAME]
    With Windows Server 2012, I'm missing the functionality to create the indexing service catalog.  I've added the Windows Search Service and see how I can configure folders for searching, but there is no naming functionality for this and I don't see how
    I can get the above query/structure to work in Windows Server 2012/SQL Server 2012 environment.  In fact, there isn't much at all online regarding the search service or the relationship back to the older versions in 2008 and before.
    Is there any way to continue this structure in 2012?  I would like to avoid recoding my application to work with a different structure.  I'm afraid that changing everything to work with the FILETABLE/FILESTREAM functionality added in SQL 2012
    will be necessary which is fine long term, but not convenient right now.
    Thanks in advance for any suggestions/help.

    Thank you Fanny Liu, based on your link the syntax has changed dramatically. I need to query SYSTEMINDEX now and the structure is very different.    It still seems that this new syntax requires creating a linked server of a different type. 
    I've tried:
    EXEC sp_addlinkedserver @server = 'TEST', @provider = 'Search.CollatorDSO.1', @datasrc = 'SYSTEMINDEX', @srvproduct = '', @provstr='Application=Windows'
    SELECT FileName FROM OPENQUERY("TEST", 'SELECT Filename FROM SYSTEMINDEX')
    Msg 7302, Level 16, State 1, Line 1
    Cannot create an instance of OLE DB provider "Search.CollatorDSO.1" for linked server "TEST".
    I've also tried using just "Search.CollatorDSO"as the provider since that is the provider name listed in management studio but basically the same error comes back.
    So I have 2 questions:
    1) Is it possible for my original process to work in Windows Server 2012 in any way (meaning that the OPENQUERY example I provided can remain relatively unchanged)?
    2) If change is necessary using this new SYSTEMINDEX and linked server combination, why is my linked server definition failing?  I'm using SQL Server 2012....Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
     Feb 10 2012 19:39:15
     Copyright (c) Microsoft Corporation
     Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
    Thank you.

  • Sql 2012 server for SCCM 2012 - Agent not starting

    Hi ,
      In our environment we have a Sql 2012, and it was working fine till now.  but after installation of RDP role and subsequent installation of certificates for remote desktop in the SCCM server ( SQL 2012 is
    installed in it) 
    we are facing the issue - Sql server management studio not connecting ( windows authenticaltion)
    1) A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)A
    2) I tried starting the sql agent service in services.msc  and the below error came 
    The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped. 
    Some services stop automatically if they are not in use by other services or programs.
    3) In the Sql Server configuration manager also tried starting the sql agent but 
    The request failed or the service did not respond in a timely fashion. 
    Consult the event log or other applicable error logs for details.
    The widows event logs show this error
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. 
    The TLS protocol defined fatal error code is 20. The Windows SChannel error state is 960.
    We have removed the certificate and the RDP role in that . 
    Can anyone please help on this
    Anand M

    I would check for error messages in the SQL Server ERROLOG file and also Agent's SQLAGENT.OUT file.
    Tibor Karaszi, SQL Server MVP |
    web | blog

  • Point Imaged/Cloned Sharepoint 2010 to different/renamed SQL 2012 server - what needs to be changed/edited?

    Newbie here... I am using our development VM's one has SP 2010 installed/working and configured and the other is SQL 2012 housing the DB's for the working SP sites and a third running IIS and hosting the pages.  I want to use clones to copy to additional
    VM's, rename the SQL and rename the SP 2010 (the IIS will stay the same just add the cloned site to it. MY question is "Is there an automated way of reconfiguring SP 2010 to point to the new SQL server? (I've already figured out how to change the SID
    information and run the queries on the SQL, just need info on the SP 2010 part.)
    Thanks,
    Jon P.

    You can't do this, don't try it. For VM purposes, SharePoint does not support:
    Time Sync
    Snapshotting/Checkpoints
    VM Backups (e.g. SAN-based or VMDK/VHD-based backups)
    You will cause problems doing what you're attempting to do, unless you isolate these VMs onto a new network that has no access to the production network -- in this case, you would also need a copy of one Domain Controller from production, as well.
    Best bet is to build a new farm and restore content to it via content database/service application database restoration.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Restore SQL 2012 Server

    I have two sql 2012 servers in a cluster.  If one of my servers, has to be rebuilt from scratch like reload os, sql server 2102, what is the best way to do this and get the server back in the cluster.

    Hi Gerald,
    Based on my understanding, you are going to rebuild a server that participated in a two-node SQL Server failover cluster.
    From my point of view, you can remove the SQL Server cluster node (assume it is Node 1) firstly, then add it to the existing SQL Server failover cluster again. The basic steps are as follows.
    1. SQL Server Failover Cluster Instance (FCI) fails over to Node 2 after Node 1 fails.
    2. Evict Node 1 from the FCI. To do this, from Node 2, open the Failover Cluster Manager snap-in, right-click Node1, click Move Actions, and then click Evict Node.
    3. Verify that Node 1 has been evicted from the cluster definition.
    4. Install new hardware in Node 1.
    5. Add Node 1 to the existing cluster using the Failover Cluster Manager snap-in. For more information, please review this article:
    Before Installing Failover Clustering
    6. Ensure that the administrator accounts are the same on all cluster nodes.
    7. Add Node 1 to the existing FCI by running SQL Server Setup. For more information, see
    Add or Remove Nodes in a SQL Server Failover Cluster (Setup).
    Reference:
    Recover from Failover Cluster Instance Failure:
    http://msdn.microsoft.com/en-us/library/ms181075(v=sql.110).aspx
    Failover Cluster Troubleshooting:
    http://msdn.microsoft.com/en-us/library/ms189117(v=sql.100).aspx
    Thanks,
    Lydia Zhang

  • VS2012 Wont Connect to SQL 2012 Server Location

    When I attempt to connect to a SQL 2012 Instance, VS2012 crashes. I can connect fine using SQL Management Studio to the SQL 2012 instance, and my VS2012 connects no problem to my SQL 2008 R2 Instances.
    Any suggestions?

    Hello,
    Have you applied Update 4 for VS 2012?
    http://www.microsoft.com/en-us/download/details.aspx?id=39305
    Could you try to reset VS settings?
    Devenv.exe /ResetSettings
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Cannot drop orphaned account on my SQL 2012 Server

    Hi all,
    I have a terrible issue that I am not able to solve by myself. I have made a lot of research on internet but I still not found a valid solution for the problem.
    All is happened when a server crashed some weeks ago and it was removed from my network.
    After that, under my SQL Server 2012 I get an orphaned account which cannot be removed. This account is a computer account related to an old SCOM installation.
    If I try to execute the command DROP USER [NETWORK\SERVERNAME$] I get the following error message:
    The database principal has granted or denied permissions to objects in the database and cannot be dropped.
    Msg 15284, Level 16, State 1, Line 1
    The database principal has granted or denied permissions to objects in the database and cannot be dropped.
    But if I run the following command to know all permission granted to the account, I get an empty result:
    select * from sys.database_permissions where grantee_principal_id = user_id ('Network\SERVERNAME$');
    Furthermore, following the instructions provided by the official KB for troubleshooting orphaned users, I get another error (http://support.microsoft.com/kb/274188/en-us).
    sp_change_users_login 'update_one', 'Network\SERVERNAME$', 'Network\SERVERNAME$'
    Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 114
    Terminating this procedure. The User name 'Network\SERVERNAME$' is absent or invalid.
    The only thing I can retrieve is 15 permissions that this account granted to another account in the past:
    select *                    
    from sys.database_permissions                    
    where grantor_principal_id = user_id ('Network\SERVERNAME$'
    class class_desc                                        
              major_id   
    minor_id    grantee_principal_id grantor_principal_id type permission_name                                                                                                                 
    state state_desc
    17    SERVICE                                                     
    65538       0          
    5                   
    19                  
    SN   SEND                                                                
                                                                G    
    GRANT
    And more 14 similar rows…
    Anyone can help me to resolve my issue and safe delete the account SERVERNAME$? I need this because I have to reinstall SCOM with the same computer name on another server, but installation fails due to this behavior.
    Thanks to all in advance.
    Marco

    DECLARE @service_name sysname,
            @username     sysname
    SELECT @service_name = name FROM sys.services WHERE service_id = 65538
    SELECT @username = name FROM sys.database_principals WHERE principal_id = 5
    DECLARE @sql nvarchar(MAX) = 'REVOKE SEND ON SERVICE:: ' +
           quotename(@service_name) + ' FROM ' + quotename(@username)
    PRINT @sql
    EXEC(@sql) AS 'Network\SERVERNAME$'
    In case you did not get it, the issue is not that the account has been granted permssions, the issue is the account itself has granted permissions.
    Since the SEND permission may actually be needed for @username, it's a good idea to look at the command and re-grant the permission, but now as dbo.
    If you have more of them, Sebastian Meines script to get commands for database permissions is really nice. You would need to add a filter for grantor_principal_id.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Report service Integration (sql 2012 and SharePoint 2013) error Report Server WMI Provider error: Invalid namespace

    Report Server WMI Provider Error: Invalid namespace
    Domain Server, Sql2012 server and SP2013 Server (3 vm servers)
    the sql server reporting services service application and applications Proxy are installed and started (SP2013 Sever)
    the sql server PowerPivot system Service and SQL server Reporting Services Service are Started (in Services on Server)
    in sql server 2012 sp1 reporting service configured (web service URL and Report Manager URL are configured and tested,  the database report server mode is native) (SQl 2012 Server)
    under general Application Settings .. trying to setup the "Reporting Service Integration" give us the above error message (Report Server WMI Provider Error: Invalid namespace)
    I was looking for all blogs and TechNet material but without success.

    Follow these steps:
    1) Uninstall SSRS from the Database Engine server (MSSQLSERVER instance).
    2) Install SSRS on the SharePoint server using the "Reporting Services - SharePoint" install option during SQL Feature selection, no other services are required (e.g. you do not need to install Database Engine services).
    3) You should then see SSRS as a Service Instance in Central Admin -> Manage Services on Server, at which point you can also create an SSRS Service Application.
    While this guide (http://msdn.microsoft.com/en-us/library/jj219068.aspx#bkmk_install_SSRS) walks you through it, this is for a single server install where the Database Engine is also installed on SharePoint, not something you want to do.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Adding existing SQL Server 2012 to a New SQL 2012 Cluster

    We currently have a SQL 20012 Server setup and running on our domain.  We would like to switch this to a clustered environment.  Is it possible to setup the new  SQL 2012 Cluster and add the existing SQL 2012 server as a node in the cluster
    without losing any functionality.  All servers will be built with same drive letter.

    We currently have a SQL 20012 Server setup and running on our domain.  We would like to switch this to a clustered environment.  Is it possible to setup the new  SQL 2012 Cluster and add the existing SQL 2012 server as a node in the
    cluster without losing any functionality.  All servers will be built with same drive letter.
    No its not possible to convert standalone installation to cluster.Moreover first you need to configure Windows cluster then backup all SQL server databases logins jobs packages and install fresh instance of SQL Server in cluster aware mode
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • "The certificate chain was issued by an authority that is not trusted" when migrating to SQL 2012

    Environment:
    1 Primary Site (USSCCM-Site.domain.com)
    1 CAS (USSCCM-CAS.domain.com)
    SQL 2008 R2 (USSCCM-CAS.domain.com)
    SQL 2012 SP1 CU6 (USSQL12.domain.com)
    Issue:
    We were successfully able to migrate the CAS to the new SQL 2012 server, almost without incident. When attempting to migrate the Site instance however, we are getting errors. Screenshot below.
    Attached is a copy of the log. But below is a highlight of what I think are the errors… It appears that either SQL or SCCM doesn’t like a certificate somewhere, but it is contradicting because the logs say that it has successfully tested connection to SQL.
    I am lost.
    Logs stating it can connect successfully to SQL
    Machine certificate has been created successfully on server USSQL12.domain.com.        Configuration Manager Setup                10/21/2013 10:20:10
    AM               2100 (0x0834)
    Deinstalled service SMS_SERVER_BOOTSTRAP_USSCCM-Site.domain.com_SMS_SQL_SERVER on USSQL12.domain.com.  Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    SQL Server instance [sccmsite] is already running under the certificate with thumbprint[f671be844bf39dec7e7fdd725dc30e225991f28a].       Configuration Manager Setup    10/21/2013 10:20:10 AM        
    2100 (0x0834)
    INFO: Testing SQL Server [USSQL12.domain.com] connection ...                Configuration Manager Setup    10/21/2013 10:20:10 AM      
    2100 (0x0834)
    INFO: SQL Connection succeeded. Connection: USSQL12.domain.com SCCMSITE\MASTER, Type: Unsecure                Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: Tested SQL Server [USSQL12.domain.com] connection successfully.  Any preceding SQL connection errors may be safely ignored.            Configuration Manager Setup    10/21/2013
    10:20:10 AM               2100 (0x0834)
    INFO: Certificate: 308202FC308201E4A003020102021011BA47041BB0609D4097BC19F5AB96B5300D06092A864886F70D01010B0500301D311B301906035504031312555353514C31322E7063756265642E636F6D3020170D3133313031373139343632345A180F32313133303932343139343632345A301D311B301906035504031312555353514C31322E7063756265642E636F6D30820122300D06092A864886F70D01010105000382010F003082010A0282010100CFAC23CEA8920051C8C24DF4E96D76D9E034931867C4DBF74F8AE863C5BDE6D1EAEAAF363F6B97DEF1D7A1FC292CB870F353D72F04472EBE3D31DCA009BD3F8C58E2AAB69C892C20598306537F5EEAA43FA6DE55D4A784CEB6FD07486AB2CC2DE1A8651648EBC31A5CD918E8ED6E184FC560B3A8B0F76F83E310BBA8C4EB27F46707E3A6377D8DD06C6808146E407EF9DB464F453798B6C1748216665884A7F2CDE03D9DA1CB4E59E67516E4F345755E35450F84F4B039642851EFFA96B22D8E77EC11C01D389989F740923B58799E34FC8F4F19CD55830FA7E786C993A08A1EEDCA87F209268CE9D5E86AC9E2A14668207721D94ACE9FACE3AA55B53507F6BF0203010001A3363034301D0603551D11041630148212555353514C31322E7063756265642E636F6D30130603551D25040C300A06082B06010505070301300D06092A864886F70D01010B05000382010100A0E33BF490B60C2B8A73BF7FA90EBB69D92DA27B439EF0569650F388EBA34B9F382CEF52DAAB543C2924E1B8DC7BEE828FB0C276330B0FF67340CBFA0CC24F47431E5272DC76C7610C290A04411036441E9822FBF8AB52B4BBE43F5FF48074BA420FF690A94D53AFCEF7AC75E2D2723520A9EF64AF06759814AE92D41CEA2F0D6CC8D9E5DEF121234F5DD97A7E886BE55F57DC0B79052A554724E8A0146C08A74AE75672FBD8C8BD6B7FCA82C1CC69906A45128CDDD1BC3985ED9603C16E712FFBAA8AA6878F853367F3E1F69E727DB96864DF6B47EBDA82659036EC82A8B04E77535CEA314D7518D02C401969C77B91C8C210C57AA991A622D679B994AEED3C               
    Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: Created SQL Server machine certificate for Server [USSQL12.domain.com] successfully.    Configuration Manager Setup 10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: Configuration Manager Setup - Application Shutdown       Configuration Manager Setup    10/21/2013 10:20:10 AM         2100 (0x0834)
    INFO: Running SQL Server test query.    Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: SQL Connection succeeded. Connection: USSQL12.domain.com SCCMSITE\MASTER, Type: Secure                Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: SQL Server Test query succeeded.              Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: SQLInstance Name: sccmsite         Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: SQL Server version detected is 11.0, 11.0.3381.0 (SP1).      Configuration Manager Setup    10/21/2013 10:20:10 AM         2100 (0x0834)
    Logs saying certificate is not trusted
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:49 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:49
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:49 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:49 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:49
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:52 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:52 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:52
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:52 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:52 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:52
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:55 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:55 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:55
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:55 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:55 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:55
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:58 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:58 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:58
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:58 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:58 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:58
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:01 AM              
    2100 (0x0834)
    More logs saying cert is not trusted
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:20 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:21:20 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:21:20
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:21:20 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:21:20 AM              
    2100 (0x0834)
    INFO: Updated the site control information on the SQL Server USSQL12.domain.com.    Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:39 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:21:39 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:21:39
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:21:39 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    CSiteSettings::WriteActualSCFToDatabase: Failed to get SQL connection                Configuration Manager Setup               
    10/21/2013 10:21:39 AM               2100 (0x0834)
    CSiteSettings::WriteActualSCFToDatabaseForNewSite: WriteActualSCFToDatabase(USA) returns 0x87D20002                Configuration Manager Setup    10/21/2013 10:21:39
    AM               2100 (0x0834)
    ERROR: Failed to insert the recovery site control image to the parent database. Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    Troubleshooting:
    I have read on a few articles of other people having this issue that states to find the certificate on SQL 2012 that’s being used and export it to the SCCM server – which I’ve done.
    http://damianflynn.com/2012/08/22/sccm-2012-and-sql-certificates/
    http://trevorsullivan.net/2013/05/16/configmgr-2012-sp1-remote-sql-connectivity-problem/
    http://scug.be/sccm/2012/09/19/configmgr-2012-rtm-sp1-and-remote-management-points-not-healthy-when-running-configmgr-db-on-a-sql-cluster/
    -Brad

    Hi,
    How about importing certificate in the personal folder under SQL server computer account into SCCM server computer account or SCCM server service account? That certificate is for SQL Server Identification. And you could
    set the value of the ForceEncryption option to NO. (SQL Server Configuration Manager->SQL Server Network Configuration->
    Protocols for <server instance>->Properties)
    Best Regards,
    Joyce Li
    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.

  • DPM 2012 SP1 and SharePoint 2013 on a SQL 2012 AlwaysOn AG

    I am trying to protect a new SharePoint Foundation 2013 farm with it's databases stored on an SQL 2012 AlwaysOn Availability Group.  I've run configureSharePoint.exe -EnableSharePointProtection on my WFE and SharePoint shows up in DPM when I try to
    add it to a protection group.  But I get the 32008 referenced here: http://support.microsoft.com/kb/970641 when trying to select the farm to back up.
    If I run ConfigureSharePoint.exe -resolveallSQLAliases on the WFE it doesn't return anything.
    I'm directly backing up databases on the SQL 2012 server, but not any of the SharePoint DBs.
    K

    Hi,
    I'm having some trouble understanding what I'm seeing in the writer output from the WFE server.  Specifically the machine names that the writer is reporting.
    If you look in the wfewtiters.txt, What is the machine that ends in 02 ?  Is that a physical machine or an alias ?
    The machine ending in 06 is the Secondary SQL Server and that is what the Sharepoint writer is pointing to.
    The WFE VSS Sharepoint writer shows this for two content DB’s
     * WRITER "SharePoint Services Writer"
      - Writer ID   = {da452614-4858-5e53-a512-38aab25c61ad}
      - Writer instance ID = {c0c46d7b-1c01-44bd-8353-e3433f5b8f07}
      - Supports restore events = TRUE
      - Writer restore conditions = VSS_WRE_ALWAYS
      - Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
      - Requires reboot after restore = FALSE
      - Excluded files:
    + Component "SharePoint Services Writer:\XXXX02\WSS_Content_at.contoso.local"
    - Name: WSS_Content_at.Contoso.local
    - Logical path: XXXX02
    - Full path: \XXXX02\WSS_Content_at.Contoso.local
    - Caption: Content Database WSS_Content_at.Contoso.local
    - Type: VSS_CT_DATABASE [1]
    - Is selectable: TRUE
    - Is top level: TRUE
    - Notify on backup complete: FALSE
    - Paths affected by this component:
    - Volumes affected by this component:
    - Component Dependencies:
    - Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_at.contoso.local"
                                    + Component "SharePoint Services Writer:\XXXX02\WSS_Content_fw.Contoso.local"
    - Name: WSS_Content_fw.contoso.local
    - Logical path: XXXX02
    - Full path: \XXXX02\WSS_Content_fw.Contoso.local
    - Caption: Content Database WSS_Content_fw.Contoso.local
    - Type: VSS_CT_DATABASE [1]
    - Is selectable: TRUE
    - Is top level: TRUE
    - Notify on backup complete: FALSE
    - Paths affected by this component:
    - Volumes affected by this component:
    - Component Dependencies:
    - Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_fw.contoso.local"
    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. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

Maybe you are looking for