Corrupt (?) designer file


#1

We are using Aspose.Excel with designer files. While our web application worked fine on our development server we encountered a huge problem after copying the application to our provider's server. During executing the Process()-method something wrong happened and after a few minutes the browser showed the message "Cannot find server - The page cannot be displayed".

We could not replicate this error on our developmentserver but we could solve the problem by creating a new designer file (which has exactly the same fields than the old one).

Our designer file contains about 50 columns and we are inserting about 3000 records (inserting only a few records did not cause an error!).

Can you tell us what could be the reason for the problem and how we could avoid that this problem occurs again?

Thank you for your help in advance,
Petra


#2

Which version of Aspose.Excel are you using? What’s the size of your designer file? Is it possible that your program times out which caused this problem?


#3

And please check the memory size allocation of your server. Maybe your program consume too many memory which causes IIS to re-start automatically.


#4

We are using Aspose.Excel 3.6.1 but a test with a new Aspose.Cells dll caused the same problem.
Our old designer file was about 334 KB. The new one has only 33 KB. I assume the difference depends on some copy-and-paste and delete actions during developing the old file.
We did not get any "timeout" error but we cannot monitor our provider's server directly.


#5

Our designer file contains about 50 columns and we are inserting about 3000 records (inserting only a few records did not cause an error!).

From above description, I guess this problem is caused by that your program exceeds the memory limitation. A 3000 row X 50 column Excel file will be more than 4MB size and Aspose.Cells takes about 60MB memory when manipulating and saving it. If your program contains other formatting code or your designer file contains complex formattings while inserting rows, more memory will be used. I think your service provider doesn't allow your program to consume so much memory.


#6

Well, our new designer file has the same content like the old one and it does work! I think this does not correspond to your explanation.

The application does only insert the data and no other formatting tasks.


#7

If you changed your designer file and now everything is OK, I have to say this problem may relate to the old designer file. Could you post the old file here?