PBIRS config error at setup database

[qplc]

After install PBIRS and setup the config report . I got error at running database. The error said profile name is invalid. Not sure what to look for to fix this. Anyone know the solution. Thank you.

[v-saisrao-msft]

Hi @qplc,

If the issue is not resolved and you continue to experience the same problem, please submit a support ticket. Below is the link to raise the support ticket for further assistance.

Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Thank you.

[qplc]

All of the advice and still not solve the issue. I gave up. Thanks all.

[Nasif_Azam]

Hey  @qplc ,

The error “profile name is not valid” during PBIRS (Power BI Report Server) configuration typically indicates an issue with permissions or an invalid Database Mail profile reference in SQL Server. This usually happens when the PBIRS configuration wizard tries to run the database setup script but the service account doesn’t have the required permissions or the Database Mail profile is missing or misconfigured. Steps to Fix:

1) Verify SQL Server Connection: Open SQL Server Management Studio (SSMS) and connect using the same credentials you used in the PBIRS configuration. Ensure the SQL instance name and authentication type (Windows/SQL Auth) are correct.

2) Check PBIRS Service Account Permissions: In Report Server Configuration Manager → Service Account, note the account being used. That account must have the following roles on the SQL Server instance: dbcreator or securityadmin

3) Validate Database Mail Profile

• In SSMS, go to: Management → Database Mail → Manage Database Mail accounts and profiles

• Make sure the profile name exists, is active, and accessible.

• PBIRS might refer to an invalid or missing profile if the SQL instance has been copied or renamed.

4) Check for DDL triggers that send mail

-- Server-level triggers
SELECT name, isdisabled FROM sys.servertriggers;
SELECT t.name, sm.definition
FROM sys.servertriggers AS t
JOIN sys.serversqlmodules AS sm ON sm.objectid = t.objectid
WHERE sm.definition LIKE '%spsend_dbmail%';

Email alerts when new databases are created in SQL Server

5) Fix Database Mail profile or permissions

• Verify profiles: 

SELECT profileid, name FROM msdb.dbo.sysmailprofile;

• Grant access:

USE msdb;
EXEC spaddrolemember 'DatabaseMailUserRole', 'YourLogin';
EXEC msdb.dbo.sysmailaddprincipalprofilesp
     @profilename = 'YourMailProfile',
     @principalname = 'YourLogin',
     @is_default = 1;

Common errors with database mail

'profile name is not valid' error when executing the sp_send_dbmail command

6) Run Configuration as Administrator: Close PBIRS Configuration Manager and reopen it using Run as Administrator. Retry the Database Configuration step.

7) If the Database Already Exists: Choose “Existing Report Server Database” instead of creating a new one during setup. Then point to your existing ReportServer and ReportServerTempDB databases.

For Detailed Information:

Microsoft Learn: Configure a Report Server Database Connection (SSRS Configuration Manager)

Microsoft Learn: Power BI Report Server - Troubleshoot Configuration Issues

SQL Server Docs: Database Mail Configuration - Manage Database Mail Accounts and Profiles

Community Thread: PBIRS setup - “Profile name is not valid” fix 

Stack Overflow:  Fix “profile name is not valid”

Best Regards,
Nasif Azam

[Poojara_D12]

Hi @qplc 

This error typically occurs during Power BI Report Server (PBIRS) configuration when the Report Server database creation step tries to connect using a SQL profile / credential that SQL Server does not recognize. Although the message “profile name is invalid” looks unusual, it generally points to a problem with the SQL connection settings — such as using a SQL alias that isn’t configured correctly, a wrong SQL authentication mode, or missing permissions. When you configure PBIRS, the wizard attempts to run database creation scripts under the credentials you supplied, and if SQL Server cannot validate the login profile or resolve the connection, the script execution fails.

To fix this, first verify that you can connect manually to the SQL instance using the same credentials and server name (or alias) you entered in the PBIRS configuration tool. Make sure SQL Server Browser service is running and the SQL instance is reachable over the network if you’re pointing to a remote server. If you're using a SQL alias, confirm it exists in SQL Server Configuration Manager (both 32-bit and 64-bit alias entries may be required). Also confirm that the service account used by PBIRS has dbcreator / sysadmin rights during the setup phase because it needs to create the ReportServer and ReportServerTempDB databases. If SQL authentication is being used, ensure mixed-mode authentication is enabled in SQL Server. After validating connectivity and permissions, retry the configuration wizard. In most cases, correcting the SQL connection parameters or granting the proper roles resolves this issue and allows PBIRS to complete database configuration successfully.

[v-saisrao-msft]

Hi @qplc,

The issue might occur because the specified database name is already in use. Try changing the database name and run the configuration again.

please refer the below link:

Database Configuration | microsoft/ReportingServicesTools | DeepWiki

Thank you.