Please forgive me as my head is spinning. I have tried so many solutions to this issue, that I'm almost not sure where I am at this point.
At this point in time I have these issues in my Production, Test, and Dev environments. For simplicity sake, I will just try to get it working in Dev first. Here is my setup:
Database/Reporting Server (Same server):
Windows Server 2003 SP2
SQL Server 2005 SP3
Development Box:
Windows 7
Visual Studio 2008 SP1
SQL Server 2008 SP1 (not being used in this case, but wanted to include it in case it is relative)
Internet Explorer 8
Details:
* I have a custom ASP.NET application that is using ReportViewer to access reports on my Database/Reporting Server.
* I am able to connect directly to Report Manager and print with no trouble.
* When I view source on the page with ReportViewer, it says I'm am using version 9.0.30729.4402 .
* The classid of the rsclientprint.dll that keeps getting installed to my c:\windows\downloaded program files directory is {41861299-EAB2-4DCC-986C-802AE12AC499}.
* I have tried taking the rsclientprint.cab file from my Database/Reporting Server and installing it directly to my Development Box and had no success. I made sure to unregister the previously installed dll first.
I feel like I have read as many solutions as I can, and so I turn to you for some assistance. Please let me know if I can provide further details that would be helpful.
Thanks
I am cross posting the solution I received on MSDN. I hope it helps someone else.
Hi mamorgan1,
From your description, I notice you
are using Report Viewer with version
9.0.30729.4402, and SQL Server Reporting Serivces 2005 with SP3.
RS Client Print control is an ActiveX
control which uses a ClassID to check
if the ActiveX is installed on the
client. By default, the ClassID for
SQL Server Reporting Services SP3 is
41861299-EAB2-4DCC-986C-802AE12AC499.
However, Report Viewer 9.0.30729.4402
would like the ClassID
0D221D00-A6ED-477C-8A91-41F3B660A832.
RSClientPrint control has been updated
after applying Cumulative Update #8
for SQL Server 2005 Service Pack 3.
So, please apply Cumulative Update #8
for SQL Server 2005 Service Pack 3 to
solve the issue.
For more information about Cumulative
Update #8 for SQL Server 2005 Service
Pack 3, please see:
http://support.microsoft.com/kb/978915/en-us
If you have any more questions, please
feel free to ask.
Thanks, Jin ChenJin Chen - MSFT
Related
I need to setup a report server using SQL Server Reporting Services with MySQL datasource. I am using a ODBC connection to connect MySQL. Using this connection I am able to add a dataset in my reporting project in Visual Studio 2015.
Using this dataset I can create a reports in Visual Studio and it show me preview as well using my table from MySQL, So far so good only problem arise when I try to deploy my reports to my local machine it show following error :
An attempt has been made to use a data extension 'ODBC' that is either not registered for this report server or is not supported in this edition of Reporting Services.
I am using SQL Server 2012 Express Edition and I follow this tutorial to connect report with MySql.
https://www.mssqltips.com/sqlservertip/2615/creating-a-ssrs-report-using-a-mysql-data-source/
Can you please help me to know what I am doing wrong here? Any help will be highly appreciated. Please let me know if any other information needed.
Thank you
I do not think this is supported in express dev version.
http://www.c-sharpcorner.com/UploadFile/ff2f08/feature-supported-and-unsupported-by-ssrs-with-express-advan/
If you have the full version, it can be easily done, via the instructions you linked above.
I'm having an issue with the soft render of a simple report in both SSDT and Report Builder environments in 2016. I'm sure there is a sample solution but I'm unable to find a solution on the web/forum.
I'm actually just using a simple tablix from AdventureworksDW2016CTP3 with a couple of fields inserted. The data might initially display but disappears after modifying the field length or switching between design and preview. More interestingly, the report views perfectly when utilising print preview and it exports to .pdf correctly... and also views correctly when deployed to the report server.
All is installed locally on my laptop with Windows 10 and Administrator privileges. I have repaired and upgraded Visual Studio and SSDT to the latest version but without any luck.
I've added images of the simple design, soft render and print preview as well as Visual Studio System Info at the bottom.
Thanks
Visual Studio Info
Microsoft Visual Studio 2015 Shell (Integrated) Version 14.0.25420.01 Update 3
Microsoft .NET Framework Version 4.6.01586
SQL Server Analysis Services 13.0.1701.8
Microsoft SQL Server Analysis Services Designer Version 13.0.1701.8
SQL Server Data Tools 14.0.61021.0
Microsoft SQL Server Data Tools
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer Version 13.0.1601.5
SQL Server Reporting Services 13.0.1701.8
Microsoft SQL Server Reporting Services Designers Version 13.0.1701.8
Images
Design Images
Soft Render / HTML
Print Render
After much testing it appears that the problem came down to my graphics driver - Intel HD Graphics 5500.
The problem still occurred after I updated the driver so I then disabled it... which solved the problem. I then reinstalled the driver and all is now working as expected.
This link gave me the initial indication of the issue:
https://support.microsoft.com/en-us/help/2894215/you-experience-performance-issues,-product-crashes,-or-rendering-issues-in-visual-studio-2015-and-visual-studio-2013
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.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Below is a list of the SQL components that I installed in the Visual Studio 2010 Professional setup. Sadly, while trying to work I could not find SQL Server Management Studio 2008.
Is there a way to download SQL Server Management Studio 2008 separately and install only that component?
Since in the past I installed SQL Server Management Studio 2005 with a whole new instance of SQL Server 2005 and had couple of instances, and it was a bit messy.
I found some articles to be of major use:
This link is an experience someone else had:
http://goneale.com/2009/05/24/cant-install-microsoft-sql-server-2008-management-studio-express/
This link has the exact steps involved to install everything properly:
http://www.codefrenzy.net/2011/06/03/how-to-install-sql-server-2008-management-studio/
This link confirms the previous link:
https://superuser.com/questions/88244/installing-sql-server-management-studio-when-vs2010-beta-2-is-already-installed
My Instructions
I am not sure if my instructions will be 100% accurate, but in my instance, because I installed VS2010 on a fresh copy of Windows 7, the VS2010 installer installs SQL Server 2008 Express for you, so from this point I just need the Management Studio.
What I gathered from these explanations is to do the following:
Download the SQL Server Management Studio install from
http://www.microsoft.com/download/en/details.aspx?id=22973
Run the setup, when you get to the point where it asks you to "Perform a new installation of SQL Server 2008" or "Add features to an existing instance of SQL Server 2008", this part is the CONFUSING PART (HEY MICROSOFT TAKE NOTES, DON'T DO THIS KIND OF STUFF).
As much as you want to select "Add features to an existing instance of SQL Server 2008" DON'T!!!!
You need to select "Perform a new installation of SQL Server 2008". It doesn't sound right I know - it is very confusing and counter intuitive, but this seems to be the way to install management studio. :(
Press next until you see the features selection portion. Heeeeeyyyy look at that, it has a check box for Management Studio. It should be selected already, if not then select it of course and press next.
Press Next next next next next next... basically just install it at this point.
Enjoy, it has installed.
If you have the SQL Server 2008 Installation media, you can install just the Client/Workstation Components. You don't have to install the database engine to install the workstation tools, but if you plan to do Integration Services development, you do need to install the Integration Services Engine on the workstation for BIDS to be able to be used for development. Keep in mind that Visual Studio 2010 does not have BI development support currently, so you have to install BIDS from the SQL Installation media and use the Visual Studio 2008 BI Development Studio that installs under the SQL Server 2008 folder in Program Files if you need to do any SSIS, SSRS, or SSAS development from the workstation.
As mentioned in the comments you can download Management Studio Express free from Microsoft, but if you already have the installation media for SQL Server Standard/Enterprise/Developer edition, you'd be better off using what you have.
Download SSMS 2008 Express
I am just updating this with Microsoft SQL Server Management Studio 2008 R2 version. if you run the installer normally, you can just add Management Tools – Basic, and by clicking Basic it should select Management Tools – Complete.
That is what worked for me.
The accepted answer was correct up until July 2011. To get the latest version, including the Service Pack you should find the latest version as described here:
http://support.microsoft.com/kb/2527041
For example, if you check the SP2 CTP and SP1, you'll find the latest version of SQL Server Management Studio under SP1:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
Download the 32-bit (x86) or 64-bit (x64) version of the SQLManagementStudio*.exe files as appropriate and install it. You can find out whether your system is 32-bit or 64-bit by right clicking Computer, selecting Properties and looking at the System Type.
Although you could apply the service pack to the base version that results from following the accepted answer, it's easier to just download the latest version of SQL Server Management Studio and simply install it in one step.
For any of you still having problems as of Sept. 2012, go here: http://support.microsoft.com/kb/2527041 ...and grab the SQLManagementStudio_x(32|64)_ENU.exe (if you've already installed SQL Server 2008 Express R2), or SQL Server 2008 Express R2 with Tools, i.e. SQLEXPRWT_x64_ENU.exe or SQLEXPRWT_x32_ENU.exe (if you haven't).
From there, follow similar instructions as above (i.e. use the "Perform new installation and add shared features" selection, as "Management Tools - Basic" is considered a "shared feature"), if you've already installed SQL Server Express 2008 R2 (as I had). And if you haven't done that yet, then of course you're going to follow this way as you need to install the new instance anyway.
This solved things for me, and hopefully it will for you, too!
SQL Server Management Studio 2008 R2 Express commandline:
The answer by dyslexicanaboko hits the crucial point, but this one is even simpler and suited for command line (unattended scenarios):
(tried out with SQL Server 2008 R2 Express, one instance installed and having downloaded SQLManagementStudio_x64_ENU.exe)
As pointed out in this thread often enough, it is better to use the original SQL server setup (e.g. SQL Express with Tools), if possible, but there are some scenarios, where you want to add SSMS at a SQL derivative without that tools, afterwards:
I´ve already put it in a batch syntax here:
#echo off
"%~dp0SQLManagementStudio_x64_ENU.exe" /Q /ACTION="Install" /FEATURES="SSMS" /IACCEPTSQLSERVERLICENSETERMS
Remarks:
For 2008 without R2 it should be enough to omit the /IACCEPTSQLSERVERLICENSETERMS flag, i guess.
The /INDICATEPROGRESS parameter is useless here, the whole command takes a number of minutes and is 100% silent without any acknowledgement. Just look at the start menu, if the command is ready, if it has succeeded.
This should work for the "ADV_SSMS" Feature (instead of "SSMS") too, which is the management studio extended variant (profiling, reporting, tuning, etc.)
I'm being driven to insanity trying to figure out why Intellisense just fails to work at all. The server I'm using is local and is 2008, the database is set to 2008 compatibility, Intellisense is on in every menu I can find, and yet no member list will pop up even with a CTRL-J.
Has anyone experienced something like this and found a way to fix it? I really can't bring myself to start work unless I have Intellisense working.
I understand this post is old but if anybody is still searching and has not found a solution to the intellisense issue even after re-installing, applying the cumulative updates, or other methods, then I hope I may be of assistance.
I have Applied SQL 2008 R2 Service Pack 1 which you can download here
http://www.microsoft.com/download/en/details.aspx?id=26727
32 Bit:
SQLServer2008R2SP1-KB2528583-x86-ENU.exe
64 Bit:
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
I have applied this SP1 and now my intellisense works again.
Visual Studio 2010 SP1 breaks SSMS 2008 R2's IntelliSense. There is a connect about that, and fortunately there is also a fix for that.
(In short, you will need to install Cumulative Update package 7 for SQL Server 2008 R2 by requesting
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
from this hotfix request page.)
EDIT: As #Paul Lemke noted, one might need to get the latest CU package. This blog contains the SQL server releases. (As of this writing, the latest is CU14)
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
No need to reinstall.
Click on the setup file. Then go to maintenance and click on Repair. This should correct the intellisense problem.
I just the had same problem. I figured out that Intellisense stopped working after I took some databases offline and doing an Intellisense refresh (Ctrl-Shift-R). I brought the offline databases back online, did a refresh (Ctl-Shft-R) again and VOILA! Intellisense is working again.
What a crappy design. Maybe the population of Intellisense's lists chokes when a database exists but is offline. Thanks Microsoft.
I don't want to suggest a product out of turn, since getting Intellisense running is probably the best option, but I've struggled with the accursed no intellisense on Management Studio for months. Reinstallation, CU7 update, refreshing caches, sacrificing chickens to pagan gods; nothing has helped.
I was about to pay for RedGate's SqlPrompt (pretty damned pricey, $195 US), when I found SqlComplete.
http://www.devart.com/dbforge/sql/sqlcomplete/?gclid=CN2xs_Lw7akCFcYZHAodpicXXw
There is a free version which does the basics, and the full version is only $50!
I'm a database architect, and while I can remember the commands, auto complete saves me heaps of time. If you're stuck and can't get Intellisense to work, try SqlComplete. It saved me hours of hassle.
I recently wrote a tip about troubleshooting IntelliSense. The title says SQL Server 2012 but most of the techniques can be applied to earlier versions of Management Studio as well.
Troubleshooting IntelliSense in SQL Server Management Studio
I ended up fixing it by reinstalling SQL Server 2008. This wasn't at all optimal, but if someone comes across a similar problem be sure to know this route will probably work.
I tried all the fixes - taking databases offline and then bringing them online, installed Cumulative update 10, repaired SQL Server Installation, refreshed local cache, made changes to the required settings on SQL Server Management Studio but everything was in vain. Finally installing the correct service pack (SP1) did the trick for me !
Follow the link below, and download SQLServer2008R2SP1-KB2528583-x86-ENU.exe (or the x64 file for a x64 bit instance of SQL Server)
http://www.microsoft.com/download/en/details.aspx?id=26727
Finally i have Intellisense enabled !
I'm posting this here as I am sure more people will be comeing across this issue. I installed Security Update for microsoft Visual Studio 2010 Service Pack 1 (KB2565057) and lost Intellisense in SQL Server Management studio 2008 (not R2).
An uninstall of the SP restored Intellisense .. Don't you just love Microsoft????
After finding this thread, I discovered that my Intellisense only broke after taking a database offline, and any offline database(s) on the instance would kill Intellisense.
In this thread, explaining that in order to restore Intellisense, you must
take the necessary databases offline, then
restart the server instance, and finally
refresh the Intellisense cache.
This procedure has worked for me and Intellisense is now working again.
I've had the same problem too. Searched everywhere online and can't find a solution. I did install Redgate's SQL Prompt which functions similarly to Intellisense, so maybe there was a conflict. I've since stopped the Prompt from running, but now no intellisense at all. Using SQL Server 2008 will SQLCMD mode off, no luck at all. This has happened before, a reinstall of SQL Server was the only thing that I could get to work.
Same problem, but just re-installing SQL Management Studio 2008 R2 Service Pack 1 worked for me. I left my DB engine alone. The DB engine is not the problem, just SQL Management Studio getting hosed by Visual Studio SP1.
Installers here...
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26727
I installed SQLManagementStudio_x86_ENU.exe (32 bit for my machine).
When trying the accepted answer, I was getting an installation error: A failure was detected for a previous installation, patch, or repair blah, blah, blah...
To fix this, in my registry, I changed all DWORD values to 1 in the following Keys: (As always be careful modifying the registry and create a backup of the key before changing anything)
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\ConfigurationState
See my full post about Fixing Intellisense issue in SSMS.
Here is the official word on this from MS.
http://support.microsoft.com/kb/2531482
Their solution is the same as above, install the SQL Server 2008 R2 updates with the version 10.50.1777.0.
http://support.microsoft.com/kb/2507770
I did all of the above and ultimately gave up. Then one last resort was a third part SQL Intellisense add-on I found SQL Complete Express by devArt.
It's Intellisense plus more. Intellisense is back and all is well.
Supports SSMS 2005 - 2012 also includes Visual Studio Add-In.
SQL Complete
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
this is Direct Link From MS that i was got it Hot Fix