I have a single project with multiple packages that I recently moved to a new
development server by copying the .dtsx files to the new server. Then I
broke them out into individual projects by importing the .dstx files using
the "Add Existing Package" tool (when you right-click on the "SSIS Package"
folder in the "Solution Explorer".)

Now, the Properties Window for each of the Data Flow tasks in each of the
packages is blank. If I go into the Data Flow task tab and open the
Properties Window for any of the components (OLE DB Source, OLE DB
Destination or Derived Column) , the only thing that shows up is "Common
Properties" and "Misc" with very minimal information in each of these
categories. I do not know if I was ever able to view the properties
immediately after importing these packages.

Does anyone have any idea (1) what I did that caused this, (2) how to
prevent it from happening again, and (3) how to fix it? This problem is with
with all projects on this server; I've even tried creating a new project from
scratch. There is no difference between the two servers, as far as O/S or
SQL Server versions and editions go.

As you can imagine, not being able to view / modify the properties on these
tasks is extremely frustrating; I really need some feedback on this!

Thanks in advance,

Mike

Mike: Were your Connection Managers based on Shared Data Sources? That might
be an issue. Did you get errors when you tried to open the .dtsx files on the
new machine? What EncryptionLevel did you specify when they were created?
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike" wrote:

Todd,

My connection managers are pointing to the SQL Server destination and
multiple DB2 sources - I'm not sure what you mean by Shared Data Sources.

I did have troubles opening the .dtsx files and had to register:
%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL
Server\90\dts\binn\MsDtsSrvrUtil.dll" and %windir%\syswow64\regsvr32
"%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll" (included the
full path so you can see where the files are located, how they were
registered, etc.)

After registering the .dll files, the packages opened up without any problem.

Re: encryption level - I may have been messing around with it (this is my
first attempt at SSIS package development); the source server and original
package are still available - if you point me in the right direction, I can
go find out.

Thanks, Todd!

Mike

Based on having to register DLL's manually, I would guess that the install of
SSIS and/or BIDS (Businessis Intelligence Development Studio) is hosed up
some how. I would recommend un-installing and re-installing those two
components.

Doing pure 'swapnostics', can you port the .dtsx packages to a third machine
and open them (and edit) without issue? That would tell you something.

BTW:
Look for a Shared Data Sources node under the SSIS Project. Create data
sources here instead of making new ones for each and every package in the
project.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Todd C" wrote:

New development - whenever I try to enable / disable multiple parts of the
package at the same time, I get:

TITLE: Microsoft Visual Studio
------------------------------

The object does not support type information. This occurs when the runtime
attempts to get the type information from an object to populate the
Properties collection. The object must support type information.


------------------------------
ADDITIONAL INFORMATION:

The object does not support type information. This occurs when the runtime
attempts to get the type information from an object to populate the
Properties collection. The object must support type information.


------------------------------
BUTTONS:

OK
------------------------------


Doesn't seem to be a problem to enable / disable individually.

Yeah, I'm starting to think "messed up installation". Unfortunately I am on
a very short timeline and I'll have to convince the sysadmins to do the
uninstall / reinstall.

Mike

Time out, Mike. Are you installing BIDS on your SERVER? Not recommended!

Generally, you install the Development tools (and perhaps a SQL Express
isntance) on the developer's workstation, and on the server, only install the
components to run the services.

--
Todd C

Yep - I know. I'll just leave it at that.

"Todd C" wrote:

The SA ended up reinstalling SSIS and BIDS.

Mike