Overall summary:
  Final result:                  Failed: see details below

Exit code (Decimal):           -2055733247

  Exit facility code:            1400
  Exit error code:               1
  Exit message:                  A publishing loop has been detected by the PublishingQueue, which has LoopThreshold=10000, while publishing to the subscribed delegate "Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()".

Machine Properties:

  Machine name:                  x
  Machine processor count:       8
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   Deutsch (Deutschland)
  OS architecture:               x64
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2008 R2                                                       Management Tools - Basic                 1033                 Standard Edition     10.52.4321.0    No         Yes       
  SQL Server 2008 R2                                                       Management Tools - Complete              1033                 Standard Edition     10.52.4321.0    No         Yes       
  SQL Server 2008 R2                                                       Client Tools Connectivity                1033                 Standard Edition     10.52.4321.0    No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         \\xx\Media\DVD_1\SQL2014STDSP1\SQLFULL_ENU\x86\setup\
  Installation edition:          Standard

Product Update Status:
  None discovered.

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.Deployment.PrioritizedPublishing.PublishingLoopException
    Message: 
        A publishing loop has been
        FacilityCode : 1400 (578)
        ErrorCode : 1 (0001)
    Data: 
      Threshold = 10000
      DelegateDescription = Microsoft.SqlServer.Configuration.SmartSetupExtension.SelectedUpdatesSetting : Void CalculateValue()
      WatsonData = Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingLoopException@1
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.Publisher.Publish()
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.set_Value(T value)
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.SetValue(Object newValue, InputSettingSource source)
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.SetSettingValue[T](String settingName, T value, InputSettingSource source)
        at Microsoft.SqlServer.Configuration.SetupExtension.ComponentUpdateProgressMsgFormatter.SetProgressMessage(Object notification, Object[] objectArray)
        at Microsoft.SqlServer.Chainer.Infrastructure.NotificationService.OnNotify(Object eventKey, Object notification, Object[] objectArray)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifySkipped(ActionKey skippedAction)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.SequenceStep.EvaluateState(Boolean noisy, TextWriter logging)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionScheduler.SequenceReadyActions(List`1 readyActions, TextWriter logging)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
        at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

Hello,

Could you try to copy the SQL Server media from the remote location and copy it to the local C:\ drive? Please create a folder on the C:\ drive (C:\SQLMedia), copy the media there and run setup from there.

Hope this helps.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Shanky_621MVP 14 hours 58 minutes ago

I would like to see setup logs if setup failed even after running locally, as suggested by Alberto.

I am quite sure the problem is because of

\\xx\Media\DVD_1\SQL2014STDSP1\SQLFULL_ENU\x86\setup\

There is also a wired error message which I have never seen and AFAIK such messages occur because when you use shared location to install things.

Can you copy media to a local folder and then try running the setup

Hello,

Many thanks for your suggestions.

But I have a requirement to support installation of SQL Server from a network location.

I have report from my customer that nearly 5 instances of such failures.

The network installation is successful for some users and failure for 5 users.

And the failure cases are SPORADIC  we are trying to understand the root cause of this exception.

-- Sakthi --

And the failure cases are SPORADIC  we are trying to understand the root cause of this exception.

-- Sakthi --

I would first suggest you install from local drive and see if issue resolves. Then share the log file as already asked and see if somebody can help. I would also suggest you to open case with Microsoft if you are not able to find solution here, opening case would give you exact reason for the failure