The application was developed on VB.Net 2003 Framework 1.0.3705. I have reports that use Aspose.Excel and Aspose.Cells. This application has been stable and in production for almost 4 months. Last week I tried to run the app in debug mode and got this error (See the attached file for a screen shot of the error message and a copy of the stack trace.
I’ve compared my machine.config file with one from one another developer’s computer and they are identical. I’ve completely deleted this project from my computer and loaded a copy of the code from production and still get this error. Others in the group can run the project in debug mode from their computers with no errors.
I don’t believe this error is coming from Aspose.Excel, but was wondering if you’ve seen anything like this and could point me in the right direction.
Thank you for any help you may be able to provide.
David Roy
Hi David,
Well, it looks to be a configuration problem. Please check the configuration settings if they are properly documented and make sure that you got sufficient rights to access the assembly.
I think you may create a fresh project similar to your existing one and create all the web forms into it, add reference to the component, paste the code segments to the forms and copy other files to include to your project, finally build and run it to check if you still get the issue.
Thank you.
Thank you for your suggestion. This is a large project and I was trying to avoid taking this step, but I’ve run out of other ideas. If you or the team come up with any other thoughts, please post them. I’ll begin rebuilding this into a new project and hope for the best.
Hi,
Well, since you are using older Aspose.Excel component for which we are not very sure. I think you may try to register the component using the .NET command prompt utility e.g
regasm Aspose.Excel.dll /codebase if it makes the difference on your production server.
And for the last resort, we can only recommend you to create a fresh project with all the files in it. build with the component and run it if it works fine.
Thank you.
Please check our license to see if it’s still valid:
Oklahoma State Regents Higher Education
Enterprise
9c4100d2-2765-4ddf-8c46-c0e790c2f0ec
20090107
The problem I’m experiencing only happens when Aspose.Cells is brought into a vb.net application on my computer. The same application works fine with Aspose.Excel.
This license file and dll (4.5.00) works on other computers.
Before I rebuild this application, I want to eliminate all other possibilities.
Thank you for your assistance.
Hi,
Well, your license expiry date (as described in your license file) is Jan 07, 2009. So, this license should work fine for your Aspose.Cells for .NET v4.5.0, but will not work with recent versions e.g v 4.7.0, 4.7.1 or 4.8.0 etc. though.
Thank you.
I’m still having the same problem and looking for anyone who’s had to deal with this. Please see the attached file for our attempts and the results. I’ve also completely rebuilt the application and have a clean build, but the results are the same.
I’ve even tried registering the dll through Windows. I’ve never had to do this before and I’m not even sure if this is possible, but the attempt was not successful:
regsvr32.exe Aspost.Excel.dll
Aspose.Excel.dll was loaded, but the DllRegisterServer entry point was not found. The file can not be registered.
At this point, upgrading the application to dotNet 2005 or higher is not an option.
Thank you for any assistance.
Hi,
Well, since you are using both Aspose.Excel(older) and Aspose.Cells in a single project, so we appreciate if you could create two simple projects separately i.e…, one using Aspose.Excel and other using Aspose.Cells for .NET… to find out where is the issue.
For registering Aspose.Excel or Aspose.Cells please use:
regasm.exe instead (do not use regsvr32), e.g.
Regasm Aspose.Excel.dll /codebase …
and you should use VS.NET command prompt instead of Windows default prompt. For your info, this Regasm utility is present in the .NET framework, please click on the Start menu, then click |Programs|Microsoft Visual Studio .NET…|Visual Studio .NET Tools|Visual Studio .NET command prompt option.
Also, it looks very strange to us as other developers are not finding this issue at all. I think the problem is only with your machine. We also suggest you to create a dll by himself in .NET and register it, then create a project without Aspose.Cells or Aspose.Excel to check if the component registration works on your machine or not.
Thank you.