you running the report in SERIALIZABLE transaction isolation level
look for TransactionType property of the report
If it is ::Update or ::Snapshot you can try to change it to ::UpdateNoLocks or ::Browse however in this case u may accidentaly read uncommited data.
If your report is modifying data then there is nothing you can do because UpdateNoLocks upon first modification automatically switches from READ UNCOMMITED to SERIALIZABLE transaction isolation level
well there are some options to reduce the frequency of the error.
If your report is modifying data you can try to split the logic of the report into smaller transactions (if logic allows it then use COMMITS inside the report)
Also you can try to increase the LockTimeout waiting time (hoping other sessions unlock the data you need).
My report does not contain any Locktable thats y i cant use the COMMIT.I have changed the property Transaction type of report from snapshot to update nolocks again same error is comming.
Try it locally first to see if it locks itself. If it isnt then make someone explaing in what sequence your report is modifying the tables. Generally you should lock in the same sequence as the posting CUs do.
Comments
look for TransactionType property of the report
If it is ::Update or ::Snapshot you can try to change it to ::UpdateNoLocks or ::Browse however in this case u may accidentaly read uncommited data.
If your report is modifying data then there is nothing you can do because UpdateNoLocks upon first modification automatically switches from READ UNCOMMITED to SERIALIZABLE transaction isolation level
If your report is modifying data you can try to split the logic of the report into smaller transactions (if logic allows it then use COMMITS inside the report)
Also you can try to increase the LockTimeout waiting time (hoping other sessions unlock the data you need).
Navision Technical Consultant
Navision Technical Consultant
Navision Technical Consultant