ASO SEND Issue

Good morning
How robust is the send function when using an ASO database? I have had an issue recently where the database locks up
(error message "Cannot Send, Cannot Receive data") This seems to corrupt the database
Has anyone experienced this before? Is there an explanation for this?

It is typically the other way around. The database has some sort of corruption so when you try to send\recieve data from it it has already crashed. There could be a lot of reasons for this a couple are
Bad Disk sector
Bad formula in the database
It is not easy to diagnose this issue, I would try the second one first and see if the retrieves are hitting a formula that is bad.

Similar Messages

I have Adobe CS4..... now when I want to print my picture, I get the message "Adobe CS4 has stopped working, sending issue to windows and then disappears.... nothing can print anymore...Help??

I have Adobe CS4..... now when I want to print my picture, I get the message "Adobe CS4 has stopped working, sending issue to windows and then disappears.... nothing can print anymore...Help??

Try updating the printer driver.

Icloud 2.0 and outlook 2007 send issues

icloud 2.0 and outlook 2007 send issues
i cannot send email any longer in outlook 2007

Look at this discussion:
Re: Excel 2007 problem opening xlsx files when iCloud control panel is installed
.... and the problem is still not solved (iCloud 3.1.0.40) and I guess will never be. We need to rename or delete the shellstreams.dll or save the excel-files as .xls to solve the problem for ourselves!
What a shame!

Send Issues with Outlook for Mac (2011 / V15) and Exchange 2013 SP1

Hi all,
we have a strange issue with only with Outlook for Mac Users (version 2011 and the newest Outlook Version (V15) from Office 365) connected to our Exchange Server 2013 SP1. Some emails which we send out to the exactly same recipient are not sent through our
Exchange Server.
We have sent 8 emails with subject "test1, test2, test3...". Only test 3-6 was arriving to the recipient. The other emails are in the "sent" folder but it was not sent out through the Exchange.
What we can see with "Get-MessageTrackingLog" is, that the Recipients and MessageSubject are empty for these emails:
Timestamp Sender Recipients MessageSubject
25.02.2015 16:48:52 [email protected].. {}
25.02.2015 17:04:43 [email protected].. {}
25.02.2015 17:08:25 [email protected].. {[email protected]} test 3
25.02.2015 17:08:56 [email protected].. {[email protected]} test 4
25.02.2015 17:09:38 [email protected].. {[email protected]} test 5
25.02.2015 17:09:38 [email protected].. {[email protected]} test 6
25.02.2015 17:13:45 [email protected].. {}
25.02.2015 17:13:55 [email protected].. {}
We can still reproduce the issue on different Mac computers.
Thanks for any help in advance!
Thanks and best regards
Reto

Here is the mailheader form the successfully sent email:
Date: Wed, 25 Feb 2015 17:08:25 +0100
Subject: test 3
From: sender <[email protected]>
To: "'[email protected]'" <[email protected]>
This mailheader is from an email which was not sent out:
User-Agent: Microsoft-MacOutlook/15.6.0.150113
Date: Wed, 25 Feb 2015 16:48:52 +0100
Subject: test 1
From: sender <[email protected]>
To: [email protected] <[email protected]>
Interesting: Only the not received messages contains User-Agent string and have some quotation marks missing in the To field.

Hp officejet j4580 Fax sending issue

I can send faxes to 800- numbers but when I use an area code, I hear a ring and then my landline phone clicks on, evidently to intercept the fax and the fax machine rings for a while and then quits.

Hi there @PGROWTH ,
Welcome to the forums
I read about the faxing issues you're having with your Officejet J4580 when sending a fax to a number either than a 1-800 number.
I would suggest trying these steps in this guide: Can Receive Faxes But Cannot Send Them
Also try a power reset:
Press the Power button to turn on the product.
With the product turned on, disconnect the power cord from the rear of the product.
Unplug the power cord from the wall outlet.
Wait at least 15 seconds.
Plug the power cord back into the wall outlet.
Reconnect the power cord to the rear of the product.
If the product does not turn on by itself, press the Power button to turn it on.
If the troubleshooting does not help resolve your fax issue, I would then suggest calling HP's Technical Support to see about further options for you, such as a replacement or trade in. If you are calling within North America, the number is 1-800-474-6836 and if you are calling outside of the US/Canada region,: click here.
Best wishes
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

JDBC sender issue no data in PI

Hello,
We have a scenario Database to SAP we are using JDBC adapter at sender side and the Qos is EO.
Now the issue is database sender complained that they have sent the data from database but the data is not updating in SAP system as a result no Idoc created.
In the DB trace the DBA said that the SELECT executed successfully.
But I checked in PI and no failed or scheduled message in the Component Channel monitoring. The message id is greyed out. All I see is that Polling started and Processing finished successfully.
In SXMB_MONI there are no xml messages.
SELECT * FROM sys.tables works fine and I can see xml messages in SXMB_MONI and also see the audit trace log in RWB under CC monitoring.
Why is it not picking up data from other user tables in SQL server database?
I have analyzed the issue end to end .
Where is the adapter sending the converted xml messages if it has picked up data? If it has not then why cannot i see the trace and why is the message id greyed out in the CC monitoring?
Please help me to resolve this problem .
Thank you,
Teresa

Dear Thomas,
Same issue i am facing in Production,
Please suggest me,
my scenario is also like JDBC -->XI--> SAP( Proxy).
The database server sending data to xi, here signals are coming xi perfectly but suppose 100 messages db people sending only 1 or 2 messages lost and it is not shown in xi.
when i checked with SXMB_MONI, RWB(Messages Monitoring, component monitoring) and logs no error message.
DB side it is showing XI_Read time status also changed 'N' to 'S'.
Query:
Select Query:SELECT * FROM MCON_INTF_OPS WHERE CSTATUS = 'N' FOR UPDATE
Update Query:UPDATE MCON_INTF_OPS set CSTATUS = 'S',CXI_READ = sysdate WHERE CSTATUS = 'N'
why few signals are lost please suggest me

Email send issue using "Mail Server Load balancer" (Cisco ACE 20)

Please let me know if someone have experienced this kind of issue or any suggestions.
The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
MII still sends email if direct ip address of email server provided but not through email Load balancer .
Any suggestions ?
Could not authenticate mail account (Unknown Source)
[EXCEPTION]
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at javax.mail.Service.connect(Service.java:169)
at javax.mail.Service.connect(Service.java:118)
at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Repeater.doExecute(Repeater.java:113)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:158)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.processQueryRequest(XacuteRequestHandler.java:342)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.QueryRequest(XacuteRequestHandler.java:135)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteConnector.doProcessRequest(XacuteConnector.java:86)
at com.sap.xmii.Illuminator.connectors.AbstractConnector.processRequest(AbstractConnector.java:83)
at com.sap.xmii.Illuminator.server.QueryEngine.run(QueryEngine.java:41)
at com.sap.xmii.Illuminator.services.handlers.IlluminatorService.processRequest(IlluminatorService.java:68)
at com.sap.xmii.Illuminator.services.ServiceManager.run(ServiceManager.java:68)
at com.sap.xmii.servlet.Illuminator.service(Illuminator.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:80)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:44)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.processServletRequest(ReportParser.java:610)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseServletTag(ReportParser.java:276)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseFile(ReportParser.java:154)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parse(ReportParser.java:119)
at com.sap.xmii.servlet.ReportServlet.service(ReportServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
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:78)
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:78)
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:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Date:
2014-03-25
Time:
14:04:06:176
Category:
com.sap.xmii.storage.connections.MailConnection
Location:
com.sap.xmii.storage.connections.MailConnection
Application:
sap.com/xapps~xmii~ear
Thread:
Thread[HTTP Worker [@629095796],5,Dedicated_Application_Thread]
Data Source:
j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction:

Have a look at this thread please:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11f3079-b04a-4a8e-b89e-d56eb0532c42/the-mail-could-not-be-sent-to-the-recipients-because-of-the-mail-server-failure-sending-mail-using?forum=sqldatabaseengine
Saeid Hasani [sqldevelop]

SAP PI7.11 adapter RFC sender issue after migrating to SAP ECC6

Hi,
After the migration of our backend from SAP 4.700 x 200 to SAP ECC6 unicode (kernel 7.20)), we have a issue of connexion to our SAP PI 7.11.
A part of the field in ECC6 are not well mapped by the abapter sender RFC to the xml in PI.
I join a screen shot what I have in SAP ECC6 (inquiryECC6.jpg) and the result in SAP PI 7.11in xml format ofcourse (Inquiryxml.jpg).
Is there someone who can help me?
Regards.
Eric Koralewski

In SM59, there is a new tab <unicode>.
In that tab, I checked the unicode checkbox and that's ok.
Regards

Mail sender issue

Hi all
since upgrading to iOS7.1.1 I've had a weird issue. In the sidebar of mail on my ipad2 the sender is listed as the same person for all messages. When I rap on it and go into the body of the message the correct sender is listed in the "from" line and I am able to reply to that correctly.
I have deleted and added my exchange account on several occasions but this hasn't rectified the problem. This problem does not occur on my iphone 5 (running 7.1), on my MacBook Pro (running 10.6.8) or on the webmail page of my email server.
Any thoughts?
Many thanks in advance.
Bugsy

Hello there, Bugsy.
Great job troubleshooting your issue on your own, so far! As simple as it may seem, I find the following Knowledge Base article helpful when an App on iOS doesn't seem to be functioning as expected:
iOS: Understanding multitasking
http://support.apple.com/kb/ht4211
If an app doesn't respond to your input, or doesn't perform as expected, do the following, testing after each step:
Check for app updates.
Force the app to close.
Restart your device.
Update your iOS device.
Learn more about troubleshooting apps.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Evolution-mapi send issue

If anyone is familiar with evolution-mapi, perhaps you can help me. I have no problem connecting to our exchange (2007) server. I have full access to my mailbox and can sync and read my mail. My issue is I cannot send. I get this error message:
Could not send message: WriteStream: MAPI error MAPI_E_CALL_FAILED (0x80004005) occurred
I've tried poking through my outlook profile from windows using MFCMapi, but I don't see anything glaringly obvious that would prevent me sending mail when logged into Arch using Evolution . . . especially as I can authenticate to receive mail with no issue.

If anyone is familiar with evolution-mapi, perhaps you can help me. I have no problem connecting to our exchange (2007) server. I have full access to my mailbox and can sync and read my mail. My issue is I cannot send. I get this error message:
Could not send message: WriteStream: MAPI error MAPI_E_CALL_FAILED (0x80004005) occurred
I've tried poking through my outlook profile from windows using MFCMapi, but I don't see anything glaringly obvious that would prevent me sending mail when logged into Arch using Evolution . . . especially as I can authenticate to receive mail with no issue.

Questionnaire send issue

Hi Experts,
We have implemented ROS scenario and created questionnaires for vendor selection. We have 2 kinds of questionnaire u2013 General Questionnaire (send for all product categories) and Specific product category based questionnaire. In standard ROS, General and Product Specific questionnaires are sent automatically after the vendor submits the Initial Registration page.
For our scenario, we donu2019t want the questionnaire to be sent automatically. After the vendor details are received from initial registration, employee will view the data and decides to send or not to send the questionnaires. He/She then goes to u2018Categories/ Questionnaireu2019 tab in ROS prescreen page and sends the questionnaires.
The issue we are facing is when the automatic email send functionality is deactivated; the General Questionnaire does not appear in the u2018Categories/ Questionnaireu2019 tab in prescreen page. Only the product specific questionnaires for product categories the vendor selected during registration appear. As a result the employee cannot send the General Questionnaire to the supplier.
Is this a standard SAP behavior or are we missing any settings? Please advice.
Regards,
SKN

HHmmm...
One more time to make sure I am being clear. I have three accounts - a .mac account, an excite account, and an adelphia account. Adelphia is my ISP - I do not use that email service - although I did set it up just to test the mail system and it sends/receives fine. .mac also sends / receives fine. When I use Excite.com account to send email, I get the following reject message by checking webmail - no indication that the message was not sent in Mail; I get no errors back. It is as if Excite is rejecting the email as Spam...
I checked all server settings for excite account - they are all correct - the server selected in preferences is the excite smtp server for outgoing mail...
Does the following really say that mac.com is refusing to send??
Thanks again - this is annoying and I am ready to dump Excite...
Date: Sun Oct 29 19:04:34 2006
From: Mail Delivery Subsystem <[email protected]>
[ Add to Address Book | Block Address | Report as Spam | This is not Bulk Mail ]
To: <[email protected]>
Subject: Returned mail: see transcript for details
The original message was received at Sun, 29 Oct 2006 16:04:32 -0800 (PST)
from mail23-ce1 [10.13.11.50]
----- The following addresses had permanent fatal errors -----
<[email protected]>
(reason: 554 <[email protected]>: Sender address rejected: The mailserver used does not match the excite.com domain Error: WS-13)
----- Transcript of session follows -----
... while talking to xmxatip.excite.com.:
DATA
<<< 554 <[email protected]>: Sender address rejected: The mailserver used does not match the excite.com domain Error: WS-13
554 5.0.0 Service unavailable
<<< 554 Error: no valid recipients
<div class="jive-quote">RSET
<<< 421 xprdmx30.nwk.excite.com Error: too many errors
<br>
iMac 20" core 2 duo Mac OS X (10.4.8)
iMac 20" core 2 duo Mac OS X (10.4.8)

Essbase ASO Calculation Issue

Hi All
I am writing a calculation for a client to copy one version to another version for an Essbase ASO application.
It seems to work correctly when my POV is set on a smaller datapoints. Hower it seem to have issues when fixed on larger datapoints.
The calculations is pretty simple
[ActualFinal] := [ActualWorking];
I tried creating and running the calculation both using MaxL and Calculation Manager. However the same issue seem to occur.
I first thought it might have been an implied share issue, but further investigation, it doesn't seem to be the issue as I can get the data copied using a smaller POV.
The client is on version 11.1.2.3 of Essbase.
Any one have any thoughts of what may be causing this?
Thanks
Jimmy

I had this issue in 11.1.2.1. Never tried on the later versions
FYI - Have a look at this post (http://www.network54.com/Forum/58296/thread/1359579119/MDX+Query+-+Error+127001)
Below is an excert from the post by Joe Watkins
Joe Watkins
167.107.191.217
ASO Performance
No score for this post
February 11 2013, 1:18 PM
Here are the current limitations as I see them when trying to go ASO only:
- These scripts are not as fast as calc scripts
- performance is worse when users are on the system
- Cannot run these types of calcs when loads are taking place
- need to watch for incremental slices
- Users cannot natively execute these types of scripts
- These scripts can be very fussy to get working
- When I ran the exact same scripts (per my examples) as 'Calculation' versus 'Allocation' the 'Calculation' would skip random cells which was really weird and impossible to fix which is why I switched to using 'Allocation'
In my mind the technology is not mature enough at the moment to get rid of BSO but its getting better..
Amarnath
ORACLE | Essbase

IMessage sender issues

I share my apple account between several devices. For some reason lately when I use iMessage it is changing the user name or the sender name from the user that it should be (me). Anyone have any ideas how to fix this so it shows as the correct sender?

I've noticed this happening too. My wife & I both have the iPhone 4S and since we got the iPad last Friday we noticed iMessages working oddly. If I send her a message via iMessages from my phone it sometimes will show up on her phone as if she had sent it to herself. And if I'm using iMessages on the iPad the conversation automatically shows up on her phone and even an old iPhone 3GS that our son uses as an iPod touch. I thought it might be because we just got the iPad but now I'm thinking it's a wider issue.
Any help would be great!
Thanks.

EMail sending issues?

I seem to be having mixed results when I get an email on my phone, using my wireless network at home or in public.
About 50% of the time I get a bounce "Server rejected Address" or something to that effect - when I am REPLYING to an incoming email.
The rest of the time it works. Sending and receiving email was one of the main reasons I bought the phone. Any idea what is up with this?
Thanks!
Mark

One suggestion for all having send problems.. I have found that using a service such as GoDaddy works very well with the iPhone. They provide domain registration and web email packages for reasonable prices (less than $20/yr).
I ran into a similar problem even with them and the answer ended up being you have to specify the port on the send server address:
Example:
GoDaddy's send server would be entered as follows:
smtpout.secureserver.net:80
Without specifying port 80, it automatically defaults to port 25 which depending on if you are EDGE connected or WiFi connected may or may not work.
You may be able to solve the problem for your specific ISP if you contact them and ask them for the specific port used.
If they can't help, services like GoDaddy appear to work.. Also a plus is the ability to have your own custom domain name..
Also another plus is that this particular service appears to handle the pop lock connect/disconnect issue smoothly which often happens when connected via EDGE.

ASO SEND Issue

Similar Messages

Maybe you are looking for