during the installation of SplendidCRM, the Configuration Tool connect to our SQL Server 2005 (Workgroup Edition).This is done successfully, and the database dump begins.But *every* time, this process times out, and the wizard complete itself with errors, saying "Processing XXXX: Timeout expired".To resolve this issue, we re-run this process, and doing so a few times, sooner or later the process finish correctly without a timeout.
This is clearly a workaround: do we have to modify something in our configuration? If yes, what?If no, do you think you'll resolve this bug?
Cheers,Matteo
It sounds like you need a faster computer. For our part, we can increase the command timeout in the configuration wizard. ADO allowed you to specify the command timeout in the connection string, but I don't think that ADO.NET does, otherwise I would make that suggestion.
If you have the SQL Source Code, the other thing you could have done is used Query Analyzer do run the Build.sql script.
Uhm, I don't think so. I think our 3 Ghz, 2 GB ram development server is enough, or I'm wrong? :(
Thank you,
Matteo
Update: yes, we've found a pattern.We have repeated the installation in different load conditions, and the result is always the same.Having nothing installed, the first time you launch the installation process, the wizard has the "Configuration completed with the following errors" screen with this message:
"Data\TERMINOLOGY en-us.2.sql ... Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."(please note that this is unrelated with our request of italian language pack).
You have to note that the wizard doesn't stay a lot of time writing the Terminology, but a lot of time instead in the previous step, "Shortcuts module.2.sql"
Hope this helps,
Your server seems fine. We suggested the server hardware because the only time we have seen this error is on a underpowered machine running SBS.
The shortcuts file is not large and is not dealing with a lot of data, so it is odd that it would take a long time to run that step. The Terminology file is very large and is likely the location of the timeout.
On a side note, we do have to break-up the Terminology file for Oracle and DB2 as they both caused regular timeouts.
