SQL 2012 spt_values

Hi,
Our spt_values view is missing on our SQL 2012 server. I tried running the u_tables.sql file to fix it, but I get the following error:
Msg 208, Level 16, State 1, Procedure spt_values, Line 7
Invalid object name 'sys.spt_values'.
sp_MS_marksystemobject: Invalid object name 'spt_values'
Msg 15151, Level 16, State 1, Line 2
Cannot find the object 'spt_values', because it does not exist or you do not have permission
How can we fix this on 2012?
Thanks!
-Mike

Hi Mike,
According to your description, the u_tables.sql file can be used to create the spt_values table in SQL Server 2008 or SQL Server 2008 R2. But it will fail when you use the u_tables.sql file to create the spt_values view in SQL Server 2012 because the table
sys.spt_values doesn’t exist.
To solve this issue, I recommend you to restore the master database if you have a backup of master database which contains the view dbo.spt_value. For more details about restoring master database, you can review this blog:
HOW TO: Restore the Master Database in SQL Server 2012. However, If you don’t backup the master database, you can try to rebuild the master database then recreate logins, linked servers, jobs and so on. For more details. please review this article:
Rebuild System Databases.
Thanks
Lydia Zhang

Similar Messages

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).

Object reference not set to an instance of an object. Unable to finish the SQL 2012 installation on a VM Machine

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 instructions

Hello,
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.
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.

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, Dinesh

Thank 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/
-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.

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

32-bit iFilter with Reader 11.0.10 cannot be found by SQL 2012 Fulltext Indexing on Windows 7 32 bit. How can I fix this?

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,
Dave

I 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.

Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015. SQL 2012 SP1

Hi,
Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'.
Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
is not a possible owner of the resource.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
BUTTONS:
OK
I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
application SQL Server SG1DB. Could not move the resource to available storage. An error occured
while moving the resource BCK_SG1DB to the clustered service or application Available Storage
Any ideas why it failed or how could I delete the SQL server instance from Clauster?
Thx

Hello,
Please read the following resource.
https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to configure log files in SQL 2012?

I'm installing a SharePoint Solution and using Microsoft SQL 2012 and I have limited knowledge in installing SQL. I simply run the wizard and create the DB for SharePoint.
Is there any links/materials available demonstrating how to correctly configure the log files step by step in a specific partition during the SQL installation for SharePoint 2013?
thanks,

Hello,
SQL Server database log files benefit from RAID 1 and RAID 10 configurations. RAID 10 is recommended for both data files and log files.
To control de grow of transaction log files, please backup them regularly. The following article may explain you in detail why:
http://technet.microsoft.com/en-us/library/ms175495.aspx
Monitor the growth of log files using Performance Monitor and the SQLServer:Databases --> Log Growths counter. Adjust the size of log files until Log Growths
is constantly zero.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error while trying to upgrade SQL 2008 (SP2) to SQL 2012: There was a failure to calculate the applicability of setting LICENSEPATH.

Hi,
I am trying to upgrade one of our SQL Server Enterprise (2008 (SP2)) to 2012. I am using the upgrade option but it gives me the following error:
Error Code 0x85640002: There was a failure to calculate the applicability of setting LICENSEPATH
We have downloaded the image from our Volume Licensing account. Also, the same image was used to install SQL 2012 on Windows Server 2012 R2 servers without any issues.
Below is the install summary.txt. I have tried everywhere but no go. Would really appreciate any assistance.
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2057043966
Exit facility code:            1380
Exit error code:               2
Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
Start time:                    2014-02-28 10:58:49
End time:                      2014-02-28 10:58:58
Requested action:              RunRules
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9
Machine Properties:
Machine name:                  xxxxxxx
Machine processor count:       2
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     U.A.E.
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         D:\x64\setup\
Installation edition:
User Input Settings:
ACTION:                        RunRules
CONFIGURATIONFILE:
ENU:                           true
FEATURES:
HELP:                          false
INDICATEPROGRESS:              false
INSTANCENAME:                  <empty>
PID:                           *****
QUIET:                         true
QUIETSIMPLE:                   false
RULES:                         GlobalRules
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140228_105848\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
    Message:
        There was a failure to calculate the applicability of setting LICENSEPATH.
    HResult : 0x85640002
        FacilityCode : 1380 (564)
        ErrorCode : 2 (0002)
    Data:
      SettingId = LICENSEPATH
      WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
    Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
        Message:
                There was a failure to calculate the default value of setting LICENSEPATH.
        HResult : 0x85640001
                FacilityCode : 1380 (564)
                ErrorCode : 1 (0001)
        Data:
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
        Stack:
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        Inner exception type: System.ArgumentException
            Message:
                        Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
            Stack:
                        at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                        at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate
subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
Regards,
Mohammed

Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
This appears to be the root problem. It seems that the regional settings on this machine is messed up. 0x0C00 is an unusual LCID, they do not normally not end in two zeroes.
is there a custom culture installed on this machine?
Review the regional settings and also check the System locale. If it looks spooky, set it to Arabic - U.A.E. if this is where you are located.
Erland Sommarskog, SQL Server MVP, [email protected]

Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   OS service pack:
   OS region:                     United States
   OS language:                   English (United States)
   OS architecture:               x64
   Process architecture:          64 Bit
   OS clustered:                  No
Product features discovered:
   Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
   Description:                   Microsoft SQL Server 2012
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
   Installation edition:          Standard
Product Update Status:
   None discovered.
User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   CLTCTLRNAME:
   CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
   CLTSTARTUPTYPE:                Manual
   CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
   CLTSVCPASSWORD:                <empty>
   CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
   COMMFABRICENCRYPTION:          0
   COMMFABRICNETWORKLEVEL:        0
   COMMFABRICPORT:                0
   CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          false
   INDICATEPROGRESS:              false
   INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
   INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
   INSTALLSQLDATADIR:             <empty>
   INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
   INSTANCEID:                    MSSQLSERVER
   INSTANCENAME:                  MSSQLSERVER
   ISSVCACCOUNT:                  NT Service\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
   Feature:                       Database Engine Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Analysis Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - SharePoint
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services Add-in for SharePoint Products
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Controller
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Data Tools
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData =
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this ..

Error while configuring SQL 2012 DB as a Subscriber to a Oracle Publisher.

When Configuring the Subscription for Oracle as a publisher, we receive the following error message.
Msg 18757, Level 16, State 4, Procedure sp_replpostcmd, Line 1
Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
The Subscriber was dropped.
Same message is received if add the subscription through script or through SQL Management studio.
However Oracle as a publisher has been configured successfully on a SQL 2012 DB server, Which is also the Distribution server
using the following links.
https://msdn.microsoft.com/en-us/library/ms151243(v=sql.110).aspx
https://msdn.microsoft.com/en-us/library/ms152481(v=sql.110).aspx
Note: Same Steps successfully work from a SQL 2008 Machine. i.e If i use SQL 2008 machine to configure Oracle as a Publisher and then subscribe to SQL 2012 machine as Subscriber.
Is there a known issue? or some extra steps for 2012 that are not documented. Any help will be much appreciated.
Client Oracle Version:9i
Subscriber DB Version: SQL Server 2012 SP2
Thanks and Regards, Ibrahim Mehdi. MCSE-DataPlatform

Yes . The SQL Server 2012 is EE.
As Informed before, The Oracle Publisher configuration is working successfully without any error. It is giving the error provided while trying to create a subscriber to this Oracle Publisher.
Thanks and Regards, Ibrahim Mehdi. MCSE-DataPlatform

SQL 2012 spt_values

Similar Messages

Maybe you are looking for