The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi !
I'm configuring the Report Server in the Configuration Manager.
I'm on the "Database" part. I click on "Change Database" then "Create a new report server database". I leave everything as it is :
I've seen several tutorials where they just leave it like that without changing anything and moving to the next step, but when I do it I get the following error :
I'm still fairly new to all of this so sorry if the answer is obvious but I'm kind of stuck...
Thank you very much in advance.
Solved! Go to Solution.
Hi @Antoine,
First, verify that the server name and username you typed in is correct. Make sure current user account has access to this SQL Server Database Engine. Please test whether you can connect to database engine in SSMS using current credential.
Based on my research, in most cases, the above error message occurs because the Database Engine instance that hosts the report server database is not configured for remote connections.
To resolve the issue, please follow the steps as suggested in this thread.
For more suggestion to troubleshoot this problem, please refer to:
An error has occurred while establishing a connection to the server.
Best regards,
Yuliana Gu
Hi @Antoine,
First, verify that the server name and username you typed in is correct. Make sure current user account has access to this SQL Server Database Engine. Please test whether you can connect to database engine in SSMS using current credential.
Based on my research, in most cases, the above error message occurs because the Database Engine instance that hosts the report server database is not configured for remote connections.
To resolve the issue, please follow the steps as suggested in this thread.
For more suggestion to troubleshoot this problem, please refer to:
An error has occurred while establishing a connection to the server.
Best regards,
Yuliana Gu
Hi Yuliana !
Thank you very much for your help 🙂 It was indeed a SQL Server problem, it's fixed now.
Kind regards
Antoine