cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Gui 720 SOFFICEINTEGRATION Error 207 Error during method call

Former Member
0 Kudos

Hello SDN.

I ve got a strange thing in the combination of MS OFFICE2010 32 BIT package and SAP Gui 7.20 PL9 for windows released on 14.11.2011

Related to SAP Note, Note 1611709 - Office 2010 crashes on using quick option "SaveAs", "Print" we waited 3 weeks for the release of the patch. We 've applied 7.20 PL9 yesterday! Now, in transaction VA22 the same result.Header output preview, form conditioning (Formularaufbereitung)

Error during method call

Message no. SOFFICEINTEGRATION207 during call

Where we could see which Method fails.The trace didnt show an real error, only DOI kill, last entry was OLE_FLUSH_CALL Prog:SAPLOLEAZeile:

T100 Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:DSOFFICEINTEGRATION 207

DOKIL Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:NASOFFICEINTEGRATION207

DOKIL Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:NASOFFICEINTEGRATION207

D347T Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:SAPMSDYP

DOKIL Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:NASOFFICEINTEGRATION207

DOKIL Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:NASOFFICEINTEGRATION207

D347T Prog: SAPMSDYP Zeile: 0 Puffer: PSuchstring:SAPMSDYP

D347T Prog: SAPMSDYP Zeile: 0 Retcode: 0

Which mehod call goes wrong? Where we could find the issue? Is it maybe related to your OFFICE2010 Package?

Thx

Ralf

Accepted Solutions (0)

Answers (1)

Answers (1)

jude_bradley
Advisor
Advisor
0 Kudos

Hello Ralf,

Better to open a message for this one.

Before you submit the message, recreate the issue with the automation trace active.

There is a new feature in patch 9 which makes this easier to to now.

Run the ALT +F12 => Options => Traces => Session Trace, and check the Automation and Office Integration options

then apply and recreate the issue.

Regards,

Jude

Former Member
0 Kudos

Thx, right now i opened a message related to this transaction problem.

Thanks for your advice.