Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Report Server expired log file clean up

Dear Team,

 

I've expected an little issue when deleting expired log files especially msmdsrv.log.

Looks like msmdsrv.log is started and created when Report Server Service is started / restarted. During this process log-file is created with new timestamp. Within Report Server cleanup settings is configured that files older than 14 days shall be removed. When cleanup is started within RSHostingService is every minute reported that msmdsrv.log can't be delete because it's in use by ASEngine when it exceeds 14 days of restarting Report Server Service and re-writing / updating logfile.

Therefore all log files are stored by default within "C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles" I'd like to send you my findings, because it's default behaviour and my also affect other customer installations and fill up unnessary their "RSHostingService_XXXX" Log File.

 

If you need additional information don't hesitate to contact me.

 

Many thanks

Daniel

Status: New
Comments
v-qiuyu-msft
Community Support

Hi @Anonymous,

 

Would you clarify your findings? I'm not very clear about it now. 

 

You can send your findings via private message to me if it contains sensitive data. 

 

Best Regards,
Qiuyun Yu 

Anonymous
Not applicable

Dear Power BI Report Server team,

 

I'd like to add two pictures show which processes block log files and therefore these log files can't be cleaned up by cleanup process.

 

msmdsrv_Sperrt-Log-Files.PNGWmiPrvSE_Sperrt-Log-Files.PNG

 

As you can see, when system isn't restarted log files aren't updated and therefore there is no new timestamp of file and cleanup job will try to delete logs. But logs can't be cleaned up because log files are in use by processes e.g. msmdsrv.exe, wmiprvse.exe.

 

Many thanks,

Daniel

dhawal16
Advocate I

Hello Daniel,

 

Did you received any response on this?

We are observing the same issue, though it is not a big deal but wanted to understand the reason.

 

Thanks,

Dhawal

Anonymous
Not applicable

@dhawal16

 

Hello Dhawal,

 

until jet I haven't received any news about it yet. But I'm currently testing 2019-01 if issue is fixed at this version. I have expected that not all fixes are listed within the "fix report" within change log.

 

If I have any news on this topic I'll add information in this issue report.

 

Best regards

Daniel

dhawal16
Advocate I

Hello Daniel,

 

Thanks a lot for your quick response. We are also installing Jan-2019 version in this or next week. I will also try to test this and will let you know my findings.

 

Thanks,

Dhawal Mehta

Anonymous
Not applicable

Hello @v-qiuyu-msft ,

 

could you give me an update on this issue report, please?

It's still listed with status "new".

 

Many thanks

Daniel

Anonymous
Not applicable

Dear all,

 

issue is currently under investigation of Microsoft's Power BI Report Server Team.

If I get information when it will be fixed, I'll post information here.

 

Best regards

Daniel

Anonymous
Not applicable

Dear all,

 

sorry for delayed info. Issue should be fixed since last year 2020-10 Release.

 

Best regards

Daniel

ChrisMuthmann
Resolver I

Hi Daniel,

I can still see these messages:

2021-08-24 00:00:01.0527|WARN|153|Exception deleting expired log fileSystem.IO.IOException: The process cannot access the file 'C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at Microsoft.BIServer.HostingEnvironment.Logger.DeleteExpiredFilesInternal(Int32 keepUntilDays, FileInfo[] logFiles)

 

There are 8598 matches when searching for "Exception deleting expired log".

 

I'm using Power BI Report Server May 2021.

Kind regards,

Christoph

giwi
Frequent Visitor

Hi,

Is there any news about this error? It is still there in our environment.

Thanks and best regards

Wilfried