I have SP webpart for importing budget items in SP List. For some 4000 items it took about 3-4 minutes (it do some custom checking, parsing and importing) to import that (on my dev pc). But if I start that import on my production test server he start to import, it manage to import about 2000 items in list(in about 2 minutes), and than unexpected exception occur. Log say
"System.Web.HttpException: Request timed out."
I looked into IIS to compare setting(app pool,web application) between my pc and server. They are same. Then I looked in web.config to check executiontimeout. Web.config said:
<httpRuntime maxRequestLength="2097151" executionTimeout="3600" />
which should be more than enough (2GB, and 60 minutes). Please any suggestion why webpart goes to timeout, when he is able to connect to SP, to read input files, to insert half of records in list?