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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
rohithkothaneth
Resolver I
Resolver I

Power BI Report Server application is not coming up after weekly reboot completes

Hello PBI Team,

 

We have been noticing that the Power BI Report Server application is not coming up after weekly reboot completes. We noticed this behaviour continouly for the 4th time.  Everytime time during weekly reboot of the windows server, apps goes down and once the reboot completes, app doesnt comes up by itself. We have to go in to the Reprot server configuration wizard and manually configure the account again.

 

Could anyone direct us on how we can fix this issue.

 

Error log details:

 

--msmdsrv log entry
(3/10/2019 3:00:04 AM) Message: Service stopped. (Source: \\?\C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\msmdsrv.log, Type: 1, Category: 289, Event ID: 0x41210001)

++++++++++++++++++++++++++++++++++++

--Reportservices log file entries

<Header>
<Product>Report Server Version 2018.0150.1102.235 ((BI_Server_Release).190130-0310)</Product>
<Locale>English (United States)</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft Power BI Report Server\PBIRS\Logfiles\ReportingServicesService_2019_03_10_00_01_58.log</Path>
<SystemName>O171-S021-WD01</SystemName>
<OSName>Microsoft Windows NT 6.2.9200</OSName>
<OSVersion>6.2.9200</OSVersion>
<ProcessID>8132</ProcessID>
<Virtualization>Hypervisor</Virtualization>
</Header>
<ProcessorArchitecture>AMD64</ProcessorArchitecture>
<ApplicationArchitecture>AMD64</ApplicationArchitecture>
library!WindowsService_11!29a8!03/10/2019-00:01:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!29a8!03/10/2019-00:01:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!29a8!03/10/2019-00:01:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!1694!03/10/2019-00:11:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!1694!03/10/2019-00:11:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!1694!03/10/2019-00:11:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!2760!03/10/2019-00:21:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!2760!03/10/2019-00:21:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!2760!03/10/2019-00:21:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!1b64!03/10/2019-00:31:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!1b64!03/10/2019-00:31:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!1b64!03/10/2019-00:31:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!1b64!03/10/2019-00:41:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!1b64!03/10/2019-00:41:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!1b64!03/10/2019-00:41:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!2760!03/10/2019-00:51:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!2760!03/10/2019-00:51:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!2760!03/10/2019-00:51:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!1b64!03/10/2019-01:01:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!1b64!03/10/2019-01:01:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!1b64!03/10/2019-01:01:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!bd8!03/10/2019-01:11:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!bd8!03/10/2019-01:11:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!bd8!03/10/2019-01:11:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!2f10!03/10/2019-01:21:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!2f10!03/10/2019-01:21:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!2f10!03/10/2019-01:21:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!bcc!03/10/2019-01:31:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!bcc!03/10/2019-01:31:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!bcc!03/10/2019-01:31:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!2760!03/10/2019-01:41:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!2760!03/10/2019-01:41:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!2760!03/10/2019-01:41:58:: i INFO: Call to CleanBatch() ends
library!WindowsService_11!1134!03/10/2019-01:51:58:: i INFO: Call to CleanBatch()
library!WindowsService_11!1134!03/10/2019-01:51:58:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions, 0 extended content cache.
library!WindowsService_11!1134!03/10/2019-01:51:58:: i INFO: Call to CleanBatch() ends
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Expiring old execution log entries
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Expiration of old execution log entries is complete. Removed 275 entries.
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Cleaned 0 broken snapshots, 0 chunks, there were 0 unsuccessful attempts
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Cleaned 0 parameters values
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Cleaned 0 unused segment mappings.
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Cleaned 0 unused segments.
library!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Using folder C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\RSTempFiles for temporary files.
dbcleanup!WindowsService_11!279c!03/10/2019-03:00:00:: i INFO: Completed cleaning 0 files
rshost!rshost!bd8!03/10/2019-03:00:03:: i INFO: Control-Shutdown event
rpcserver!DefaultDomain!4c!03/10/2019-03:00:03:: i INFO: Process monitoring stopped.
rpcserver!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: RPC Server stopped.
servicecontroller!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: ServiceAppDomainController - RPC Server stopped.
servicecontroller!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: InternalStop: stop the service code running in the worker domain
servicecontroller!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: InternalStop: found a worker domain
servicecontroller!WindowsService_11!bd8!03/10/2019-03:00:03:: i INFO: Service controller exiting.
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: UnloadAppDomain: 14, 'WindowsService_11'
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: Unregistering AppDomain id='14'
dbpolling!WindowsService_11!aa0!03/10/2019-03:00:03:: i INFO: EventPolling polling service stopped
dbpolling!WindowsService_11!aa0!03/10/2019-03:00:03:: i INFO: NotificationPolling polling service stopped
dbpolling!WindowsService_11!aa0!03/10/2019-03:00:03:: i INFO: SchedulePolling polling service stopped
dbpolling!WindowsService_11!aa0!03/10/2019-03:00:03:: i INFO: UpgradePolling polling service stopped
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: Unregistering AppDomain: searching for AppDomain id '14'
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: Appdomain:14 WindowsService_11 unregistered.
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: UnloadAppDomain WindowsService: 14, 'WindowsService_11'
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: SetUnloadStarted AppDomain id '14': unloadStarted = 1
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: Appdomain:14 WindowsService_11 unloading.
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: AsyncDomainUnloading::Start - waiting for the unloading thread to finish unloading AppDomain '14'; Mark the WindowsService (worker) AppDomain as active.
appdomainmanager!DefaultDomain!bd8!03/10/2019-03:00:03:: i INFO: ReportService::MarkProcessAsActive - Mark the WindowsService (worker) AppDomain as active.
appdomainmanager!DefaultDomain!ac4!03/10/2019-03:00:03:: i INFO: AppDomain:14 0 pending unload(s)
appdomainmanager!DefaultDomain!ac4!03/10/2019-03:00:03:: i INFO: AppDomain: calling AppDomain.Unload(AppDomain 14)
appdomainmanager!DefaultDomain!1b20!03/10/2019-03:00:03:: i INFO: Unregistering AppDomain id='14'
appdomainmanager!DefaultDomain!1b20!03/10/2019-03:00:03:: i INFO: Unregistering AppDomain: searching for AppDomain id '14'
appdomainmanager!DefaultDomain!1b20!03/10/2019-03:00:03:: i INFO: Appdomain:14 was not registered. Its registration was probably already replaced with a new AppDomain (since this one is getting recycled).
rshost!rshost!1b20!03/10/2019-03:00:03:: i INFO: Application domain type WindowsService statistics: created: 12, unloaded: 12, failed: 0, timed out: 0.
servicecontroller!DefaultDomain!bd8!03/10/2019-03:00:04:: i INFO: Service shutting down.

++++++++++++++++++++++++++++++++++++++++++++++++++++

--RShostingservices log file entries

2019-03-10 01:47:07.1736|INFO|21|Deleting expired log file: C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_2019_02_24_00_02_02.log Last written: 2/24/2019 1:47:02 AM
2019-03-10 03:00:03.9957|INFO|1|Logger shutting down
2019-03-10 03:00:04.0847|WARN|34|Child Process [AS] Died. Check the log for further information
2019-03-10 03:00:04.0847|WARN|59|Child Process [RS Service] Died. Check the log for further information
2019-03-10 03:00:04.0917|INFO|34|Immediate restart of process AS

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

1 ACCEPTED SOLUTION
rohithkothaneth
Resolver I
Resolver I

Fixed this issue after adding the service account to the local administartor within the windows server.

 

Thanks,

Rohith

View solution in original post

1 REPLY 1
rohithkothaneth
Resolver I
Resolver I

Fixed this issue after adding the service account to the local administartor within the windows server.

 

Thanks,

Rohith

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.