Question

Why do I get an error due to system privilege configuration?

  • 1 August 2022
  • 7 replies
  • 265 views

Userlevel 5
Badge +14

We have errors during the execution of background jobs for the document management.

 

 

Where it states that it failed to save due to the following error: Access denied due to system privilege configuration

 

Restarting it is working fine in Enterprise Explorer

 

We got some strange timeslot where it seems the system did not progress anything on the http_server. Marked in red

 

 

Error coming from
yvdms_ext_archive_util_api

IF (NVL(result_, 'FALSE') <> 'TRUE') THEN
               Error_SYS.Record_General(lu_name_, 'ERREXAM: The following error occured: :P1', message_);

The message is generated in 
            Save_Document (
               result_,
               message_,
               doc_id_,
               doc_path_,
               doc_class_,
               doc_no_, 
               doc_sheet_, 
               doc_rev_, 
               doc_type_, 
               file_no_, 
               file_name_, 
               schema_,
               archive_,
               Edm_File_API.Get_Checked_In_Sign(doc_class_, doc_no_, doc_sheet_, doc_rev_, 'ORIGINAL'),
               attr_ );

Triggers
  IF (Yvdms_Archive_API.Get_Auth_Write_Db(archive_id_) IN ('LOGIN', 'LOGOFF')) THEN
         Invoke_BizAPI( 
            result_,
            message_,
            user_, 
            password_, 
            login_token_, 
            doc_id_,
            doc_path_,
            doc_class_,
            doc_no_,
            doc_sheet_,
            doc_rev_,
            doc_type_,
            file_no_,
            file_name_,
            schema_,
            archive_id_,
            NULL, -- attr_
            reference1_, 
            reference2_, 
            reference3_,
            doc_user_,
            Yvdms_Archive_Action_API.DB_LOGIN );

Plsqlap_Server_API.Invoke_Outbound_Request_BizAPI(
            bizapi_name_  => BIZAPI_NAME,
            message_body_ => task_,
            sender_       => NVL(archive_id_, Fnd_Session_API.Get_App_Owner),
            receiver_     => 'CONNECT');

The message is generated via
      response_      := Plsqlap_Record_API.Get_Element(task_, 'MESSAGE_BODY', 1);   
      message_  := Plsqlap_Record_API.Get_Value(response_, 'MESSAGE');

Which leads to PLSQLAP_RECORD_API issues
 

But I am not able to track down why it is most of the times working and then failing some times.

Any ideas about that?


Kind regards

TT


7 replies

Userlevel 6
Badge +18

What form of repository are you using?  FTP, Shared folder or DB storage?

I’m wondering if there is a problem that prevents the connection (e.g. FTP) during that time, or if the DB is being put into a particular state for some maintenance item that prevents the connection (e.g. DB storage)

Nick

Userlevel 5
Badge +14

Hi @NickPorter 

Thanks for your response. Not sure about the repository though.

Where can I check this?

 

There had been no maintenance for nine minutes on the system. That, I can guarantee.

Kind regards
TT

Userlevel 5
Badge +14

I checked on the archive id and I can only see a server and a port.

 

Customer is using D3 for archiving documents.

 

Userlevel 6
Badge +18

One easy way to double check is to look at the Change Document Repository wizard under Doc Man / Basic Data.  In the first screen of the wizard, if you select the repository in question it will show you what type it is using currently (e.g. FTP).  Obviously cancel the wizard without proceeding.

Without any more info my best guess to start looking at things is to ensure that IFS doesn’t lose access or connection to that target location for some reason, e.g. network or server maintenance, or even some kind of scan that runs which impacts the connectivity.

HTH,

Nick

Userlevel 5
Badge +14

Investigation is going on via IFS Case G2343346

Userlevel 4
Badge +9

@Technical Toby Do you have any news about the case? I have the same issue. 

 

Userlevel 5
Badge +14

Hi @K4uLinalM 

By now, there is no solution to this topic in the case. It is going back and forth between Support and the customer.

The only thing the customer is doing by now, after one hour of not working, they restart the jobs and everything turns out fine.

 

Will keep you posted.

Regards

TT

Reply