Reporting Error after publishing

Question

1.00/5 (1 vote)

See more:

I developed Desktop Application after publishing the application when I am running .exe filein My PC it's properly and reporting part is also running properly.But I am Migrating Folder which has been published to another PC and I am opening .exe file whole application is running properly but the problem I am getting below error in Reporting.

"Unable to find requested .net framwork data provider.It may not be installed"
Please provide me solution as much earlier as possible.

Regards
Zakaria

Posted 19-Jun-15 21:18pm

Zakaria Jagral

Add a Solution

Comments

virusstorm 20-Jun-15 7:53am

Make sure the target PC has the same version of .NET installed all of the dependencies for application are installed or included in your publish profile.

Zakaria Jagral 22-Jun-15 2:20am

I installed same .net framework and I have all dependencies .dll file then also it's showing error.

virusstorm 22-Jun-15 8:00am

What data provider are you using? The error is saying that a component could not be located. I've had issues where certain components get deploy to the GAC on my local machine but are not there on a clients machine. The easiest way to resolve this is to right click on the reference and go to properties. In the properties window, for "Copy local", select "Always". This will ensure the DLL is there when you publish.

Zakaria Jagral 23-Jun-15 5:18am

Thanks I got the Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)