I just upgraded SSRS Express 2016 to SSRS Express 2017.
When configuring the service I can set the web service url and the Web Portal url.
When creating a new database I can use the wizard without any issue. Database credentials are ok, connection test are successful and so on.
However, when it is time to make the creation effective, the last step of the wizard, there is an error when "Generating database script".
Here are the details:
Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.
---> System.Runtime.InteropServices.COMException: The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)
at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.GenerateDatabaseScript(String databaseName, Int32 lcid, Boolean isSharePointIntegrated, String& script)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseScript(String databaseName, Int32 lcid, Boolean isSharePointIntegrated, String& script)
The only clue it gives it to make sure the service is running. I confirm the service is really running. What do I don't understand?
Thanks in advance for your help
I just had the same issue a few days ago. I solved it by adding local admin rights to the service account that I have, that runs the SSRS instance. I guess it needs more than normal user rights to start the WMIProvider.
Related
I've been trying to deploy an ASP.NET Boilerplate application to Azure for the last couple of days and I haven't been able to do so. I keep stumbling upon this error:
First I make a Web App + SQL resource and then publish my project to it from inside Visual Studio using the right click -> deploy option, and then importing the publication profile I got from Azure. I make sure the database connection string in the appsettings.production.json are correct but I can't seem to connect to the database. If I try to connect to the database through the SQL Server Management Studio I get a similar error. This means something is wrong with the database itself.
Do I need to create a separate SQL database in Azure that makes use of the SQL database server that comes with the Web App + MySQL resource?
Any help would be greatly appreciated! I have been spending way too much time on this problem already.
This is a screenshot of all the resources in the Azure portal, these were created while creating the Web app + MySQL resource:
Edit: This is the error I am getting:
Win32Exception: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Unknown location SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) Microsoft.Data.ProviderBase.DbConnectionPool.CheckPoolBlockingPeriod(Exception e) InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure()' to the 'UseSqlServer' call. Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute<TState, TResult>(TState state, Func<DbContext, TState, TResult> operation, Func<DbContext, TState, ExecutionResult<TResult>> verifySucceeded) Win32Exception: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Since you mentioned you can't access db in any other way, I provided step-by-step instruction
You can get your connection string from Azure resource panel
Navigate to Connection security tab and enable access from other Azure resources. This way WebApp will be able access database server inside Azure network. I also added my client IP to test db connection from my PC later. Click Save at the top when you are done
On the same page there is setting called configure SSL connection. Certificate can be downloaded from https://learn.microsoft.com/uk-ua/azure/mysql/howto-configure-ssl. I used this file https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem . Optionally, you could disable this feature for now.
Now we have everything to test db connection. I will show it with the use of HeidiSQL client.
Click open and see your databases
According to this you need to have CACertificateFile parameter appended to connection string to use SSL, so you need to put file into repository and provide its relative path in connection string
This was all caused by a stupid mistake, in the Azure portal I selected the Web App + MySQL resource instead of the Web App + SQL resource. For the ASP.NET Boilerplate project I am using you need a Web App + SQL resource.
I'm having a problem while deploying SSIS Package in Integration Services Catalog. It gives me error like this when I try to create a folder in SSISDB
"Operation 'Create' on object 'CatalogFolder[#Name=SSISTEST']' failed
during execution. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.5058.0+((SQL11_PCU_Main).140514-1820+)&LinkId=20476
------------------------------ ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The operation cannot be started by an account that uses SQL Server
Authentication. Start the operation with an account that uses Windows
Authentication. The operation cannot be started by an account that
uses SQL Server Authentication. Start the operation with an account
that uses Windows Authentication. (Microsoft SQL Server, Error:
27123)"
It seems like I cannot use SQL server authentication user for creating a catalog. When I was trying to Deploy the project through BIDS the same thing happens it's going to use windows authentication which is not valid in my case.
Is there any way I can use SQL server authentication for deployment purpose.
SQL Server Authentication is not supported for the Project Deployment model.
There is no hack, no workaround - a windows account must be authenticated to SQL Server and authorized to do the deploy.
I am trying to debug a stored Procedure from Microsoft SQL Server Management Studio 2008 which is connected to MS SQL Server 2008 Database Instance running on a different system.
System Information:
1. Remote system is running with Symantec End Point Security
I have done the following settings for running the remote debugger:
I have added the inbound Rules for TCP 139, TCP 445, UDP 137 and UDP 138 ports.
My local system's instance is running with sysadmin user role.
I have added the sqlservr.exe and svchost.exe at server windows firewall exception list.
I have added the svchost.exe and ssms.exe at client windows firewall exception list.
The SSMS and SQL server services are running in the same domain.
Following necessary services are running properly
TCP/IP NetBIOS Helper
Remote Registry
RPC Service
But after doing all these specified steps i am getting following error after clicking the debugger button in client SSMS.
Unable to start T-SQL Debugging. Could not attach to SQL Server process on 'remotesystem_name'. Click Help for more information.
If there is another alternative please let make me aware of that.
I solved this problem by creating a new login account (windows authentication account) on server for my machine.
I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.
I am getting an error when I try and upload a import an ssis project onto our server. The server only has integration and reporting services installed as the live sql server is on another server. I log onto the integration service fine but as soon as I try to right click the MSDB folder to import a package I get the error listed at the end of this question. I have added my local user account as an administrator on the server where the Integration Service is installed and I have added the administrators group to the security permissions for MsDtsServer in component services. Any help with this would be appreciated.
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
ADDITIONAL INFORMATION:
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
BUTTONS:
OK
I had this problem recently. It was a little tricky to figure out.
Here is a nice link from MSDN on how to hack, err, I mean fix it.
Configuring the Integration Services Service
"To manage packages that are stored in a named instance or a remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file." - MSDN
Thanks Microsoft??
To be more specific, you need to edit this file on your server:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml
Change:
<ServerName>.</ServerName>
to
<ServerName>ServerName\InstanceName</ServerName>
Save. and reboot.
Is your server set up to accept remote sql connections? Maybe check your firewall on the server to check that all the SSIS ports are allowed through, and also check in the SQL Surface Area Configuration tool to make sure all the services are set up to allow remote connections.