TF270015 MSTest.exe returned an unexpected exit code when publishing results of test run
Hello, I have a problem only with one of my three build servers.
The build log is the follow:
Publishing results of test run tfsbuild@HXCI07 2013-01-29 07:41:05_Any CPU_Release to
http://server.domain.com:8080/tfs/Rivendell...
.Value does not fall within the expected range.
Publish failed or canceled.
00:00
Handle MSTest Exception
TF270015: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '1'.
It's very strange because I have 3 build server with the same configuration and only this has the problem with publishing test results.
My server: TFS 2010 SP1
Can somebody help me?
Thanks,
EriC#
Hi Eric,
Thanks for your reply.
If you can run the same builds on another Build Service without this error, it seems that this issue relate to your current Build Service. So you can try to restart this Build Service(in TFS Admin Console), then compare if there’s
some specific difference between the current build agent machine and another build agent machine(configured in another Build Service).
To clean the TFS 2010 Cache and restart TFS Server, please refer to the following steps(delete the content of the folder only, not the cache folder itself):
Clean the Cache folder on client computer. The folder path is: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache. (os: Windows Server 2008 R2)
Clean the Cache folder on Server machine. The folder path is:
C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v10.0.
(os: Windows Server 2008 R2)
After cleaned, on Server machine, click
Start and select Run… to open the dialog box, then input
iisreset.exe and click OK, wait it run completely.
John Qiao [MSFT]
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
YES!!!! Cleaning the build server
cache solved the
problem! Thanks John!
EriC#
Similar Messages
-
Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks aheadHi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards, -
I've created a package in SSDT (Visual Studio 2012) to import DBF tables into MSSQL 2014 via a wizard.
Source DBF files contain tables with Russian (Cyrillic) characters in records fields.
Created package works fine, produces correct results (imports Cyrillic characters as needed) while:
•debugging in VS2012
•deploying package in SSISDB and running the package via PowerShell x86:
&"c:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\DTExec.exe" /Server "server\mssql2014" /ISServer "\SSISDB\import\Integration Services Project16\Package1.dtsx";
But when I create a SQL Agent job with a single PowerShell step that contains the same command and run the job it produces wrong characters in resulting tables. So, the problem is in wrong code page (or encoding). The correct tables with records are
produced and job runs without errors.
I tried
chcp 1251; # 855, 866 -- all of them
&"c:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\DTExec.exe" /Server "server\mssql2014" /ISServer "\SSISDB\import\Integration Services Project16\Package1.dtsx";
in SQL Agent PowerShell step, but with no positive result.
Anyone encountered such a behavior? How to fix it?
vWhat if you run this package without PowerShell?
Arthur My Blog -
Hello,
i'm using a software that is automatically running Vbscripts and prints out the output. i want the software
to print out the same message each time the script fails to run, due to a VBScript runtime error. the software runs the script as a command, like this:
cscript c:\script.vbs Hostname.
does anyone know what Exit Code does vbscript use when it fails to run? i don't need to know the exact value, just different from X.
up until now i i used a comparison to 0. if the exit code is different then 0 i printed out the failed message, but it looks like vbscript returns 0 as exit code even if it fails to run. is that possible and does anyone have a solution?
Thanks.Pegusus, this is a bit trickier than I thought at first. I just checked and found that syntax and runtime errors return zero exit codes at a command prompt. That surprises me. I would have thought they would return an errorlevel
of one or more. So, I think the ultimate solution may require more than one piece.
Momer,
For starters, though it's not something I often suggest, but you could add an "On Error Resume Next" statement at the head of the script and then add a statement like this ...
if err.number <> 0 then wsh.quit err.number
at likely points of error in the script. It returns the error number as an exit code.
If you do this, I would recommend you also try to manage the likely errors, but that's more complicated. At least, the placement of the Quit statements will give indications of the 'real' problems, based on the returned error number.
If you also have control of how the script gets called, you could try modifying the command to be something like this to try to react to syntax errors ...
%comspec% /c cscript //nologo c:\script.vbs Hostname | find /v /i "error" > nul
Though I assume the Hostname part is a replaceable argument, which complicates this approach. It just might not be possible in your case. I'd need to know a lot more about the way the script gets invoked to say any more about this approach.
Tom Lavedas
This is the best answer for many reasons:
1.You don't have to change the script. It's the hosts' (CSCRIPT) fault not your script and that is where it should be dealt with.
2.Some "syntax" errors are treated as runtime errors, e.g. when "Option Explicit" is on and you try to use an undefined variable/have a typo.
3.Because of #2 it is very dangerous to use "On Error Resume Next" because it is impossible and crazy to have to check after every part of every statement whether the Err.Number has been set. And this number is reset at the next successful statement so it's
just useless. Imagine a script doing something important like creating users or configuring a database, it could go off and damage your environment or corrupt data. Definitely not a sound solution. MS should have added On Error Do <something>, i.e. "WScript.Quit
Err.Number" being the most sensible default.
Here's an extended version of Tom's solution with a bit more accuracy, which also supports log files (remove " >> c:\logfile.txt 2>>&1" if you don't want that):
%comspec% /c cscript //nologo c:\script.vbs parameters >> c:\logfile.txt 2>>&1
set myreturncode=%ERRORLEVEL%
if %myreturncode% == 0 (
rem Also check for VBScript runtime errors which CSCRIPT does not return
for /f "delims=" %%x in ('findstr /C:"Microsoft VBScript runtime error:" "c:\logfile.txt"') do @set myreturncode=1
if %myreturncode% neq 0 exit /b %myreturncode%
Does the job for me. This issue seems to have been known for a long time so I guess MS don't want to change that behaviour. I guess the long term solution is to migrate to PowerShell. What an oversight that was. Who thought it was okay to return zero for
runtime errors when On Error Resume Next was NOT set?!?!?!!!
Key Artefacts -
DQS installation fails: Exit code 255
Hello, I am having a heck of a time installing DQS. I have tried installing from command, from specific Instance directory, etc. No matter what method , the below error is thrown. Also, There are no system restrictions, elevated prompt
issues, etc. at play, so those rudimentary causes can be ruled out.
Environment:
Virtual Machine running on HyperV
Clean/New installation of OS and SQL
Server 2008 R2 SP1 Datacenter Edition
SQL Server 2012 Developer Edition - I have applied CU1 hotfix but that did not help. Hotfix location = http://support.microsoft.com/kb/2679368
-------------------ERROR during install-----------------------
[8/24/2012 11:01:54 AM] Executing action: Create data quality schema.
[8/24/2012 11:01:54 AM] Script: 'recreate_schema.bat BISQL12 DQS SQL_Lat
n1_General_CP1_CI_AS'
[8/24/2012 11:01:54 AM]
[8/24/2012 11:01:54 AM] ! was unexpected at this time.
[8/24/2012 11:01:54 AM]
[8/24/2012 11:01:54 AM] Script process returned unexpected exit code: '255'.
[8/24/2012 11:01:54 AM] Action 'Create data quality schema' finished with error
, aborting installation.
[8/24/2012 11:01:54 AM] Starting installation rollback...
[8/24/2012 11:01:54 AM] Installation rollback completed successfully.
[8/24/2012 11:01:54 AM] DQS Installer finished with errors. Please see installa
ion log file at C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL
Log\DQS_install.log
Looking at the 'recreate_schema.bat' file, I see that it attempts to create the DQS databases by calling create_databases.sql. If I try to manually execute that script through SSMS, it fails as well. It throws errors such as....
Msg 102, Level 15, State 1, Line 31
Incorrect syntax near ':'.
:r db\drop_dq_databases.sql
---- and ------
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '$'.
CREATE DATABASE [$(DQS_DB)] COLLATE $(DQS_COLLATION)
I am at a loss. Any thoughts?
Thank you in advance!net helpmsg 255 shows the error means something cryptic... The extended attributes are inconsistent.
1. Is your computer in US English, or is it set to another locale?
2. Is there any command interpreters / command shells installed? I saw a wierd problem like this on the forum when someone had a command shell system installed that overrode the Windows default cmd with some add-ins.
3. If I recall, one of the first things the .bat file does is to use SQLCMD to run the .sql scripts. Do you have SQLCMD on the box? I think it is under C:\Program Files\Microsoft SQL Server\110\Tools\Binn\sqlcmd.exe
Is there any older instance of SQL installed? The reason I ask is that if the older version is in the PATH environment variable, it might be picking up the wrong SQLCMD and getting an error because of that. You could search the hard drive to be sure.
Try to change the PATH for the command prompt session to only include the right folder
SET PATH=C:\Program Files\Microsoft SQL Server\110\Tools\Binn
If you have an MSDN subscription, you can also open up a ticket with our support team for assistance, see my signature to get started.
Thanks, Jason
Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance -
Hi all,
I've a problem with windows shell, I've search through the entire forum database without success.
I need to return a custom exit code to the windows shell that is calling the Form Builder application (through Form Builder runtime). By this way I can determine from an another application (calling my forms through window shell) if I pressed one button or another.
How i can solve this problem?
I use Form Builder 6
Thanks a lotI need to open a Forms application from an HTML page and get a custom exit code from this application in order to use it in the HTML page.
With Javascript I call a shell function to start the forms application and ask to the HTML page to wait to the application exit code response.
The shell command I execute from Javascript is described bellow:
WshShell.run("c:\...\...\ifrun60.exe formname.fmx parametername=parameter",1,true)
where parameter identified a specific code that I've to send from HTML page to Forms application.
The page is waiting for application response. When I close the Forms application I receive the '0' code. What I need is to customize this exit code from my forms application.
Thanks to all -
Error on Installing CS5.1, CS6 - Exit Code 15, ERROR: Media DB Error 6
Hi. I am trying to install Photoshop CS6 trial on my machine (win 8 x64) but all the time it returns the error:
Exit code : 15
Summary
- 0 fatal error(s), 1 error(s), 0 warning(s)
ERROR: Media DB Error : 6
I have already used all the steps described on the forum (restarting the PC, downloading again the app, using Adobe Clean Tool) and no success. I even tried to install Photoshop CS5.1, but it goes with the very same error.
I currently have Fireworks CS6 installed, which I managed to install several months ago without a problem. However, when I try to uninstall it, it shows me also an error message:
UNINSTALL FAILED
Your uninstallation encountered errors.
Troubleshooting tips:
1. Restart your computer.
2. Exit all applications [...]
3. Uninstall again.
You may also download & run the Cleaner Tool. If the problems persist, please contact Customer Support for further assistance.
Well... here I am, Customer Support!
I can't seem to make this thing work. I've passed my whole weekend reading about it on the web and no solution found whatsoever. How can I sort it out, please?
Thank you,After using the Adobe Clean tool, I checked its output log and it mentioned it couldn't find a "caps.db" in the Common Files/Adobe/caps/ folder under Program Files or Program Files (x86).
So what I did: I manually deleted the Adobe folders from:
- Program Files
- Program Files (x86)
- Program Files (x86)/Common Files
After that, I was able to install successfully Photoshop CS5.1 and at this very moment I'm able to install PS CS6 (it's been already 50% of the installing progress).
So far, this action of deleting the Adobe folders from my Program Files folders seems to be sorting out the matter... -
Inconsistent exit code from Runtime.getRuntime().exec
I'm getting non-deterministic behavior from a call to a native process. Here is the code:
public class Test {
public static void main (String[] pArgs) {
try {
String cmd[] = { "cmp", "-s",
pArgs[0],
pArgs[1] };
System.err.println("running command: ");
Process p = Runtime.getRuntime().exec(cmd);
System.err.println("getting exitcode...");
int exitcode = p.waitFor();
System.err.println(exitcode);
System.err.println(p.exitValue());
} catch(Exception e) {
System.err.println("Caught exception while executing cmd");
e.printStackTrace();
And here is the output:
bock@homeruns[~/work/index]10:08> java Test output output.old
running command:
getting exitcode...
0
0
bock@homeruns[~/work/index]10:08> java Test output output.old
running command:
getting exitcode...
1
1
bock@homeruns[~/work/index]10:08> java Test output output.old
running command:
getting exitcode...
0
0
they should all be 1's because the files are different. when i run it on the command line i get:
bock@homeruns[~/work/index]10:13> cmp -s output output.old ; echo $?
1
any help would definitely be appreciated!
thanks,
rogerthanks for the link. i read through it but it doesn't seem to address why the exit code would be inconsistently reported. the other problems described by that link don't seem to apply to this case because i have not experienced hanging and there is no standard input, standard output, or standard error associated with "cmp -s" - all it does is return the appropriate exit code.
should i be reporting this as a bug to sun? up till recently i've been assuming it was a problem with my code but now i'm not so sure... -
On top of RMAN error codes RMAN will return a non-zero OS exit code when it encounters an error. Can anyone point me to a document/thread/etc that would explain the meaning of each of these codes? (An "OS exit code" vs. "RMAN error" mapping perhaps...?)
You can check the exit status of the script and if it is non-zero you can query V$RMAN_OUTPUT and/or any log file that you generate.
Additional information is included in Identifying RMAN Return Codes and RMAN Error Message Ranges -
ShellScriptResourceAdapter ignores STDERR and non zero exit codes?
My ShellScript Resource seems to ignore any output to STDERR and also ignores script commands failing with exit codes other than 0.
Let's say I run this in bash:
meh@moo ~$ perl -e 'print(STDERR "Error "); die("foo");' 1>/dev/null
Error foo at -e line 1.
meh@moo ~$ echo $?
255Perl clearly exits with STDERR Output and exit code -1.
Now, if I run this as the "Update User" ResourceAction in IDM 6 SP1, it always tells me everything went fine without any errors.
Running it as "Create User" ResourceAction at least gives me:
Error foo at -e line 1.
null
Result Code = 255
And the CREATE actually fails.
But Update and Delete seem to ignore STDERR and exit codes.
Or am I missing something? It would be great to see any error in IDM when one of the ResourceAction scripts' steps is failing...Somkeit,
What did you change in UME Configuration?
Please look in defaulttrace_# log and paste error here.
What is exit code ?
Can you revert back your UME changes and see if system starts or no.
Thanks,
Digesh Joshi -
We have some Intel and HP application installation task sequences that are successful, but the end of the deployment there is always a yellow screen warning about unexpected return codes such as "14".
I think most of these are because the applications are looking for a interactive restart that is not done until the MDT task sequence does a reboot. For instance, a task sequence that installs Intel AMT software and drivers pops up a dialog box asking
the user to click to restart now or restart later even though the command is run as "setup.exe -s." Since no one clicks on this pop up and the machine reboots via the task sequence, it creates this unexpected return code.
Are there additional command line switches that can be added to the task sequences to suppress the reboot prompts and make these applications exit gracefully without causing these warnings at the end of the deployment?I usually create a powershell wrapper for applications that exit funny. An example would be -
#GET CURRENT DIR
$mydir = Split-Path -parent $MyInvocation.MyCommand.Path
#SET VARAIBLE TO PASS INSTALL COMMAND WITH SPACES
$command = @"
setup.exe /s
#MOVE TO INSTALL DIR
Set-Location C:\Install\Folder\
#RUN INSTALL
cmd.exe /c ""$command | out-null
#EXIT CLEANLY
exit 0
Save this script inside where your Application is located, and then create an application that runs the script inside of the Deployment Workbench. The only problem with this is you need to be sure your install works, as you're basically just ignoring
any errors the application has. Down at the bottom, you can see the exit being passed back to MDT to continue cleanly. Good luck.
I don't understand how to do this sine I have never users Powershell in MDT.
Do I just edit the script changing C:\Install\Folder to the actual local path the application is stored on in the MDT server?
Do I just name it with a .PS1 extension and run it as a command line or as an application? -
Installing SQL Server 2008 R2 via command line - setup100.exe returned exit code 0x84BC06B2
I am receiving an exit code 0x84BC06B2 when installing SQLExpress via the command line on a PC that also has SQL Server 2012 installed. Below is the log file generated:
11/18/2014 01:02:41.631 Help display: false
11/18/2014 01:02:41.642 Checking to see if we need to install .Net version 2.0
11/18/2014 01:02:41.653 Determining the cluster status of the local machine.
11/18/2014 01:02:41.665 The local machine is not configured as a cluster node.
11/18/2014 01:02:41.675 Attempting to find media for .Net version 2.0
11/18/2014 01:02:41.686 .Net version 2.0 is installed
11/18/2014 01:02:41.697 RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
11/18/2014 01:02:41.709 Attempting to get Windows Installer version
11/18/2014 01:02:41.721 Windows Installer version detected: 5.0.7601.18493
11/18/2014 01:02:41.733 RedistMSI::IsVistaRTM - Not Vista RTM build
11/18/2014 01:02:41.745 Required version of Windows Installer is already installed
11/18/2014 01:02:41.772 Strong name verification disabling is not required
11/18/2014 01:02:41.781 /? or /HELP or /ACTION=HELP specified: false
11/18/2014 01:02:41.793 Help display: false
11/18/2014 01:02:41.805 Attempting to launch landing page workflow
11/18/2014 01:02:41.816 Attempting to set setup mutex
11/18/2014 01:02:41.827 Setup mutex has been set
11/18/2014 01:02:41.838 Attempting to launch global rules workflow
11/18/2014 01:02:41.849 Media source: c:\sqlexpress\
11/18/2014 01:02:41.860 Install media path: c:\sqlexpress\x86\setup\
11/18/2014 01:02:41.870 Media layout: Core
11/18/2014 01:02:41.881 Attempting to get execution timestamp
11/18/2014 01:02:41.892 Timestamp: 20141118_010240
11/18/2014 01:02:41.903 Attempting to run workflow RUNRULES /RULES=GlobalRules
11/18/2014 01:02:41.915 Attempting to launch process c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
11/18/2014 01:02:50.467 Process returned exit code: 0x00000000
11/18/2014 01:02:50.484 Workflow RUNRULES /RULES=GlobalRules returned exit code: 0x00000000
11/18/2014 01:02:50.496 Attempting to launch component update workflow
11/18/2014 01:02:50.509 Media source: c:\sqlexpress\
11/18/2014 01:02:50.522 Install media path: c:\sqlexpress\x86\setup\
11/18/2014 01:02:50.534 Media layout: Core
11/18/2014 01:02:50.546 Attempting to get execution timestamp
11/18/2014 01:02:50.558 Timestamp: 20141118_010240
11/18/2014 01:02:50.570 Attempting to run workflow COMPONENTUPDATE
11/18/2014 01:02:50.581 Attempting to launch process c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
11/18/2014 01:03:02.572 Process returned exit code: 0x00000000
11/18/2014 01:03:02.590 Workflow COMPONENTUPDATE returned exit code: 0x00000000
11/18/2014 01:03:02.602 Attempting to launch user requested workflow locally
11/18/2014 01:03:02.614 Attempting to find local setup.exe
11/18/2014 01:03:02.626 Local bootstrap folder path: c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\
11/18/2014 01:03:02.639 Local setup100.exe full path: c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
11/18/2014 01:03:02.650 Media source: c:\sqlexpress\
11/18/2014 01:03:02.661 Install media path: c:\sqlexpress\x86\setup\
11/18/2014 01:03:02.672 Media layout: Core
11/18/2014 01:03:02.684 Attempting to get execution timestamp
11/18/2014 01:03:02.695 Timestamp: 20141118_010240
11/18/2014 01:03:02.706 Attempting to run user requested action from local setup100.exe
11/18/2014 01:03:02.717 Attempting to launch process c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
11/18/2014 01:07:28.302 Process returned exit code: 0x84BC06B2
11/18/2014 01:07:28.314 Local setup100.exe returned exit code: 0x84BC06B2
11/18/2014 01:07:28.326 Attempting to release setup mutex
11/18/2014 01:07:28.338 Setup mutex has been released
11/18/2014 01:07:28.351 Setup closed with exit code: 0x84C40013
11/18/2014 01:07:28.362 ======================================================================
Does anyone have any ideas of why this is failing?Here is the summary.txt:
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052302
Exit facility code: 1212
Exit error code: 1714
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-11-18 01:03:03
End time: 2014-11-18 01:07:23
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xE53883A0%400xBE03358B%401306%4023
Machine Properties:
Machine name: PC81372
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services 1033
Express Edition 10.2.4000.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication 1033
Express Edition 10.2.4000.0 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: c:\sqlexpress\x86\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: True
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: WORKSTUDIO
INSTANCENAME: WORKSTUDIO
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: True
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: BUILTIN\USERS
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1714
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\sql_engine_core_shared_loc_Cpu32_1033_1.log
MSI error description: The older version of SQL Server 2008 R2 Database Engine Shared cannot be removed. Contact your technical support group.
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@23
Configuration error description: Could not find the Database Engine startup handle.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@23
Configuration error description: Could not find the Database Engine startup handle.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_010240\SystemConfigurationCheck_Report.htm -
Vcredist_x86.exe returned failure exit code 1602
Client install is failing where I have copied source files to a restricted server and initiated install with /source.
Installing file 'C:\Windows\ccmsetup\vcredist_x86.exe' with options '/q /norestart /c:"msiexec /i vc_red.msi /qn REBOOT=ReallySuppress" /msioptions "REBOOT=ReallySuppress"'. ccmsetup 12/8/2014 2:51:06 PM 4808 (0x12C8)
File 'C:\Windows\ccmsetup\vcredist_x86.exe' returned failure exit code 1602. Fail the installation. ccmsetup 12/8/2014 3:01:18 PM 4808 (0x12C8)
InstallFromManifest failed 0x80070642 ccmsetup 12/8/2014 3:01:18 PM 4808 (0x12C8)
I have only Port 80 and 8530 opened on this restricted server talking to Primary Site Server (SCCM 2012 R2).
ThanksIts VC++ 2010.
Interesting after 8530 port opened... at 8pm CCMSetup installed fine from retry:
Running on platform X64 ccmsetup 12/8/2014 8:01:22 PM 3828 (0x0EF4)
Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 12/8/2014 8:01:22 PM 3828 (0x0EF4)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 12/8/2014 8:01:22 PM 3828 (0x0EF4)
CcmSetup version: 5.0.7958.1000 ccmsetup 12/8/2014 8:01:22 PM 3828 (0x0EF4)
Running on 'Microsoft Windows Server 2008 R2 Standard ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Ccmsetup command line: C:\Windows\ccmsetup\ccmsetup.exe "/source:C:\Temp\SCCM2012Agent\Client" /RetryWinTask:1 ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Command line: C:\Windows\ccmsetup\ccmsetup.exe "/source:C:\Temp\SCCM2012Agent\Client"
/RetryWinTask:1 ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
SslState value: 224 ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
No version of the client is currently detected. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
ccmsetup service is stopped. ccmsetup 12/8/2014 8:01:23 PM 3828 (0x0EF4)
Successfully deleted the ccmsetup service ccmsetup 12/8/2014 8:01:28 PM 3828 (0x0EF4)
Successfully created the ccmsetup service ccmsetup 12/8/2014 8:01:28 PM 3828 (0x0EF4)
Could you please confirm what other ports are required apart from 80 (communication to Primary site server) and 8530 (updates/defs)?
Thanks -
Hi,
I am using SignTool.exe from a new Process() to verify a codesigned assembly and it returns the exit code 1 whereas it returns exit code 0 while i run the same from Visual Studio Command prompt. Please let me know your thoughts...
Here is my code snippet from VS2012 ultimate on Win7 PC.
p = new Process();
p.StartInfo.FileName = "C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v7.0A\\Bin\\SignTool.exe";
string args = @"verify";
p.StartInfo.Arguments = args + " "+ "/pa " + "/v "+ name;
p.Start();
p.WaitForExit();
pexitcode = p.ExitCode;
//name = "C:\\Users\\v-maparn\\Documents\\Visual Studio 2012\\Projects\\CodesignVerification\\CodesignVerification\\bin\\Release\\Microsoft.IT.Core.dll"
Thanks,
ManiHi Amy,
Thanks for your reply. I am receiving the exit code 1 by the Process even though the SignTool is able to successfully verify the assembly. I ran the below command from command prompt and received no errors or warnings. I assume the exit code should be 0.
I have also verified that this assembly has digital signature embedded as you can see from the output.
output:
C:\Windows\system32>signtool.exe verify /pa /v "C:\Users\v-maparn\Documents\Visu
al Studio 2012\Projects\CodesignVerification\CodesignVerification\bin\Release\Mi
crosoft.IT.Security.UI.SystemSecurityManagement.SSMUIWebHost.dll"
Verifying: C:\Users\v-maparn\Documents\Visual Studio 2012\Projects\CodesignVerif
ication\CodesignVerification\bin\Release\Microsoft.IT.Security.UI.SystemSecurity
Management.SSMUIWebHost.dll
Signature Index: 0 (Primary Signature)
Hash of file (sha1): 1B58113B218260837A6B850561538A804B034F2A
Signing Certificate Chain:
Issued to: Microsoft Root Certificate Authority
Issued by: Microsoft Root Certificate Authority
Expires: Sun May 09 15:28:13 2021
SHA1 hash: CDD4EEAE6000AC7F40C3802C171E30148030C072
Issued to: Microsoft Code Signing PCA
Issued by: Microsoft Root Certificate Authority
Expires: Mon Aug 31 14:29:32 2020
SHA1 hash: 3CAF9BA2DB5570CAF76942FF99101B993888E257
Issued to: Microsoft Corporation
Issued by: Microsoft Code Signing PCA
Expires: Thu Apr 24 14:33:39 2014
SHA1 hash: 108E2BA23632620C427C570B6D9DB51AC31387FE
The signature is timestamped: Mon Dec 30 02:58:12 2013
Timestamp Verified by:
Issued to: Microsoft Root Certificate Authority
Issued by: Microsoft Root Certificate Authority
Expires: Sun May 09 15:28:13 2021
SHA1 hash: CDD4EEAE6000AC7F40C3802C171E30148030C072
Issued to: Microsoft Time-Stamp PCA
Issued by: Microsoft Root Certificate Authority
Expires: Sat Apr 03 05:03:09 2021
SHA1 hash: 375FCB825C3DC3752A02E34EB70993B4997191EF
Issued to: Microsoft Time-Stamp Service
Issued by: Microsoft Time-Stamp PCA
Expires: Wed Feb 11 14:11:31 2015
SHA1 hash: D967AB4CF991F11DA6E318C880F1AF1A9C8D2C7C
Successfully verified: C:\Users\v-maparn\Documents\Visual Studio 2012\Projects\C
odesignVerification\CodesignVerification\bin\Release\Microsoft.IT.Security.UI.Sy
stemSecurityManagement.SSMUIWebHost.dll
Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 0
C:\Windows\system32>
Thanks,
Mani -
Third party payload installer DistillrStarter.exe failed with exit code: 1603
I need to reinstall FrameMaker 11 after a system crash. At 99% of the installation process, I get the following message.
(For my understanding, downloading a new DistillrStarter.exe should solve the issue.
The file is for creating Japanese PDFs. I do not even need it. :-)
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR: DW030 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
----------- Payload: Adobe PDF Creation Add-On 10 10.0.0.0 {AC76D478-1033-0000-3478-000000000005} -----------
ERROR: Third party payload installer DistillrStarter.exe failed with exit code: 1603
----------- Payload: Adobe FrameMaker 11_AdobeFrameMaker11_en_US 11.0.0.0 {E26880FB-DEB4-4299-A1EB-FDEB85C09FD7} -----------
ERROR: DW030: Custom Action for payload Adobe FrameMaker 11_AdobeFrameMaker11_en_US 11.0.0.0 {E26880FB-DEB4-4299-A1EB-FDEB85C09FD7} returned error. Failing this payload.Hi Mylenium,
from the notifications, IMHO, FrameMaker installation failed because of a corrupt DistillrStart.exe file in the installer.
What I did not know, in the installation options, I could disable PDF maker.
I do not need this module, that is already installed with Acrobat Pro on my system.
In the support chat, I was not pointed to this, either. Although I asked if I really had to uninstall
all Adobe software from my system before re-installing, even Acrobat...
Thank God, my company's administration remembered this issue from a previous installation.
Best regards,
Michael
Maybe you are looking for
-
Unable to capture HDV with Sony HVR-V1E camcorder
Has any one else solved this problem? Thanks Lawrence Cave
-
SWCV import error in PI 7.1
Hi Experts, I have created Product and Software Component in SLD. In PI 7.0 usually we import the SWCV from Tools -> Transfer from System Landscape Directory -> Import Software Component Versions. But I couldn't find the above option in PI 7.1. So, I
-
The program would enter info for me. I only had to type the first letter or number of the info needed. For example, my first name is OSCAR. So, to enter this info in the box marked "First name", I only had to type in the box the letter "O". The progr
-
Calendar published with iCal not available in .Mac?
Hi! I have published a calendar with iCal successfully and without any issues - this is a home calendar and so has a limited amount of dates, events etc. However I recently imported my work calendar (which has large amounts of data) and I also publis
-
RMI (Internet, LAN, Firewall)
Hello everybody. In the last view days I solved a lot of problems with my RMI based System... There was the registry problem, the IE problem (no RMI support), the access permission problem and so on... But now everythiung is working properely. I use