One or more errors occurred

Question

0.00/5 (No votes)

See more:

Good day folks,

I have Winform solution with two projects. One is DAL and the other project is client UI.

The DAL project uses EntityFramework with MySql as server.

The project deployed and installed successfully. The database has also been seeded but when I run the application on the testing machine it returns an error message 'One or more errors occurred' and then terminate.

The application uses EntityFramework version 6.2.0 and MySql.Data.EntityFramework version 8.0.15
have spent several hours to resolve it but have not been successful.

Any assistance is greatly appreciated.

What I have tried:

I have google the error with the hope of get solution but to no avail.

Posted 3-Dec-19 9:15am

noblepaulaziz

Updated 3-Dec-19 9:55am

v2

Add a Solution

1 solution

Add a 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)

OriginalGriff · Answer 1 · 2019-12-03T09:53:00

We can't help you much directly - without your code, the systems you are running it on (client and the DB), and even a vague idea what the code is supposed to do or how to use it we haven't got access to anything to work out what could be causing the problem.

So, it's going to be up to you. Normally I'd tell you to break out the debugger, but since it presumably works on your dev machine and only fails in production, you pretty much can't do that. You will have to fall back on older (and more time consuming) debug methods. Start by adding a whole pile of logging statements to your code, and redeploy. When it fails, look at the log and see where it was last working. Add more logging between that point and the next log - the one it didn't get to. Repeat, and repeat, until you have a good idea where it happens. You can now start improving your logging to include data contents, and from that start working out why it's different between dev and prod.

Sorry, but we can't do any of that for you!