An Error Occurred In Program So_object_mime_get
ABAP DevelopmentWhere is this place located?All Places ABAP Development 9 Replies Latest reply: Aug 3, 2011 12:42 PM by Elton Witbooi Tweet SO_OBJECT_MIME_GET Exception: 2 susin message cannot currently be transferred to node smtp due to connection error 18 Oct 22, 2008 7:43 AM Currently Being Moderated Gurus sap notes , i have gone through but still i could not solve the problem . The default domain is set code page is setbut i am not sure why is this problem still persisting . help me solve this 13880Views Tagsnone (add) Topics: abap Re: SO_OBJECT_MIME_GET Exception: 2 Madhan Doraikannan Oct 22, 2008 11:10 AM (in response to susin 18) Currently Being Moderated HiWhen you are getting this error, i mean during which process / transaction in SAPRegardsMadhan Alert Moderator Like (0) Re: SO_OBJECT_MIME_GET Exception: 2 susin 18 Oct 22, 2008 11:14 AM (in response to Madhan Doraikannan) Currently Being Moderated the problem is i am unable to send mails this is the error message i get , when i traced the log in SCOT "Internal error: SO_OBJECT_MIME_GET Exception: 2Message no. XS829DiagnosisAn error occurred in program SO_OBJECT_MIME_GETError text: Exception:Additional information:2System ResponseMessage processing terminated." Alert Moderator Like (0) Re: SO_OBJECT_MIME_GET Exception: 2 Madhan Doraikannan Oct 22, 2008 11:18 AM (in response to susin 18) Currently Being Moderated HiAnswer is pure assumption.Pls check OSS noteNote 487754 - Error sending mail: SO_OBJECT_MIME_GETPls take opinion from SAP / Basis team, if you want to implement the noteRegardsMadhan Alert Moderator Like (0) Re: SO_OBJECT_MIME_GET Exception: 2 susin 18 Oct 22, 2008 11:56 AM (in response to Madhan Doraikannan) Currently Being Moderated we have relayed the IP in exchange server and alsi i alreay took a look into 487754 I have configured all of them , but still the problem persists Alert Moderator Like (0) Re: SO_OBJECT_MIME_GET Exception: 2 susin 18 Oct 23, 2008
Monitor ERROR MESSAGES IN SOST (incoming and outgoing emails in SAP) Monitor ERROR MESSAGES IN SOST (incoming and outgoing emails in SAP) 27 December 2012 | Davy Pelssers | 17 Comments | SAP basic knowledge If you have access to the transaction code SOST you can monitor incoming and outgoing emails in SAP. Alternatively you could also use the following transaction codes: SOIN BCS: Inbound Send Requests (SMTP) SOSG Send Request Overview (Groups) SOSB Send Request Overview (Users) https://scn.sap.com/thread/1097357 By default SAP shows you the “outgoing emails” sent from SAP. In the first tab “Period” you can define the period that you want to monitor. In the Second tab “Send Status” you can choose to only show “Errors”. If you take a look at such outgoing emails containing an error you will probably see many different error http://sapuniversity.eu/monitor-error-messages-in-sost-incoming-and-outgoing-emails-in-sap/ message types. If you select such an email and press the “glasses”, you see more details: On the tab “Recipient list” you’ll see the addressee and further below you will see the error messages: If you click on the error message “No Delivery to xxx as recipient unknown” itself you see more technical details: If we take a look at the most frequent error messages in our system we identify the following ones: 1. Message no. XS802 No delivery to xxx, as recipient unknown This means the email address that was used in the field “TO” (recipient) is incorrect. Potential causes: The person you tried to email no longer works at a particular company and therefore the email address is no longer valid You made a typo when manually entering the email address (and as such the email address is not valid) Check: You can use free online services to check whether an email address is a valid one or not. Just do a simple Google search on “Email Valid
Error MessageSAP ProgramASEASE Error Message DatabaseOracleOracle Error MessageMySQLMaxDBMSSQLDB2ASEASE Error MessageInternetWebWordpressGoogleOperating SystemLinuxRed HatSuSeUNIXAIXSolarisHP-UXVirtualizationWindowsWindows 8Windows 7Windows XPWindows ServerAndroidSoftwareMicrosoftSAPSAP BasisSAP SolmanSAP SecuritySAP ABAPSAP ParameterSAP ProgramSOST: Error while automatically determining the default internet domain By ITsiti · Category SAP Basis · Updated http://itsiti.com/sost-error-automatically-determining-default-internet-domain November 23, 2013 Share this article :Facebook0Google+0Twitter0LinkedIn0In transaction SOST, your http://www.se80.co.uk/sapossnotes/8/8061/806169.htm are getting error, "Internal error: SO_OBJECT_MIME_GET Exception:2" while checking the email delivery status. In order to dig further details, you need to look onto the trace file. You can get the trace from transaction code SOST. Highlight the error email, an error select Send Request > Display Trace from the top menu. Then, select Choose (or F2) to view the trace. In this exercise, below error was found. BCS->MIME_MESSAGE_GENERATE Error when generating MIME flow BCS->MIME_MESSAGE_GENERATE Error while automatically determining the default internet domain SO_OBJECT_MIME_GET No MIME Document Received. Error Code: MIME_BCS SX_GENERATE_NDR Internal an error occurred error: SO_OBJECT_MIME_GET Exception: 2 Solution1. From the top menu of transaction code SCOT, select Settings > Default Domain. Define the default domain and save. You can resend the email again ReferenceSAP Note 487754 Tags: scot default domainRelated postsSM02: System MessagesDefine SAP Support Package QueueStart & Stop the Software Deployment ManagerRun ABAP reports - Time limit exceeded Get the latest posts delivered to your inbox PopularLatest Execute OS Commands from SAP GUI 14 Comments Delete Imported Request in SAP 8 Comments System Change Option to Modifiable or Not Modifiable in SE06 6 Comments ST03N: SAP Workload Monitor 5 Comments SM01: Lock & Unlock Transaction Codes 5 Comments VirtualBox: Your PC needs to restart. Error Code: 0x000000C4 (Windows 8) 5 Comments Steps to Upgrade SAP Support Package Stack using SUM 4 Comments Procedure Before Stopping an SAP System - ABAP Stack 4 Comments How to Remove & Reschedule a Process Chain Septembe
instructions on how to fix it. Click here for more information about SAP OSS Notes and how they are downloaded and implemented using transaction code SNOTE Contribute (Add Comments) Use the comments section below to add any links, information or screen shots that you feel are relevant to this SAP Note. This could include issues you have found that are associated with this fix as well as any additional fixes you have found or other relevant SAP OSS notes. This information can then be found quickly, simply by searching on the note number 806169 . Note Details: When does this problem occur External shipping of documents triggers an error. The following entry is found in the SAPconnect trace: "Internal error: SO_OBJECT_MIME_GET exception: 2". Cause of the problem and Pre-requisites You try to send a document that consists of exactly one empty line. This causes an error when creating the mail. Solution instructions Implement the source code correction in accordance with the correction instructions. Also refer to Notes 487754 and 671260. Description of problem E-mail, fax, SO_OBJECT_GET_MIME, Smartform 805035 807737 Please enable JavaScript to view the comments powered by Disqus. comments powered by Disqus Terms of Service     Contact Us     Privacy Policy     Useful SAP related sites