Just wanted to share a tip while moving a very large board from linux Apache to windows IIS6.
The Apache box was on another host, so I had to pull down the .sql backup from the server to the windows box and import the .sql db in mysql (mine took about 3 hrs to do that, as unzipped it is a 7.9gb db)...
Installing 3.6.10 fresh and importing from 3.5.1 to 3.6.10 using Impex was going fine until I hit the tables that were over a GB... FastCGI would come back with a "time out" error. The key is a setting in the fcgiext.ini file. At the bottom after you declare your application type (php) and the path, add in:
ActivityTimeout=28800
28800 seconds is about 8 hours - should be plenty of time for a big board with big tables!
Here's a thread about FastCGI timeouts on iis.net:
HTH
PS Thanks to Christian Evans for helping me out with this and of course the vBulletin support team
The Apache box was on another host, so I had to pull down the .sql backup from the server to the windows box and import the .sql db in mysql (mine took about 3 hrs to do that, as unzipped it is a 7.9gb db)...
Installing 3.6.10 fresh and importing from 3.5.1 to 3.6.10 using Impex was going fine until I hit the tables that were over a GB... FastCGI would come back with a "time out" error. The key is a setting in the fcgiext.ini file. At the bottom after you declare your application type (php) and the path, add in:
ActivityTimeout=28800
28800 seconds is about 8 hours - should be plenty of time for a big board with big tables!
Here's a thread about FastCGI timeouts on iis.net:
HTH
PS Thanks to Christian Evans for helping me out with this and of course the vBulletin support team