cancel
Showing results for 
Search instead for 
Did you mean: 

SAP DIAPI & B1if Errors : XCE208 resource is busy & Entry already exists -2035

former_member264639
Participant
0 Kudos

Hi Experts,


     We recently upgraded from SAP 8.82 PL07 to 9.1 PL05.

    

     We use two kind of  own addons ,


          1. Windows application which posts to SAP B1 using DI API

          2. Posts using B1if (HTTP Rest protocol) with b1if version 1.20.9 and its SLD Type is SAP B1 9.0.  


      Issues :

     1. B1if returns the error in version 1.20.9

          “Exception: XCE208 resource is busy B1Server|company = ‘********’ “

             But, its posting without above error using B1if version 1.18.9 with SLD Type SAP B1 9.0  for SAP 9.1 DB.


         Solution Required : What i have to do for in b1if 1.20.9 with out above error?.


        2.  We getting below error in  above two applications


             "This Entry already exists in following tables (ODBC -2035)"


         Solution Required : What is the issue and how to resolve?.


Thanks & Regards,

Venki .A

+91 9585505514

         

         



            

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member264639
Participant
0 Kudos

Hi Experts, 

     We tried to find the problem through SQL Profiler for Issue no. 2 , "This Entry already exists in following tables (ODBC -2035)".  It shows following error line.

   "Violation of Primary Key constraint 'ocpr_primary'. cannot insert duplicate key in object 'dbo.ocpr".

( Please refer attached file)

   But, we are not inserting own number in (ocpr-CntctCode) contact person table. Number is coming from sap internal number system table.

  How to check  and resolve this issue.

Thanks & Regards,

Venki .A

  

    


former_member203816
Active Contributor
0 Kudos

Hi,

Please try to Restore numbering series fro Help menu & then try again.

Note : Please take back-up first before this activity else do in test database.

Thanks,

Tushar

former_member192773
Active Participant
0 Kudos

Hi,

use in your SBO atom "updateWithSubDeletion" as method.

Best Regards Teun

bastian_schaefer
Active Contributor
0 Kudos

Hi,

please check the following SAPNotes:

The "XCE208 resource is busy" error will be automatically handled by B1i error handling, the default is a message retry after ten seconds.

Please check the SAPNotes above to generally optimize the DI Proxy handling of the integration framework. Especially the attached documentation "HowToUseEnhancedDIAdapter.pdf" from SAPNote 1993784 about using the enhanced DI Adapter functionality.

Best regards

Bastian

P.S.: Please try to use the actual version of the integration framework (part of SAP B1 9.1 pl07).