Seeburger error

Hi,
My customer sends EDI data, but i am unable to receive that data to PI (I am able to receive upto our network), when i checked the log/trace file it is displaying below errors
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:121 - the table or view >>SEE_MSGIDSTOREAS1<< does not exist
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:121 - the table or view >>SEE_MSGIDSTOREEBXMLC
<< does not exist
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:121 - the table or view >>SEE_MSGIDSTOREFTP
<< does not exist
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:121 - the table or view >>SEE_MSGIDSTOREHTTP
<< does not exist
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:121 - the table or view >>SEE_MSGIDSTORESEDEB2B
<< does not exist
Could you please provide me what is the cause.
Thanks
Ramesh
Edited by: Venkataramesh Boppana on Nov 3, 2010 4:23 PM

Hi
I am using V4010 EDI version E2X mapping, i didn't get any message in RWB or MONI, in the Seeburger trace files i found those errors.
Thanks
Ramesh

Similar Messages

SEEBURGER Error (Outbound from XI): SSLHandshake Exception

Dear SAP experts,
Need your help regarding Seeburger error that i was encountering during our testing.
SAP have successfully triggered an IDoc from their system and was successfully sent to SAP XI for message translation. SAP XI have successfully translated the message and will be sending the output message via AS2 of XI to AS2 of the third party.
But, as looking the Seeburger (message monitor) of XI, there is an error logged:
Status Description: Could not deliver as2 message to partner: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found # null
The AS2 of the third party is also their SSL certificate.
Can somebody help me what is the root cause of the error?
Thank you very much in advance.
Have a great day!
Godofredo

Hi Soumya,
Thank you for your information.
The XI certificate we are using wa not yet expired. (will be expired by Sept 2008).
The second link, i think, was not applicable, since, we are using AS2 adapter and not Soap adapter.
Im still checking what could be the root cause of the issue.
Hope you can help me with this one.
Thanks!

PI 7.1 and seeburger error

Need some help on this error.
SQLException while getting MessageId entries! Caused by: com.sap.sql.log.OpenSQLException: The SQL statement "SELECT "CID","CSECONDARYID","CSTATE","CINCOMING","CCREATIONDATE","CLASTMODIFIEDDATE","CTIMEOUTDATE","CCUSTOMDATA","CINSTANCEID","CENV" FROM "SEE_MSGIDSTOREP7" WHERE "CENV" = ? AND "CCREATIONDATE" >= ? AND "CCREATIONDATE" <= ? ORDER BY "CCREATIONDATE" DESC" contains the semantics error[s]: - 1:121 - the table or view >>SEE_MSGIDSTOREP7<< does not exist
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:37)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:115)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:91)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:476)
at com.sap.sql.jdbc.common.CommonPooledStatement.<init>(CommonPooledStatement.java:236)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnectionImpl.java:1522)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:258)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:79)
at com.seeburger.dt.messageidstore.spi.db.SimpleAccessHandler.buildQueryStatement(SimpleAccessHandler.java:1104)
at com.seeburger.dt.messageidstore.spi.db.SimpleAccessHandler.getByQueryCriteria(SimpleAccessHandler.java:580)
at com.seeburger.xi.workbench.systemstatus.db.MessageIDQueryManager.getResult(MessageIDQueryManager.java:80)
at com.seeburger.xi.workbench.systemstatus.db.MessageIDQueryManager.getSpecificCount(MessageIDQueryManager.java:49)
at com.seeburger.xi.workbench.systemstatus.infoprovider.MessageIDStoreInfoProvider.getMessageIDStoreInfo(MessageIDStoreInfoProvider.java:26)
at com.seeburger.xi.workbench.systemstatus.infoprovider.MessageIDStoreInfoProvider.getInfo(MessageIDStoreInfoProvider.java:41)
at com.seeburger.xi.workbench.systemstatus.infoprovider.OverviewInfoProvider.fillAllInfo(OverviewInfoProvider.java:36)
at com.seeburger.xi.workbench.systemstatus.infoprovider.OverviewInfoProvider.getInfo(OverviewInfoProvider.java:18)
at com.seeburger.xi.workbench.systemstatus.actions.OverviewInfoAction.getSpecificInfo(OverviewInfoAction.java:35)
at com.seeburger.xi.workbench.systemstatus.actions.OverviewInfoAction.run(OverviewInfoAction.java:22)
at com.seeburger.xi.workbench.systemstatus.Controller.service(Controller.java:122)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:173)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

Check the table?
"1:121 - the table or view >>SEE_MSGIDSTOREP7<< does not exist"
Could also be insufficient access rights.

AS2 Seeburger error troubleshooting

Hi,
I just would like to ask if anybody knows how to troubleshoot errors on AS2 Seeburger. We usually have the below errors in the Seeburger Monitor:
- Error on send, will not be retried     Could not send ansynchrone MDN to partner!
- Error on receive, task will not be retried     Cannot initiate received message to backend system AND max retry reached!
- Error on receive, task will not be retried      Could not send ansynchrone MDN to partner - url not set!
- Initiation to Backend Pending                    Could not send ansynchrone MDN to partner!
- MIC error
Do you happen to have materials about Seeburger which shows how to resolve and prevent such issues? I also need to get the root cause of these issues, can you kindly help me identify the actions I need to take to get to the root cause?
I look forward to hearing form you.
Kind regards,
Grace

- Error on send, will not be retried Could not send ansynchrone MDN to partner!
   1. Tell Business partner to not to request MDN when they send document to you.
   2. check the authentication certificate in your sender agreement
- Error on receive, task will not be retried Cannot initiate received message to backend system AND max retry reached!
   1.Sender might be using wrong certificate.
- Error on receive, task will not be retried Could not send ansynchrone MDN to partner - url not set!
same like first answer
- Initiation to Backend Pending Could not send ansynchrone MDN to partner!
same like like first answer
- MIC error
valide sender is not identified, check the AS2 id and certifcates

Idoc to X12 file seeburger error

I get the below error at the receiver file adpter,tested the mapping internally and it works fine.Can you help me please.D_165 is mapped to a constant 'U'.
SEEBURGER BICXIADAPTER --- CONVERSION ERROR ---InhouseDocReader doSyntaxCheck(): offset[281]: the found segment D_I65 is not in the message description. DESCRIPTION: InhouseDocReader Error: The Segment D_I65 is missing in the message description. Check your file.
Thanks

( I have define a party and make a connection under Idoc Partner
Do you really need a party in your communication? Should it not be a partly-less communication.
In the receiver agreement ensure that you have included the inbound message interface.
communication party = space
No need to give any space.
In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
Regards,
Abhishek.

SEEburger error in conversion from EDI to EDI-XML

Dear SAP experts,
Good day!
Can i seek your inputs regarding this error i'm getting when i've tried to convert the EDI (D93A_RECADV message) into EDI-XML?
I am using BIC for this one.
This is the error i am getting,
[Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[78167]: the found segment is not in the message description.
Conversion error
Does this mean the source file is in wrong structure?
Kindly advise.
Thank you very much!
Fred

Hi,
Make sure that You used the Source structure in the IR from the External Def of the Seeburger SWCV only.
And deployed the necessary mappings on XI server by making the .sda file in BIC.
And the Incoming file should have the valid values while parsing the EDI file inorder to convert the EDI ti EDI_XML
Check this also
/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Regards
Seshagiri

Seeburger error - No matching inbound binding found

Hi
I am trying to buld a interface using Seeburger AS2 adapter. I have done all the config in XI and Seeburger level. But when customer sent the message he gets following error.
HTTP/1.1 403 Forbidden^M
server: SAP J2EE Engine/7.00^M
content-type: text/html^M
content-length: 826^M
date: Tue, 18 Nov 2008 23:50:04 GMT^M
^M
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
   <head>
      <title>SEEBURGER AS2 Server: Forbidden </title>
   </head>
   <body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="
#551a8b">
      <table cellpadding="0" cellspacing="0" border="0" width="100%" bgcolor="#dc4560">
         <tbody>
            <tr><td> </td></tr>
            <tr>
               <td> </td>
               <td valign="middle">
                  <h3>
                     <font face="sans-serif" color="#ffffff">SEEBURGER AS2 Controller</font>
                  </h3>
               </td>
            </tr>
         </tbody>
      </table>
      <br/>
         <font face="sans-serif" size="-1">
           <b>
403 Forbidden
           </b>
         </font>
      <br/>
   </body>
</html>
When I checked the Seebuger log I noticed following
seeburger.as2.AS2Plugin#Plain###Inbound communication from TESTEDI to GFB2BDPI not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No matching inbound binding (message) found for FromParty:PT_TOLL ToParty:PT_GOODMANFIELDER subject:<20081119091602.651278.2248792@> [LOC: com.seeburger.as2.component.AS2Server.checkInboundRelation]#
If someone can help that will be great.
Thanks
Shantha Bandara

Hi,
403 is a standard error if the AS2-IDs are not setup correct. You can also seet his in your log-file:
"Inbound communication from TESTEDI to GFB2BDPI not allowed"
Looks like the SenderAgreement is not referring to the correct parties...
Greetings
Stefan

AS2 Async mdn issue in seeburger monitor

Hi PI Experts,
My scenario is B2B Inbound Interface.
Partner(AS2)------->PI(7.31)--------->SAP.
MDN:Async
While Partner sending data from Third Party to PI getting below error in Seeburger Monitor.
Error : Could not send ansynchrone MDN to partner!
for Inbound interfaces from Partner side they did the MDN:Aync settings .But PI not able to receive the data from Partner ,getting the above error in seeburger monitor.
Could you please help me on this issue ,this is very urgent.
Thanks,
Aadi

Hi,
Have you had a look at these links?
Error in Seeburger Message Monitoring
AS2 Seeburger error troubleshooting
Regards,
Jannus Botha

Information on AS2 Seeburger monitoring

Hi All,
Recently a Seeburger interface got introduced in our production,could any one please share their experience or documents for monitoring AS2 .
2)In As2 scenarios ,how to correlate the MDN number with XI Message Ids.
Regards,
Vidya

Hi look at this Thread
Re: Mapping and Monitoring in B2B(Seeburger adapters) scenarios
AS2 Seeburger error troubleshooting
Regards
Abhishek
Edited by: Abhishek Agrahari on Jun 1, 2009 7:02 AM

As2 receiver channel, SEEBURGER AS2: 500 Internal Server Error

Hi,
There is one scenario in our landscape, its running in production, Proxy to As2. The interface working fine for last 2 weeks, today its showing error in As2 receiver channel saying
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: 500 Internal Server Error # , SEEBURGER AS2: 500 Internal Server Error #
I have searched in forum, but couldnt get much idea on why this error encounters and how can we resolve it.
Kindly provide your inputs to help me resolve this.
Thanks,
Ruchi

Hi Ruchi,
500 means the requested server does not understand the request (the requested service is unknown). The reason is obvisiously outside of PI. You have to contact the 3rd party owner and ask why the system is refusing the request instead of responsing like before.
Regards,
Udo

Error in Seeburger Message Monitoring

Hi ,
I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file.
I m getting error in seeburger message monitoring with status as "Could not send ansynchrone MDN to partner - url not set!". can anybody tell me whats the reason behind it,where it went wrong.

Really didn't understand your scenario. That sentence makes no sense:
"I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file."
But what I understand from the error message you have provided...................
if you are using Seeburger AS2 adapter as Receiver Comm Channel..........then there is definitely some cofig error is settings for MDN acknowledgement.
Under Parameters Tab:
You must have set the following parameter
MDN Mode = "ASYNC"
And has not provided the following parameter just below it :
Receipt Delivery Address
This parameter should have value: the URL of your own AS2
server where the asynchronous MDNs are
to be delivered.
Hope this solves your problem.
Regards,
Suddha

Variable substitution error while using Seeburger module parameter

Hi Freinds,
I would like to use the variable substitution in a receiver file adapter to add the invoice no.
(which is contained in the XML file) to the target filename.
In addition I have to convert the XML file to an X12 EDI format using the seeburger module "localejbs/CallBicXIRaBean".
As soon as this entry is made in the modules the following error message occurs:
"com.sap.aii.adapter.file.configuration.DynamicConfigurationException:
Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException:
Caught SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
XMLParser: No data allowed here: (hex) 53, 4f, 48(:main:, row:1, col:3)"
My problem is that the conversion from XML to X12 EDI is done before the variable substitution is started.
That`s why the reference for the variable is no longer valid as the file is already converted to a X12 EDI (=flatfile) format.
If I disable one of the two steps (either 1:1-mapping or variable substitution) the other step runs properly.
Has anybody an idea how to solve this topic?
Is it possible to specify the variable substitution as module?
If this is possible I could solve it by just reordering the two steps in the module chain.
Regards
Venkatesh

Use Dynamic Configuration Bean to set this value. You have to use this well before "localejbs/CallBicXIRaBean".
Check SAP note : 974481 for more information.
Blog: [/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean|/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean]
Second Approach if the above approach doesnt work.
Use Dynamic Configuration concept in UDF to set the filename under message Mapping.
Thanks,
- Gujjeti.
Edited by: Praveen Gujjeti on Feb 25, 2009 11:25 AM

Error with Seeburger Splitter module

Hi all,
I had configured Seeburger Splitter and using seeburger splitter module in file adapter with classifier,convertor and splitter in same sequence.But,while testing i m getting null
error for sender file adapter in communication channel monitoring.It isn't able to process the file placed in directory.
When audit log of same is seen,it shows
ERROR : getXmlContentFromMessage()
ERROR : process()
ERROR : Attempt to process file failed with null
Any inputs why is it so.
Regards,
Anoop

Hello Ravi,
We have seen this issue on a few occasions. It might be related to the ConverterJNI class.
In the defaulttrace file you can check for error such as
Caused by: com.sap.i18n.cp.ConverterRuntimeException........
Got exceptions: null
at com.sap.i18n.cp.ConverterJNI.<clinit>(ConverterJNI.java:46).....
If this is the case, Then the problems is within the Startup Framework. I would advise you to update the Startup Framework as described in note #710914.
Thanks,
David

Seeburger : DECRYPTION ERROR

Hi guys,
I'm having the following error :
I'm using Seeburger AS2 adapter and I'm trying to receive a message from an external partner.
I've the corresponding configs on the sender agreement from the external partner:
sender agreement
Sender Configuration
     Authentication Certificate : \AS2\testPartner
Receiver Configuration
     Decryption Key: \AS2\testMykey
     Signing Key: \AS2\testMyKey
And I'm getting the following error
Error while parsing AS2 message: DECRYPTION_ERROR # Error while loading decryption certificate: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystorecom.seeburger.ediint.edi.EDIMessageException: cannot decrypt message (certificate or private key missing)
I've tried several certificates, generated other keys but the error is always the same....
It seems that the alias is not found? But it's there...
Does anyone had the same problem?

Hi Peter,
Thanks for your quick response.
I'll restart the J2EE Engine and I'll give you feedback. Thanks for remembering.
I've noticed that you used on the receiver agreement the partnersKey for the encryptionCertificate. It was a mistake, right?
"receiver agreement:
Signing Key: TRUSTED/AS2/AS2myKey
Encryption Certificate: TRUSTED/AS2/partnersKey
Authentication Certificate: TRUSTED/AS2/AS2myKey"
it should be
"receiver agreement:
Signing Key: TRUSTED/AS2/partnersKey
Encryption Certificate: TRUSTED/AS2/AS2myKey
Authentication Certificate: TRUSTED/AS2/AS2myKey"
Right?
Again, thanks for your quick reply.
P.S. - I'll give you feedback on the other threads. I'm doing stress tests with my external partner, and literally stressed tests

Seeburger AS2 HTTPS receiver channel error

Hi,
I am getting the following error in the receiver Seeburger AS2 channel with HTPS connection and going through a proxy to the Partner.All the certificates have been installed,proxy server information gives,mentioned the key store values and encryption certificate values have been mentioned in the receiver agreement that is using the channel.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection., SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection.
Can you please give me an idea whether I am missing something or any configuration settings I need to make.
Thank you,
Sri

hi Neetesh,
Thank you for the link.The first thing I have looked at is the link you gave me.But when I give with * it is complaining that it is not able to retrieve the certificates.
TRUSTED/AS2CERTS/*,but I have backward slashes..may be OS is different ,I think the original poste might have Windows servers.
any other ideas please.
thank you.

Seeburger error

Similar Messages

Maybe you are looking for