Perhaps the occurrence rate is directly related to the number of people installing osTicket on IIS who prefer to use Web servers that don't require hours of convoluted setup and foreign terminology. (eg, those of us installing on IIS for AD integration or some other similar reason who generally work on a *nix stack)what version of osTicket your running?
what version of
IIS your running? I'm guessing now that you told me that your running
Windows Server 2012 that its 8.0, but it could be 8.5.
you have not provided us with your web.config file (or told us if its the one we shipped with)
It's the one you shipped
Is this a new install or an upgrade? (was it ever working)
Fresh install. No, upon copying the files into a fresh website container, the site is completely inaccessible.
Have you tried removing the web.config like the post you mentioned (http://forum.osticket.com/d/discussion//configuration-error) suggested?
Yes, I've renamed it to web.config.bak however this breaks any kind of pretty URL functionaliy intended to be used. I'm up and running now though, and while pretty URLs would have been nice, we'll survive I think.
I found 4 unanswered/sub-par solutions. The issue is common enough that there should be a Wiki page to resolve it (not just a band-aid solution). I hate Windows, Microsoft, and everything in between, so I don't know how to resolve it, or I would have gladly contributed this Wiki myself. (We need AD integration, thus the Windows based osT install.) Don't get me wrong, M$FT support is pretty crap, and partly to blame as well (we spend thousands and thousands of dollars on licensing, and software, and more licensing, and they STILL want money to answer questions about their sub-standard products).
Yes, I've seen the Wiki, it's next to useless sadly. (5 topics, each of which provides hardly enough information to actually be useful).
You're not my scapegoat. It's not your fault the people behind this project care more about getting commercial support licenses than providing up-to-date documentation (unless of course you are the people behind this project. But still, it doesn't make you my scapegoat, nothing I've written has been unmerited or otherwise untrue). You just happened to be the person reading my rant. I get that this is OSS, but if they expect people to pay for something they have to give me a reason to pay for it (we typically just donate money/resources to these projects, providing the OSS license is one we approve of). And by reason to pay for it, I don't mean making it so hard to find an answer to a problem that you HAVE to pay for it. (We ditched ZurmoCRM like a bad habit for this very reason. We loved everything else about it, but the documentation they did have (and it wasn't much) they wanted you to pay for.)
I spent several hours trying to find a solution to this on these fan sites, by searching this forum, with Google, etc. The best I could find was to delete the web.config.
And yes, while I can appreciate the forums are free of charge, proper documentation would have quite possibly eliminated the necessity of these forums for me.