Thread Details
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 365 subscribers
  • Views 2928 views
  • Users 0 members are here
Forum Actions

Error when I save a record

Stefano Mapelli

Hi,

I'm working with Sugarcrm 7.6 pro and I have a big problem when I save a record with the regular user but not with the Admin user.

When I try to save an Account or a Contact record, sugar stops me with this error " There was an error while connecting to the server. Please try again.":

I try to do the same thing with my admin user and there's no problems.

I try to take a look to the log files and this is the report:

php_error.log   :   no error

apache_error.log   :   no error

sugarcrm.log   :   

09/02/16 09:18:47 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 424: ERROR_DNB_CONFIG)Your request failed to complete.
09/02/16 09:18:48 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 424: ERROR_DNB_CONFIG)Your request failed to complete.
09/02/16 09:18:50 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 424: ERROR_DNB_CONFIG)Your request failed to complete.
09/02/16 09:18:51 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 424: ERROR_DNB_CONFIG)Your request failed to complete.
09/02/16 09:18:52 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 424: ERROR_DNB_CONFIG)Your request failed to complete.
09/02/16 09:18:54 [13760][29394d50-6289-df31-993a-57c820dd03b0][ERROR] An exception happened: ( 403: not_authorized)Not allowed to perform action "save" on this record

browser console   :   

sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:29

POST http://localhost/sugarcrm/rest/v10/Accounts?viewed=1 403 (Forbidden)send @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:29ajax @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:29execute @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:38call @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:38records @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:38sync @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:41save @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:36save @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:40saveModel @ components_8a4e432….js:5405createRecordWaterfall @ components_8a4e432….js:5403r @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:37(anonymous function) @ sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:37
sidecar.min.js?v=M6nv9q_bdTkCucHQgJQzng:40

ERROR[2016-9-2 9:30:54]: Not allowed to perform action "save" on this record

Please help me

Best regards

Stefano

  • 0 Sugar Employee Badge

    Hi Stefano,

    It seems like this user does not have access to read/write. This can be due to role or team. 

    Double check that the user has correct Team who can read/write. 

    Best Regards
    Tevfik Tümer
    Developer Support Engineer

  • 0

    The problem is solved with a relationships rebuild.

    Thanks for the help

    Stefano

  • 0 in reply to Stefano Mapelli

    Hi, Stefano.  I am curious to see if this issue has occurred again for you?  We have been having the same exact issue for the past several months.  In fact, there have been several other forum posts on this, specifically with 7.6.

    Not sure if you investigated further, but regular users receive the error but the record is, in fact created.  Each time they hit the Save button to, "retry", a duplicate record is created but with a different ID number and they still see the error message.  

    In our system, all users have the default team set to Global, however when these records are saved the team field is empty.  That is why admins don't receive the error, and can also see the record.

    Doing a relationships rebuild does not always fix the issue for us.  Can you offer any other insight?

  • 0 in reply to Angelo Bovino

    Hi Angelo,

    I had your same issue two or three times during my implementation but I couldn't find a simple standard resolution.

    I try with different random rebuild and repair and cache deletion.

    Sorry but I can't further help you.

    Good luck

    Stefano

  • 0 in reply to Stefano Mapelli

    This just happened to me as well.  After an hour and half of debugging, rebuilding roles as well as rebuilding teams, then running Quick Repair and Rebuild solved the issue.  Sugar 7.6 Enterprise.