Deployment Utility error

I am getting the following error when trying to run a deployment utility. The server only has .net framework 2.0 and sql server 2005 (rtm) installed.
If it's any help, this server was recently upgraded from the june ctp to rtm.
This is a production server, so a solution involving as little disturbance to it's current state would be preferrable.
Thanks in advance for any suggestions.
-Jeremy
TITLE: Package Installation Wizard
Unexpected error occurred.
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
BUTTONS:
OK

Looks like the SSIS is not corectly installed on the machine. Can you uninstall SQL Server and reinstall it?

HTH,
Ovidiu

|||unfortunately, no. I'm not even sure that would have any affect, as we just installed it an hour before this error, and I saw no point in the install process where it could have gone awry.|||

We're having the exact same issue with a WinForm app deployed via ClickOnce.

What's the deal here?

Deployment Utility error

I am getting the following error when trying to run a deployment utility. The server only has .net framework 2.0 and sql server 2005 (rtm) installed.
If it's any help, this server was recently upgraded from the june ctp to rtm.
This is a production server, so a solution involving as little disturbance to it's current state would be preferrable.
Thanks in advance for any suggestions.
-Jeremy
TITLE: Package Installation Wizard
Unexpected error occurred.
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
BUTTONS:
OK

Looks like the SSIS is not corectly installed on the machine. Can you uninstall SQL Server and reinstall it?

HTH,
Ovidiu

|||unfortunately, no. I'm not even sure that would have any affect, as we just installed it an hour before this error, and I saw no point in the install process where it could have gone awry.|||

We're having the exact same issue with a WinForm app deployed via ClickOnce.

What's the deal here?

Deployment Problem - Unable to find the requested .Net Framework Data Provider

I am able to work fine in my development environment, however when I deploy the application to a clean machine, I get the dreaded "Unable to find the requested .Net Framework Data Provider" error.

I have included the eight dlls required by the Sql Server 2005 CE engine (per the documentation) in the deployment project.

Any help would be greatly appreciated.

(I presume that you are deploying on a desktop.)

The recommended method is to install the runtime package (through click once or otherwise). No manual intervention is needed. The data provider (i.e. System.Data.SqlServerCe.dll) is put in GAC. It is easy to update the package too.

If you do not want to use the installer for some reason, then ensure that all SSC binaries are in the executable folder.

Deploy apps using sql 2005 express

i'm building apps using sql server express and I want to deploy to servers that have the 2.0 .net framework but have sql server 2000 database.

Can this be done, and if so, how?

Observing God’s Holy Spirit, I see God saying that The Lord Jesus influences every natural occurrence of kindness, righteousness, and judgment _{(Jeremiah 9:23-24)}. I believe God, so I thank The Lord Jesus for your grace in these matters.

The database format used by SQL 2005 is not compatible with that used in SQL 2000, so you can't deploy the database by copying and attaching the mdf file to the deployed server.

You could deploy your application by using scripts to create your database on the target server. The Embedding SQL Express white paper discusses one way to do this.

|||

WHy do you want to develop in a much higher version of SQL Server for deploying it to an older version of SQL Server ? I am a developer on my own, and I never would do that due to compability issues. YOu can either use the developer edition for developing of SQL 2000 or the msde which would give you in most cases the same results that you will have like on the deployed system.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I'm experimenting with the new Microsoft express technologies, but my production hosting company has not yet upgraded to sql server 2005, but is still using sql server 2000. I found information that leads me to understand that the visual web developer express edition does not support any database except sql server 2005 express. So, I tried this new MS tech that did not work on the old servers.

Nevertheless, by the faith of The Lord Jesus, I thank The Lord Jesus for His kindness to me by the information you provided . And, by God's grace thru Christ Jesus, I'm a improved person after trying something different. Perhaps, you will find similar satisfaction in God's mercy through Christ Jesus if you did things that you thought you would never do.

Best Wishes