How to resolve the entity validation errors in Visual Studio? - html

I am getting the following error in my ASP.Net Web application using Entity Framework model with the Database first approach. Can anybody please tell me how to solve it? I am attaching two related screenshots.The actual error snapshotThe line in my code where it is showing error
I am actually new to Visual Studio. So , I havent really tried any solution.

Related

SSIS/SSRS -- I am getting this error, when I am creating a new project for SSIS in VS 2017

New to Reporting Services, I am getting this error when creating a new project
Expanding my train of thought from comments
The Class not registered error smelled like something was wrong in the registry but what was missing was going to impossible to troubleshoot. Going through the uninstall/reinstall process appears to have gotten all the correct classes registered and the tool is now working.

How do I get rid of the CreationName Error in my SSIS package in SSMS?

I have created an SSIS-Package, which is supposed to import Data from Flatfiles (txt. Files) into a Database.
When I execute the package via Visual Studio (Enterprise, 2015), there are no problems and everything works just fine.
The problem occurs when I deploy the package into SSMS (Express, 2014). When I execute the package from SSMS, I get an Error (no idea if there is an Error Code or where to find it) concerning the property "CreationName". SSMS doesn't seem to give me any other information.
In the package are 5 scripts, which all do the same but with different flatfiles.
They all get this CreationName Error.
Has anyone any idea on how to fix it or the source of the problem?
i solved the problem, but it had nothing to do with the creationname apparently - i made some wrong settings in my sql agent + i made it work by deplying it from my hard drive instead of the virtual drive. I also had a typo in one of the scripts :x Idk why it had problems with the virtual drive though; maybe it was an authentication problem. Still THANK YOU ALL SO MUCH! You guys kinda brought me there :)
I don't understand what's written on the attached image, but I would disable 4 out of 5 components then run through the job. If there's no error than disable 3 out of 5 and run it again...you get the point. Obviously this has to be done in a non-prod environment. I believe that will help you narrow down the problem within your package. Maybe you can debug from thereon?

Cannot create .edmx for MySql Database with mysql.data.entity.EF6 in Visual Studio

Recently i am trying to developing n-tier asp.net mvc application using Entity Framework with MySQL as the backend database. I wanted to use latest EntityFramework ie 6.9.9.0 version, so i downloaded sqlconnector package through "Nuget package Installer". These are the libraries that it installed for me:
mysql.data.dll(ver. 6.9.9.0)
mysql.data.entity.EF6(ver 6.9.9.0)
But i could not successfully create .edmx file for my project. During the final steps of creation of .edmx , it ends in the error. Here are the steps I applied:
1) first I selected '.net framework database provider' for mysql as in screenshot
2)Then I clicked 'next' button as in the screenshot
3)Finally i selected the tables for the database that i want to import in the entity data model before i click 'finish'
4) Click on "finish" button pops up "null object reference" error.
closing the error dialog displays the "add entity model" dialog again
The process creates a blank .edmx file with not a single DB tables on it.Also I find no errors in visual studio error list at the bottom of the window.
Could anyone share insight on what could be the possible issues here, i am really stuck at the first step of code my application and has already spent almost whole day searching for solution over the internet. I personally tried many alternatives seeking for solution too, but no luck so far. Anyone's help would be truly appreciated.
Thank you.
I somehow sensed that I am not using the right version of
EF tools for Visual Studio 2013
with corresponding version of MYSQL server installation and mysqlconnector for .net. So i downloaded and compared several versions of EF tools, MYSQL installer and MYSQL(Nuget package) for entity framework and finally found the right combination as follows:
Entity Framework 6.1.3 tools for Visual Studio 2013
MYSQL-installer-community-5.6.32.0.msi (you can find archived mysql
version in google)
MYSQL(Nuget package) for entity framework like in the screen shot below:
As it worked for me , i think mysql.data dll version and mysqlconnector for net that comes with MYSQL installer should match , i have them highlighted here in picture:
After the proper installation ,i finally got EDMX diagram loaded fully and correctly upon creating one.
P.S: after every un-installation of MYSQL server version that did not work for me, I used the useful tool (Advanced_Uninstaller11.exe) to clean all left out registry entries and here is the download link for the tool
enter link description here
I Hope that I have explained it clearly of the problem and its resolution. I could not make any of the above points or scenario clear, hope you would comment on it and i would try to explain more and better.
And Thank you #ErikEJ for your continued support on the problem.

generating report with birt

im using birt report designer plugin in eclipse pdt. i successfully built the datasource and data set from mysql database. but when i try to use the data column in my report it generates error with
error message
"An error has occurred. See error log for more details.
org/mozilla/javascript/ScriptOrFnNode".
i have already built many reports in same configuration without any such problem. but now its not working what may be the reasons behind this?
i have tried many suggestions like birt updating, from this as well as some other forums without any improvement
Thanks..

TFS Build partially succeeded when LINQ to SQL is added

VS2008 / TFS Build 3.5 / Ent Lib 4.1
I have a rather large solution that contains several apps. They are all currently using Enterprise Library (v.4.1) for their data access layer.
I added and locally tested a new data access layer that uses LINQ to SQL- it was fast and easy to add and the test went fine. But...
When I checked in the project, it would not complete the build - I get a "Partially Succeeded". There are some warnings, but those exact same warnings were there prior to the build failing.
I took the data access class back out (along with the code that calls it) and rebuilt and it builds fine.
I then added an empty new class and put a single variable in it and referenced it from the code. That built. I then created a new LINQ to SQL class in that new project and did not even reference it. When I checked that in, the build failed again with the "Partially Succeeded" message. No extra errors or warnings.
I love LINQ to SQL, I have used it in a few projects outside of this system, but I now have many hours into attempting to get this to build with no success.
Are all the same tools/libraries installed on the build server as on your desktop - Perhaps the server doesn't have the same vs or .net service pack level? Try running the build "manually" on the build server - load up the solution in Visual Studio on the server and execute the build within the IDE rather than under the TFS build system - this may report problems that you don't see so easily in the automated build.
Check the build log. Visual Studio often reports errors in the output pane text or build-server log text that are not picked up by the GUI error windows. So you will think a build succeeded but an output file has "quietly" not been generated. TFS build logs are usually huge so they are a pain to work through, so start by searching for keywords like "error" or the name of the project that fails rather than trying to read through line by line.
OK, we found it. The issue is on stack overflow elsewhere at
Visual Studio Setup and Deployment build fails with no errors
The issue is a bug in MS setup and deploy that breaks when it hits a line in the project that uses Linq. You have to comment out a line in the project to get it to work. Amazing, ridiculous, and no surprise.
Thanks for the input, it was that input that helped us get to the eventual answer (already on StackOverflow, but didn't have Linq in the title).