-
mhearn said 1 year, 2 months ago:
Running on a 64 bit machine, get this error
Error: 53: Could not load file or assembly 'C1.C1Report.2, Version=2.6.20121.54503, Culture=neutral, PublicKeyToken=594a0605db190bb9′ or one of its dependencies. The system cannot find the file specified.
Any suggesitions| # -
Hello,
Hope you are doing well.
It seems that the files are either not present on the system or are not referenced properly. I would request you to please make sure that the dll is present on the system and is referenced from the correct location. Also make sure that the licenses.licx file has the correct version entries with respect to the dll(s) referenced to.
Also refer to the following link:
Let me know, if you still face any issue.
Regards,
Mohita| # -
I have the files on Both Machines i tested it on.
Your response is not clear as to the Licence.
"Also make sure that the licenses.licx file has the correct version entries with respect to the dll(s) referenced to."What is it that is to be done to accomplish this?
Here is more information from our Developer:
we just purchased the product after briefly using it on a trial basis. i am a Florida developer for a company that is located in California. I added your c1.report product into my program and distributed the product to my employer (who is the one who purchased the product and wrote this original issue and question) and when he went to install the program i had sent him (installer by visual studio) he is getting the following message:
Error: 53: Could not load file or assembly 'C1.C1Report.2,
Version=2.6.20121.54503, Culture=neutral, PublicKeyToken=594a0605db190bb9′ or one of its dependencies. The system cannot find the file specified.i tried the distribution to a laptop that i have and it worked fine. His machine was 64 bit and want to know if there is some issue with that or something else that would cause him to get this message. is there anything we need to do re the licence in creating the install fro his machine? Please let us know what we need to do so that we can distribute a program using your control to its market.
| # -
Hi
If I am understanding this correctly you have built an application using c1 report version 2.6.20121.54503. You have then built said application and distributed it to your employer who is now reporting the error that you initially reported.
Have him / her check the installation folder where your application has been loaded to on their machine and see if it a) contains the relevant c1 report dll and then if it does what version it is. My initial thoughts on this would be that it ( the dll ) either isn’t there or if it is it’s the wrong version.
One other thing springs to mind, The report dll is present on you end users machine but it is the 4.6.20121.54503 version as opposed to the 2.6.20121.54503 that you referenced in your project. If that is the case (and if you are targeting the .net 4 framework) then look at your project and see which version of the c1 report you have referenced. If everying you have is prefixed 4 bar the report dll then I would delete that from your project, re reference the .net 4 version and then in the licences file strip out the version specific information from the line referencing the c1 report dll. Save and re build your application and then re distribute and you should then find that it works.
Dom
| # -
I am running the correct version, and also installed the application of C1Designeer on my machine, could it be that i am running 64 Bit Windows OS?
| # -
Also, i have all the DLL’s in the Following Folder – (Which should be fine – correct?)
Program Files(x86) ComponentOneStudio for WinFormsC1Reportdesigner| # -
Hi
The important thing to check first is what dll is installed in the application folder that was created on your employer’s machine. He / she is the one getting the error, therefore the problem in the first instance is on that machine.
Get them to check which version of the report dll has been installed into the application folder that your installer created on their machine if indeed it has been installed and then reply with that information here.
Dom
| # -
Just wanted to add to what have already been said, the error should have nothing to do with whether the OS is 32 or 64 bit. The cause most probably is either a missing dll, or a one with the wrong version number.
| #
You must be logged in to reply to this topic.
