Power BI Report Schedule Refresh Error

[Zubeyr]

In the report server database connection is successful but whenever doing schedule refresh its not connecting. throwing error like "an error occurred within the report server database. this may be due to a connection failure, timeout or low disk condition within the database. "

[hackcrr · Accepted solution]

Hi, @Zubeyr 

Check the performance metrics of the database server. Look for high CPU, memory utilization, or I/O wait times, which may indicate a performance bottleneck.
Make sure the database server has enough resources (CPU, memory, disk space) to handle the load.
Check the timeout settings in the Power BI Reporting Server and Database Server. If necessary, adjust these settings to ensure that operations have enough time to complete. If applicable, increase the CommandTimeout property in the data source connection string.
Test the database connection:

# Example PowerShell command to test SQL Server connection
$connectionString = "Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;"
$connection = New-Object System.Data.SqlClient.SqlConnection
$connection.ConnectionString = $connectionString
try {
    $connection.Open()
    Write-Host "Connection successful!"
} catch {
    Write-Host "Connection failed: $_"
} finally {
    $connection.Close()
}

Use SQL Server Management Studio (SSMS) to monitor database server performance. Execute queries to check disk space and performance metrics.

-- Check disk space
EXEC xp_fixeddrives;

-- Check CPU and memory usage
SELECT 
    sqlserver_start_time, 
    cpu_count, 
    physical_memory_kb 
FROM 
    sys.dm_os_sys_info;

Add a timeout setting in the data source connection string

Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;CommandTimeout=300;

hackcrr

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly

[v-yohua-msft · Accepted solution]

Hi, @Zubeyr 

As stated in the error message, this could be due to a connection failure, timeout, or insufficient disk in the database.

For troubleshooting, you can view the logs related to scheduled refreshes for Power BI reports
The log files that hold information about scheduled refreshes are RSPowerBI_ logs. They are located in the LogFiles folder of the location where the report server is installed:

C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_*.log

You can refer to the following link:

Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Learn

How to Get Your Question Answered Quickly

Best Regards

Yongkang Hua

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[hackcrr · Accepted solution]

Hi, @Zubeyr 

Check the performance metrics of the database server. Look for high CPU, memory utilization, or I/O wait times, which may indicate a performance bottleneck.
Make sure the database server has enough resources (CPU, memory, disk space) to handle the load.
Check the timeout settings in the Power BI Reporting Server and Database Server. If necessary, adjust these settings to ensure that operations have enough time to complete. If applicable, increase the CommandTimeout property in the data source connection string.
Test the database connection:

# Example PowerShell command to test SQL Server connection
$connectionString = "Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;"
$connection = New-Object System.Data.SqlClient.SqlConnection
$connection.ConnectionString = $connectionString
try {
    $connection.Open()
    Write-Host "Connection successful!"
} catch {
    Write-Host "Connection failed: $_"
} finally {
    $connection.Close()
}

Use SQL Server Management Studio (SSMS) to monitor database server performance. Execute queries to check disk space and performance metrics.

-- Check disk space
EXEC xp_fixeddrives;

-- Check CPU and memory usage
SELECT 
    sqlserver_start_time, 
    cpu_count, 
    physical_memory_kb 
FROM 
    sys.dm_os_sys_info;

Add a timeout setting in the data source connection string

Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;CommandTimeout=300;

hackcrr

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly