error in latest version #63
Comments
|
Hi @vvhor, Have you successfully used the older version(s) with the same app registration before, or are you trying for the first time? If it's the first time you could check if the API permissions are properly set, and if auditing is enabled for the tenant (this might take a while to sync after enabling it). Both these actions are described in README.md. If it was already working before then we'll have to figure where it's coming from. I'm currently working on a new release with improved logging, so once that's out in the coming days I will link it here. Then hopefully we can see more with the increased logs. |
|
Hi, I've used it in previous version on other tenant. I've followed all of the steps in the READEME some days ago |
did you have an estimation for this release? |
|
I have released the new version with fixed logging and also extended logging, hopefully we'll be able to capture the error: https://github.com/ddbnl/office365-audit-log-collector/releases/tag/v2.3.1 Make sure to also enable logging in the config: If you get it working consider disabling debug again, it's very noisy. Let me know what it does for you. |
|
Hi, many thanks. Now the log is very helpful. I'll do some test and let you know |
|
As a heads up, there's a new release that added an interactice interface that can be used for testing. If you have the new release, you can run the command as you did before, but add the '--interactive' command line parameter. This allows you to test the connection and immediately see the logs for any errors. https://github.com/ddbnl/office365-audit-log-collector/releases/tag/v2.3.2
|
|
Hello, I'm now having different errors in "Run Collector": Non error in "Test API Connection" |
|
That's odd, so far I'm not able to reproduce. Best we can do is improve logging. I've added the full output of the JSON response as a debug log, in the section where you are receiving the error. This should give us the full response you are getting from the API. Can you run it again with the latest release, and enabling debug logging? Also, just to ensure you are not being rate limited, could you use a publisher ID? For the ID you can just use your tenant ID again. This will isolate your requests to avoid rate limiting as much as possible. You can the executable like before, but adding "--publisher-id %tenant-id%" https://github.com/ddbnl/office365-audit-log-collector/releases/tag/v2.3.3 |
|
PS. The new version not write the log in interactive mode. in attach the full log |
|
Hi, just to ask if you have any news about the errors.. |
|
can I do any other test to help you? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I'm trying the latest version but I got this error
the request is:
./OfficeAuditLogCollector.exe --tenant-id "xxxxxxx" --client-id "xxxxx" --secret-key "xxxxx" --config config.yamlconfig file:
I'm using the client on window system
The text was updated successfully, but these errors were encountered: