Clearing returned an unexpected returned code: 1 in MDT 2013

I am testing some application deployment in MDT 2013 but I keep getting error code 1 in a yellow summary page even when the applications were deployed successfully onto the devices.
Can some advised how to clear this error

Sure, whenever you are seeing Yellow at the Deployment Summary wizard, it means that there is an error somewhere in the bdd.log file.
If you need assistance looking at the bdd.log file, upload to a public site like OneDrive, and share the link here.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

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 ahead

Hi 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,

Application returned an unexpected return code 1632 - MDT 2012

Hi,
I am getting the following error while installing Adobe reader, office 2010 only in few PC's.
applicatio adobe reader x1 returned an unexpected return code 1632
applicatio MS office 2010 returned an unexpected return code 1632
can any help on this.
Please note that the above mentioned problem comes only in some PC's.
D. Sendil Kumar

http://support.microsoft.com/kb/290158/en-us
ERROR_INSTALL_TEMP_
UNWRITABLE              1632   The temp folder is either full or
                                inaccessible. Verify that the temp folder
                                exists and that you can write to it.
Check the MSI installation logs. Whenever I install *.msi packages in MDT I turn on logging:
Msiexec.exe /qb- /l*vx %LogPath%\<file>.log REBOOT=ReallySuppress UILevel=67 ALLUSERS=2 /i <File>.msi
http://keithga.wordpress.com/2013/09/04/application-installation-and-packaging-via-mdt-and-sccm/
Keith Garner - keithga.wordpress.com

MDT capture warning: Unexpected return code while re-arming office 2010, RC= -1073425657

Greetings,
I have a base image I have created with an MDT task sequence, than I am then immediately capturing with another MDT task sequence (the capture sequence is basically the default). After capture, I get 0 errors, 1 warning: "Unexpected return code
while re-arming office 2010, RC= -1073425657".
I am capturing immedaitely after the base image build, and even more strangely, even with Office 2010 removed from my base build, I STILL get this warning! Office isn't even on there anymore (I verified before capture just to double check).
Not sure how or why this is happening - or more importantly, should I care? I've deployed a couple of machines using this image, and both Office and Windows show as activated. Can this safely be ignored, or if not... what is the fix?
Thanks in advance!

Freddie,
Please read your own post again, can you tie the knots together, because your phrasing is going crazy!?!
However, if using the sysprep step from within a MDT task sequence, please scroll through the ZTISysprep.wsf to find that not only the machine will be sysprepped, but also Office 2010 will be automatically re-armed, this is provided in the script already,
so no need to run it on your own.
Ok how do i undo that because thatswhy the message appears to many rearms...
If a machine is domain joined, it will not sysprep and capture. Also I wouldn't sysprep and capture an already sysprepped and captured image again (based on gut feeling) and as always check your logfiles, they can reveal what is going on here.
The machine is not domain joined in the Vm. And i do not sysprep and capture twice.Which logfiles exactly to see?
If this post is helpful please click "Mark for answer", thanks! Kind regards
freddie

MDT application install returns unexpected return code: 16

Hi, I'm using MDT 2013 (Version: 6.2.5019.0) and deploying Server 2012 R2 Standard.
The deployment runs fine, but an application install fails. Here is the relevant content from the BDD.LOG file:
Run Command: \\MDT\Share$\Tools\X64\bddrun.exe robocopy \\MDT\Share$\BuildFiles "C:" /MIR /W:5 /R:3 /LOG \\MDT\Share$\LOGS
ZTI installing application
About to run command: \\MDT\Share$\Tools\X64\bddrun.exe robocopy \\MDT\Share$\BuildFiles "C:" /MIR /W:5 /R:3 /LOG \\MDT\Share$\LOGS
Command has been started (process ID 2896)
Return code from command = 16
Application Copy Files 1.0 returned an unexpected return code: 16
Property InstalledApplications001 is now = {9d0ba76d-96f9-4f4f-a6b8-4b1d0ffd2007}
ZTIApplications processing completed successfully.
I've searched for the error code 16 but can't find any results. What does it mean?
Cheers.

I think that I may have found the solution. On different site I've found the robocopy exit codes and 16 is listed there as "Robocopy
did not copy any files. Check the command line parameters and verify that Robocopy has enough rights to write to the destination folder."
I guess that I need to alter the destination folder to something other than the root of C:\
I'll respond with the result later.
UPDATE: Yep, that was the problem.

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#

How can we know the return code of BDC Program ?

Hi All,
Please tell me : How can we know the return code of BDC Program when being exceuted in Session or in Transaction mode.
In my program, we are uploading data from Excel sheet to SAP via BDC
The records that are not updated we want to create a log file.
Now to know whether a record is updated ot not, wat syst field shloud be used?
Its urgent....
<b>Reward Point will be there ....</b>
Thanks,
Harish

Hi harish,
try the logic in this code ...
i had attached input file in the end.
TYPES: begin of errmess,
        msgnr type t100-msgnr,
        text type t100-text,
       end of errmess.
TABLES : t100.
DATA: BEGIN OF DD_VA01,
       AUART TYPE VBAK-AUART,
       KUNNR TYPE RV45A-KUNNR,
       BSTKD TYPE VBKD-BSTKD,
       MABNR TYPE RV45A-MABNR,
       KWMENG(2) type C,
       KBETR(2) type C,
      END OF DD_VA01.
DATA:IT_VA01     Like TABLE OF DD_VA01,
     WA_VA01     Like LINE OF IT_VA01,
     WA_VA01_F   Like LINE OF IT_VA01,
     IT_BDCDATA TYPE TABLE OF BDCDATA,
     WA_BDCDATA Like Line OF IT_BDCDATA,
     W_FNAME     TYPE STRING,
     messtab like bdcmsgcoll occurs 0 with header line,
     it_errmess type table of errmess,
     wa_errmess like line of it_errmess,
     err_message type string.
data: zf1 type i,
      zc1 type c value '2',
      fn(20) type c.
Main Code ************************************************************
PERFORM get_input using 'C:\Documents and Settings\ic881592\Desktop\Daran_bdc_VA01-e.txt'.
SORT IT_VA01 BY AUART KUNNR BSTKD.
LOOP AT IT_VA01 INTO WA_VA01.
if WA_VA01_F-AUART <> WA_VA01-AUART OR
     WA_VA01_F-KUNNR <> WA_VA01-KUNNR OR
     WA_VA01_F-BSTKD <> WA_VA01-BSTKD.
       PERFORM set_header_flag.
       PERFORM create_bdc_header_data.
endif.
PERFORM create_bdc_item_data.
ENDLOOP.
PERFORM call_transaction.
PERFORM errorlog.
Procedures ***********************************************************
form get_input using w_fname.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME            = W_FNAME
      HAS_FIELD_SEPARATOR = '#'
    TABLES
      DATA_TAB            = IT_VA01.
endform.
form call_transaction.
    PERFORM bdc_field       using 'BDC_OKCODE' '/11'.
    CALL TRANSACTION 'VA01' USING IT_BDCDATA MODE 'A' messages into messtab.
    refresh it_bdcdata.
endform.
FORM set_header_flag.
       WA_VA01_F-AUART = WA_VA01-AUART.
       WA_VA01_F-KUNNR = WA_VA01-KUNNR.
       WA_VA01_F-BSTKD = WA_VA01-BSTKD.
       if zf1 = 1.
           PERFORM call_transaction.
       endif.
       zf1 = 1.
endform.   "set_header_flag.
form create_bdc_header_data.
     perform bdc_dynpro      using 'SAPMV45A' '0101'.
     perform bdc_field       using 'VBAK-AUART' WA_VA01-AUART.
     perform bdc_field       using 'BDC_OKCODE' '/00'.
     perform bdc_dynpro      using 'SAPMV45A' '4001'.
     perform bdc_field       using 'KUAGV-KUNNR' WA_VA01-KUNNR.
     perform bdc_field       using 'VBKD-BSTKD' WA_VA01-BSTKD.
     perform bdc_field       using 'BDC_OKCODE' '/00'.
     perform bdc_dynpro      using 'SAPMSSY0' '0120'.
     perform bdc_field       using 'BDC_CURSOR' '04/06'.
     perform bdc_field       using 'BDC_OKCODE' '=CHOO'.
     perform bdc_dynpro      using 'SAPMV45A' '4001'.
     PERFORM bdc_field       USING 'BDC_OKCODE' '=POAN'.
endform. "create_bdcdata
FORM create_bdc_item_data.
     CONCATENATE 'RV45A-KWMENG(' zc1 ')' INTO FN.
     perform bdc_field       using 'BDC_CURSOR' FN.
     perform bdc_field       using FN WA_VA01-KWMENG.
     CONCATENATE 'KOMV-KBETR(' zc1 ')' INTO FN.
     perform bdc_field       using FN WA_VA01-KBETR.
     CONCATENATE 'RV45A-MABNR(' zc1 ')' INTO FN.
     perform bdc_field       using FN WA_VA01-MABNR.
     perform bdc_dynpro      using 'SAPMV45A' '4001'.
     PERFORM bdc_field       USING 'BDC_OKCODE' '=POAN'.
ENDFORM.
form errorlog.
LOOP AT MESSTAB .
    if MESSTAB-MSGNR = '311' or MESSTAB-MSGTYP = 'E'.
        SELECT SINGLE msgnr text FROM T100
                        into wa_errmess
                        WHERE SPRSL = MESSTAB-MSGSPRA
                          AND ARBGB = MESSTAB-MSGID
                          AND MSGNR = MESSTAB-MSGNR.
        IF SY-SUBRC = 0.
          err_message = wa_errmess-TEXT.
          IF err_message CS '&1'.
            REPLACE '&1' WITH MESSTAB-MSGV1 INTO err_message.
            REPLACE '&2' WITH MESSTAB-MSGV2 INTO err_message.
            REPLACE '&3' WITH MESSTAB-MSGV3 INTO err_message.
            REPLACE '&4' WITH MESSTAB-MSGV4 INTO err_message.
          ELSE.
            REPLACE '&' WITH MESSTAB-MSGV1 INTO err_message.
            REPLACE '&' WITH MESSTAB-MSGV2 INTO err_message.
            REPLACE '&' WITH MESSTAB-MSGV3 INTO err_message.
            REPLACE '&' WITH MESSTAB-MSGV4 INTO err_message.
          ENDIF.
          CONDENSE err_message.
          WRITE: / MESSTAB-MSGTYP, err_message .
        ELSE.
          WRITE: / MESSTAB.
        ENDIF.
    endif.
ENDLOOP.
endform. "errorlog
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
WA_BDCDATA-PROGRAM = PROGRAM.
WA_BDCDATA-DYNPRO   = DYNPRO.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO IT_BDCDATA.
CLEAR WA_BDCDATA.
ENDFORM.
FORM BDC_FIELD USING FNAM FVAL.
WA_BDCDATA-FNAM = FNAM.
WA_BDCDATA-FVAL = FVAL.
APPEND WA_BDCDATA TO IT_BDCDATA.
CLEAR WA_BDCDATA.
ENDFORM.
input file :
OR     2148     0001235     R-1162     8     17
OR     2148     0001235     R-1161     2     30
OR     2148     0001235     100-400     6     25
OR     2148     0001235     R-1162     4     12
OR     2148     0001236     R-1162     3     12
OR     2148     0001236     R-1161     2     30
OR     2148     0001236     100-400     1     25
OR     2148     0001236     R-1162     7     12
OR     2148     0001236     R-1161     8     30
OR     2148     0001236     100-400     10     25
OR     2148     0001235     R-1161     5     30
OR     2148     0001235     100-400     2     25
OR     2148     0001235     R-11621     3     12
OR     2148     0001235     R-1161     2     30
OR     2148     0001235     100-400     1     25
OR     2148     0001235     R-1162     7     12
OR     2148     0001235     R-1161     8     30
OR     2148     0001235     100-400     10     25
OR     2148     0001236     R-1162     8     17
OR     2148     0001236     R-1161     2     30
OR     2148     0001236     100-400     6     25
OR     2148     0001236     R-1162     4     12
OR     2148     0001236     R-1161     5     30
OR     2148     0001236     100-400     2     25

DB-Connect Failed, Return Code 000256

Hello,
When I try to start SAP I get a SQL error saying "DB-Connect failed, return code 000256". Does anybody know what could cause this error and how to slove this problem.
I checked the dev_w0 file as the following.
trc file: "dev_w0", trc level: 1, release: "46D"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
B
B Sat May 09 21:08:37 2015
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\PRD\SYS\exe\run\dboraslib.dll' ...
B Library 'D:\usr\sap\PRD\SYS\exe\run\dboraslib.dll' loaded
B Version of 'D:\usr\sap\PRD\SYS\exe\run\dboraslib.dll' is '46D.00'
B New connection 0 created
M relno      4640
M patchlevel 0
M patchno    534
M intno      0
M pid        2444
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2444) [dpxxdisp.c   911]
I MtxInit: -2 0 0
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation std
M <ES> Memory Reset enabled
X ES initialized.
M ThSysUsrCheck: clear T0
M calling db_connect ...
B find_con found the following connection for reuse:
B 0: name = R/3, concnt= 000000 state = DISCONNECTED, perm = YES, reco = NO
C Got ORACLE_HOME=D:\oracle\ora81 from environment
C Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@PRD on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12505
[dboci.c      2423]
C *** ERROR => CONNECT failed with sql error '12505'
[dboci.c      6550]
C Try to connect with default password
C Connecting as SAPR3/<pwd>@PRD on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12505
[dboci.c      2423]
C *** ERROR => CONNECT failed with sql error '12505'
[dboci.c      6550]
C Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@PRD on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12505
[dboci.c      2423]
C *** ERROR => CONNECT failed with sql error '12505'
[dboci.c      6550]
C Try to connect with default password
C Connecting as SAPR3/<pwd>@PRD on connection 0 ...
C *** ERROR => OCI-call 'olog' failed: rc = 12505
[dboci.c      2423]
C *** ERROR => CONNECT failed with sql error '12505'
[dboci.c      6550]
B ***LOG BY2=> sql error 12505 performing CON [dbsh    0695 ]
B ***LOG BY0=> [dbsh    0695 ]
B ***LOG BY2=> sql error 12505 performing CON [dblink 0627 ]
B ***LOG BY0=> [dblink 0627 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1069]
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   7751]
M
M Info for wp 0
M
M    stat = 4
M    reqtype = 1
M    act_reqtype = -1
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = -1
M    rq_source = 255
M    last_tid = 0
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server sap_PRD_00 on host sap (wp 0)
M * ERROR       tskh_init: db_connect
M *
M * TIME        Sat May 09 21:08:37 2015
M * RELEASE     46D
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        7831
M * COUNTER     1
M *
M *****************************************************************************
M
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 2444) [dpnttool.c   300]

Hi,
Restart the listener and try again. If that doesnt work, follow this note - 576919.
Regards
Cyrus

WARNING - Attempting to resync due to missed delta reports (sp return code = 7)

Hello,
I have investigated and found out that there are more than 150 machines which are not reporting their H/W inventory.
When checking on some of the machines, there are following entries in dataldr.log
Processing Inventory for Machine: ABC Version 44.2 Generated: 12/05/2014 11:42:15
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
Begin transaction: Machine=ABC(GUID:############)
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
WARNING - Attempting to resync due to missed delta reports (sp return code = 7)
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
Rollback transaction: Machine=ABC(GUID:#############)
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
SQL MESSAGE: spAddInventoryLog - Inventory Log for machine:ABC,Server:1.10,Client:44.2,Message:Missing Delta. Resync,Detail:
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
Remote client hardware inventory resync generated for client GUID:#############; update/insert result = 1
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
Send resync command to local site for machine GUID:#############.
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
STATMSG: ID=2722 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_INVENTORY_DATA_LOADER" SYS=<primary server> SITE=SiteCode PID=19068 TID=15432 GMTDATE=Fri Dec 05 10:43:09.184 2014 ISTR0="ABC" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)
Cannot process MIF XHAOPNXZQ.MIF, moving it to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\DeltaMismatch\1ub4cajr.MIF
SMS_INVENTORY_DATA_LOADER 12/5/2014 4:13:09 PM
15432 (0x3C48)

Hey Garth,
I have forced the full inventory already but here are the results.
Inventoryagent.log - Before the full inventory
Inventory: *********************** Start of message processing. ***********************
InventoryAgent 12/6/2014 6:23:14 PM
5776 (0x1690)
Inventory: Message type is InventoryAction InventoryAgent
12/6/2014 6:23:15 PM 5776 (0x1690)
Inventory: Temp directory = C:\Windows\CCM\Inventory\Temp\
InventoryAgent 12/6/2014 6:23:15 PM
5776 (0x1690)
Inventory: Clearing old collected files. InventoryAgent
12/6/2014 6:23:15 PM 5776 (0x1690)
Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} ...
InventoryAgent 12/6/2014 6:23:15 PM
5776 (0x1690)
Inventory: Action=Hardware, ReportType=Delta, MajorVersion=48, MinorVersion=1
InventoryAgent 12/6/2014 6:24:09 PM
5776 (0x1690)
Inventory: Initialization completed in 54.553 seconds
InventoryAgent 12/6/2014 6:24:09 PM
5776 (0x1690)
Inventoryagent.log - Full Inventory
Inventory: *********************** Start of message processing. ***********************
InventoryAgent 12/6/2014 6:31:11 PM
5668 (0x1624)
Inventory: Message type is InventoryAction InventoryAgent
12/6/2014 6:31:11 PM 5668 (0x1624)
Inventory: Temp directory = C:\Windows\CCM\Inventory\Temp\
InventoryAgent 12/6/2014 6:31:11 PM
5668 (0x1624)
Inventory: Clearing old collected files. InventoryAgent
12/6/2014 6:31:11 PM 5668 (0x1624)
Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} ...
InventoryAgent 12/6/2014 6:31:11 PM
5668 (0x1624)
CInvState::VerifyInventoryVersionNumber: Mismatch found for '{00000000-0000-0000-0000-000000000001}': 48.1 vs. 0.0
InventoryAgent 12/6/2014 6:32:05 PM
5668 (0x1624)
Inventory: Version number mismatch; will do a Full report.
InventoryAgent 12/6/2014 6:32:05 PM
5668 (0x1624)
Inventory: Action=Hardware, ReportType=ReSync, MajorVersion=49, MinorVersion=0
InventoryAgent 12/6/2014 6:32:05 PM
5668 (0x1624)
Inventory: Initialization completed in 53.212 seconds
InventoryAgent 12/6/2014 6:32:05 PM
5668 (0x1624)
*+*+*++*+*+*+
*+*+*+*+*+*+
Collection: 57/69 inventory data items successfully inventoried.
InventoryAgent 12/6/2014 6:32:29 PM
6596 (0x19C4)
Inventory: Collection Task completed in 23.993 seconds
InventoryAgent 12/6/2014 6:32:29 PM
6596 (0x19C4)
Inventory: 12 Collection Task(s) failed. InventoryAgent
12/6/2014 6:32:29 PM 6596 (0x19C4)
Inventory: Temp report = C:\Windows\CCM\Inventory\Temp\d3d81696-58c0-4313-a108-258996a0a75f.xml
InventoryAgent 12/6/2014 6:32:29 PM
6596 (0x19C4)
dataldr.log
*** [22001][8152][Microsoft][SQL Server Native Client 11.0][SQL Server]String or binary data would be truncated. : pINSTALLED_SOFTWARE_DATA
SMS_INVENTORY_DATA_LOADER 12/6/2014 3:03:16 PM
11696 (0x2DB0)
ERROR - SQL Error in SMS_INVENTORY_DATA_LOADER
12/6/2014 3:03:16 PM 11696 (0x2DB0)
ERROR - is NOT retyrable. SMS_INVENTORY_DATA_LOADER
12/6/2014 3:03:16 PM 11696 (0x2DB0)
Rollback transaction: Machine=ABC(GUID:EE4DB508-7271-4568-9A6D-0C4A64569AE4)
SMS_INVENTORY_DATA_LOADER 12/6/2014 3:03:16 PM
11696 (0x2DB0)
Cannot process MIF XHFR7KJDQ.MIF, moving it to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\ErrorCode_4\hnue114o.MIF
SMS_INVENTORY_DATA_LOADER 12/6/2014 3:03:16 PM
11696 (0x2DB0)
STATMSG: ID=2703 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_INVENTORY_DATA_LOADER" SYS=PRIMARY SERVER SITE=SITECODE PID=12272 TID=11696 GMTDATE=Sat Dec 06 09:33:16.513 2014 ISTR0="XHFR7KJDQ.MIF" ISTR1="C:\Program Files\Microsoft
Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\ErrorCode_4\hnue114o.MIF" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_INVENTORY_DATA_LOADER 12/6/2014 3:03:16 PM
11696 (0x2DB0)
The error here is C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\ErrorCode_4, but it is different for other machines where i tried the full inventory.

DBM_CONNECT error, return code -11, tp error

Hello
I have an SCM 5.0 ABAP-only system (sid=APC) not correctly communicating with a 7.6.0.3 liveCache. In transaction LC10, clicking the monitoring button for any DB connection results in:
Name and Server     : LPC - dngdbs07
DBMRFC Function     : DBM_CONNECT
Error               : DBM Error
Return Code         :        -11
Error Message       : tp error: sapparam: SAPSYSTEMNAME neithe
Notice how error message is cut off ...
1. LCA, LDA, and LEA connection tests in DB59 all fail with the same error.
2. From transaction SM49, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> fails with the same error.
3. From the command-line, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> succeeds for both apcadm and SAPserviceAPC users. (ABAP system is Windows, liveCache system is HP-UX.)
4. RFC destinations SAPDB_DBM, SAPDB_DBM_DAEMON, and SAPXPG_DBDEST_<HOSTNAME> are all successful.
5. I un-checked the Central Authorization checkbox in LC10 --> Integration and the error goes away, so I can then see the liveCache system status.
I tried debugging the ABAP and it appears sapxpg is having trouble calling the external command when Central Authorization is enabled. Does anyone have any ideas about what's wrong with this?
SAP_BASIS SP 14
NW 700 kernel patch 159
non-unicode
Thanks

> Name and Server     : LPC - dngdbs07
> DBMRFC Function     : DBM_CONNECT
> Error               : DBM Error
> Return Code         :        -11
> Error Message       : tp error: sapparam: SAPSYSTEMNAME neithe
>
> Notice how error message is cut off ...
Ok, the cutoff is just due to the error handling routine - I believe the full error message would be "SAPSYSTMNAME neiter in environment or parameterfile specified" or something like this.
> 1. LCA, LDA, and LEA connection tests in DB59 all fail with the same error.
Of course they do - they are all the same connection setup, just for different purposes.
> 2. From transaction SM49, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> fails with the same error.
Of course it does. The TP is used to get logon data from the SCM database (central authorization) for the logon to the liveCache. with the -tpp -tpi -tpc arguments you tell dbmcli to use TP.
> 3. From the command-line, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> succeeds for both apcadm and SAPserviceAPC users. (ABAP system is Windows, liveCache system is HP-UX.)
Well, perhaps you've a different environment setup here? On Windows it's a quite common issue that everything works fine as <SID>adm but the SAP workprocesses run as SAPSERVICE<SID> ... so checking the environment variables for both might be a good idea.
> 4. RFC destinations SAPDB_DBM, SAPDB_DBM_DAEMON, and SAPXPG_DBDEST_<HOSTNAME> are all successful.
Sure - they've nothing to do with TP. Instead these are just calls to the dbmcli command. SAPDB_DBM is just running one command and returning the result, where SAPDB_DBM_DEAMON is used for multiple commands in one DBM session.
> 5. I un-checked the Central Authorization checkbox in LC10 --> Integration and the error goes away, so I can then see the liveCache system status.
Also quite clear - TP is only used with dbmcli when central authorization is used. If it's not used, then XUSER data is used to connect to the liveCache.
> I tried debugging the ABAP and it appears sapxpg is having trouble calling the external command when Central Authorization is enabled. Does anyone have any ideas about what's wrong with this?
As already said: check the environment variables. Also check the Transportprofile (TMS).
If you don't succeed: open a support message.
regards,
Lars

BAPI-RETURN CODE INF

Hi everybody what is the main purpose of return code.
Data dictionary structures
-BAPIRETURN
-BAPIRETURN1
-BAPIRET1
-BAPRET2.
THANKS IN ADVANCE.

Each BAPI has a return parameter that is either an export parameter or an export table.
A BAPI should be able to record and classify all possible errors that may occur.
You have to create a parameter named Return for every BAPI. This parameter returns exception messages or success messages to the calling program.
BAPIs themselves must not trigger any messages (such as MESSAGE xnnn) in the coding. In particular they must not generate terminations or display dialog boxes. Instead, all messages must be intercepted internally and reported back to the calling program in the Return parameter. Otherwise the BAPI will not be processed correctly and control may not be given back to the calling program.
The export parameter Return can be implemented as follows:
As a structure, whereby it must be defined in the function module as an export parameter, as well as in the method in the BOR.
As a table, whereby it must be defined in the function module as a table parameter, as well as in the method in the BOR as an export parameter.
Before filling the Return parameter you should either initialize the structure with CLEAR or the table with REFRESH and CLEAR.
If the return parameter is not set or is set to an initial value this means that no error has occurred.
The Return parameter may be based on the following reference structures:
BAPIRET2
You must use this reference structure when developing new BAPIS.
BAPIRET1, BAPIRETURN
These reference structures are still partly used in old BAPIs.
Both structures must be filled in the logon language.
Have a look at return parameters in below link.
http://help.sap.com/saphelp_nw04/helpdata/en/a5/3ec9f74ac011d1894e0000e829fbbd/frameset.htm
Best Regards,
Vibha
*Please mark all the helpful answers

Return code 99 in BPM

Hi,
I tried to activate manaully (SXI_CACHE) in BPM and also cleared full cache in RWB. But even thought the return code is 99 for my BPM processs. I am not using any sychronous communcation my versionis PI 7.0 with sp 9. Please let me know is there any other way of making return code as 0
regards,
Dhil

Hi Dhil,
Perform a complete cache refresh using the url
http://host:port/CPACache/refresh?mode=full
u hav to use PIDIRUSER for this. After cache refresh, activate ur Integration Process in the SXI_CACHE tcode.
Anil

Return code and handle

Back to basics! but I do not have clear idea of what the "Return Code" and "Handle" are? I have a small VI that I want to incorporate into another VI. WHat role these two terms play such case?
Thanks

Sorry about ot being clear about my issue. I have a Trigger Enable VI that someone (in fact, a company whose DAQ card we use for our experiements) wrote for us. The VI, when corrently incorporated into the main VI (which performs data acquisition and analysis) will trigger the acquisition system at right instant and gather data for next 1/10 sec. The main VI controls the DAQ card installed in our computer. It takes two signals (f=25KHz) as inputs from 2 photo detectors. The card can take the ramp output (f=10Hz, Amp=1Vpp) from an external signal generator and should begin DAQ and processing when the ramp signal reaches its peak (+0.5V) and continue taking data until it reaches trough (-0.5V), i.e. 5000 samples in one cycle of trigger signal.
Now, the main VI has multiple Sub-VI's and one of them configures the card for input signal levels, trigger levels, etc. This sub-VI also has a couple of sub-VIs regarding the extermal triggering. Since I figured that the Trigger Enable VI will have to be placed inside this VI, I was looking at the block diagram of the Trigger Enable VI and the two outputs it has are "Handle Out" and "Return Code". I am not sure what they are/mean hence the post.
Thank you

Return code 4 when converting field GN_PAR_SSY in record

Hi friends,
This is very much urgent.
I am getting error
"Record 1 :Return code 4 when converting field GN_PAR_SSY in record " while extracting customer text through 0customer_text.
In the transfer rule there is nothing assigned to the infobjects 0GN_PAR_SSY.
My source system is EEC 6.0.
I am not getting this error on development and quality servers.
Regards,
Sane M. V.

Hi mahendra , just have a look on the routine , for this infobject.
PROGRAM CONVERSION_ROUTINE.
Type pools used by conversion program
TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
InfoObject 0PLANT: CHAR - 000004
WERKS(000004) TYPE C,
InfoObject 0POSTAL_CD: CHAR - 000010
PSTLZ(000010) TYPE C,
InfoObject 0PURCH_ORG: CHAR - 000004
EKORG(000004) TYPE C,
InfoObject 0SALESORG: CHAR - 000004
VKORG(000004) TYPE C,
InfoObject 0FACTCAL_ID: CHAR - 000002
FABKL(000002) TYPE C,
InfoObject 0COUNTRY: CHAR - 000003
LAND1(000003) TYPE C,
InfoObject 0REGION: CHAR - 000003
REGIO(000003) TYPE C,
InfoObject 0COUNTY_CDE: CHAR - 000003
COUNC(000003) TYPE C,
InfoObject 0DISTR_CHAN: CHAR - 000002
VTWEG(000002) TYPE C,
InfoObject 0RT_CUSTPL: CHAR - 000010
KUNNR(000010) TYPE C,
InfoObject 0PLANTCAT: CHAR - 000001
VLFKZ(000001) TYPE C,
InfoObject 0SALES_DIST: CHAR - 000006
BZIRK(000006) TYPE C,
dummy field to avoid syntax error
    $dummy(1) type c,
END OF TRANSFER_STRUCTURE .
Global code used by conversion rules
$$ begin of global - insert your declaration only below this line -
DATA:   l_s_errorlog TYPE rssm_s_errorlog_int,
        l_text TYPE string.
$$ end of global - insert your declaration only before this line   -
      FORM COMPUTE_GN_R3_SSY
Compute value of InfoObject 0GN_R3_SSY
in communication structure /BIC/CS0PLANT_ATTR
Technical properties:
    field name      = GN_R3_SSY
    data element    = /BI0/OIGN_R3_SSY
    data type       = CHAR
    length          = 000002
    decimals        = 000000
    ABAP type       = C
    ABAP length     = 000004
    reference field =
Parameters:
--> RECORD_NO       Record number
--> TRAN_STRUCTURE Transfer structure
<-- RESULT          Return value of InfoObject
<-> G_T_ERRORLOG    Error log
<-- RETURNCODE      Return code (to skip one record)
<-- ABORT           Abort code (to skip whole data package)
FORM COMPUTE_GN_R3_SSY
USING    RECORD_NO LIKE SY-TABIX
           TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
           G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OIGN_R3_SSY
           G_T_ERRORLOG TYPE rssm_t_errorlog_int
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
$$ begin of routine - insert your code only below this line        -
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
CALL FUNCTION 'RSDG_ID_GET_FROM_LOGSYS'
    EXPORTING
      i_source_system = G_S_MINFO-LOGSYS
    IMPORTING
      e_soursysid     = RESULT
    EXCEPTIONS
      id_not_found    = 1.
IF sy-subrc <> 0.
    RETURNCODE = 4.
    MESSAGE e087(r7) WITH G_S_MINFO-LOGSYS INTO l_text.
    MOVE-CORRESPONDING syst TO l_s_errorlog.
    l_s_errorlog-record = RECORD_NO.
    APPEND l_s_errorlog TO g_t_errorlog.
ABORT = 1.
ENDIF.
$$ end of routine - insert your code only before this line         -
ENDFORM.
      FORM INVERT_GN_R3_SSY
      Inversion of selection criteria for InfoObject 0GN_R3_SSY
      This subroutine needs to be implemented only for SAP RemoteCubes
      (for better performance) and for the Report/Report Interface
      (drill through).
--> I_RT_CHAVL_CS       Ranges table for current InfoObject
--> I_THX_SELECTION_CS Selection criteria for all other InfoObjects
<-- C_T_SELECTION       Selection criteria for fields of
                          transfer structure
<-- E_EXACT             Flag: Inversion was exact
FORM INVERT_GN_R3_SSY
USING    I_RT_CHAVL_CS      TYPE RSARC_RT_CHAVL
           I_THX_SELECTION_CS TYPE RSARC_THX_SELCS
CHANGING C_T_SELECTION      TYPE SBIWA_T_SELECT
           E_EXACT            TYPE RS_BOOL.
$$ begin of inverse routine - insert your code only below this line-
DATA:
    L_S_SELECTION LIKE LINE OF C_T_SELECTION.
An empty selection means all values
CLEAR C_T_SELECTION.
Selection of all values may be not exact
E_EXACT = RS_C_FALSE.
$$ end of inverse routine - insert your code only before this line -
ENDFORM.
Hope it helps , assign pts if helpful

Return code 3 when converting field /BIC/IHRBGCF in record 31

Hi All,
i got an error in psa
Return code 3 when converting field /BIC/IHRBGCF in record 31
Could you please help me on this error
Thanks in advance
Nitya

Hi ,
error in PSA
FORM COMPUTE_/BIC/IHRBGCF
USING    RECORD_NO LIKE SY-TABIX
           TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
           G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BIC/OIIHRBGCF
           G_T_ERRORLOG TYPE rssm_t_errorlog_int
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel datapackage
$$ begin of routine - insert your code only below this line        -
DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
V_PROD_LN = TRAN_STRUCTURE-PROD_LN .
Have to add the strange logic below, because ALPHA conversion
on 0PROFIT_CTR in the data source does not seem to work...
IF V_PROD_LN CO ' 0123456789' .
i.e. if input is numberic or empty,
then add 00000000 to "make" it into ALPA
Otherwise (if alpha) keep as-is, i.e. no ELSE
    CONCATENATE '00000000' V_PROD_LN+0(2) INTO V_PROD_LN.
ENDIF.
End of "ALPHA" logic
Do the lookup in IHRPLSEG first...
SELECT SINGLE /BIC/IFISEGCD
INTO V_IFISEGCD
FROM /BIC/PIHRPLSEG
WHERE PROFIT_CTR = V_PROD_LN
     AND CO_AREA = TRAN_STRUCTURE-KOKRS .
If no match found in IHRPLSEG,
then take incoming PROD_LN as-is.
IF SY-SUBRC <> 0.
    V_IFISEGCD = TRAN_STRUCTURE-PROD_LN .
ENDIF.
IF V_IFISEGCD CO ' '.
i.e. if incoming PROD_LN was blank
or if SEGCD returned from IHRPLSEG is blank...
    RETURNCODE = 1.
ELSE.
Getting date ...
    SELECT SINGLE LOW
    INTO TVARVC-LOW
    FROM TVARVC
    WHERE NAME = 'ZIHRBW_DATE' AND TYPE = 'P'.
    TO DETERMINE CAL PERIOD...
    V_CALPER = TVARVC-LOW(6).
    For numeric incoming values we have to add 00
    to find the match, because in BW 0COMPANY is CHAR(6)...
    CONCATENATE '00' TRAN_STRUCTURE-BUKRS INTO COMPANY_STR.
    get M/L indicator from 0COMPANY..
    SELECT SINGLE /BIC/IMYSEPAR
    INTO /BI0/PCOMPANY-/BIC/IMYSEPAR
    FROM /BI0/PCOMPANY
    WHERE COMPANY = COMPANY_STR
      AND OBJVERS = 'A'
      AND /BIC/IFIVFR =< V_CALPER
      AND /BIC/IFIVTO => V_CALPER.
    IF SY-SUBRC <> 0.
    i.e. if no match found in 0COMPANY,
    then try to find a match without added zeros...
      SELECT SINGLE /BIC/IMYSEPAR
      INTO /BI0/PCOMPANY-/BIC/IMYSEPAR
      FROM /BI0/PCOMPANY
      WHERE COMPANY = TRAN_STRUCTURE-BUKRS
        AND OBJVERS = 'A'
        AND /BIC/IFIVFR =< V_CALPER
        AND /BIC/IFIVTO => V_CALPER.
    ENDIF.
do the lookup in InfoObject IHRPLBG...
Need to strip zeros first...
    SHIFT V_IFISEGCD LEFT DELETING LEADING '0'.
    SELECT SINGLE /BIC/IHRBGCF
    INTO /BIC/PIHRPLBG-/BIC/IHRBGCF
    FROM /BIC/PIHRPLBG
    WHERE /BIC/IFISEGCD = V_IFISEGCD
      AND /BIC/IMYSEPAR = /BI0/PCOMPANY-/BIC/IMYSEPAR
      AND OBJVERS = 'A'.
    IF NOT /BIC/PIHRPLBG-/BIC/IHRBGCF IS INITIAL.
i.e. if match found in IHRPLBG...
      RESULT = /BIC/PIHRPLBG-/BIC/IHRBGCF.
      RETURNCODE = 0.
    ELSE.
      IF /BI0/PCOMPANY-/BIC/IMYSEPAR IS INITIAL .
i.e. no match found in 0COMPANY
        RETURNCODE = 3.
      ELSE.
i.e. no match found in IHRPLBG
        RETURNCODE = 2.
      ENDIF.
    ENDIF.
ENDIF.
CLEAR: ZTHRBW_SEG_MAP-IFISEGCD, /BIC/PIHRPLBG-/BIC/IHRBGCF.
CLEAR: /BIC/PIHRPLBG-/BIC/IHRBGCF, /BI0/PCOMPANY-/BIC/IMYSEPAR.
CLEAR: V_IFISEGCD, V_PROD_LN, COMPANY_STR, V_CALPER.
returncode <> 0 means skip this record
RETURNCODE = 0.
abort <> 0 means skip whole data package !!!
ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.
      FORM INVERT_/BIC/IHRBGCF
      Inversion of selection criteria for InfoObject IHRBGCF
      This subroutine needs to be implemented only for SAP RemoteCubes
      (for better performance) and for the Report/Report Interface
      (drill through).
--> I_RT_CHAVL_CS       Ranges table for current InfoObject
--> I_THX_SELECTION_CS Selection criteria for all other InfoObjects
<-- C_T_SELECTION       Selection criteria for fields of
                          transfer structure
<-- E_EXACT             Flag: Inversion was exact
FORM INVERT_/BIC/IHRBGCF
USING    I_RT_CHAVL_CS      TYPE RSARC_RT_CHAVL
           I_THX_SELECTION_CS TYPE RSARC_THX_SELCS
CHANGING C_T_SELECTION      TYPE SBIWA_T_SELECT
           E_EXACT            TYPE RS_BOOL.
$$ begin of inverse routine - insert your code only below this line-
DATA:
    L_S_SELECTION LIKE LINE OF C_T_SELECTION.
An empty selection means all values
CLEAR C_T_SELECTION.
L_S_SELECTION-FIELDNM = 'BUKRS'.
L_S_SELECTION-FIELDNM = 'KOKRS'.
L_S_SELECTION-FIELDNM = 'PROD_LN'.
Selection of all values may be not exact
E_EXACT = RS_C_FALSE.
$$ end of inverse routine - insert your code only before this line -
ENDFORM.
Please advise
Thanks in Advance
Nitya

Clearing returned an unexpected returned code: 1 in MDT 2013

Similar Messages

Maybe you are looking for