I am getting the following error in SQL Server 2008 R2 (build 10.50.1734) x86 platform BI Development Studio (BIDS) 9.0.30729.4462 with .NET Framework 3.5 SP1 in a Integration Services project Data Source View table when I attempt to Explore Data: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)) This happens on a Windows 7 Professional workstation x86 platform, (but has not been observed on Windows XP). The error occurs on Data Source Views bound to a Data Source connected to a SQL Server 2005 SP3 (build 9.0.4053) and SQL Server 2008 R2 server (I'm sure it's not a server issue, but a workstation issue). I have successfully unregistered and re-registered DTS.DLL and DTSComm.DLL in the registry, with no resolution to the issue. Does anyone have any ideas? Thanks.Greg

Please describe what you're trying to do, and at what point the error occurs. Talk to me now on

As it mentioned above, I am using BIDS and open my Integration Services project. The project contains a Data Source View with a few tables. I right click in the table and select Explore Data. BIDS then open the dialog box with the error above.Greg

Have you tried "repairing" the SQL install? Talk to me now on

Yes, I just did and I still get the same error. Thanks.Greg

OK - your initial post is very unclear. You have two versions of SQL listed - 2008R2 and 2005, and a mish-mash of what's running what. Can you please state what SQL version(s) you have installed on the computer you're logged in to interactively? Please give us a name for that machine, or refer to it as your DEV machine. Does this DEV machine have multiple versions of SQL installed? The engine only, or SSIS? Is this machine's OS x86 or x64? Are the SQL instances x86 or x64? If you are connecting to other machines, please give them names, and list what SQL components are installed on them, and what bitness the OS and SQL installs are. Can you provide the design/definition of your Data Source View? What servers/connection types are you using? Does "Explore Data" fail on every table included in your DSV? Or only on one of the tables? (Assuming you have more than one.) Talk to me now on

Development Workstation DEVW: Windows 7 Enterprise x86 platform SQL Server 2008 R2 Developer Edition x86 client tools only (including BIDS and .NET Framework) versions stated above. VS 2010 Premium (build 10.0.30319.1 RTMRel) & .NET Framework (version 4.0.30319.1 RTMRel) (if that matters). Development Server 1 DEVS05: Windows Server 2008 SP2 (build 3790) x86 platform SQL Server 2005 SP3 (9.00.4053.00) Standard Edition x86 platform - database engine & SSRS, SSIS, client tools Development Server 2 DEVS08: Windows Server 2008 R2 (build 7600) x64 platform SQL Server 2008 R2 Developer Edition (build 10.50.1600) x64 platform - database engine & SSRS, SSIS, SSAS, client tools I am not sure what you mean by the design/definition of the DSV. If you need the DSV file itself, I can't give you that for security reasons. But I have two DSV definitions for each server. For DEVS05 the DSV implemented as five Generic and VDT queries based on a Data Source (DS file) with SQL connection string: Provider=SQLNCLI10.1;Data Source=DEVS05;Integrated Security=SSPI;Initial Catalog=databasename. The DSV for DEV08 is similarly configured, but it only contains tables, not named queries. BIDS fails on every table (and query) in all DSV files. Greg

Many thanks for the clarity - that's perfect. I understand completely about not being able to publish the DSV directly - but I think that your description of its contents is sufficient. I'm assuming that you can: SELECT from those tables/views you have defined in the DSV by querying similar constructs from SSMS. Create an SSIS package with an Execute SQL Task that reports success issuing similar queries with a connection manager generated from the Data Source. Create an SSIS package with an Execute SQL Task that reports success issuing similar queries with a connection manager NOT generated from the Data Source. Create an SSIS package with a Data Flow Task that issues similar queries using an OLE DB Source with a connection manager generated from the Data Source. Create an SSIS package with a Data Flow Task that issues similar queries using an OLE DB Source with a connection manager NOT generated from the Data Source. Please try any of the above if you haven't already. (If you haven't guessed, I'm shooting in the dark, trying to collect info.) In your first post, you say you've only observed this on DEVW, and not on an otherwise-similarly configured XP machine? I'm assuming similarly configured means the same version of SQL/VS are on that. Lastly - just to be a jerk - is there a particular reason you're using Data Sources and Data Source Views? I'm not familiar with any of the regulars around here recommending use of those in SSIS solutions. (Several recommend against using them.) Talk to me now on

Yes I can perform all the above bullets as you assumed above. We recently upgdraded from Windows XP to Windows 7, and I observed this issue when we upgraded. But the Windows XP workstation was otherwise similary configured to the Windows 7worktation as you stated. As this is my first project with SSIS 2008, I noticed Data Sources Views as being new to this version, so I decided to use them. I felt it was a good way to consolidate our queries against a common data model as we will be developing numberous packages, instead of risking having separatly developed SQL queries (and risk developing inconsistent ones) for each of our packages. Although I realize this can be done in other ways such as SQL server views, I wanted to try the new SSIS feature. But I will note your point. Finally, I uninstalled and re-installed SQL Server on my workstation and I still experience the same results. Greg

That's very odd behaviour. FYI - I'm running W7x64 (with 32-bit tools, of course) and didn't have a problem with exploring data on a 2K8 or 2K5 server. You may want to talk direct to MS, via your regular support channel, or through Connect. Talk to me now on

I have the same problem on a DSV in a Report Model project. I haven't been able to use the Explore Data option for a long time now across several different workstations with fresh O/S installs. I submitted a bug on Connect and referred to this post as well. The bug ID is 610674.

I called Microsoft support and they said to install (or repair if already installed) Office Web Component (OWC). It fixed my issue. We are an Office 2007 shop, and OWC only comes with Office 2003, but you can download it for free at http://www.microsoft.com/downloads/en/details.aspx?familyid=7287252C-402E-4F72-97A5-E0FD290D4B76&displaylang=enGreg

Greg, This is worked for me, I had the same problem. Its a mystery to me why this has anything to do with BIDS, but it worked. No way I could have found this out intuitively Lance Milbouer