I tried to install SplendidCRM on a Win2003 std and kept failing trying to download Dotnetfx. Obviously it did not assume that .NET is already installed on Win2003.
Anyway made a one machine installation (Sql2000 dev ed, IIS on an XP sp2) and succeeded. I then tried to install using a remote SQL2000 database and succeeded as well. Finally I tried to move the web site to the server. I copied WebSite directory to the server and created a virtual directory 'Splendid' pointing to WebSite. I received a web config error about 'enableEventValidation'.
Is there a proper documentation on installing to different IIs and SQL machines?
Also on the one box installation I did not get a logon screen. How will this work on a multi-user server environment?
.NET 2.0 is an optional install on Windows Server 2003. We have tried to cover all the bases with our install, but you can make things go quicker by ensuring that .NET 2.0 is already installed as well as IIS. I cannot explain why the download would fail. The download of .NET has never failed for us.
The issue with enableEventValidation is likely because the virtual directory was not configured for .NET 2.0. Our install does this automatically.
SplendidCRM defaults to Windows Authentication. This works very well on a Windows Domain, but if you wan to manage users within SplendidCRM, simply modify the virtual directory to allow Anonymous users.
New problem! After installing .NET 2.0 everything seemed to be ok. Because of some other .NET 1.1 applications running on the same server I created a separate application pool for SplendidCRM and I thought that I was a genius!
A couple of hours later the application presentation started to display the internal names of the fields instead of the lables. 'Activities' tab displays .moduleList.Activities, 'Last Name' in Contacts displays "Contacts.LBL_LAST_NAME.LBL_REQUIRED_SYMBOL" etc.
What can be wrong here?
Also how can we provide more options in users/language and date format?
When you have both .NET 2.0 apps and .NET 1.1 apps, you do need to use separate application pools.
Typically, when the terminology does not display the text properly it is either a bad database connection or an unsupported language. You can import SugarCRM language packs to solve the latter issue.
We display all available date formats for the selected language as provided by .NET 2.0. Is the reason why you want more date formats because you are not in the US? If so, then the solution is to import the appropriate language pack or create the appropriate language pack for the desired culture.
