RfcClientException: functiontemplate from repository was null

HI All,
I am doing the File to RFC, the file was picked from FTP but data is not loaded into target sytem. When i have checked the Communication chennal for receiver (RFC) its showing this msg
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>"
Please help me how to reslove this problem.
Thanks in advance,
Venkat.

HI Venkat.
Please Refer SAP Note: 730870. Q16.
Fyr from SAP Note:
>Q 16: While sending a message to the RfcAdapter the error "... functiontemplate from repository was ><null>" is shown. Which reasons are possible?
>
>A: After receiving a message from the Adapter Engine, the RfcAdapter extracts the payload from the message. Normally this should be an XML document in the RFC-XML format. In this format the root element of the XML document represents the name of the function module and is enclosed in the fixed RFC namespace 'urn:sap-com:document:sap:rfc:functions'. But this only will be checked at a later >point, when the conversion from XML to native RFC is done. As prerequisite of this conversion the structures and types of the function module parameters has to be known. This is also called metadata or function template. To get this function template the name of the function module is extracted from the root element of the XML document and is queried against the metadata repository of the communication channel. If the metadata repository doesn't have a function module with this name, the exception named above is thrown. Possible reasons are
>
>The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository.
>
>The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37.
Regards
Goli Sridhar

Similar Messages

RFC call - RfcClientException: functiontemplate from repository was null

Hi all,
We are attempting to retrieve data from the ABAP stack of XI via the RFC adapter. However the call to the RFC is returning the following error:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have already come across SAP note 730870 but it didn't help.
Any suggestion?
Many thanks,
Aldo

Hi all,
I have found the problem.
The mapping to the RFC request was not creating the correct namespace prefix in the root xml element.
I have downloaded the file rfcnormalizer.jar from SAP note 730870 and used it in my interface mapping. It solved the problem.
Regards,
Aldo

Functiontemplate from repository was null

I have a sceanrio file rfc file,All my design config seems to be good i have double checked the rfc adapter configuation.I have an error in moni
Error
<?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="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>******
Can any please tell me what would be the problem..
Thanks
sriram

Hi Sriram,
Is RFC adapter is active/up and running? RFC xml structure is incorrect?
Refer SAP Note - 730870 Question no 16.
Regards,
Moorthy

Error in RFC Receiver Adapter: functiontemplate from repository was null

Hi Friends,
i am working on JDBC -> RFC Scenario, JDBC Sender Adapter is working fine, but RFC Receiver Adapter is throwing this error message... can some one help me to solve this issue...
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Thanks
Srikanth

Hi,
I think the logon details what you are giving in Receiver CC may be wrong. Check all those details like Application Server,System Number,User,Password and client.
Thanks.

SOAP-XI-CRM via RFC:Exception: functiontemplate from repository was null

Hi
I am doing a simple SOAP-XI-CRM scenario where a webservice from the customer is fed into CRM using RFC in XI in a sysnc mode.
I am using a receiver RFC adapter which i've used in other scenarios as well and it always worked fine...but now for this scenario it gives the following error:
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Body>
          <SOAP:Fault>
               <faultcode>SOAP:Server</faultcode>
               <faultstring>Server Error</faultstring>
               <detail>
                    <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>ADAPTER.JAVA_EXCEPTION</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
I even tried to replace my RFC with other one and it again worked fine...could this be a RFC structure issue...i m not sure where to look for the problem as the CC is working fine with other RFCs.
Regards
Naina

you will find many pointers in these threads;
functiontemplate from repository was <null>
functiontemplate from repository was <null>+SAP XI
also try to do a search;
http://forums.sdn.sap.com/search.jspa?forumID=44&threadID=&q=functiontemplatefromrepositorywas&objID=f44&dateRange=all&numResults=15&rankBy=10001

Functiontemplate from repository was null BAPI_ROUTING_CREATE

Hi all,
i'm trying to set up communication between a third party sistem and R3 via XI. I'm using BAPI_ROUTING_CREATE but , when i send the XML message (you can read it below),   the rfc adapter starts this exception:
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
I'm sure that the bapi is defined into the R3 system, i checked via se37, and the Communication channel for the BAPI is set properly since it works with other bapis.
May be someone can help me?
Best Regards
Luca
<rfc:BAPI_ROUTING_CREATE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
     <APPLICATION/>
     <BOMUSAGE/>
     <PROFILE/>
     <TESTRUN>
          <BAPIFLAG>' '</BAPIFLAG>
     </TESTRUN>
     <COMPONENTALLOCATION>
          <item>
               <TASK_LIST_GROUP/>
               <GROUP_COUNTER/>
               <SEQUENCE_NO/>
               <CHANGE_NO/>
               <VALID_FROM>2009-02-01</VALID_FROM>
               <CHANGE_NO_TO/>
               <VALID_TO_DATE>2009-12-31</VALID_TO_DATE>
               <DEL_IND/>
               <ACTIVITY/>
               <OPERATION_ID/>
               <BOM_TYPE/>
               <BOM_NO/>
               <ALTERNATIVE_BOM/>
               <ITEM_ID/>
               <ITEM_NO/>
               <CUTTING_MEASURE_UNIT/>
               <CUTTING_MEASURE_UNIT_ISO/>
               <COMP_UNIT/>
               <COMP_UNIT_ISO/>
               <BACKFLUSH/>
               <PLANT/>
               <MATERIAL/>
               <BOM_TYPE_ROOT/>
               <BOM_NO_ROOT/>
               <ALTERNATIVE_BOM_ROOT/>
          </item>
     </COMPONENTALLOCATION>
     <MATERIALTASKALLOCATION>
          <item>
               <MATERIAL>A10060</MATERIAL>
               <PLANT>2000</PLANT>
               <TASK_LIST_GROUP>50000007</TASK_LIST_GROUP>
               <GROUP_COUNTER>2</GROUP_COUNTER>
               <CHANGE_NO/>
               <VALID_FROM>2009-02-01</VALID_FROM>
               <CHANGE_NO_TO/>
               <VALID_TO_DATE>2009-12-31</VALID_TO_DATE>
               <DEL_IND/>
               <DOC_NUMBER/>
          </item>
     </MATERIALTASKALLOCATION>
     <OPERATION>
          <item>
               <TASK_LIST_GROUP>50000007</TASK_LIST_GROUP>
               <GROUP_COUNTER>2</GROUP_COUNTER>
               <SEQUENCE_NO>0</SEQUENCE_NO>
               <CHANGE_NO/>
               <VALID_FROM>2009-02-01</VALID_FROM>
               <CHANGE_NO_TO/>
               <VALID_TO_DATE>2009-12-31</VALID_TO_DATE>
               <DEL_IND/>
               <ACTIVITY>0010</ACTIVITY>
               <OPERATION_ID/>
               <CONTROL_KEY>PP01</CONTROL_KEY>
               <OBJ_ID>10000017</OBJ_ID>
               <OBJECT_TYPE_CIM_RESOURCE>A</OBJECT_TYPE_CIM_RESOURCE>
               <WORK_CNTR>A4010</WORK_CNTR>
               <PLANT>2000</PLANT>
               <STANDARD_TEXT_KEY/>
               <DESCRIPTION>ASSEMBLY</DESCRIPTION>
               <OPERATION_MEASURE_UNIT>PC</OPERATION_MEASURE_UNIT>
               <OPERATION_MEASURE_UNIT_ISO/>
</rfc:BAPI_ROUTING_CREATE>

Hi Luca,
Please see the thread if you havn't yet.. u may get some help
RFC error
RfcClientException: functiontemplate from repository was <null>

Functiontemplate from repository was null +SAP XI

hi,all
can any one suggest me why this error is coming
>>>functiontemplate from repository was <null>
thanx

when I am sending data from JDBC-XI-RFC
I am using BAPI function module as RFC at receiver side
sxmb_moni shows all is working nice but RWB showing waiting ,after some time it is showing "system error"
and in message detail I can see this error
"functiontemplate from repository was <null>"
Thx,

Receiver RFC error- RfcClientException: functiontemplate from repository wa

Hi All,
I am in an R/3(IDOC) - XI - 3rd party(File) scenario. Need to do a lookup to R/3 from XI before file is sent to 3rd party system.
For RFC, I followed various blogs( currently using Michaels blog https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439 )
However I get the error in RWB:
"Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>"
Came across note : 730870 and it talks of metadata refresh. So I reimported the function module into IR, reactivated the comm channel but still the same error.
Do you guys have any idea why it could be happening.
To sum up,for RFC lookup I have created
1. RFC enabled FM in R/3
2. Comm Channel in ID
3. UDF (supplied the above comm channel and Buss syst name here and FM xml signature)
4. Used the UDF in existing Message mapping
( I have not created any separate Interface mappings for this...is it OK)
( My RFC function module will return a single field, but when I import RFC FM in IR, I do not see the return field, it has only the FM incoming fields...is that OK.....??? )
Any help/pouinters are welcome
Many thanks
Shirin

Hi Praveen,
Yes its an R/3 - XI - 3rd Party scenario.
To cut the story short, I am doing lookup to R/3 Due to some file sequencing requirements. This is the only option left as getting this data in the IDOC initially didnt help.
As you have pointed, can you help let me know how can I correct it in the UDF. (I am a javao novice, so appreciate if you could help me with it)
I have attached the UDF code below.
Many thanks
Shirin
Imports: java.io.*;com.sap.aii.mapping.lookup.*;
//write your code here
String content = "";
MappingTrace importanttrace;
importanttrace = container.getTrace() ;
//Filling the string with our RFC-XML (With Values)
String m = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:ZIFMS_GET_NEXT_NUMBER>xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><I_NR_RANGE_NR>01</I_NR_RANGE_NR><I_OBJECT>ZIFMS_INT</I_OBJECT></ns0:ZIFMS_GET_NEXT_NUMBER> ";
RfcAccessor accessor = null;
ByteArrayOutputStream out = null;
try
//1. Determine a channel (Business System, Communication channel)
Channel channel = LookupService.getChannel("BS_IFMS_GENIUS_UAT" , "CC_RFC_LOOKUP");
//2. Get a RFC accesor for a channel.
accessor = LookupService.getRfcAccessor(channel);
//3. Create a xml input stream representing the FM request message.
InputStream inputstream = new ByteArrayInputStream(m.getBytes());
//4. Create xml Payload
XmlPayload payload = LookupService.getXmlPayload(inputstream);
//5. Execute Lookup
Payload result = accessor.call(payload);
InputStream in = result.getContent();
out = new ByteArrayOutputStream(1024);
byte[] buffer = new byte[1024];
for (int read = in.read(buffer); read > 0; read = in.read(buffer)) {
out.write(buffer, 0, read);
content = out.toString();
catch(LookupException e)
importanttrace.addWarning("Error while lookup " + e.getMessage() );
catch(IOException e)
importanttrace.addWarning("Error " + e.getMessage() );
finally
if (out!=null) {
try {
out.close();
} catch (IOException e) {
importanttrace.addWarning("Error while closing stream " + e.getMessage() );
// 7. close the accessor in order to free resources.
if (accessor!=null) {
try {
accessor.close();
} catch (LookupException e) {
importanttrace.addWarning("Error while closing accessor " + e.getMessage() );
//returning the result u2013 RFC-XML.response
return content;

Error in RFC Receiver Adapter: functiontemplate from repository

Hi Experts,
i am working on JDBC -> RFC Scenario, JDBC Sender Adapter is working fine, but RFC Receiver Adapter is throwing this error message... can some one help me to solve this issue...
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Thanks
Srikanth

Possible reasons are
The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository.
The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37.
Here my suggestion is, if you are using Java/xslt mapping, write your code in line with result structure of your mapping instead source pay load structure. May be helpful.
Cheers
Madhu

Saml2 error validateArtifactRequester: certificate from client is null

Hi,
I got this error ArtifactResolutionService.validateArtifactRequester: certificate from client is null, authentication is failed.>
If you see the log then you can see the handshaking between assertion and indentity works but somehow the assertion refuses the response of the identity
assertion provider
####<12-sep-2009 17:30:24 uur CEST><SAML2Filter: Processing request on URI '/appB/faces/aut/restricted.jspx'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): request URI is '/appB/faces/aut/restricted.jspx'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): request URI is not a service URI>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): returning service type 'SPinitiator'>
####<12-sep-2009 17:30:24 uur CEST><SP initiating authn request: processing>
####<12-sep-2009 17:30:24 uur CEST><SP initiating authn request: partner id is null>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyInfo>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyStore>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyStore Checking if the Keystore file was modified>
####<12-sep-2009 17:30:24 uur CEST><SP initiating authn request: use partner binding HTTP/Artifact>
####<12-sep-2009 17:30:24 uur CEST><store saml object org.opensaml.saml2.core.impl.AuthnRequestImpl@168c85b, BASE64 encoded artifact is AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH/NaPWjnhgmqYEpXMWX2STBHg=>
####<12-sep-2009 17:30:24 uur CEST><post artifact: false>
####<12-sep-2009 17:30:24 uur CEST><local ARS binding location: http://laptopedwin.wh.lan:8001/saml2/idp/sso/artifact>
####<12-sep-2009 17:30:24 uur CEST><post form template url: null>
####<12-sep-2009 17:30:24 uur CEST><URL encoded artifact: AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH%2FNaPWjnhgmqYEpXMWX2STBHg%3D>
####<12-sep-2009 17:30:24 uur CEST><URL encoded relay state: null>
####<12-sep-2009 17:30:24 uur CEST><artifact is sent in http url:http://laptopedwin.wh.lan:8001/saml2/idp/sso/artifact?SAMLart=AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH%2FNaPWjnhgmqYEpXMWX2STBHg%3D>
####<12-sep-2009 17:30:24 uur CEST><SAML2Servlet: Processing request on URI '/saml2/sp/ars/soap'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): request URI is '/saml2/sp/ars/soap'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): service URI is '/sp/ars/soap'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): returning service type 'ARS'>
####<12-sep-2009 17:30:24 uur CEST><ArtifactResolutionService.process: get SoapHttpBindingReceiver as receiver and SoapHttpBindingSender as sender.>
####<12-sep-2009 17:30:24 uur CEST><ArtifactResolutionService.validateArtifactRequester: certificate from client is null, authentication is failed.>
####<12-sep-2009 17:30:24 uur CEST> <Warning> <Security> <LAPTOPEDWIN> <DefaultServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1252769424812> <BEA-000000> <[Security:096565]Artifact requester authentication failed.>
####<12-sep-2009 17:30:24 uur CEST><SoapHttpBindingSender.sendResponse: Set HTTP headers to prevent HTTP proxies cache SAML protocol messages.>
####<12-sep-2009 17:30:24 uur CEST><SoapHttpBindingSender.send: the SOAP envelope to be sent is :
>
####<12-sep-2009 17:30:24 uur CEST> <<?xml version="1.0" encoding="UTF-8"?><soap11:Envelope xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"><soap11:Body><samlp:ArtifactResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="_0xf34d9596cf9f8d37715fdf3529266b40" InResponseTo="_0xe219b059e77568bc835736caa94d6855" IssueInstant="2009-09-12T15:30:24.812Z" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">jdev_wls</saml:Issuer><samlp:Status><samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/><samlp:StatusMessage>[Security:096565]Artifact requester authentication failed.</samlp:StatusMessage></samlp:Status></samlp:ArtifactResponse></soap11:Body></soap11:Envelope>>
####<12-sep-2009 17:35:24 uur CEST> <authn_request - item: _0x9061f430c89cd074398250c710c83045 expired.>
identity provider
####<12-sep-2009 17:30:24 uur CEST><SAML2Servlet: Initialized logger service>
####<12-sep-2009 17:30:24 uur CEST><SAML2Servlet: Initialized SAML2 service>
####<12-sep-2009 17:30:24 uur CEST><SAML2Servlet: setConfigKey called with key 'default'>
####<12-sep-2009 17:30:24 uur CEST><SAML2Servlet: Processing request on URI '/saml2/idp/sso/artifact'>
####<12-sep-2009 17:30:24 uur CEST><Redirect URI cache updated.>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyInfo>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyStore>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyStore Checking if the Keystore file was modified>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): request URI is '/saml2/idp/sso/artifact'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): service URI is '/idp/sso/artifact'>
####<12-sep-2009 17:30:24 uur CEST><getServiceTypeFromURI(): returning service type 'SSO'>
####<12-sep-2009 17:30:24 uur CEST><Request URI: /saml2/idp/sso/artifact>
####<12-sep-2009 17:30:24 uur CEST><Method: GET>
####<12-sep-2009 17:30:24 uur CEST><Query string: SAMLart=AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH%2FNaPWjnhgmqYEpXMWX2STBHg%3D>
####<12-sep-2009 17:30:24 uur CEST><     Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-shockwave-flash, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*>
####<12-sep-2009 17:30:24 uur CEST><     Referer: http://127.0.0.1:7101/appB/faces/appBStart.jspx;jsessionid=TtbvKr5Myy7hC5y2j9YVZMLp2dxvYlGP3nV8KnJPtnB5svv4cnDL!-453074333?_adf.ctrl-state=m6b65gdxq_4>
####<12-sep-2009 17:30:24 uur CEST><     Accept-Language: nl>
####<12-sep-2009 17:30:24 uur CEST><     User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)>
####<12-sep-2009 17:30:24 uur CEST><     Host: laptopedwin.wh.lan:8001>
####<12-sep-2009 17:30:24 uur CEST><     Accept-Encoding: gzip, deflate>
####<12-sep-2009 17:30:24 uur CEST><     Connection: Keep-Alive>
####<12-sep-2009 17:30:24 uur CEST><     Cache-Control: no-cache>
####<12-sep-2009 17:30:24 uur CEST><weblogic.security.service.internal.SAMLKeyServiceImpl.getKeyInfo>
####<12-sep-2009 17:30:24 uur CEST><ssl client key:Sun RSA private CRT key, 1024 bits
modulus: 135256530343776309493378499238723474761809537383354856443783031405724842963590896515127253614442774833330163469306346998433606124817086312759138932710087080464501074410925139095622741276531270633324573257815772267862467588496928149465417098076218732040047455958122894583653703895415828491462423303970267662119
public exponent: 65537
private exponent: 70314326087743699962454879977162652930937500017561071746336998641882377889887267410323718367396514008446506086626901479113065301623787031382331559843030136237857866934906267741351110674239213829006129063775109788707087302538026535943257466578949319062480441789214176315827916248430287133081293921721804088033
prime p: 11974625102832097583118096114610793613205242504983701060834332690026001982375077665162762308523793650653350947197100038932023730202787298553029195261347327
prime q: 11295262205059515784067784104204404656057034968759802138195417174670025481580489505249455835611140503620524999898446032906677280702668039750528726228078297
prime exponent p: 10636051419212951957075964614303506523311875298802298281157626077164099690190818102244374273181234298154969131746805474255337189050985724645168110919912251
prime exponent q: 9180707495599589343206474566470241653094376286920321960074362300079694178141042692915879784722129977674567430529173188898986608915112396683265394948155617
crt coefficient: 3999529359604887198322520465212803445668432210961019729502103914530388247742016641237995952808703712482862506414062073383339683451433625683775233168415551, ssl client cert chain:[Ljava.security.cert.Certificate;@767c0d>
####<12-sep-2009 17:30:24 uur CEST><get BASE64 encoded artifact from http request, value is:AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH/NaPWjnhgmqYEpXMWX2STBHg=>
####<12-sep-2009 17:30:24 uur CEST><ArtifactResolver: sha-1 hash value of remote partner id is '0xc46d956aa4de6f55a95df24aeeea8c9706a34f0f'>
####<12-sep-2009 17:30:24 uur CEST><ArtifactResolver: found remote partner 'jdev' with entity ID 'jdev_wls'>
####<12-sep-2009 17:30:24 uur CEST><ArtifactResolver: returning partner: [email protected]779>
####<12-sep-2009 17:30:24 uur CEST><partner entityid isjdev_wls, end point index is:0>
####<12-sep-2009 17:30:24 uur CEST><find end point:[email protected]2a7, binding location is:http://laptopedwin.wh.lan:7101/saml2/sp/ars/soap>
####<12-sep-2009 17:30:24 uur CEST><<?xml version="1.0" encoding="UTF-8"?><samlp:ArtifactResolve xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="_0xe219b059e77568bc835736caa94d6855" IssueInstant="2009-09-12T15:30:24.671Z" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">soa</saml:Issuer><samlp:Artifact>AAQAAMRtlWqk3m9VqV3ySu7qjJcGo08PSwH/NaPWjnhgmqYEpXMWX2STBHg=</samlp:Artifact></samlp:ArtifactResolve>>
####<12-sep-2009 17:30:24 uur CEST><open connection to send samlp:ArtifactResolve. partner id:jdev_wls, endpoint url:http://laptopedwin.wh.lan:7101/saml2/sp/ars/soap>
####<12-sep-2009 17:30:24 uur CEST><isClientPasswordSet:false>
####<12-sep-2009 17:30:24 uur CEST><connect to remote ARS.>
####<12-sep-2009 17:30:24 uur CEST><SoapSynchronousBindingClient.sendAndReceive: begin to send SAMLObject to server.>
####<12-sep-2009 17:30:24 uur CEST><SoapSynchronousBindingClient.sendAndReceive: sending completed, now waiting for server response.>
####<12-sep-2009 17:30:24 uur CEST><SoapSynchronousBindingClient.sendAndReceive: response code from server is: 200>
####<12-sep-2009 17:30:24 uur CEST><SoapSynchronousBindingClient.sendAndReceive: get a HTTP_OK response, now receive a SOAP envelope message.>
####<12-sep-2009 17:30:24 uur CEST><SoapSynchronousBindingClient.sendAndReceive: found XMLObject in envelope, return it.>
####<12-sep-2009 17:30:24 uur CEST><http url connection disconnect.>
####<12-sep-2009 17:30:24 uur CEST><<?xml version="1.0" encoding="UTF-8"?><samlp:ArtifactResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="_0xf34d9596cf9f8d37715fdf3529266b40" InResponseTo="_0xe219b059e77568bc835736caa94d6855" IssueInstant="2009-09-12T15:30:24.812Z" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">jdev_wls</saml:Issuer><samlp:Status><samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/><samlp:StatusMessage>[Security:096565]Artifact requester authentication failed.</samlp:StatusMessage></samlp:Status></samlp:ArtifactResponse>>
####<12-sep-2009 17:30:24 uur CEST><get samlp:ArtifactResponse and verify it.>
####<12-sep-2009 17:30:24 uur CEST><saml version:2.0>
####<12-sep-2009 17:30:24 uur CEST><inResponseTo:_0xe219b059e77568bc835736caa94d6855>
####<12-sep-2009 17:30:24 uur CEST><status code: urn:oasis:names:tc:SAML:2.0:status:Success>
####<12-sep-2009 17:30:24 uur CEST><status message: [Security:096565]Artifact requester authentication failed.>
####<12-sep-2009 17:30:24 uur CEST><[Security:096577]Failed to receive AuthnRequest document from the requester.>
####<12-sep-2009 17:30:24 uur CEST><Caused by: [Security:096502]There is no saml message in returned samlp:ArtifactResponse.>
####<12-sep-2009 17:30:24 uur CEST><exception info
com.bea.security.saml2.service.SAML2Exception: [Security:096577]Failed to receive AuthnRequest document from the requester.
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.receive(SSOServiceProcessor.java:301)
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.processAuthnRequest(SSOServiceProcessor.java:118)
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.process(SSOServiceProcessor.java:100)
     at com.bea.security.saml2.service.sso.SingleSignOnServiceImpl.process(SingleSignOnServiceImpl.java:50)
     at com.bea.security.saml2.cssservice.SAML2ServiceImpl.process(SAML2ServiceImpl.java:161)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.utils.ThreadClassLoaderContextInvocationHandler.invoke(ThreadClassLoaderContextInvocationHandler.java:27)
     at $Proxy26.process(Unknown Source)
     at com.bea.security.saml2.servlet.SAML2Servlet.service(SAML2Servlet.java:34)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3590)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
com.bea.security.saml2.binding.BindingHandlerException: [Security:096502]There is no saml message in returned samlp:ArtifactResponse.
     at com.bea.security.saml2.artifact.impl.AbstractArtifactResolver.getSamlMsg(AbstractArtifactResolver.java:459)
     at com.bea.security.saml2.artifact.impl.AbstractArtifactResolver.resolve(AbstractArtifactResolver.java:304)
     at com.bea.security.saml2.binding.impl.ArtifactBindingReceiver.resolve(ArtifactBindingReceiver.java:77)
     at com.bea.security.saml2.binding.impl.ArtifactBindingReceiver.receiveRequest(ArtifactBindingReceiver.java:40)
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.receive(SSOServiceProcessor.java:295)
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.processAuthnRequest(SSOServiceProcessor.java:118)
     at com.bea.security.saml2.service.sso.SSOServiceProcessor.process(SSOServiceProcessor.java:100)
     at com.bea.security.saml2.service.sso.SingleSignOnServiceImpl.process(SingleSignOnServiceImpl.java:50)
     at com.bea.security.saml2.cssservice.SAML2ServiceImpl.process(SAML2ServiceImpl.java:161)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.utils.ThreadClassLoaderContextInvocationHandler.invoke(ThreadClassLoaderContextInvocationHandler.java:27)
     at $Proxy26.process(Unknown Source)
     at com.bea.security.saml2.servlet.SAML2Servlet.service(SAML2Servlet.java:34)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3590)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

Tony,
Refer SAP Note: 730870. Q16.
Fyr from SAP Note:
Q 16: While sending a message to the RfcAdapter the error "... functiontemplate from repository was <null>" is shown. Which reasons are possible?
              A: After receiving a message from the Adapter Engine, the RfcAdapter extracts the payload from the message. Normally this should be an XML document in the RFC-XML format. In this format the root element of the XML document represents the name of the function module and is enclosed in the fixed RFC namespace 'urn:sap-com:document:sap:rfc:functions'. But this only will be checked at a later point, when the conversion from XML to native RFC is done. As prerequisite of this conversion the structures and types of the function module parameters has to be known. This is also called metadata or function template. To get this function template the name of the function module is extracted from the root element of the XML document and is queried against the metadata repository of the communication channel. If the metadata repository doesn't have a function module with this name, the exception named above is thrown. Possible reasons are
The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository.
The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37.
raj.

Calling QAAWS from MII - Context was null

I'm having trouble invoking a Query As A Web Service call into BW. If I call the service using SOAPUI, the call goes through successfully and returns 1800+ rows. If I use the MII Web Service Action to call the Convert Temperature WS used in the training classes, it returns the expected results. When I try and call QAAWS via the MII Web Service, the call returns no data and I see an error message in the logs "Error Invoking Web Service Action: Context Was Null".
I haven't seen this error message described in the forums so far. We're using MII v12.0
Thanks,
Adam Doyle

We're currently trying to get this working with the HttpPost action, but I'm running into trouble getting the results. Using the sample XML below, I'm not able to get at the nodes under runQueryAsAServiceResponse. My Repeater (INV_HttpPost_TRX_0.OutputXml{/soap:Envelope/soap:Body/runQueryAsAServiceResponse/table/row}) can't find them.
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><runQueryAsAServiceResponse xmlns="MII_Dashboard"><table><row><L01_Plant>PLANT</L01_Plant><L01_Material>GASKETS/RINGS</L01_Material><L01_Calendar_Year_Month>09.1999</L01_Calendar_Year_Month><L01_Base_Unit>Each</L01_Base_Unit><Value>28</Value></row>
</table><message></message><creatorname>CREATORy</creatorname><creationdate>2010-06-09T20:22:33.284</creationdate><creationdateformated>06/09/2010 8:22:33 PM </creationdateformated><description></description><universe>SAP_MII_POC</universe><queryruntime>1</queryruntime><fetchedrows>1884</fetchedrows></runQueryAsAServiceResponse></soap:Body></soap:Envelope>
I'm very confused.
Adam

Cannot import from repository to Design Center

Why when I try to import an object from repository into the design center of Warehouse Builder, no objects are imported and when I save all this error message is shown:
API5072: Internal Error: Null message for exception. Please contact Oracle Support with the stack trace and details on how to reproduce it.
oracle.wh.util.Assert: API5072: Internal Error: Null message for exception. Please contact Oracle Support with the stack trace and details on how to reproduce it.
The stack trace is the following:
+     at oracle.wh.util.Assert.owbAssert(Assert.java:51)+
+     at oracle.wh.ui.jcommon.OutputConfigure.showMsg(OutputConfigure.java:216)+
+     at oracle.wh.ui.jcommon.CommonUtils.error(CommonUtils.java:297)+
+     at oracle.wh.ui.console.commands.CommitCmd.performAction(CommitCmd.java:27)+
+     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)+
+     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:189)+
+     at java.awt.EventQueue.dispatchEvent(EventQueue.java:478)+
+     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)+
+     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)+
+     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)+
+     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)+
+     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)+
In this way, I can't import any object from repository and the only way to create a new object is to create it on Design Center and then deploy it. It's so boring creating table or views adding a field by hand...

The issue may be a bit more complex than just missing roles. If a target schema has been rebuilt (i.e. dropped and recreated) you will need to re-register it as a valid location with it's local runtime repository.
I have, on a couple of occassions, had problems re-registering a user through the GUI if that schema was not unregistered prior to being rebuilt. Make an OMBPLUS connection to the runtime environment on the instance where your target is located, and re-register it with:
OMB+> OMBCONNECT OWB_MGR/OWB_MGR_PWD@YOUR_HOST:YOUR_PORT:YOUR_SRVC USE REPOSITORY 'OWB_MGR_SCHEMA'
OMB+> OMBUNREGISTER USER 'TARGET_SCHEMA' IDENTIFIED BY 'TARGET_SCHEMA_PASSWORD'
OMB+> OMBREGISTER USER 'TARGET_SCHEMA' SET PROPERTIES (DESCRIPTION, ISTARGETSCHEMA, TARGETSCHEMAPWD) VALUES ('TARGET_SCHEMA', 'true', 'TARGET_SCHEMA_PASSWORD')
OMB+> OMBSAVE
OMB+> OMBDISCONNECT

The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error

We are getting the below error when we see in Crawl logs
"The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error."
This is happening in FAST search.
Here I can see soke of the logs related to this search crawl.
Could anyone please help on this?
web application 'http://xvy/' doesn't use search application 'FAST Query SSA', skipping it.
ABC\sp_search' on web application 'http://xvy/'. 2d7dba01-3d2e-4903-b59f-9a8601627bcd
07/30/2014 01:30:46.65 OWSTIMER.EXE (0x28DC)                   0x1BC0 SharePoint Server Search      Administration
dl2m Verbose Search application 'Search Service Application 1': Skipping web application '48ed7882-9f70-424e-bf72-e3c9f5340b97' because its outbound url 'http://ebc:30347' was automatically added once.
Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvcp/'. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dl2m Verbose Search application 'FAST Query SSA': Skipping web application '57718ea1-8cb5-4adc-abd2-9e55415e5791' because its outbound url 'http://nvcp' was automatically added once. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dl2n Verbose Search application 'FAST Query SSA': Adding start address 'http://nvcp' for web application '57718ea1-8cb5-4adc-abd2-9e55415e5791' to list of valid start addresses. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dmb6 Verbose Ensure full read access to the indexing account 'ABc\sp_search' on web application 'http://nvcp'ext/'. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dl2m Verbose Search application 'FAST Query SSA': Skipping web application '64d562a1-535e-4917-8979-88840e2a67fe' because its outbound url 'http://nvcp'ext' was automatically added once. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dl2n Verbose Search application 'FAST Query SSA': Adding start address 'http://nvcpext' for web application '64d562a1-535e-4917-8979-88840e2a67fe' to list of valid start addresses. 85041609-d618-4132-ac8e-195a910d99a0
07/30/2014 01:31:46.53 OWSTIMER.EXE (0x28DC)                   0x05F4 SharePoint Server Search      Administration
dmb6 Verbose Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvcpnew/'. 85041609-d618-4132-ac8e-195a910d99a0
executing SQL query {? = call dbo.proc_MSS_PropagationIndexerGetReadyQueryComponents} [propdatabase.cxx:70] d:\office\source\search\native\ytrip\tripoli\propagation\propdatabase.cxx
07/30/2014 01:32:04.31 mssearch.exe (0x0588)                   0x1DE4 SharePoint Server Search      Propagation Manager
e3o3 Verbose executing SQL query {? = call dbo.proc_MSS_PropagationIndexerGetReadyQueryComponents} [propdatabase.cxx:70] d:\office\source\search\native\ytrip\tripoli\propagation\propdatabase.cxx
07/30/2014 01:32:04.68 mssdmn.exe (0x15CC)                     0x1060 SharePoint Server Search      HTTP Protocol
Handler         du4i                    0x29E4 SharePoint Server Search      HTTP
Protocol Handler         du4i Verbose CHttpAccessorHelper::InitRequestInternal - opening request for '/robots.txt'.   [httpacchelper.cxx:353] d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx
07/30/2014 01:32:04.70 mssdmn.exe (0x15CC)                     0x29E4 SharePoint Server Search      HTTP Protocol
Handler         du54 High    CHttpAccessorHelper::InitRequestInternal - unexpected status (503) on request for 'http://ppecpnew/robots.txt' Authentication 0. [httpacchelper.cxx:703]
d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx
07/30/2014 01:32:04.70 mssearch.exe (0x0588)                   0x130C SharePoint Server Search      Gatherer
cd11 Warning The start address http://nvcp'/sites/quipme cannot be crawled. Context: Application 'FAST_Content_SSA', Catalog 'Portal_Content' Details:
The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.   (0x80041200)
07/30/2014 01:32:04.70 mssdmn.exe (0x15CC)                     0x104C SharePoint Server Search      HTTP Protocol
Handler         du4i Verbose CHttpAccessorHelper::InitRequestInternal - opening request for '/robots.txt'.   [httpacchelper.cxx:353] d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx
07/30/2014 01:32:04.70 mssdmn.exe (0x15CC)                     0x104C SharePoint Server Search      HTTP Protocol
Handler         du54 High
07/30/2014 01:32:04.70 mssearch.exe (0x0588)                   0x2948 SharePoint Server Search      Gatherer
cd11 Warning The start address
http://nvcp'/sites/MDPPubng cannot be crawled. Context: Application 'FAST_Content_SSA', Catalog 'Portal_Content' Details: The crawler could not communicate with the server. Check that the server is
available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.   (0x80041200)
CHttpProbeHelper::ProbeServer: InitRequest failed for 'http://ppecpnew/_vti_bin/sitedata.asmx'. Return error to caller, hr=80041200 [stscommon.cxx:490] d:\office\source\search\native\gather\protocols\common\stscommon.cxx
07/30/2014 01:32:26.06 mssdmn.exe (0x15CC)                     0x193C SharePoint Server Search      PHSts
dvg0 High    STS3::COWSServer::InitializeClaimsCookie: Probing url 'http://pncvr' failed. Return error to caller, hr=80041200 [sts3util.cxx:1332] d:\office\source\search\native\gather\protocols\sts3\sts3util.cxx
07/30/2014 01:32:26.06 mssdmn.exe (0x15CC)                     0x193C SharePoint Server Search      PHSts
en0e High    CSTS3Accessor::InitURLType: Return error to caller, hr=80041200                 [sts3acc.cxx:2214] d:\office\source\search\native\gather\protocols\sts3\sts3acc.cxx
07/30/2014 01:32:26.06 mssdmn.exe (0x15CC)                     0x193C SharePoint Server Search      PHSts
dv3p High    CSTS3Accessor::GetServer fails, Url sts4://pnvpr/siteurl=sites/product/siteid={7ebfb072-08a8-4df7-8f74-e06730325d9a}/weburl=/webid={bd7ae724-1256-4b26-9633-416447d6bc5c}, hr=80041200 [sts3acc.cxx:185]
d:\office\source\search\native\gather\protocols\sts3\sts3acc.cxx
07/30/2014 01:32:26.06 mssdmn.exe (0x15CC)                     0x193C SharePoint Server Search      PHSts
dvb1 High    CSTS3Accessor::Init fails, Url sts4:/mngbv/siteurl=sites/product/siteid={7ebfb072-08a8-4df7-8f74-e06730325d9a}/weburl=/webid={bd7ae724-1256-4b26-9633-416447d6bc5c}, hr=80041200 [sts3handler.cxx:312]
d:\office\source\search\native\gather\protocols\sts3\sts3handler.cxx
07/30/2014 01:32:26.06 mssdmn.exe (0x15CC)                     0x16FC SharePoint Server Search      HTTP Protocol
Handler         du2z Verbose CHttpProbeHelper::ProbeServer: Probing server with url 'http://pnvpr/_vti_bin/sitedata.asmx'. [stscommon.cxx:476] d:\office\source\search\native\gather\protocols\common\stscommon.cxx
07/30/2014 01:32:26.08 mssdmn.exe (0x15CC)                     0x193C SharePoint Server Search      PHSts
dvb2 High    CSTS3Handler::CreateAccessorExD: Return error to caller, hr=80041200            [sts3handler.cxx:330] d:\office\source\search\native\gather\protocols\sts3\sts3handler.cxx
07/30/2014 01:32:26.08 mssdmn.exe (0x15CC)                     0x16FC SharePoint Server Search      HTTP Protocol
Handler         du4i Verbose CHttpAccessorHelper::InitRequestInternal - opening request for '/_vti_bin/sitedata.asmx'. [httpacchelper.cxx:353] d:\office\source\search\native\gather\protocols\http\httpacchelper.cxx
earch application 'FAST Query SSA': Adding start address 'http://mnvfgext' for web application '64d562a1-535e-4917-8979-88840e2a67fe' to list of valid start addresses. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
07/30/2014 01:32:46.53 OWSTIMER.EXE (0x28DC)                   0x1444 SharePoint Server Search      Administration
dmb6 Verbose Ensure full read access to the indexing account 'ABC\sp_search' on web application 'http://nvpr/'. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
07/30/2014 01:32:46.53 OWSTIMER.EXE (0x28DC)                   0x1444 SharePoint Server Search      Administration
dl2m Verbose Search application 'FAST Query SSA': Skipping web application 'cea7b67b-fd5f-4c9a-a300-64a7d7ca3093' because its outbound url 'http://pnvpr' was automatically added once. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
07/30/2014 01:32:46.53 OWSTIMER.EXE (0x28DC)                   0x1444 SharePoint Server Search      Administration
dl2n Verbose Search application 'FAST Query SSA': Adding start address 'http://pnvpr' for web application 'cea7b67b-fd5f-4c9a-a300-64a7d7ca3093' to list of valid start addresses. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
07/30/2014 01:32:46.53 OWSTIMER.EXE (0x28DC)                   0x1444 SharePoint Server Search      Administration
dl2k Verbose web application 'http://abcrsp/' doesn't use search application 'FAST Query SSA', skipping it. a6b7948a-dc16-419d-b58a-0ee798a0bb9c
07/30/2014 01:32:46.53 OWSTIMER.EXE (0x28DC)                   0x1444 SharePoint Server Search      Administration
dl2k Verbose web application 'http://excb/' doesn't use search application 'FAST Query SSA', ski
Anil Loka

Hi,
According to your post, my understanding is that you got error when communicating to the server.
This happens when crawler is not able to connect to the server. Make sure server name is correct. Couple of steps to troubleshoot it
You should be able to ping the server from the server having crawl component. Make sure there is an entry for the server in the host file under c:\Windows\System32\drivers\etc folder.
          Ping <servername>
      2. You should be able to connect to the server using telnet command
Telnet< servername> <port number>
More information:
Troubleshooting of FAST Search Configuration
If the issue still exists, you can delete the old search application and recreate from the beginning.
You can also reset the index and do a full crawl after.
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/f3c61b53-304a-4c2a-a370-d0e573219d1d/an-unrecognized-http-response-was-received-when-attempting-to-crawl-this-item?forum=sharepointadminprevious
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Sender RFC adapter Error- request was null while trying to extract it.

Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
Laawanya

Hi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI.

Data source value for data source reportData was null

hi i'm using struts 2 and jasperreports my problem is
it generate a pdf file with labels but no data in it..
and when i try to look at the logs of my sun application server
it says Data source value for datasource reportData was null.
reportData is an ArrayList of Personnel object.
here is my code..
public class EIS_HR_004_JASPER extends eisSupport {
    private String reportId;
    private String dateStart = null;
    private String dateEnd = null;
    private String pdfFile;
    private final static String _REPORT_FOLDER = "EIS_HR_003";
    private Report thisReport;
    private String dateRange;
    private ArrayList<Personnel> reportData;
    public String execute(ActionMapping mapping,ActionForm form,
            HttpServletRequest request, HttpServletResponse response)
            throws Exception {
        ReportBean reportBean = new ReportBean();
        setThisReport(reportBean.getReport(getReportId()));
        reportData=new ArrayList<Personnel>();
        Personnel p1=new Personnel();
        p1.setSurname("Dela Cruz");
        p1.setFirstname("Juan");
        p1.setExamcode("CSC111");
        p1.setExamdate("January 1,2003");
        Personnel p2=new Personnel();
        p2.setSurname("Cruz");
        p2.setFirstname("Miguel");
        p2.setExamcode("CSC222");
        p2.setExamdate("December 2,2003");
        reportData.add(p1);
        reportData.add(p2);
     try {
          JasperCompileManager.compileReportToFile(
                    "apps/reports/templates/hr004.jrxml",
                    "apps/reports/templates/hr004.jasper");
     } catch (Exception e) {
          e.printStackTrace();
          return ERROR;
         return SUCCESS;
    public ArrayList<Personnel> getReportData() {
       // setReportData();
        return reportData;
    here is part of my struts.xml
<action name="EIS-HR-004_JASPER" class="eis.report.EIS_HR_004_JASPER">
            <result name="error">/apps/reports/ReportNotFound.jsp</result>
            <result name="success" type="jasper">
                <param name="location">apps/reports/templates/hr004.jasper</param>
                <param name="dataSource">reportData</param>
                <param name="format">PDF</param>
            </result>
        </action> i dont know why it doesnt retrieved the data from the ArrayList?
please help me..Thanks in advance.

Hi,
Looking at the code, it seems you are compiling a JRXML and that is all.
Instead, you should fill it with data and then export the result to PDF.
No wonder you don't see any result.
You need to learn more about how JasperReports work. For a start, I can tell you that you could compile JRXML files as part of the application build process using an Ant task, and not dynamically, like you did. But no matter how you compile the report template, you actually need to fill it with data, using the JasperFillManager and then export it to PDF using the JasperExportManager.
You can see all this in our samples in the /demo/samples folder that is part of our project distribution package. There is even a sample Web application in the /demo/samples/webapp folder.
I hope this helps.
Teodor

RfcClientException: functiontemplate from repository was null

Similar Messages

Maybe you are looking for