I'm trying to install the SSRS data connector for my CRM4 implementation.
I'm using the Method 2: Modify the Install-config.xml file from this page. But keep getting the same error message:
Unable to validate SQL Server Reporting Services Report Server
installation. Please check that it is correctly installed on the local
machine.
I've added the following to my XML file.
<reportserverurl>http://SSRS-Server/Reportserver$MYORG_MSCRM</reportserverurl>
<instancename>MYORG_MSCRM</instancename>
Anyone know what is still wrong?
I tried several instance names but they all don't work either.
I can access my SSRS server by going to http://SSRS-Server/Reports and it will give a list of all services running there.
Any help would be much appreciated.
You may need to post more details regarding this issue:
1) The 2nd method described in this link : here is used when the Reporting Server database is installed using the SQL Server named instance. Are you installing the Reporting Server database in the default instance or named instance ?
2) If you are using default instance, you might not need to use custom XML, you can just run the installer without requiring the input XML file.
3) What is the architecture of your CRM implementation ? is the CRM Application, SQL server and Reporting Server resided in the same server ? or different server ?
Hope this helps.
I realise this is a really old article however I wanted to post the resolution I found to work as I have spent the past 3 days trying to resolve this issue! I created an account just to post this.
I was having the same problem as the original article. I had SSRS 2008 installed on a server, CRM (4.0!!!) on a different server and SQL 2008 on a different server again. When all permission issues were resolved and ports were opened from the SSRS server to the SQL server, I was still having problems getting the SetupSrsDataConnector.exe to see the locally installed instance of SSRS2008 (Not R2).
I found the resolution to the issue in this article:
https://community.dynamics.com/crm/b/pabloperalta/archive/2011/07/12/unable-to-validate-sql-server-reporting-services-report-server-installation-error-while-installing-srs-data-connector
Effectively the problem I was having is that my copy of the SRS Connector installation files were old and needed updating, however my server did not have internet connectivity. In the link above, it gives you a download location to get a .mps file which contains the updates for the SRS Connector.
You need to download this .mps file and then run the installation via command prompt with a customised install-config.xml file, which specifies the SSRS ReportServer URL and the SSRS Instance Name in a custom tag (what you named the SSRS instance when you installed it) and another custom tag for <Patch update="true">C:\Path to the .msp file< /Patch>
This was my installation command:
"D:\Stage\SRSDataConnector\SetupSrsDataConnector.exe" /CONFIG "D:\Stage\SRSDataConnectorUpdates\install-config.xml"
Related
I installed SSRS on my computer with the file SSDTBI_x86_ENU.exe. I started to create a report server project which contain tow .rdl file. Now I want to deploy it so I can see my reports in the browser. When I click the start button Visual studio give me an error and say that I have to specify a valid URL. So I went to reporting services configuration manager. My problem is when I enter my server name it says invalid namespace!!
Despite taking -2 for this question, I will answer it because I resolve it and hope that will help somebody someday. It is a problem connected to the version of SQL server express with tools. It didn't allow the deployement of rapports. So I uninstall it and install sql server express with advanced services and every thing magically worked.
I am creating my first SSIS package using Business Intelligence in Visual Studio 2012. I am adding the contents of an Excel sheet to an local VS database. In the Destination Assistant I am asked Destination Type = SQL Server, New: Provider - I see no .NET Framework option. The result seems to be that I am then unable to select my server and therefore databases.
Am I just missing the point?
I would recommend that you investigate the destination server and verify that you have the providers installed on that system. Typically these are installed at the time that SQL server is installed, but is possible via custom installation to specify the providers that are installed. It may be necessary for you to install any providers needed. A second option would be to point to a database that you know that you can connect to, say a localhost sandbox or other tried database. That would help you to determine if it's server side or client installation issues.
I have difficulties connecting to my MS SQL Server and I can't find tutorial or answer how to do this, even though I think this should be something pretty standard.
My current setup is this - I have freshly new Installed Visual Studio 2010 and followed Beth Massi's article Step-by-Step: Installing SQL Server Management Studio 2008 Express after Visual Studio 2010 : http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server-management-studio-2008-express-after-visual-studio-2010.aspx
But I'm not able to connect to a SQL Server. In my Configuration Tools\SQL Server Configuration Manager I see this when I open it :
I set to Enable all TCP\IP and Named Pipes (Just saw that this may be a problem) and in the properties of the SQL Server (SQLEXPRESS) from Services I see this:
I also see in the Log On tab this :
some sort of password (not entered by me) it seems to be something default, but since I'm not sure where the problem is I try to show everything I think may have something to do with solving my problem.
At the end I tried different options to connect to my SQL Server form the Management Studio I ended up with this:
As you see I get an error (included in order to be able to read it). I read the the machine name may be required so my User Account name is Xman and my machine's name is Xman-PC. Eveh though my printscreen image is not from this try I made an attempt to connect to the Server with XMAN-PC\SQLEXPRESS but again - no success.\
Could you point me to a good tutorial on how to connect to a MS SQL Server (I can't believe there's nothing that explains in simple steps what you need to do to connect to a server) or could you tell me how to set-up my configurations so I actually can start to work with databases?
P.S
Forgot to mention in Command Prompyt - sqlcmd command also returns error - Could not open SQL connection.
P.S
Finally I managed to connect using Windows Authentication and (local)\sqlexpress for ServerName. Which at least means that everything is working. But now even more I would like to know how to connect using SQL Server Authentication. It must be something default as it was for Windows Authentication?!
Looks like you've done the hard work - last step will be turning on SQL Server Authentication.
Since you installed with the default values, only Windows Authentication is allowed; you need to set it to SQL Server and Windows Authentication mode. You can do this through Management Studio through the instance Properties -> Security.
See this link for full details: Change Server Authentication Mode.
I just installed SQL Server Management Studio, and I'm trying to add just a basic login. (I'm fairly new to SSMS).
I've connected to local server, and I right-click on Security > Logins > New Login..., and then I get a dialog that says this:
Cannot show requested dialog. (SqlMgmt)
Cannot read property Collation.This property is not available on SQL Server 7.0. (Microsoft.SqlServer.Smo)
So there is the issue I'm coming up with. I'm sure its probably an easy fix, but I can't seem to figure it out. Thanks guys!
In Management Studio, your connection should be to one of the following:
localhost\SQLEXPRESS
(local)\SQLEXPRESS
.\SQLEXPRESS
YOUR_MACHINE_NAME\SQLEXPRESS
And you should probably consider uninstalling that SQL Server 7.0 instance.
Attempting to cache my SSRS reports as referenced in
http://blogs.technet.com/b/rob/archive/2010/02/11/caching-ssrs-reports-for-performance.aspx
...I am to understand I need to set the processing options:
http://msdn.microsoft.com/en-us/library/ms178821.aspx
...which seems to dictate there should be a dropdown here:
However, notice I hover over and nothing happens.
Could this be related to my previous installation SQL Express 2008 R2 with Advanced Services somehow failing to fully upgrade all the user options back when I upgraded to SQL Server Enterprise? I understand Express does not have the ability to cache reports per the documentation - but I am using Enterprise now.
Or am I just looking in the wrong place?
Basically, the SSRS Report Server page (See above Image), is still the crippled Express version - so the upgrade must have failed on that part. I tried backing up the instance, fully uninstalling SQL Server and all it's components, and re-installed from scratch. Still no love. What is going on?
I had something similar. I believe I solved it by setting up the SSRS web under IIS? It's an option during the SSRS setup.
It gave me more control over the website configuration and I was able to manually remove it before re-installation.
Answered: Even if you "Uninstall" SSRS from the Control Panel > Uninstall a Program, you must also do the following:
Manually remove/backup the databases ReportServer and ReportServerTempDB from the SQL Server. If we already had some reports deployed to Reporting Services, we would do a backup of the databases and reconnect after the new installation. If we want to set a clean Reporting Services without reports, we can just remove them using Management Studio.
Manually remove the virtual folders Reports and ReportServer from IIS (This is only for RS 2005. As you may know, RS 2008 doesn’t use IIS)
Manually remove the folder of the instance of Reporting Services (For example for RS 2008 would be something like C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER). This folder is not removed automatically and, if we don’t remove it manually, the configuration files will contain information about the old configuration and we might conserve old problem if they existed.