Error in eCATT command TCD SU01

Dear All,
I am getting an error while working with eCATT in one of our test servers.
I am getting some errors while executing the Test Script (for creating multiple users).
Error Messages -
Error in eCATT command TCD SU01
No batch input data for screen SAPLSUU5 0050
I have done all the pre-requisites needed for eCATT script enabling.
Please suggest as soon as possible.
Points will be definitely rewarded.
It's very very urgent.
Thanks & Regards,
Sameer

Hello Sameer
Screen '0050' of function group SUU5 is the SU01 initial screen for user maintenance where you enter the user name.
If you get a batch-input error there are several possible explanations:
1. You want to create a new user but the eCATT data do not have a username
2. You want to create a new user but a user with the username does already exist
3. You want to change an existing user but the eCATT data do not have a username
4. You want to change an existing user but the user was locked by somebody else.
Conclusion: If you are very confident about the quality of your testscript then you have to search the error in your eCATT data.
Before executing command TCD 'SU01' do you check whether a user with the username of the eCATT data does exist or not? Obviously you need two different testscripts for this two scenarios.
There might also be a server specific reason. For example, if your suspicious test server is a daughter system of the CUA then you are no longer allowed to create users locally on this system.
Regards
Uwe

Similar Messages

'SESSION_MANAGER' error in ecatt

Hi ,
I am trying to record a transaction in SAPGUI mode ,then I select 'pattern' then 'SAPGUI record'
then give the granuality then when I press the 'start recording' button I am getting the following
message
Error in target system: User does not have
authorization for transaction SESSION_MANAGER or
transaction does not exist in target system
I am using target system as none
any idea how to resolve this .

Hello Sameer
Screen '0050' of function group SUU5 is the SU01 initial screen for user maintenance where you enter the user name.
If you get a batch-input error there are several possible explanations:
1. You want to create a new user but the eCATT data do not have a username
2. You want to create a new user but a user with the username does already exist
3. You want to change an existing user but the eCATT data do not have a username
4. You want to change an existing user but the user was locked by somebody else.
Conclusion: If you are very confident about the quality of your testscript then you have to search the error in your eCATT data.
Before executing command TCD 'SU01' do you check whether a user with the username of the eCATT data does exist or not? Obviously you need two different testscripts for this two scenarios.
There might also be a server specific reason. For example, if your suspicious test server is a daughter system of the CUA then you are no longer allowed to create users locally on this system.
Regards
Uwe

Error when using the REF eCATT command ....

Hi,
When the REF command is used in an eCATT test script to execute another eCATT, only the first REF command executes successfully - all subsequent REF commands fail with these error msgs 'Error in eCATT function SAPGUI', 'Error in Control', 'Message raised at CL_APL_ECATT_LINE_INTERPRETER =CM00K LINE   347'.
Executed separately, the referenced eCATT test scripts are successful.   Executed from one eCATT test script via the REF command, only the first REF command is successful. We are on SAP 6.7 6.40, GUI is 6.40 as well.
Any suggestions would be appreciated - Thanks !

Thanks for the reply, Jonathan.   Still having the same problem after implementing your suggestion.   Any other suggestions you have would be appreciated.
The ResetGUI = 'X' was done for each command interface in the REFerenced test scripts.   The ResetGUI statement was only found immediately after the 'Command Interface' statement (wasn't found after the 'Processed Screen' statement).
The error still happens for the second and all subsequent test scripts referenced by the 'REF' command.   In the failed REF test scripts, the ConnectionID, SessionID, and SystemInfo statements are the failed statments (red lights beside them).   These three statements are immediately after the ResetGUI = 'X' statment (which has a green light).
Different execution options have been tried, including closing, and not closing, generated GUI sessions.
Really at a loss here to figure out how to get the REF statement to work !

Error During ECATT test script creation

Hi,
I am creating test script using SECATT t.cde. I select traget system and click on Pattern Button and provide input as follow.
Group : UI Control
Command : TCD (Record)
Transaction : MM02
When I click continue button, I am getting error "Transaction MM02 could not be found in Target System".
I had check my RFC Configuration, its working properly.
Please help me to solve this issue.
Regards,
Nisit

Not sure what exactly you're asking, but here is a "how-to" article on eCATT creation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50bec015-14f1-2910-6080-9874b3499052

Understanding Message EndMessage ecatt command.

Hello Gurus,
Could someone please explain how we can use Message EndMessage command. I have gone through the ecatt command reference on help.sap but I am unable to follow it.
I am using a TCD command which runs a program and within that program it calls and executes different methods and function modules. If the program executes sucessfully then it updates some tables and if does not run sucessfully then it shows corresponding message. So all that I want to do is check for those messages based on return type and display the same message in ecatt log when program does not run sucessfully and the next steps should not be run.
Your help in this regard is highly appreciated.
Regards,
GS.

Hello Ajay,
I have tried using this command however I am not getting the desired output. I dont know whether I am doing it correctly or not. So I will explain it to you and please let me know if I am doing it the right way:
MESSAGE ( MSG_1 ).
TCD ( SE38 , SE38_3 ).
ENDMESSAGE ( E_MSG_1 )
Within the program I have different methods and function modules. for all of them return_type, return_id and return_no are the same only msgv1 to msgv4 are different. I am hoping return_type, return_id and return_no are same as msg_type, msg_id and msg_no. So in Message command Interface i am passing return_type, return_id and return_no into msg_type, msg_id and msg_no and setting mode as E.
When i run the script i get error "specify a program name". So i am not sure I am doing the right way.
Also i would like to know how to get the message that is there in msgv1 to msgv4 in log. That is I am looking to print the message in log for the message I get during pgm execution.
Thanks for your attention.
Regards,
GS
Hi GS,
According to me the problem doesn't lie in MSG and END MSG block rather the problem should be in your recording ( SE38 --> ABAP Editor) itself. The program name to the initial screen to be passed(along with other parameters) while playback or during execution of eCATT so i think that the program name isn't passed or this field is either not parameterized or not handled in a right way. Please check whether you have parameterized the right field or check your Dynpros(or check TCD interface again)
If you still get problem after you have checked the interface then please let us know.
Thanks and Kind Regards
Mohan Kumar K

Error MSB3073: The command exited with code -1

I am getting this error while deploying the biztalk project from visual studio using Deployment Framework for Biztalk (BTDF).
Please guide me what needs to be done. Here's the code :-
<?xml version="1.0" encoding="utf-8"?>

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="Installer" ToolsVersion="4.0">
<PropertyGroup>
<Configuration Condition="'$(Configuration)' == ''">Debug</Configuration>
<Platform Condition="'$(Platform)' == ''">x86</Platform>
<SchemaVersion>1.0</SchemaVersion>
<ProjectName>HelloWorld</ProjectName>
<ProjectVersion>1.0</ProjectVersion>
<IncludeOrchestrations>False</IncludeOrchestrations>
<IncludeTransforms>False</IncludeTransforms>
<IncludeSSO>True</IncludeSSO>
<UsingMasterBindings>True</UsingMasterBindings>
<RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
<ApplyXmlEscape>True</ApplyXmlEscape>
<SkipIISReset>True</SkipIISReset>
</PropertyGroup>
<PropertyGroup>






<ProductVersion>1.0.0</ProductVersion>
<ProductId>084986b1-d675-4383-b0ed-da2e3f4e3998</ProductId>

<ProductName>HelloWorld for BizTalk</ProductName>
<Manufacturer>Deployment Framework User</Manufacturer>
<PackageDescription>HelloWorld</PackageDescription>
<PackageComments>HelloWorld</PackageComments>

<ProductUpgradeCode>4975288c-1b94-4d42-868b-f166cdc02224</ProductUpgradeCode>
</PropertyGroup>



<PropertyGroup Condition="'$(Configuration)' == 'Debug'">
<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
<OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Debug\</OutputPath>
<OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
<DeployPDBsToGac>false</DeployPDBsToGac>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)' == 'Release'">
<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
<OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>
<OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
<DeployPDBsToGac>false</DeployPDBsToGac>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)' == 'Server'">
<DeploymentFrameworkTargetsPath>Framework\</DeploymentFrameworkTargetsPath>

<DeployPDBsToGac>true</DeployPDBsToGac>
</PropertyGroup>
<ItemGroup>
<PropsFromEnvSettings Include="SsoAppUserGroup;SsoAppAdminGroup" />
</ItemGroup>



<ItemGroup>
<Schemas Include="HelloWorld.dll">
<LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
</Schemas>
</ItemGroup>

<Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />

<Target Name="CustomRedist">
</Target>
</Project>
Error :-
Starting build...
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" /nologo /t:Deploy /p:Configuration=Debug
Build started 08-04-2015 17:43:51.
Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" on node 1 (Deploy target(s)).
SetModeDeploy:
DEPLOYING APPLICATION TO BIZTALK...
SetWinVer:
Running on Windows V62
Detected IIS 7
Detected 64-bit OS
GetSoftwarePaths:
Using .NET Framework Install Path 'C:\Windows\Microsoft.NET\Framework\v4.0.30319'.
Using BizTalk Install Path 'C:\Program Files (x86)\Microsoft BizTalk Server 2013\'.
Using Deployment Framework Install Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\'.
Using Deployment Framework Tools Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools'.
Using BizTalk ESB Toolkit Install Path 'C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\'.
ExportSettings:
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\EnvironmentSettingsExporter.exe" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings"
Environment Settings Spreadsheet to XML Exporter 1.6.1
[http://EnvSettingsManager.codeplex.com]
Copyright (C) 2007-11 Thomas F. Abraham. All Rights Reserved.
Importing from SettingsFileGenerator.xml...
Output format is XmlPreprocess (multi-file).
Exporting to Exported_LocalSettings.xml...
Exporting to Exported_DevSettings.xml...
Exporting to Exported_TestSettings.xml...
Exporting to Exported_ProdSettings.xml...
Finished.
InitSettingsFilePath:
Using settings file C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml
SetPropertiesFromEnvironmentSettings:
Setting properties from environment settings file (C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml)
Setting property to value 'BizTalk Application Users'.
Setting property to value 'BizTalk Server Administrators'.
InitializeAppName:
BizTalk Application Name is HelloWorld
PreprocessBindings:
Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml'...
Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml' appears to be valid.
Clearing file attributes for 'PortBindings.xml'.
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\xmlpreprocess.exe" /v /c /noDirectives /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /d:CurDir="C:\BTDF\Walkthrough1" /s:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
XmlPreprocess v2.0.18.0
Copyright (c) 2004-2013 Loren M Halvorson
XML File Preprocessor
Settings XML file: "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
Preprocessing "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml"...
PortBindings.xml : Set the value 'HelloWorld' of 2 node(s) matching XPath '//ApplicationName'.
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\ElementTunnel.exe" /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /x:"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\adapterXPaths.txt" /encode+
Nested XML Encoder/Decoder v5.5.100.0
Copyright (C) 2005-2014 Scott Colestock, Tim Rayburn, Thomas F. Abraham
XML encodes/decodes content of element(s) by XPath. Applies escaping rules such
as > for '<'. Namespace decls, PIs, etc. of nested XML are not preserved.
XPaths : 16
Transformed Nodes : 0
Empty Nodes (skipped) : 3
No Transform Req'd (skipped) : 3
Total Matched Nodes : 6
Complete - output file has been saved.
Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml'...
Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml' appears to be valid.
DeployFileAdapterPhysicalPaths:
Configuring FILE adapter physical paths from binding file PortBindings.xml...
Processing FILE adapter physical paths (Send)...
Setting up path 'C:\BTDF\Walkthrough1\Out'...
Directory already exists.
Granted 'BUILTIN\Users' Full Access permissions.
Processing FILE adapter physical paths (Receive)...
Setting up path 'C:\BTDF\Walkthrough1\In'...
Directory already exists.
Granted 'BUILTIN\Users' Full Access permissions.
TerminateServiceInstancesConditional:
Attempting to terminate all service instances for BizTalk app 'HelloWorld'...
Terminated 0 service instances for BizTalk app 'HelloWorld'.
VerifyBizTalkAppExists:
Checking for existence of BizTalk application 'HelloWorld'...
Did not find BizTalk application 'HelloWorld'.
DeployAppDefinition:
BTSTask.exe AddApp -ApplicationName:"HelloWorld" -Description:"HelloWorld"
Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
Copyright (c) 2013 Microsoft Corporation. All rights reserved.
Information: Adding new BizTalk application "HelloWorld" to configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
Information: Added application "HelloWorld".
Command succeeded with 0 errors, 0 warnings.
UndeploySchemas:
Adding assembly name 'HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f' to item group.
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /u "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f"
Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
Number of assemblies uninstalled = 0
Number of failures = 0
DeploySchemas:
BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\HelloWorld\bin\Debug\HelloWorld.dll" -ApplicationName:"HelloWorld" -Options:GacOnAdd,GacOnImport,GacOnInstall
Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
Copyright (c) 2013 Microsoft Corporation. All rights reserved.
Information: Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to application "HelloWorld"...
Serialized BizTalk assembly "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f" from "..\HelloWorld\bin\Debug\HelloWorld.dll".
Information: Validating resources (count=1)...
* Validating resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f")...
Information: Performing change requests...
Information: Calling BeginTypeChangeRequest for all selected resource types...
PerformingBeginChangeRequest
Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to store.
Information: * Performing change request on type "System.BizTalk:BizTalkAssembly" (count=1)...
Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
Information: Deploy operation succeeded.
Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
Information: Deploy operation succeeded.
Information: Deployed the following 1 BizTalk assemblies:
HelloWorld.dll
EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
Information: Commit the change requests...
* Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkAssembly".
Command succeeded with 0 errors, 0 warnings.
DeploySharedAssemblies:
Deploying additional assemblies to GAC...
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /f /i "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileReader.dll"
Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
Assembly successfully added to the cache
Finished deploying additional assemblies to GAC.
ImportBindings:
Copying file from "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
BTSTask.exe AddResource -Type:BizTalkBinding -Overwrite -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml" -ApplicationName:"HelloWorld"
Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
Copyright (c) 2013 Microsoft Corporation. All rights reserved.
Information: Adding resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") to application "HelloWorld"...
Information: Validating resources (count=1)...
* Validating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml")...
Information: Performing change requests...
Information: Calling BeginTypeChangeRequest for all selected resource types...
PerformingBeginChangeRequest
Updating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") in store.
Information: * Performing change request on type "System.BizTalk:BizTalkBinding" (count=1)...
Information: Commit the change requests...
* Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkBinding".
Command succeeded with 0 errors, 0 warnings.
Deleting file "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
BTSTask.exe ImportBindings -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" -ApplicationName:"HelloWorld"
Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
Copyright (c) 2013 Microsoft Corporation. All rights reserved.
Information: Importing bindings "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" into application "HelloWorld" in BizTalk configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
Information: Imported application "HelloWorld" bindings.
Command succeeded with 0 errors, 0 warnings.
DeploySSO:
"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"
Error persisting to SSO:
System.Runtime.InteropServices.COMException (0xC0002A18): The format of the account name is not valid. Domain accounts must include the domain name. Local accounts must not include a domain or computer name.
at Microsoft.BizTalk.SSOClient.Interop.ISSOAdmin.CreateApplication(String applicationName, String description, String contactInfo, String userGroupName, String adminGroupName, Int32 flags, Int32 numFields)
at SSOSettingsFileManager.SSOHelper.CreateApp(String appName, String userGroup, String adminGroup)
at SSOSettingsFileManager.SettingsFileImport.SaveSettingsToSSO(String affiliateAppName, String inSettings, String userGroupName, String adminGroupName)
at SSOSettingsFileManager.SettingsFileImport.Main(String[] args)
C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
Done Building Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target(s)) -- FAILED.
Build FAILED.
"C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
(DeploySchemas target) ->
EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
"C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
(DeploySSO target) ->
C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
1 Warning(s)
1 Error(s)
Time Elapsed 00:00:54.94

Hi Pratibha,
Thank you for posting in MSND forum.
Since
this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
Based
on your issue, since it is related to the Deployment Framework for Biztalk (BTDF), so I suggest you could consult this issue directly to this Deployment Framework for Biztalk (BTDF) website:
https://biztalkdeployment.codeplex.com/discussions , you will get better support.
Thanks for your understanding.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error OTF end command // missing in OTF dat

Hi
I am converting a smartform of a PO into a PDF. when i am using the option of pint immediately in message option of PO. I am getting this error OTF end command // missing in OTF dat . when i am using option 3 which in not print immediately. i am able to convert it into pdf file and save in my local folder. please advice.

when you click the message button while creating a PO. it will take to next page where you add your output type that is output, partner etc.. after you add and click on further data button there you will have option for dispatching here when you add slect option 4 whihc is print immediately. then i am getting the error. if i am using the other options i am able to down load into pdf but not able to see print preview. please advice

Diadem runtime error while executing command "SchemeMeasStar"

Hello:
I used DIAdem9.0 and DAQCard6062E to acquire 16 channel data. I collected 65536 data for every channel. Whereas After the data acquisition stopped, an Error Message would poped up, but the data is still stored in data portal. the Error is like follows:
-Error- DIAdem
Runtime Error While Executing Command "SchemeMeasStar"
Error Type: UNKNOWN
Error Address:00001720
Module Name:GFSBase.Dll
Would you like to give me some suggestions?
thanks very much
jing

Dear MarcusP:
Thank you very much.
your solution really works. The attached is the detailed information of the problem. Would you like to tell me more about the prolem and how to solve the problem thoroughly.
Thank you very much.
yours
Jing
Attachments:
DIAdem_Error.doc ‏305 KB

Error while executing "" command Error type ACCESS VIOLATION Error Address: 0006898E Module name:gfsdesk.DLL

Hi All,
I'm using diadem from .net Program. While on the run I'm getting the following error.
Error While executing "" Command
Error type ACCESS VIOLATION
Error Address: 0006898E
Module name:gfsdesk.DLL
Anyone have any idea why this is happening?
regards,
Swaroop

Hi Swaroop,
It would be helpful to better understand what your code really does. The information that you called DIAdem from your enviroenment is not yet sufficient to understand what the problem might be.
Andreas

Error message: "invalid command line argument" while lodaing itunes

I'm trying to load Itunes onto a computer that already has a version of itunes on it. I get a message that says "error: -1639 invalid command line argument" Does anyone know what this means? Does this mean I can't load itunes onto a computer that already has itunes on it?
Also, I was able to load itunes on my laptop, but My ipod Icon is not appearing anywhere, not in itunes, not in explorer, not in my computer. I am, however, able to transfer music automatically when I plug the Ipod into the laptop. I have created several playlists and they have transferred over to the ipod as playlists. Any ideas why I can transfer despite not being recognized anywhere on the computer?
Last thing is, I have plugged the Ipod into three different computers with itunes on them, and the ipod does not show up in the source list.
I'm somewhat perplexed by all of this. Any help or insight would be greatly appreciated
Dell Windows XP Pro

hiya!
"error: -1639 invalid command line argument"
hmmm. folks typically only get that error if they are installing from removable media (such as a CD), although i have seen it happen if someone tries to install into the "recovery partition" of certain makes of PC.
if you download and save an installer to your C drive and run the install from there, do you still get the 1639?
iTunes 6.0.4.2 Installer
love, b

ERROR: -1639 INVALID COMMAND LINE ARGUMENT

Trying to install software for Shuffle that Santa brought and get this error messsage...
"Error: -1639 invalid command line argument. Consult the windows Installer SDK for detailed command line help."
Install stops at this point.
SOMEONE HELP... My kid is chomping at the bit !
Thanks.

Ok I'll do some more searching but I found something in the community forums.
APPSearch can not return this data into a property, so instead, for some unspeakable reason, returns a value of Null, follwed by another Null. This means that the property is created, and populated with two null characters. Bad news if the property also happens to be a PUBLIC property. All public properties are passed as part of the command line sent in a stream to the background installer process by the Execute Action. Since this stream now contains a double null value in a property, the stream is prematurely terminated. This creates an invalid command line, and thus the 1639 error.
This user solved it by using the MSi Cleanup installer util.
EDIT: A little more info...
This problem is almost impossible to detect through the MSI log files since our friends at Microsoft chose to limit the length of any line in the log. It is impossible to get a dump of the full command line that generates this error.
EDIT2:Note that error 1639 only ocurrs when the install package is run from removable media. When the package is run from local storage, the behavior is far more obtuse. The background install process, failing to receive a complete command line, is forced to run as if there had been no UI session, which in turn causes the APPSearch action to run again as if the install was running in silent mode. This causes re-evaluation of all properties a second time, destroying the feature selections made in the UI session, and also forcing the install to run under user credentials instead of elevated, even though AdminUser, ALLUSERS and Privleged properties are set. This is a very serious error that causes total failure of the installation.

HELP - "Error in script command 1: InstallApp "

I've just upgraded my ipod to a jailbroken 1.1.4 and installed summerboard. But whenever I want to add a new application...i get the following message:
"Error in script command 1: InstallApp"
What do I've to do???

Sorry, these forums are only for supporting Apple's products - a jailbroken iPod is off limits.
Use Google.
Scott

Archive Smartform Copies - Error - OTF end command // missing in OTF data

Hi All,
We are printng invoices and archiving them at the same time.
When I try to print and archive just the original invoice it works fine
That is , it prints and archives.
However when I set the flag SSFCOMPOP-TDARCCOP to 'X' (Archive Copies as well),
I get the error OTF end command // missing in OTF data.
Im guessing that the system tries to archive multiple copies and the End of File Command // at the end of each copy is causing the issue. But I dont know how to go about solving it.
Regards,
Nehal.

Implemented SAP Note 1123505 - OTF-PDF conversion. Archiving several copies

Error durig FTP Command Execution

Hi All,
I run the SE38 --> RSFTP002
and putting below parameters
User: ENGO
Pass: xxxxx
Host: 195.212.13.22 10001
Command: put c:/ftp.txt /In_test/ftp.txt
it takes 10 minutes when execute and got bellow error.
Execute FTP Command
put c:/ftp.txt /In_Test/ftp.txt
NIECONN_BROKEN:TCP/IP Network Connection Broken in getreply()
TCP/IP error, connection terminated
FYI .... i m facing this issue in my office LAN while it is working fine when i execute it from my home mean
different connection(DSL).
how can i resolve this issue and where is fault?
advance thanks,
majamil

Hi ,
Dear, there are execution and output following:
put c:\ftp.txt \In_test\ftp.txt
and
put c:/ftp.txt /In_Test/ftp.txt
Execute FTP Command
put c:\ftp.txt \In_Test\ftp.txt
NIECONN_BROKEN:TCP/IP Network Connection Broken in getreply()
TCP/IP error, connection terminated
and some time i got this error,
Execute FTP Command
put c:/ftp.txt /In_Test/ftp.txt
open c:/ftp.txt errno 22: Invalid argument
about your workstation firewall.
Firewall is Disable in client end and also server end.
Is it allowing the program SAPFTP to execute
when i put SAPFTP in run then i executed mean it display FTP prompt.
Did you check your SAPFTP RFC using RSFTP005?
SA38 --> RSFTP005
SAPFTP check
Check RFC destination SAPFTP..
... OK.
Ping RFC destination SAPFTP...
... OK.
Check RFC destination SAPFTPA.
... OK.
Ping RFC destination SAPFTPA..
... OK.
and also check from SM59 where connection test completed successfully.
regards,

Printer prints ERROR: syntaxerror OFFENDING COMMAND: true cvt fpgm x -glyf

A colleague has mentioned to me that he has seen an apparently intermittent problem when printing from 10.6.6 (but thinks he saw it some time before that) in which a PostScript error page is printed instead of his document. Mac OS X is up to date. The printed page shows:
ERROR: syntaxerror
OFFENDING COMMAND: true cvt fpgm x -glyf , ,head
STACK:
-mark-
/sfnts
The keywords suggest to me that this is a TrueType typeface problem.
Frustratingly, he says he can't remember what application he was printing from, but I suspect that it was Microsoft Word 2008, as that is what he uses for document preparation.
I found another forum topic posting describing this problem - http://discussions.apple.com/thread.jspa?messageID=9264701 - which is now closed and allegedly answered; the final advice was to run FontBook to verify the typefaces. I did this on the system in question, and only a few 'minor' errors were reported. Whether this somehow magically fixed the problem, I don't know.
The user updated Microsoft Office to the 2011 version at my suggestion, this being the only thing I can think might fix the problem. Since the problem was always intermittent, we're waiting to see if the problem reoccurs.
Does anyone know for sure what the cause and fix for the problem are?

pharmastat59 wrote:
Trouble printint to a Dell Laser MFP 1815dn.
Check if the Dell driver is PPC. If it is, and if you installed the first version of Apple's latest Security Update, then that's probably where the issue is, because it broke Rosetta, the software which runs PPC code under SL. Re-install the Sec Update (the problem is fixed in v1.1, which replaced the goofy version on Apple's servers) through Software Update or by downloading it again, then re-install the Dell driver, and try again.
Apple stuff is great, except for their casual disregard of their customers who want to use any product that is not Apple
I'm sorry, but that's non-sense. I'm no fan of Apple, but they're no better and no worse than any large corporation of this type. Mostly, they do things which make business sense as they see it -- which is exactly what you'd want, if you had serious money invested in Apple shares -- wouldn't you?
In this instance, it was up to Dell to release an Intel Mac driver for this printer/scanner, which is, what, 5 or 6 years old? If they didn't, it was probably because they decided it didn't make business sense for them to spend money on developing and testing one. Keep in mind that Dell and Apple and Microsoft and all the rest are in business to make money, not to support every single customer for ever and ever and a day.

Error in eCATT command TCD SU01

Similar Messages

Maybe you are looking for