Showing posts with label unable. Show all posts
Showing posts with label unable. Show all posts

Thursday, March 22, 2012

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.

Saturday, February 25, 2012

Deploy to named instance

Is it possible to deploy to a named instance from the default instance on the same machine? I keep gettin 'unable to connect' error.

Thanks.

SQL Server 2005 sp 2/Vista

> deploy to a named instance from the default instance on the same machine?

What does it mean "deploy from instance" ? Normally the project is deployed from BI Dev Studio. There in the Deployment Options, you specify the named instance as a server to deploy to, and it will work.

|||

I get the following error message: The project could not be deployed to the '...' server because of the following connectivity problems" '....' instance was not found on '..' server

I know the instance is there because I can open it in sql server mgmt studio. I can also use the named instance as a data source.

|||

Further information: Microsoft doesn't like instance names to include the '_' character, as in SQL_TWO.

Getting closer....just one Mdx script error