Excel Connector - Creating Excel Service from an Excel Worksheet - Internal Server Error

Thu, 11/12/2009 - 18:46
fbadrud
User offline. Last seen 3 weeks 1 day ago. Offline
Joined: 11/02/2009
Points: 30
Groups: None

Hi:

I am using the excel connector to create a service using an excel worksheet.  My worksheet has over 7000 rows of data.  When I try and publish all 7000 rows I get the following error:

"Connection with Presto Mashup Server Fail:

Fail Registering Excel Service: Network Exception: The remote server returned an error: (500) internal server error"

When  I try and publish only a subset of the data (e.g 20-30 rows) - I do not get the error, please let me know how to resolve, as the connector seems pointless if it cannot handle large amounts of data.

 

Thanks,

Farzana

0
Your rating: None
Thu, 11/12/2009 - 19:38
Copy comment link
smitchell
smitchell's picture
User offline. Last seen 1 day 12 hours ago. Offline
Joined: 08/29/2008
Points: 4
Groups: Extreme Mashup Development, Mashup Fundamentals, Mashups and Dashboards, Mashups and Portals, Mashups and SOA

Unfortunately, in 2.7.0, there is a limit to how large a dataset you can publish from Excel (which will be fixed in the next release). More than likely this error is caused because your spreadsheet is too large.

And again unfortunately, there is no work around to this. The only solution is to break up the spreadsheet into smaller files and publish several services.

 

Sara, technical writer/jackbe

 

Fri, 11/13/2009 - 07:05
Copy comment link
aishmishra
aishmishra's picture
User offline. Last seen 4 hours 42 min ago. Offline
Joined: 09/24/2008
Points: 1
Groups: None

Hi Farzana,

I cannot guarantee but you could try out the following steps to give a shot at making this work for you.

i. Increase the maximum size of a POST request by modifying the sever's configuration file as follows:

<Connector port="8080" maxHttpHeaderSize="8192" maxThreads="150" ... maxPostSize="200000000"/>

(Assuming you are running Presto on the default tomcat server that it ships with)

ii. This error could also be because of Presto Repository going out of memory. You could try to increase the available memory changing the Xms and Xmx values in server.bat or server.sh (depending on whether you are running Presto on Windows or Unix) found in the following location <presto-install-directory>/prestorepository/hsqldb/

iii. You could also try to use other more 'solid' databases like MySQL or Oracle as Presto Repository (steps for this are available in Presto Administration Documentation).

Do let us know if this helps your case.

As Sara mentioned, this issue will be fixed in the next release.