Could it be LogOnExpireMinutes vs LogonExpireMinutes ?

That is strange. I had the same issue coming from 12.2.1.2 and this patch solved it. Eventually it was a JavaScript issue.

please install patch 28043947. I had the same issue after upgrading OBIEE.

You can also enable the tracking of initblocks in Usage tracking table s_nq_initblock. See Welcome to OBIEE12c - Set-up Usage Tracking – Part 1 - Red Stack Tech for an example.

I don't see any issues with the command. Used the same on 12.2.1.4 environment and uploaded successfully. Did you try remote from Windows machine to see if other logging is created?

Downgrade the RPD? That is not something you want..

Which command are you using for uploading your RPD?

You are sure the username and password provided in the -U and -P parameter are correct? Can you login to EM/Console with these?

You have seen this error in your log? [nQSError: 43126] Authentication failed: invalid user/password.

We experienced the same again. Happened between 22:05 and 23:20 CET. Our SR is still under investigation.

I already installed patch 27019889 on all our environments, but this didn't work. It stopped last week. SR is re-opened again.

Seen bug 27921011 on MOS? Although this is export and you are using import -> seems a bit similar.

i don't believe so. But with logging of initblocks enable you can also cover this.

Why not use Usage Tracking to see if a user executed reports? No customization needed and will provide insights. Only issue is that if the user never logged in, it will not be returned and you need an extra lookup to compare with your user base.

Well: the limit is not in Oracle-BI, but in EXCEL and how it opens CSV files. You can change this by including a ' in the column to prevent Excel from doing this. Otherwise do a manual import in Excel.

Do you have any filtering in the analysis pointing towards the logged-in user? Otherwise check you RPD for security enabled.

Do you also have the weblogic SQL generated? What is the user filter doing in above SQL? what is the filter on T6929.M_ID = '17D06OB02K01' doing?

Did you check the SQL generated when logged in with a normal user? Any security enabled?

Great to hear it now works Adam! Thanks for sharing the fix. Michael

Is your eBS session still active? Seems the eBS session timed-out already.