An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DSView'. (rsErrorOpeningConnection)
The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services. (rsOperationNotSupported)
Hi, I have encountered the above mentioned error while doing an SSRS project. And from the research, it seems like it is SQL server related issue.
I am trying to access a remote SQL server....so I was wondering how can I get rid of that error?
Do I have to install SQL server Standard edition on my local machine or the server that I am trying to access should be installed with Sql Standard edition?
I have got Express editions installed on both my local machine and the server...
Thx
From Books Online:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Features Supported by Reporting Services in SQL Server Express.
With SQL Server Express you can only use a Data Source where the database engine is from the same instance running SSRS.
If you need to connect to other instances your only options are to get a backup restored to your local instance or to install a SQL Server edition that allows remote Data Sources; most likely Developer for your own needs or Standard or above for any production instances.
It depends on what's allowed under your specific licencing agreement.
A neat way to get around this (that just worked for me) is to add a Linked Server on the Local machine to point to the server that hosts your remote data source.
Then modify your Dataset query in the SSRS report to look something like this...
select * from openquery(REMOTE_SERVER,'Put your original query here');
Related
I've inherited an SQL Server 2008 R2 environment running on Windows Server 2003. I do not know if it was upgraded from SQL Server 2005 or if it was a freshly built out system. Due to issues with not being able to virutalize the physical server, it was decided to build a new, identical environment on a virtual server an migrate the databases and such to the new virtual server. We did decide to make one upgrade and that was to put Windows Server 2012 on the new server. We kept the instance name and server name the same (these were modified after we took the old physical server offline). I kept the file paths and folder names the same as well on the new server. I migrated the SSIS packages from the old server to the new server using the Export option in Integration Services (right click on the package>Export Package). The packages were stored in MSDB on the old server. I copied the config files from the old server to the new server and kept them in the same file location as they were stored on the old server. Ok, so here's my problem. When I started all of the SQL Agent jobs, several of the ones that used SSIS packages failed. After researching the issue, I
discovered it was due to the SQL provider string (Provider=SQLNCLI) was set to Provider=SQLNCLI.1, which is for SQL Server 2005. Once I changed this to Provider=SQLNCLI10, all was good. A caveat to this is that other packages that are using Provider=SQLNCLI.1 and are working just fine. The question that is eating at me is this, why were these packages running successfully on the old server which was running the same version of SQL Server when SQLNCLI.1 is supposed to be a setting used in SQL 2005 AND why are some packages working successfully still using SQLNCLI.1 and other had to be changed??
the execute of some packages depends by the structure of this file.
the are some task or some expression or some parameters that have been redefined in the new releases.
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 an application written in MS ACCESS 2007 using VBA, connecting to an SQL Server at the back end. Both Access and SQL Server are running locally.
My machine runs Access 2010 and MS SQL Server Express 2008 R2 (both 32-bit, on WinXP) with no problem.
I have another machine, Win7 64-bit, running both Access 2010 and SQL Server 2008 (NOT R2) 64-bit.
When I run the Access application on the 64-bit machine, I have a drop down box to select the SQL Server which holds the various databases. When I select the server, after a few seconds I get an error:
Run-time error '-2147024703 (800700c1)':
Automation error %1 is not a valid Win32 application.
When I select the Debug option, the yellow arrow points to:
Set oServer = New SQLDMO.SQLServer
The next line is:
oServer.Connect ServerName, strSQLUser, strSQLPwd
In the watch list, I can see that ServerName, strSQLUser, and strSQLPwd hold the right values to access the SQL Server. I've tested these in sqlcmd and successfully was able to query tables.
Can anyone please help me out on this one? I'm not sure what to do next.
Seems like you've got registered a 32-bit SQLDMO on your system that is being used for connection to the 64-bit instance. Check your registry / file system for SQLDMO.dll versions and register the correct one.
Also check MSDN "Installing SQL-DMO" because SQLDMO was scheduled for remove after SQL Server 2008 R2:
Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
SQL Server Database Management Objects (SQL-DMO) has been removed from SQL Server 2008 R2 Express and the SQL Server 2008 R2 Feature Pack. SQL-DMO also does not support Database Engine features introduced after SQL Server 2000. We recommend that you modify applications that currently use this feature as soon as possible. If you must support SQL-DMO, install the Backward Compatibility Components from the SQL Server 2008 Feature Pack from the Microsoft Download Center. Do not use SQL-DMO in new development work; use SQL Server Management Objects (SMO) instead. You can obtain the SMO documentation by installing SQL Server 2008 R2 Books Online.
Thanks for this.
I looked to find SQLDMO.DLL 64-bit version, but although using the Backwards Comparability package for x64, installing using the MSI did not do the job.
I had to manually extract the files and place the correct version (which is ~2MB larger than the x86 version as an indication to knowing which one is the x64) and then run 'regsvr32 sqldmo.dll ' in the command line (very important: need to run cmd as Administrator for this to succeed).
After the module has been registered, my Access front end run great.
I have two virtual machines runs on my laptop, let's say their name are VMApp and VMDB, and both are runs the same OS, Windows Server 2008 R2.
On VMDB, I installed all SQL Server 2008 features except the Reporting Services. in contrast, I installed only SQL Server 2008 Reporting Services on VMApp.
I run Reporting Services Configuration Manager on VMApp and point the Server Name to the VMDB's computer name, then I got an error message
"A connection to the computer cannot be established"
I enabled the named pipe from SQL Server Configuration Tools on VMDB, but I still get that error message on VMApp.
I think the problem is not network connection because the VMs are connected in same domain network and they could ping each other.
Sorry for this dumb case because I am newbie in SQL Server, and I really appreciate any help from you guys!
Regards,
Chrisma Andhika
You cant set the DB path to SERVERNAME\INSTANCENAME on the configuration manager. There isnt even that option. First you set the server:
and then the DB:
where exactly are you having your issue?
FYI: try to enable SQL Browser on VMDB or to connect by IP if you cant enable browser
I have the following scenerio:-
1) Server 1 - SQL Server 2008 R2 Express - Collation SQL_Latin1_General_CS_As
2) Server 2 - SQL Server 2008 R2 Standard - Collation SQL_Latin1_General_CI_AS
I want to move the database from Server 1 to Server 2.
I tried backup and restore but does not work may be because of different collation. I also tried export but I'm getting some error. Please help me solving the issue.
The way is to use ssis (dts) wizards or, if the db is small - to do db export-import with data export option with help of data exporting embedded in management studio, and finally - try to do simple detach-attach of db
There is separate Database Publishing Wizard, available for download
Overview
SQL Server Database Publishing Wizard enables the deployment
of SQL Server databases into a hosted environment on either a SQL
Server 2000 or 2005 server. It generates a single SQL script file
which can be used to recreate a database (both schema and data) in a
shared hosting environment where the only connectivity to a server is
through a web-based control panel with a script execution window. If
supported by the hosting service provider, the Database Publishing
Wizard can also directly upload databases to servers located at the
shared hosting provider.
Optionally, SQL Server Database Publishing Wizard can integrate
directly into Visual Studio 2005 and/or Visual Web Developer 2005
allowing easy publishing of databases from within the development
environment.