My Oracle Support Banner

Sarbanes-Oxley Solution: Error in CheckinUniversal WriteSystemFile Invalid procedure call or argument (Doc ID 445931.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Governance, Risk and Compliance Manager - Version 7.5.0 to 7.5.0 [Release Stellent]
Information in this document applies to any platform.


Why do I receive the following SOXException error when I attempt to Revise a released business process in a SSOS 7.5.x environment?

CheckinDocument Error in "CheckinUniversal" WriteSystemFile Invalid procedure call or argument in CMSDocument.Checkin: Login=TEST DocId=000004.  
at SoxDocMgmt.SoxDocument.a(String& A_0, DocType A_1, String A_2, String A_3) 
at SoxDocMgmt.SoxDocument.Save(String& DocId, DocType DocumentType, String Metadata, String Document) 
at SoxNav.BusProcCover.a(DocType A_0, String A_1)

I also receive this same SOXException when I attempt to put the business process into either the Data Collection or the Approval workflow. This issue is only occurring on a few of the released business processes. After receiving the SOXException, the business process is left checked out in the content server by the ShadowAdmin user.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.