Thread

It’s the first time I’ve been asked by a client to run EE on an IIS server, and everything seemed to be going well…

It’s an old site, running 1.7.0, and is running on IIS7.5. Everything has been copied over, and the db installed successfully.

The problem
It’s possible to edit existing entries that are already in the db, but it doesn’t seem possible to add new ones.

What happens is after making the new entry, and hitting submit, I get returned to a white screen in the Edit window.

I think this has to be a server issue, but don’t even know what the question is to ask!

Is there anybody out there that has had this problem, or any idea what might be the issue?

Many thanks
A

Well, the question to ask is: will your client provide you with another box, instead of IIS? I’d rather be a garbageman than try to deploy EE on MS Server/IIS again, or try to implement apache/php on it.

I spent a goodly amount of time trying to hack MS Server and IIS into submission, and burned up a lot of uncompensated time. Unless you are a wizard at MS Server and have a good feel for EE’‘s needs, you might end up feeling like Don Quixote like I did. Solve one problem, then another crops up. Then another…

Fortunately I got the client’s CTO (of a mid level hospital) to wipe the MS Server and install Red Hat instead, before we took the site live.

Maybe not the answer you wanted to hear, but…

Believe me, wildrock, I got force screaming into this one.

But good news, it’s all to do with the server install, not EE, even the older version this site is running on.

By default, MySQL gets installed on IIS with some status called ‘strict’. Today, the hosting company have relaxed this (I can’t remember the exact name for the status it’s on now). And the client can now add new entires just fine.

But I know what you mean, just waiting for the next thing to fail. (Good news is I am trying to convinse them on a new site, and we can burn this one to the ground).

Thanks for the post…