fix

Author: v-thepet

docs/2014/integration-services/data-flow/excel-destination.md

@@ -97,14 +97,6 @@ manager: craigg
 
 -   [Set the Properties of a Data Flow Component](set-the-properties-of-a-data-flow-component.md)  
 
-## Related Content  
-  
--   Blog entry, [Excel in Integration Services, Part 1 of 3: Connections and Components](https://go.microsoft.com/fwlink/?LinkId=217674), on dougbert.com  
-  
--   Blog entry, [Excel in Integration Services, Part 2 of 3: Tables and Data Types](https://go.microsoft.com/fwlink/?LinkId=217675), on dougbert.com.  
-  
--   Blog entry, [Excel in Integration Services, Part 3 of 3: Issues and Alternatives](https://go.microsoft.com/fwlink/?LinkId=217676), on dougbert.com.  
-  
 ## See Also  
  [Excel Source](excel-source.md)   
  [Integration Services (SSIS) Variables](../integration-services-ssis-variables.md)   

docs/2014/integration-services/data-flow/excel-source.md

@@ -106,12 +106,6 @@ manager: craigg
 
 -   Blog entry, [Importing data from 64-bit Excel in SSIS](https://go.microsoft.com/fwlink/?LinkId=217673), on hrvoje.piasevoli.com  
 
--   Blog entry, [Excel in Integration Services, Part 1 of 3: Connections and Components](https://go.microsoft.com/fwlink/?LinkId=217674), on dougbert.com  
-  
--   Blog entry, [Excel in Integration Services, Part 2 of 3: Tables and Data Types](https://go.microsoft.com/fwlink/?LinkId=217675), on dougbert.com.  
-  
--   Blog entry, [Excel in Integration Services, Part 3 of 3: Issues and Alternatives](https://go.microsoft.com/fwlink/?LinkId=217676), on dougbert.com.  
-  
 -   Blog entry, [Connecting to Excel (XLSX) in SSIS](https://microsoft-ssis.blogspot.com/2014/02/connecting-to-excel-xlsx-in-ssis.html).  
 
 

docs/2014/integration-services/extending-packages-scripting/task/logging-in-the-script-task.md

@@ -88,8 +88,6 @@ public class ScriptMain
 
 ## External Resources  
 
--   Blog entry, [Logging custom events for Integration Services tasks](https://go.microsoft.com/fwlink/?LinkId=165644), on dougbert.com  
-  
 ![Integration Services icon (small)](../../media/dts-16.gif "Integration Services icon (small)")  **Stay Up to Date with Integration Services**<br /> For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the [!INCLUDE[ssISnoversion](../../../includes/ssisnoversion-md.md)] page on MSDN:<br /><br /> [Visit the Integration Services page on MSDN](https://go.microsoft.com/fwlink/?LinkId=136655)<br /><br /> For automatic notification of these updates, subscribe to the RSS feeds available on the page.  
   
 ## See Also  

docs/2014/integration-services/troubleshooting/troubleshooting-tools-for-package-execution.md

@@ -48,7 +48,7 @@ manager: craigg
 
      **Add the description of the error**. It is easy to look up the error description by using a Script component. For more information, see [Enhancing an Error Output for the Script Component](../extending-packages-scripting-data-flow-script-component-examples/enhancing-an-error-output-with-the-script-component.md).  
 
-     **Add the name of the error column**. Looking up the column name that corresponds to the column ID saved by the error output cannot easily be done in the Script component and requires additional steps. Each column ID in a data flow is unique within that Data Flow task, and is persisted in the package at design time. The following approach is one suggestion for adding the column name to the error output. For an example of how to use this approach, see [Adding the error column name to an error output](https://go.microsoft.com/fwlink/?LinkId=261546) on dougbert.com.  
+     **Add the name of the error column**. Looking up the column name that corresponds to the column ID saved by the error output cannot easily be done in the Script component and requires additional steps. Each column ID in a data flow is unique within that Data Flow task, and is persisted in the package at design time. The following approach is one suggestion for adding the column name to the error output. 
 
     1.  **Create a lookup table of column names**. Create a separate application that uses the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] API to iterate over each saved package, each data flow in the package, each object in the data flow, and each input and output in the data flow object. The application should persist the column ID and name of each column to a lookup table, along with the ID of the parent Data Flow task and the ID of the package.  
 
@@ -106,7 +106,4 @@ manager: craigg
 ## Related Tasks  
  [Configure an Error Output in a Data Flow Component](../configure-an-error-output-in-a-data-flow-component.md)  
 
-## Related Content  
- Blog entry, [Adding the error column name to an error output](https://go.microsoft.com/fwlink/?LinkId=261546), on dougbert.com.  
-