You are viewing limited content. For full access, please sign in.

Question

Question

Changing audit Trail Data range from 30 days to 365 days

asked on September 1, 2016

Hi, 

Changing the date Range from 30 days to 365 days, will it fetch the other data older than 30 days? I can confirm there are audit logs for older data as well. I have made a backup of these files just in case. There are 2 repositories, this is for the second repository which is Redacted out. 

 

0 0

Answer

SELECTED ANSWER
replied on September 1, 2016

The problem seemed it was with Internet Explorer 🤗, it is sorted now.

0 0
replied on September 1, 2016

What was done to resolve it?

0 0

Replies

replied on September 1, 2016

Hi Gert,

 

Changing the date range should trigger Audit Trail to start loading the older logs that go back to the date range you specified. If this isn't happening I would go for an audit service re-start and see if that kick starts it. Also if possible make sure you are running the latest version of LF Server and Audit Trail (10.1).

 

Hope this helps! smileyyes

0 0
replied on September 1, 2016

Hi Chris, 

 

I am running 10.1 on both, i have given the Audit Trail service a restart and didn't do the trick :(

0 0
replied on September 1, 2016

Hmmm. I'm gussing you do have the logs available in the AUDIT folder in the repository location?

 

Might be best to raise a support case to troubleshoot this further, as digging any deeper might reveal confidential stuff you don't want to post on here wink

0 0
replied on September 1, 2016

I do have all the audit logs yes, i have made a backup of the logs as well. I will open up a support case and see what they say. Alternatively i have to setup the Audit Trail on the specified repository from Scratch. 

0 0
replied on September 1, 2016

Setting it up from scratch isn't too difficult. Might be worth giving that a shot yes

0 0
replied on September 1, 2016

Hi Chris, 

 

I am running 10.1 on both, i have given the Audit Trail service a restart and didn't do the trick :(

replied on September 1, 2016

Did you already try to create a new SQL db with the new range?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.