Installation of SCCM 2012 R2 and SQL Server 2014 error

Hello All,
I am attempting to setup SQL Server 2014 and SCCM 2012 R2 but I keep running into an error stating that "Configuration Manager requires Microsoft SQL Server
2008 SP2 w/ CU9........ all the way up to Microsoft SQL Server 2012 with CU2 or higher." I am using all evaluation versions for this configuration as we are looking to test and evaluate the products. I was trying it with SQL 2014 because I was running
into the same error with SQL 2012 and according to "http://blogs.technet.com/b/configmgrteam/archive/2015/03/30/updated-sc2012-configmgr-sp1-and-sc2012r2-configmgr-support-sql-server-2014.aspx" SQL
2014 is supported with SCCM 2012 R2. SQL is installed locally on the same box.
Any suggestions would be appreciated.
Thanks,
Tucker
Update: When running the Pre-Req check these are some of the failed returns.....
SQL Server Edition: Failed: Configuration Manager primary site and central administration site don't support SQL Server Express Edition
Not sure why it is recognizing SQL Express as this is a new machine.
SQL Server service running account: Failed: The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure
the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
For the SQL Service I am using a domain account created specifically for this.

This has nothing to do with moving or restoring. The kb article says "This hotfix provides updated versions of the setup files and enables new installations
of the System Center 2012 R2 Configuration Manager site database role and the System Center 2012 Configuration Manager SP1 site database role in Microsoft SQL Server 2014"
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

System Center Operations Manager 2012 R2 and SQL Server 2014 Reporting Services

I was able to connect SCOM12 to SQL14, however when I attempted to install Reporting Service in SCOM12 the pull down box was blank.
I installed reporting services on the same instance of SystemCenter, when that didn't work I tried creating a new instance that only included SSRS; remote registry is also running. The drop-down box within the SCOM installer is blank.
Is this an issue with reporting between SC12 and SQL14, yes I understand documentation says only sql server 2012 is supported, however I've seen many threads with SCOM12 and SQL12 that are having the same issues.
Is there something I may be missing, or do I have to install SQL12 and go through the process again?

Hi,
As far as I know, the SCOM reporting server role should be installed on the same server where SQL reporting service installed.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Is there a way to trick MS Service Manager 2012 to use SQL Server 2014 when installing it?

I recently set up a virtual Lab on my laptop. I dont have much resources on my laptop and can only have around 5 servers. the problem is that i already set up SQL Server 2014 standalone and configured all of my services to use that server which works
fine. however when i try to install MS Service Manager 2012 it throws "SQL has to be either 2012 or 2008" error ..
is there a way for me to trick the Registry so Service Manager will install?
Thank you

I don't know a trick to install SCSM 2012 on a SQL Server 2014. But maybe you can use a SQL Server 2012 for installation temporary and move the db after installation is done to your SQL Server 2014?
Moving the Service Manager and DW Databases
Might be worth a try. But it's definitely not recommended for a productive environment!
Andreas Baumgarten | H&D International Group

Unable to connect to report server - on Win 8.1 and SQL Server 2014

unable to connect to report server on Win 8.1 and SQL Server 2014 version
Microsoft SQL Server 2014 - 12.0.2000.8 (Intel X86)
   Feb 20 2014 19:20:46
   Copyright (c) Microsoft Corporation
   Express Edition on Windows NT 6.3 <X64> (Build 9600: ) (WOW64)
Thanks

Hi,
I suggest you check out the following article for the steps of installing
Database Engine Services and SQL Server Reporting Service.
http://msdn.microsoft.com/en-us/library/ms143711.aspx
Best Regards,
Tracy
Tracy Cai
TechNet Community Support

Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

Hello everyone,
I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
https://msdn.microsoft.com/en-us/library/cc280547.aspx
Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
Please share your experience.
Any help would be much appreciated.
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello Arthur,
Thank you for the response.
I just got an access of the packages. They are of VS 2008 and not 2010.
Do you know how to upgrade VS 2008 packaged to VS 2013?
When I tried to open the solution file in VS 2013, it says "incompatible".
Any help would be much appreciated.
Thanks,
Ankit
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Which Laptop is good for VS 2012/2013 and SQL SERVER 2008 R2 /2012 ?

Hi,
I am planing to buy a laptop.
I am gonna be using mostly for Visual sStudio 2013 and Sql Server 2012 .
my budget is $1000.
confuse between DELL/ HP / LENOVO..!!!
please help.

This is only a personal taste of mine:
I prefer to work in Virtual Machines. In fact I did set up a VM just for my programming. This has the advantage that games and other stuff are not slowed down by SQL Server Services and similiar stuff.
This also allows me to quickly make a small virtual networks with multiple clients if I need to test some client/server stuff.
Plus I am also a bit of an adminstrator and prefer to test stuff in VM's before I try them in the real world.
I prefer using Virtual Box for Virtual Machines, so one thing of big importance was support for VT-X/AMD-V. Without them Virtual Box cannot run x64 guests even on a x64 host system.
Otherwise I wanted Windows 8 (so I could finally learn to live with it/learn programming for it's UI). And of big importance was an upgrade of gaming ability (my old one had difficulty/impossibility to run most current games).
So I bought a x64, Win8 Gaming Laptop with 8 GiB RAM (so I can run 3-6 Windows 7 hosts in paralell) and looked that the CPU supported Hardware Virtualsiation.
Otherwise pretty much every current laptop will work. x64 OS might be prefereable, as .NET has some limitations under x32/x86 OS (like the
2 GiB limit). Multicore (2 or more) is pretty much the state of the art (are there still any single core CPU's out there?).
It of course needs to be a Windows (7 or 8) to support VS. New Laptops should have UEFI (all that are sold with Windows 8 have).
If you do not need a lot of storage, using a SSD instead of a HDD will propably speed up startups (Windows, Programms) and compilation times a lot (those are disk-heavy operations) - but I only know that it should and heard of people who have them.
Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
Given:
1) Operating System Windows 2012 R2
2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource. The two VMS are called APPS08 and APPS09. They are our development environment that is setup similar to our production environment.
Problem: When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance. I then moved onto upgrading on the node that was running the instance. As soon as the install attempt to failover the running instance
an install error occurred that it could not failover. After many install attempts I consistently received the error
The SQL Server Failover cluster instance name 'Dev01'
already exists as a cluster resource. Opening Failover cluster manager there is no record of a DEV01.
New Strategy: Create a SQLCluster called DEV07. At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists. Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.
We do not see anything out of the ordinary.
Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

Hi PSCSQLDBA,
As your description, you want to upgrade the default instance in SQL Server cluster.
>> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
This error could occur when there is a previously used instance name which may not be removed completely.
To work around the issue, please use one of the ways below.
1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
For more information about the process, please refer to the article:
http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
For more information about the process, please refer to the article:
http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
>> 'Resource for instance 'MSSQLSERVER' should not exist'
This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
Regards,
Michelle Li

How to restore a database backup taken from a SQL Server 2012 instance to SQL Server 2014

I am trying to restore a database backup taken from a SQL Server 2012 instance to my new SQL Server 2014 instance. When I add the .bak through the Mgmt studio UI, it does not seem to find a backup set in the file so I cannot proceed (does not give
me any errors though either. I tried restoring through TSQL command but only got a database restore terminating abnormally error with no other details. How can I restore this database to SQL 2014?

Hello,
Please examine SQL Server Error Log and share with us any error you can find. The following article may locate the log:
http://msdn.microsoft.com/en-us/library/ms187109.aspx
Regards,
Alberto Morillo
SQLCoffee.com

MS SQL Server 2014: Error inserting into Temp table with index and identity field

In this thread, I mentioned a problem with SQL Server 2014:
SQL Server 2014: Bug with IDENTITY INSERT ON
The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
Problem:
The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
after the insert, does not help.
SET NOCOUNT ON
GO
IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
GO
CREATE PROC dbo.usp_Test AS
BEGIN
SET NOCOUNT ON
CREATE TABLE #Source(ID integer NOT NULL);
INSERT INTO #Source VALUES (1), (2), (3);
CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
CREATE INDEX #IDX_Dest ON #Dest (ID);
PRINT 'Check if the insert might cause an identity crisis';
SELECT 'Source' AS SourceTable, * FROM #Source;
SELECT 'Destination' AS DestTable, * FROM #Dest;
SET IDENTITY_INSERT #Dest ON;
PRINT 'Do the insert';
INSERT INTO #Dest (ID) SELECT ID FROM #Source;
PRINT 'Insert ready';
SET IDENTITY_INSERT #Dest OFF;
SELECT * FROM #Dest;
DROP TABLE #Source;
DROP TABLE #Dest;
END;
GO
PRINT 'First execution of the proc, everything OK';
EXEC dbo.usp_Test;
PRINT '';
PRINT 'Second execution of the proc, the insert fails.';
PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
EXEC dbo.usp_Test;
GO
DROP PROC dbo.usp_Test;
GO

There is some progress. Communication from a former Microsoft employee tells us this:
Shivendra Vishal
Engineer at Microsoft
I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
sqlmin!SetidentI2I4+0x1f3:
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
r14=00000001f49c3860 r15=00000001f58c0040
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
The stack is:
# Child-SP RetAddr Call Site
00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
Unassembling the function:
000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d86591 4533e4 xor r12d,r12d
000007fe`f4d86594 410fb7d5 movzx edx,r13w
000007fe`f4d86598 4533c9 xor r9d,r9d
000007fe`f4d8659b 4533c0 xor r8d,r8d
000007fe`f4d8659e 488bc8 mov rcx,rax
000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
000007fe`f4d865bf 4533c9 xor r9d,r9d
000007fe`f4d865c2 488bc8 mov rcx,rax
000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
000007fe`f4d865d6 488bc8 mov rcx,rax
000007fe`f4d865d9 4c8bf0 mov r14,rax
000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
000007fe`f4d865e6 488bc8 mov rcx,rax
000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
It is not getting simulated for other versions of SQL apart from SQL 2014.
Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea.

RDS 2012: Compatible with SQL Server 2014 AlwaysOn?

Is Remote Desktop Services 2012 R2 compatible with SQL Server 2014 AlwaysOn Availability Groups? Are there any procedural documents available for RDS requirements on how it expects AlwaysOn to be configured?
Thanks

Hi,
Thank you for posting in Windows Server Forum.
As per my research, we can install SQL server 2014 on RDS Server 2012\R2, you can check below article with step by step guide.
How to install SQL Server 2014
In addition for SQL AlwaysOn Consideration there is useful blog (RDS 2012 SQL AlwaysOn Considerations) you can go through for details.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014 using BISM file connection

I am getting following error while refreshing connection on excel sheet in power pivot gallery,
my scenario,
using BISM file connection to create and refresh power pivot excel sheet in power pivot gallery
throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
Microsoft.AnalysisServices.ChannelTransport is not available.
i found error in event viewer,
"Activation context generation failed for "C:\Program Files\Microsoft Analysis
Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
what should i do to fix it?
Thanks for help.
Deepak Patel

Rebecca,
yes, this is issue i am getting.
Activation
context generation failed for "C:\Program
Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
let me know if you can find fix for it.
THanks,

SharePoint 2013 and SQL Server 2014

Does SharePoint 2013 supports SQL Server 2014 for Reporting Services, PowerPivot

Yes it does (or rather, SSRS 2014/PowerPivot 2014 support SharePoint 2013). They also support SharePoint 2010.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Is SSRS 2012 compatible with SQL Server 2014?

Will it still work if a DW database is in SQL Server 2014 but the reporting services is in SSRS 2012?

Very likely. If not, probably will be at the next service pack.
Kalman Toth Database & OLAP Architect
T-SQL Scripts at sqlusa.com
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL SERVER 2014 Error :40

""A network-related or instance-specification error occured while establishing a connection to SQL Server "" Windows Firewall is on ! what should i do , or change to connect , please help , please

QUOTE from an article on the topic: "
Firstly,
Make sure your database engine is configured to accept remote connections
• Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration • Click on Surface Area Configuration for Services and Connections • Select the instance that is having a problem > Database Engine >
Remote Connections • Enable local and remote connections • Restart instance - See more at:
http://www.sswug.org/articlesection/default.aspx?TargetID=44331#sthash.kzSfADZL.dpuf
Secondly,
You may need to create an exception on the firewall for the SQL Server instance and port you are using • Start > Run > Firewall.cpl • Click on exceptions tab • Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft
SQL Server\MSSQL.x\MSSQL\Binn, check your installs for the actual folder path), and port (default is 1433) • Check your connection string as well - See more at:
http://www.sswug.org/articlesection/default.aspx?TargetID=44331#sthash.kzSfADZL.dpuf
Thirdly Check if your SQL server services is up and running properly
Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Services, and check if SQL Server service status is “Running”.
In addition, ensure that your remote server is in the same network. Run “sqlcmd -L” in your command prompt to ascertain if your server is included in your network list. You can even find tutorial for the same here SQL SERVER – Find All Servers From Local
Network – Using sqlcmd – Detect Installed SQL Server on Network.
Next Enable TCP/IP in SQL Server Configuration
Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP. Right click and select enable
Lastly Go to your firewall setting, under exception tab, select add port include TCP:1433 and tick the SQL check box."
LINK:
http://stackoverflow.com/questions/18060667/connect-to-server-a-network-related-or-instance-specific-error
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Sql Server 2014 - Error message: Failed to read BLOB column

Hi all,
Am experiencing this error in Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Enterprise Edition (Build 7601: Service Pack 1).
Error messages:
Message: Failed to read BLOB column
Stack:    at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String
strWhereClause, Boolean useTableLockHint, Int32 bcpFileFormatVersion)
   at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem)
   at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
   at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)
Get help: http://help/0
Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Please can you assist me on this issue.

The error message states a communication link failure has occurred.
This is most likely a network related error and usually is transient.
Try to generate the snapshot again and see if the error still occurs. If the error still occurs, you will need to have a network admin check the links.
Brandon Williams (blog |
linkedin)

Installation of SCCM 2012 R2 and SQL Server 2014 error

Similar Messages

Maybe you are looking for