Error in determining receiver

Hi Experts,
I am facing an error in one of the file to Proxy scenario. It's giving the following error.
SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Error when parsing receiver listLength of XML Document 411 An error occurred when deserializing in the simple transformation program SXI_PARSE_RECEIVERS Data loss occurred when converting ExceptionMessage: LookupValueNotFound: SourceContext: http://sap.com/xi/XI SourceAgency: SenderBusinessService SourceScheme: Payments TargetContext: http://sap.com/xi/XI TargetAgency: ReceiverBusinessSystem TargetScheme: ReceiverCheck KeyValue: BusService</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The same scenario is working fine in production but in quality,its giving teh above error. We have used the value mapping. I have checked each and everything. Every thing is matching with teh production. The XSLT mapping program is working well in production but in quality same program is not working. I have also checked the extended receiver configuration setting. Everything is same as in production.
Please help me out. I would be greatful to every one.
Thanks
Veeru

HI,
Error clerly says that there is error in value mapping ..
Check the target values exist for the source scheme and agency..
Check the cache is updated in RWB..
HTH
Rajesh

Similar Messages

Errors about 'No receiver could be determined'

Hi all:
I am setting up one scenario about ' IDOC to file '.
When I send IDOC from one R3 system to XI , I meet with the following errors.
No receiver could be determined
The SOAP Error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The trace is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: KEN</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0012</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Could anybody give me some clue to debug this problem ?

Hi Jianhong,
Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.
Configure your receiver file adapter according to this:
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm
Do ask if you require further information.
Regards,
Chandra

Intermittent JDBC error in Enhanced Receiver Determination

Hi,
I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
The database is DB2 on i5/os 6.1
Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
But the same message with same values is successfull earlier.
This is not a design problem; the interface is working well 95% of the time.
I found some JDBC error in NWA java logs:
Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
Thrown:
com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
Any idea? Can high volume cause the JDBC Receiver to fail?
Martin

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Error in Extended Receiver Determination

Hello Experts,
We are working on a scenario where, we are using Extended Receiver Determination.
In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
Also, we have a default receiver in mapping.
We are using: SAP PO 7.4 SP 7
We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
Error:
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>ADAPTER.JAVA_EXCEPTION</code>
          <text><![CDATA[
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
Kindly help.

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Error when determining the inbound interface

Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.

Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark

Error while determining logical Port

Hi
This is a ECC to SRM scenario:
I get this error in the Call Adapter step. I am using WS Adapter at the receiving side.
"Error while determining logical port Cannot find logical port for agreement abc and interface xyz"
Why do I get that error and any suggestions ?
Regards
Harish

Baskar,
I didn't fix any issue. I was trying tofind out why the error happens. There is a proxy created at ECC side. I saw that. But target is using WS Adapter and it's that adapter which is throwing errors about logical port.
I read the blog but couldn't figure out. Does WS Adapter need proxy code? Can it work without proxy code? I don't see any proxy code for receiver WS Adapter. I was wondering whether the absence of the proxy code gave this error about logical port
Regards
Harish

Unable to Determine Receiver

Hi,
I am getting some problem in Receiver Determination. The error is generated at the Receiver Grouping tag in SXMB_MONI. The error description is Unable to Determine receiver(processing type:QOS = EO or EOIO)
I am also putting the trace snippet where the error is getting generated.
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="3" type="System_Error">System-Error: ROUTING.NO_RECEIVER_CASE_ASYNC</Trace>
<Trace level="3" type="System_Error">Unable to determine a receiver (processing type: QoS = EO or EOIO)</Trace>
<Trace level="1" type="Timestamp">2004-08-05T16:36:52ZEnd of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
Any one having any clue. Thanks in advance.
Ashish

Hi Hart,
I think that should be correctly specified as all the values that I have been choosing have been from the look up help and they are properly appearing there.
However, still that message is appearing... Anything else that you can please specify...
Thanks in Advance.
Ashish

Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /

Guyz,
Firstly despite the plant+storage location + warehouse no. assignments are done , my replenishment delivery (delivery for stock transport order between plants under same company code) is not picking up storage location and warehouse no and thus stopping me from doing picking and PGI (post goods issue).
However in VL02N when i'm trying to change storage location for line item, i'm getting following weird error
*Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /*
I found a SAP Note(133223) regarding this error and VL02 transaction but that note was specific to older versions. I'm on ECC 6.0
Any suggestions please ?
Thanks

Warehouse managment has its own movement types, most identical to inventory management movement types.
These WM movement types are determined via reference movement types.
the error you have just looks like your customizing is not complete.
IMG > LE > WM > Interfaces > IM > define movement types.

Error while determining the form function module

Hi everyone,
We are experiencing problems while displaying one adobe form in ESS. Its the Travel Expense form (PTRV_EXPENSE_FORM). When pressing the button to Display/Print the form we get an error message: "Error while determining the form function module", and no form I shown. The ADS server is configured correctly and there are other forms that are actually working, for example the Travel Request form. We are running WAS 7.0 with SP12.
Anyone has an idea what can cause the problem? Any help is greatly appreciated.
Thanks in advance!
Regards,
Sophie

Viktor,
Thank you for your answer, it solved our problem!
Regards,
Sophie

Error when determining a number from object BI_ODS

Error When determining a number from object BI_ODS and number 01 when flat file source system is assigned to transfer rules of infosource , when activating this error occured .
plz need solution.

Hi,
Number ranges can be maintained through the transaction SNRO. For details check:
http://help.sap.com/saphelp_nw70/helpdata/EN/2a/fa02e3493111d182b70000e829fbfe/frameset.htm
Rgds-
Sonal

Error when determining a number from object BI_TSDTEL and number 01

Hi BW Experts,
After Transporting Infosources (Master & Transaction) to BW QA, the transfer rules were not getting activated in QA. The following error message was diaplyed.
"Error when determining a number from object BI_TSDTEL and number 01
Object name can only contain characters from syntactical character set
Object name can only contain characters from syntactical character set
Data element for InfoObject KOKRS 0CO_AREA could not be created
Data element for InfoObject KOKRS 0CO_AREA could not be created
Transfer structure 0IM_FA_IQ_2_SB activated under the name 0IM_FA_IQ_2_SA
It is not necessary to copy dependent objects for transfer structure 0IM_FA_IQ_2_SA
Transfer structure 0IM_FA_IQ_2_SA does not exist
Error RSAR 440 when handling objects with type R3TR ISTS."
I have gone through the Note: 674818.
Could someone clear me about BI_TSDTEl, By using this do we need to maintain object intervals manually in all the systems like BW ( Dev & QA ), R/3 (Dev & QA).
Because I have not seen the Intervals in R/3 ( Dev & QA) systems.
please could someone provide Inputs for this.
Thanks in Advance
Regards
SK

Hi,
Try to see that transfer structure is existing in the sytem which is connecting in
the BW quality.
You need the same to be transported from the development server of R/3 to quality server of R/3.
Just check if this helps.
Regards
Rahul Bindroo

Error messag -'Error while determining ref.mov.type for WM via Table 156S:'

Hi Guys,
I am currently facing some issues with respect to the deliver creation.
The scenario is somthing like this.
I have assigned a FOC Item category to an Consignment Issue order type.
The system is able to determine the Item category successfully.
However when the delivery is created it throws an error message
'Error while determining ref.mov.type for WM via Table 156S: 903/X/X/W/L/X/'
Not sure why this occurs.
All the settings seem to be set.
If any one of you can help me out it would be great.
Thanks.
Regards,
Pandi

Dear Pandiraj
The standard process is that consignment issue order should be created with reference to Proforma invoice. Having said that I dont understand why you have assigned a FOC item category to issue order. Not sure, whether this will work. Also I feel that you should explain in detail the process for which you are configuring this.
thanks
G. Lakshmipathi

Error while determining ref.mov.type for WM via table 156S:601///

Hi SAP gurus
while doing delivery i am getting error like
Error while determining ref.mov.type for WM via table 156S:601///
please give me needful solution
regards
Sarvesh

Chk via
SPRO>LE>WM>Interfaces>IM>Define mvt>Assign MVt reference...and then LE-WM interface...
maintina the correspoding entries..
BR,
Krishna

SQL Service Broker 2012: the connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'

Anyone can help with the below issue please? Much appreciated.
We have about 2k+ messages in sys.transmission_queue
Telnet to the ports 4022 is working fine.
Network connectivity has been ruled out.
The firewalls are OFF.
We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
GRANT
CONNECT ON
ENDPOINT <broker> <domain\serviceaccount>
Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
The
connection was
closed by the
remote end,
or an
error occurred while
receiving data:
'64(The specified network name is no longer available.)'

We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
Microsoft SQL Server 11.0.2100.60
Service Broker Diagnostic Utility
An internal exception occurred: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
P 29830 Could not find the connection to the SQL Server that
corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
Once, we are able to nail down the root cause, I will share more information.

A Kerberos Error Message was received: on logon session

Hi i am getting this error in event viewer in a client machine, from where powershell sccripts collecting data from our sharepoint servers
Log Name:      System
Source:        Microsoft-Windows-Security-Kerberos
Date:          9/16/2014 11:09:42 PM
Event ID:      3
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
    <EventID Qualifiers="32768">3</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
    <EventRecordID>5466</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>PortalHealthChe.XYZportal.com</Computer>
    <Security />
</System>
<EventData>
    <Data Name="LogonSession">
    </Data>
    <Data Name="ClientTime">
    </Data>
    <Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
    <Data Name="ErrorCode">0x7</Data>
    <Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
    <Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
    <Data Name="ClientRealm">
    </Data>
    <Data Name="ClientName">
    </Data>
    <Data Name="ServerRealm">XYZPORTAL.COM</Data>
    <Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
    <Data Name="TargetName">HTTP/[email protected]</Data>
    <Data Name="ErrorText">
    </Data>
    <Data Name="File">9</Data>
    <Data Name="Line">f09</Data>
    <Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adil

Hi
i am getting this error in a client machine
Log Name:      System
Source:        Microsoft-Windows-Security-Kerberos
Date:          9/16/2014 11:09:42 PM
Event ID:      3
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
    <EventID Qualifiers="32768">3</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
    <EventRecordID>5466</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>PortalHealthChe.XYZportal.com</Computer>
    <Security />
</System>
<EventData>
    <Data Name="LogonSession">
    </Data>
    <Data Name="ClientTime">
    </Data>
    <Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
    <Data Name="ErrorCode">0x7</Data>
    <Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
    <Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
    <Data Name="ClientRealm">
    </Data>
    <Data Name="ClientName">
    </Data>
    <Data Name="ServerRealm">XYZPORTAL.COM</Data>
    <Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
    <Data Name="TargetName">HTTP/[email protected]</Data>
    <Data Name="ErrorText">
    </Data>
    <Data Name="File">9</Data>
    <Data Name="Line">f09</Data>
    <Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adil

Error in determining receiver

Similar Messages

Maybe you are looking for