Since I have updated to the Version 2014.2.15.0, I receive a lot! of build warnings in my solution.
Release | x86
0 error(s), 14289 warning(s)
$/trunk/Source/Client.sln - 0 error(s), 923 warning(s), View Log File
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'T:System.Windows.FrameworkElement'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'M:System.Windows.FrameworkElement.ShouldSerializeTriggers'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'P:System.Windows.FrameworkElement.Triggers'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'T:System.Windows.FrameworkElement'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'M:System.Windows.Controls.Control.ToString'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [T:DialogTestView] MSDN URL not found for target 'T:System.Windows.Controls.Control'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
...
$/trunk/Source/Server.sln - 0 error(s), 13366 warning(s), View Log File
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [Methods.T:Configuration] MSDN URL not found for target 'T:System.Object'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [Methods.T:Configuration] MSDN URL not found for target 'T:System.Object'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [Methods.T:Configuration] MSDN URL not found for target 'T:System.Object'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [Methods.T:Configuration] MSDN URL not found for target 'M:System.Object.Finalize'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
C:\Program Files (x86)\EWSoftware\Sandcastle Help File Builder\SandcastleHelpFileBuilder.targets (38): BuildAssembler : warning : ResolveReferenceLinksComponent: [Methods.T:Configuration] MSDN URL not found for target 'T:System.Object'. [C:\Builds\bin\Working\BuildReferenceTopics.proj]
...
In the previous Version 1.9.8.0 there wasn't warnings on the solution.
Comments: ** Comment from web user: EWoodruff **
Since it appears to be a proxy issue, there isn't anything I can do since it's not something I can troubleshoot. One of the set of BuildAssembler.exe.config settings usually allow it to pass through. The best I can suggest is you try to connect to the MTPS content service directly in a test project (not SHFB, something like a console app) and see if you can find the correct settings to communicate with it. You should then be able to apply them to the config file. If you find them, let me know and I can add them as another possible solution.