SQL 2012 Witness suspended?
Hi All,
We have x2 SQL 2012 servers configured in a mirrored setup and are using an offsite (non-domain) server as our witness. This setup has been working fine for some time. Yesterday we had an internet outage which of course meant that the witness
server could not be contacted by either of the SQL servers. This was confirmed by going into management studio and seeing the witness listed as 'disconnected'. Around 4 hours later the internet connection was restored and we could see the witness
(from a networking perspective) but SQL server just refused to use it or acknowledge that it was up again. We have run all kinds of tests that prove that the previous working configuration is still valid so why wont SQL accept the witness now that it
can be contacted again? Is there something we have to do on the x2 SQL servers to resume the witness functionality?
Any help greatly appreciated!
Cheers
Rob
Hi,
1. Make sure that you are able to ping of FDQN among the three servers successfully.
2. Make sure the servers are listening on the correct ports.
Use:
SELECT type_desc, port FROM sys.tcp_endpoints;
3. On the Principal server, use ALTER DATABASE <database_name>
SET WITNESS OFF to remove the witness. Then re-add the witness by using ALTER DATABASE <database_name> SET WITNESS =’TCP://<system-address>:<port>’. Also, check the error log on witness server.
Thanks.
Tracy Cai
TechNet Community Support
Similar Messages
-
SQL 2012 Database Availability Group - Force Automatic Failover
Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
BobHi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob -
SQL 2012 AlwaysOn AG with 3 Nodes
First, what would be the best option of quorum/quorum witness for my SQL 2012 AlwaysOn group?
I have setup the following:
SQL 2012 AlwaysOn with 3 nodes.
1 primary
2 secondaries - one of them is read-only (for reporting and backup)
Dynamics CRM and Reporting DBs are running on them.
How can I achieve the highest avalability and DR with my SQL? Do I even need to create the quorum witness? What kind of Quorum (majority nod with network share?)
Second, Is it good idea to run the backup on that read-only node? If I setup the maintenance plan on this 3rd read-only mode with full and transactional backups, I should be able to restore without any issues?
Third, I have another DB (SharePoint) that needs to be moved over to this SQL AlwaysOn AG but wondering if I can restore it in the secondary node to utilize the unused resources. Is that possible or not recommended?Are the replicas on the same network subnet? If they are, then, you already have a quorum with node majority (odd number of votes.) Since you are already paying for an additional license to run read-only workloads on your readable secondary, you can take
backups on this replica. Full database backups are in COPY_ONLY mode but you can take regular log backups which will truncate the log on the primary replica. In theory, you will be able to restore the backups taken from your readable secondary but you should
test (hence, why I mentioned "in theory.") I wouldn't move my SharePoint databases to this SQL Server Availability Group mainly because of the different requirements between the two - SharePoint and Dynamics CRM. MAXDOP =1, disabling index maintenance and
statistics updates on SharePoint databases, etc. are just a few of them. Besides, I doubt that the recovery objectives and service level agreements between those two applications are the same within your organization.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course -
Lync 2013 SQL Backend Witness replacement
Can we replace backend SQL witness server via lync 2013 topology builder as H/W of existing witness server needs to be released due to some technical reason.
We don’t prefer P2V. I want fresh installation of SQL witness server with SQL 2012 express edition and then move the witness role
What is the procedure for the same?
Please help me for the sameHi,
deploy the new SQL server which dedicated for Witness. Configure the topology and associate the new SQL server as the witness server and publish. remove the old SQL store which was configured as the Witness form the topology.
Z-Hire -- Automate Lync User Account creation process ( AD / Exchange / Lync ) -
Trouble installing SQL 2012 CU7 on an AlwaysOn environment
Windows Server 2012 R2 Datacenter
SQL server 2012 Developer (64 bit)
Failover Cluster
AlwaysOn Availability Group running
Trying to install CU7 for SQL 2012 and get the following error:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Error details:
§ Error installing SQL Server Database Engine Services Instance Features
There was an error to lookup cluster resource types. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4154. Description: Invalid object path.
Error code: 0x86D80018
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3393.0&EvtType=0xE8049925%400x42B4DED7&EvtType=0xE8049925%400x42B4DED7 to get help
on troubleshooting.
Has anyone run across this issue?It doesn't appear to be what's happening here. Below is the output from "ClusterResourceType":
PS C:\Windows\system32> Get-ClusterResourceType
Name DisplayName
DFS Replicated Folder DFS Replicated Folder
DHCP Service DHCP
Service
Disjoint IPv4 Address Disjoint IPv4 Address
Disjoint IPv6 Address Disjoint IPv6 Address
Distributed File System Distributed File System
Distributed Network Name Distributed Network Name
Distributed Transaction Coordinator Distributed Transaction Coordinator
File Server File
Server
File Share Witness File Share Quorum Witness
Generic Application Generic Application
Generic Script
Generic Script
Generic Service Generic
Service
IP Address
IP Address
IPv6 Address
IPv6 Address
IPv6 Tunnel Address IPv6 Tunnel Address
iSCSI Target Server iSCSI Target Server
Microsoft iSNS
iSNS Cluster Resource
Nat
Network Address Translator
Network File System Network File System
Network Name
Network Name
Physical Disk
Physical Disk
Provider Address Hyper-V Network
Virtualization Provider Address
RAM Disk (SuperSpeed LLC) RAM Disk (SuperSpeed LLC)
Scale Out File Server Scale Out File Server
SQL Server Availability Group SQL Server Availability Group
SQL Server FILESTREAM Share SQL Server FILESTREAM Share
Storage Pool
Storage Pool
Task Scheduler Task
Scheduler
Virtual Machine Virtual
Machine
Virtual Machine Configuration Virtual Machine Configuration
Virtual Machine Replication Broker Virtual Machine Replication Broker
WINS Service WINS
Service
Thanks,
Darren. -
We need to move an SQL DB, so we decided to upgrade at the same time.
The upgrade will be both in software and hardware.
My question, can we setup a mirror between SQL 2012 and SQl 2005 in order to migrate the DB's to new hardware and SQL instance?
Thanks!Hi wmikef,
We cannot set up a mirror between SQL Server 2012 and SQL Server 2005. Please note that the
prerequisites for setting up database mirroring.
• For a mirroring session to be established, the partners and the witness, if any, must be running on the same version of SQL Server.
• The principal server and mirror server, must be running the same edition of SQL Server. The witness, if any, can run on any edition of SQL Server that supports database mirroring.
• The database must use the full recovery model.
• Verify that the mirror server has sufficient disk space for the mirror database.
• Make sure that you restore the backup of the principal database specifying the same database name WITH NORECOVERY when creating the mirror database on the mirror server.
For more information, please review the following article.
http://msdn.microsoft.com/en-us/library/ms366349.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here. -
Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1
I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support -
T-sql 2012 accept null parameter values
The following t-sql 2012 works fine in sql management studio. However when I place it in a .net 2010 web form application, I am told the sql does not work when the parameter values are null. Thus can you tell me what I can change in the sql below that will
accept null as 3 possible input values?
SELECT i.[lastName]
,i.[firstName]
,i.[middleName]
,i.[suffix]
,a.[userid]
,a.schoolnum
,a.spa
,a.mrref
from [OPS].[dbo].[Identity] i
inner join [OPS].[dbo].[Person] p on i.identityID = p.currentIdentityID
inner join [OPS].[dbo].[UserAccount] u on u.personID = p.personID
inner join [CampusOps].[dbo].[AtnLtrUsers] a on a.userid =u.username
where (i.[lastName] like '%' + @lname + '%' or i.[firstName] like'%' +
@fname + '%'
or i.[middleName] like'%' + @mname + '%')
or (@fname is null and @lname is null and @mname is null)
order by i.[lastName], i.[firstName], i.[middleName]"You should create a stored procedure for this.
create procedure GetNames
(@lname varchar(max) = null, @fname varchar(max) = null, @mname varchar(max) = null)
as
begin
SELECT i.[lastName]
,i.[firstName]
,i.[middleName]
,i.[suffix]
,a.[userid]
,a.schoolnum
,a.spa
,a.mrref
from [OPS].[dbo].[Identity] i
inner join [OPS].[dbo].[Person] p on i.identityID = p.currentIdentityID
inner join [OPS].[dbo].[UserAccount] u on u.personID = p.personID
inner join [CampusOps].[dbo].[AtnLtrUsers] a on a.userid =u.username
where (i.[lastName] like '%' + @lname + '%' or @lname is null) and
(i.[firstName] like'%' + @fname + '%' or @fname is null) and
(i.[middleName] like'%' + @mname + '%' or @mname is null)
order by i.[lastName], i.[firstName], i.[middleName]
end
Also keep in mind that NULL is different than an empty string but it should work exactly like a null anyway (unless your columns/fields are also NULLable). -
Hi, My name is Leonard and I am studying SQL. I have downloaded the newest MS SQL 2012 and also MS 2012 Hyper-V. I have set a MS 2012 Hyper-V on a laptop with AMD Turion 64 X2 and 3G of RAM (Planing
to add more to max at 8G).
Following the instructions in the free online
Administering Microsoft SQL Server 2012 Databases” Training Kit, I have set 6 virtual machines as instructed in the Training Kit. While the installation of the MS Server Core 2008 R2 SP1 completed with no
problem, the same cannot be said for the SQL Server 2012 installation. I have encountered an error that I have not seen anyone address in any of the SQL web forums.
After running the unattended setup instruction (Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER
/SQLSVCACCOUNT="Njowa\Pa$$worD>" /SQLSVCPASSWORD=" Pa$$worD” /SQLSYSADMINACCOUNTS="Njowa\lenny#4!@" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"
/IACCEPTSQLSERVERLICENSETERMS) this is what I get after a series SQL setup
initiation windows popups then disappears.
The following error occurred:
Object reference not set to an instance of an object.
Error result: -2147467261
Result facility Code: 0
Result error Code: 16387
Please review the summary.txt log for further details
My question is: What instance of an object is not properly initialize in the Setup instructionsHello,
Please note that SQL Server requires at least 1 GB of RAM. The operating system (Windows Server) requires 2 GB of RAM (recommended) or 512 MB (minimum). This means any virtual machine that will receive the installation of a SQL Server instance requires 1.5
or 2 GB at least.
The behavior of SQL Server setup tells me that the virtual machine does not have enough memory assigned or .NET Framework 3.5 was not enable on Control Panel->Program
and Features before trying to install SQL Server.
The following thread is about another possible cause of this error:
http://social.msdn.microsoft.com/Forums/mr-IN/sqlsetupandupgrade/thread/575d3025-69f5-4152-a473-44496b008811
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
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.
KHi,
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. -
Issue with SSIS Custom Components - 64 bit SQL 2012
Hello All,
Our SSIS packages built on SQL 2008 R2 make use of some custom components. These custom components are installed as part of an MSI. The dll's are copied over to the Windows/assemble [GAC Folder] and also to the Program Files(x86)/SQL Server/110/DTS/* folder.
The installation does not copy the dll's to the 64 bit program files folder.
X:\Program Files\Microsoft SQL Server\110\DTS
These packages are executed via SQL Agent jobs on a 64 bit SQL server and there does not seem be any issue.
Now we are upgrading our servers to SQL 2012 and we have a new installer for the custom components as well. The new custom components use .NET Framework 4.0 and when installed the dll files get copied over to the Ms.NET 32 bit runtime GAC folder and also
to the SQL Server DTS Folder in x86. The upgraded packages work only when we set the runtime mode to 32 bit. The packages successfully executes within the 32 bit dtexec utility, but when we try to run the same package using a 64 bit dtexec utility the
process errors out with a component failed to load message. The package moves data between two SQL Server instances.
The custom components have always been built for 32 bit runtime. I can run a older package through the dtexec utility (from the 64 bit folder in program files) and it does work without any issues. After the upgrade the package will only execute on
a 32 bit utility. can someone help me understand this issue?
Regards, DineshThank you Arthur.
i think we got the answer as well, as the .NET framework 3.0 installer copied the files over to the C:\windows assembly the dtexec utility [32 bit/64 bit] was able to load the components.
Now with the new installer the files are copied to specific runtime gac folders as Arthur has mentioned. The 64 bit utility does not find the dlls in the GAC whereas the 32 bit version will find them.
Regards, Dinesh -
"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/
-BradHi,
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. -
SQL 2012 AlwaysON High Availability for SharePoint 2013
Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
We got one more Server & we don't have Storage so need to configure Always On.
There are Some Confusions:
1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
2- What are the Changes need to be done on Production Server?
3- What are the Steps to be followed While Configuring new Database Server?
Regards,Hi Genius1985,
According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
to the following article:
http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012. This needs to be done on all of the SQL Server instances that we will configure as replicas in our
Availability Group.
For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li -
I have verified that a record shows up in the fulltext system components (EXEC sys.sp_help_fulltext_system_components 'filter').
componenttype componentname clsid fullpath version manufacturer
filter .pdf E8978DA6-047F-4E3D-9C78-CDBE46041603 C:\Program Files\Adobe\Reader 11.0\Reader\AcroRdIF.dll 11.0.0.379 Adobe Systems, Inc.
I have also added Reader's installation folder to my system PATH variable, and ran these 3 things:
EXEC sp_fulltext_service 'update_languages';
EXEC sp_fulltext_service 'load_os_resources', 1;
EXEC sp_fulltext_service 'restart_all_fdhosts';
and then dropped and re-created my fulltext index. For each row in the table, I receive a message like this:
Warning: No appropriate filter was found during full-text index population for table or indexed view '[DocumentIndexing].[dbo].[Document]' (table or indexed view ID '277576027', database ID '8'), full-text key value '17'. Some columns of the row were not indexed.
In the Registry, under HKEY_CLASSES_ROOT / .pdf / PersistentHandler is the value {F6594A6D-D57F-4EFD-B2C3-DCD9779E382E}.
I have tried several times to install/fix my PDF installation, restart SQL Server, Reboot my laptop, etc. All to no avail.
I saw the article on the 64-bit filter and was able to successfully do that on another workstation (Windows 8.1 64-bit SQL 2012). However, I really need this working on my laptop.
Do you have a solution or workaround or some recommendations for me to move forward with this?
Thanks,
DaveI found the solution. Here it is:
Take backup of below registry key.
HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Then delete the braces.
Try to reboot and start the SQL service . If service don’t start then Uninstall and reinstall SQL.
The MachineGuid had curly braces so I removed them and rebooted my laptop. Now both instances of SQL Server start. It is the last post of this thread:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/56f14665-3f00-41ff-b002-bb5e86b3f219/sql-server-not-starting-fallback-certificate-initialization-failed?forum=sqlsecurity
He states that he got it from Microsoft but did not give the url.
Thanks for all your help.
Fred Schmid -
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.
Maybe you are looking for
-
Report Designer Control - Redistribution Issue
Hi: I use Report Designer Control(RDC) in my program to allow user to modify reports. I made a build and installed the build but when I try to access report designer from program I am getting the error about license. "This system does not have a va
-
We have a situation in our project. We have weblogic8 sp5 server having a MDB deployed which consumes messages from distributed queues created on WLS8. OSB business services post messages on these distributed destinations. Set up: Non production envi
-
Is there a way to run Windows programs on an Ultra SPARC 64-Bit Solaris 10?
I know the answer is more than likely going to be no, but I just thought I would ask... I have an Sparc Ultra-60 running Solaris 10 64-Bit sitting here that is a web / forum / ftp server, and I would like to run a Telnet BBS program on it that is a W
-
The -profile command line switch is not passed to the windows 7 jumplist properly.
I start Firefox with a shortcut like this one: "C:\Program Files (x86)\Mozilla Firefox\firefox.exe -no-remote -profile SomeProfileButNotTheDefaultOne -win7appid SomeUniqueAppId". When pinning to the Windows 7 taskbar, the jumplist items "New Tab" and
-
Will Oracle be making any enchancements to the Essbase Excel Add-in?
Will Oracle be making any enchancements to the Essbase Excel Add-in?