Error in external report?

Question

1C

There is an external report that behaves in an incomprehensible way.
For some users, it can freeze for a whole day and eventually display a whole bunch of duplicates, for others it works fine. The same report is launched in the same database. In this case, the error occurs with one specific counterparty, when the report is built for another counterparty, then it works fine.
The report has already been uploaded to the database, the cache has been cleared, it has been launched on another test database, the same thing: for some it works, for others it doesn’t.
Where to look for an error? On the database server, in the database itself, or is it still in the report?

Answer 1

- Access rights to database objects for users who form it.
- How are Rls configured in the database.
Well, the report itself, its formation logic.

Answer 2

The situation is incomprehensible and therefore you need to go sequentially:
1) Clear the server cache and restart the 1C server service
2) Clear the local cache
3) Start re-indexing tables.
If the situation continues to be reproduced:
1) Check the rights of users and the presence of a radar in them
2) Write a processing that makes information selections using the Request object.
If everything is transparent with the rights, and there are no duplicates in the Request, then there are problems in the external report. Perhaps some glitches in the layout scheme or user settings that will disappear if everything is redone from scratch.