|
Hi there,
We need to set up a series of individual C1 websites on a Virtual Private Server which is based upon Windows Server 2008, IIS 7.0 and, naturally, .Net Framework 4.0.
The solutions/websites are reached via a series of sub domains such as
clientname.yourcms.com.
The websites themselves seem to function just fine, however, that is not the case with Composite C1 CMS itself. After a slow login process, the application simply stalls while displaying 'Working' in the status bar. The mouse etc. works fine, but there is
absolutely no contact with the CMS, which has apparently become frozen or stalled.
Clicking the 'Content' tab and attempting to open a page for editing is all it takes to induce this 'comatose-like' state of the CMS. It is, however, imperative that we get this issue solved, as we intend to make numerous client solutions available this
way during the development and proofing process prior to the actual deployment.
We have actually experienced this problem on two separate VPS-solutions; one based on Win.Server 2005 and IIS 6, and our current setup based on Win.Server 2008 and IIS 7. The exact same situation occurs; the websites seem to function fine - but the CMS stalls
after just a few seconds.
I really do hope that someone can find a solution for this. Thank you in advance. :o)
Best regards,
Tom/InHouse
|