sapAdapter, ErrorGroup=RFC_ERROR_LOGON_FAILURE. SapErrorMessage=Incomplete logon data ???


hi, have scenario need listen sap send data biztalk. biztalk sends success response back. succesfully created reference in visual studio sap rfc using consume adapter service add-in in visual studio. able connect sap system , choose rfc. deployed application in bts. , used binding file created add-in add receive location. provided username , password in other tab. however, when run application, following results.. 1. when receive port started, starts , keeps running, when in trace file, see following error "details: errorcode=rfc_ok. errorgroup=rfc_error_logon_failure. saperrormessage=incomplete logon data.. adaptererrormessage=.". receive port not stop working , stays green. 2. when sap program invoked send data bts, runs, on biztalk side, complete silence. no errors no running processes, no event log entry, nothing @ all. wrong?? make sure have right, built simple app , got same results. added send port input go file. http://msdn.microsoft.com/en-us/library/cc185318(v=bts.10).aspx 1 have idea wrong?? feedback appreciated. thanks

the receive location tab tricked it's green. press f5 (refresh) on page can see actual status, suspect it's red.

double check connection info, username , retype password if needed.

randy aldrich paulo

mcts(biztalk 2010/2006,wcf net4.0), mcpd | my blog


biztalk message archiving - sql , file
automating/silent installation of biztalk deployment framework using powershell >
sending idocs using ssis



BizTalk Server  >  BizTalk Server Adapters and Adapter Pack



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more