Deployment problems - no components for DataFlow

I’ve created a SSIS package that has 2 tasks. The first is selecting some information from a SQL Server table and the second is exporting this information to a flat file.

I created the package on my desktop client and I am able to run it successfully in Debug mode from my client. The information is selected from the LIVE SQL Server database and the file is created on the LIVE SQL Server.

I have built the package for deployment, copied it to the LIVE SQL Server and have run the manifest file to deploy it.

I’ve logged into the SSIS on the LIVE server and the package is listed there. However when I right click on it and run it I get some error messages indicating that the dataflow tasks have no components, presumably the select statement and the export to the flat file.

It’s as if when I build the package the data components are not being included or when I deploy it on the LIVE server the data components are not being deployed.

Does anyone have suggestions?

Could you report the actual error message you are getting? Empty data flows only generate warnings, not errors.|||

The exact error is:

DocumentL Listing

Validation has started.

Export Document Listing

Validation has started

Warning: The DataFlow task has no components. Add components or remove the task

Validation is completed

Validation has started

Warning: The DataFlow task has no components. Add components or remove the task

...

|||

Rob,

I know about this problem only too well. Are you using a source control system?

-Jamie

|||

We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.

Are you saying that this may be a problem with the Source Safe integration with SQL 2005?

|||

Rob Woods wrote:

We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.

Rob Woods wrote:

So that package that we're talking about. Does it ever get stored in SourceSafe?

Are you saying that this may be a problem with the Source Safe integration with SQL 2005?

Not exactly. There's a problem with all source control systems when used in conjunction with the SSIS Designer - I have seen it happen with SourceSafe and TFS. The SSIS team are aware of it and are investigating. Long answer is that the contents of the data-flow doesn't get serialized correctly into the .dtsx file due to some sort of problem when used with a source control system. Short answer is that there is a bug.

I really should blog this

-Jamie

|||So is there a work around?|||

Rob Woods wrote:

So is there a work around?

Best I can offer is that seeing as you are using a source control system you can go back and find the most recent version that still contains all the components, and redo all of your changes. Not great!

-Jamie

|||

Jamie Thomson wrote:

I really should blog this

And now I have done: http://blogs.conchango.com/jamiethomson/archive/2007/04/24/SSIS_3A00_-Bug-when-using-source-control-systems.aspx

-Jamie

Deploying RS server components on server without MSSQL

For the application I need to integrate RS with, I have a physical server
running MSSQL 2000 SP3a Standard Edition and another physical server that
runs my web apps. Both servers are running windows 2000 SP2. We do not want
to install RS server components on the db server itself because we want it to
remain a dedicated database server.
So, we want to host the Report Server database on the db physical server and
run all of the RS server components on the application physical server.
Yet when I try to install RS on my application server, I get the following
message in the install 'System Prerequisite Check': 'This edition of
Reporting Services does not support installing the server components on this
operating system'. What does this mean? How can I get around it?
-kind regards, Brian ParkerThe issue is not the database. RS is designed to run this way (note that you
need to have another SQL Server license if RS is on another server than
where the DB resides but that is a licensing issue). The issue is the OS.
Here is a link on the prereqs:
http://www.microsoft.com/sql/reporting/productinfo/sysreqs.asp
a.. Windows® 2000 Server with Service Pack 4 (SP4) or later
a.. Windows 2000 Professional with SP4 or later1
I wasn't sure if you had server or professional. If server then it needs
SP4. If professional then this additional info holds:
Windows XP Professional and Windows 2000 Professional only support Reporting
Services Developer Edition
So, one of those two things is what is happening.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian Parker" <BrianParker@.discussions.microsoft.com> wrote in message
news:97ECE792-B9F0-4762-A278-1BC8790797A0@.microsoft.com...
> For the application I need to integrate RS with, I have a physical server
> running MSSQL 2000 SP3a Standard Edition and another physical server that
> runs my web apps. Both servers are running windows 2000 SP2. We do not
> want
> to install RS server components on the db server itself because we want it
> to
> remain a dedicated database server.
> So, we want to host the Report Server database on the db physical server
> and
> run all of the RS server components on the application physical server.
> Yet when I try to install RS on my application server, I get the following
> message in the install 'System Prerequisite Check': 'This edition of
> Reporting Services does not support installing the server components on
> this
> operating system'. What does this mean? How can I get around it?
> -kind regards, Brian Parker

Deploy SMO project

Hi,
I'm writting a tools with SMO that supports SQL Server 2005 and 2000 and I'm wondering wich components do I have to include in my setup to support both versions ?

With SQLServer 2000 my application throws a following message :

"Could not load type ‘Microsoft.sqlServer.Management.Smo.TriggerBaseCollection’ from assembly ‘Microsoft.sqlServer.Management.Smo’, version = 9.0.242.0"
Thank you.You should obtain the "Microsoft SQL Server 2005 Management Objects Collection", which contains SMO. See http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&DisplayLang=en

Peter