-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RetrieveRecordChangeHistory: Error if history has very much entries #254
Comments
Thanks for the details, I'm just trying to reproduce it now. Might take me a while to create enough audit entries to get the error though! |
I'm now up to over 9,000 audit entries and it's still working fine. I wonder if there's something specific in one of the audit entries that's causing the problem rather than just the total number of them. Can you check in the log file ( |
Here is the log: |
I'm afraid you are right that it does not depend on the high number of entries. Sorry for sending you in the wrong direction. |
I've tested this on my instances and it still works with a Disassociate type audit entry. I can't reproduce the error so far but thanks to your stack trace details I can see where it's occurring so I can try to add in a potential fix in the next update anyway. |
@olaf-matthes Can you confirm if you can still reproduce this error with the latest version please? |
No, the error cannot be reproduced anymore. Thanks you
27.10.2022 10:25:24 Mark Carrington ***@***.***>:
… @olaf-matthes[https://github.com/olaf-matthes] Can you confirm if you can still reproduce this error with the latest version please?
—
Reply to this email directly, view it on GitHub[#254 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AXR43DCXOAKQEQLY4E4CRJ3WFI37FANCNFSM6AAAAAAQ4HZ66I].
You are receiving this because you were mentioned.[Verfolgungsbild][https://github.com/notifications/beacon/AXR43DC3HDHB5N5FWEO3V33WFI37FA5CNFSM6AAAAAAQ4HZ66KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSNCQ3EK.gif]
|
If I execute RetrieveRecordChangeHistory on an object having very much audit entries (>15.000), I just get the following error message:
"Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
See the Execution Plan tab for details of where this error occurred"
The text was updated successfully, but these errors were encountered: