March 04, 2010
First I would like to thank you all for your feedback so far. Almost 130 downloads within 3 days is quite impressive for such a solution.
And although just released it was necessary to already patch a small bug. Cleaning up the code close before publishing the first version created a small bug that will cause an error on the access role evaluation. Sadly this affects all non-admin users configured in the frontend so it’s highly recommended to implement this patch. Luckily it’s enough to replace a single dll (MaikKoster.MDT.MVC.dll) in the bin folder of the FrontEnd. Find the download on CodePlex. It brings the FrontEnd to version 1.0.1.
Additionally a second download has been made available. It turned out that it was necessary to create a specific version for 64 Bit systems due to some libraries used for database access that need a special 64 Bit version.
Some general recommendations on Troubleshooting
- Make sure you have the .Net Framework 3.5 SP1 installed. Be aware that it needs to be enabled as a “Feature” on Windows Server 2008 R2
- Make sure you have IIS with ASP.Net Support configured
- On IIS 6 you need to configure Wildcard mapping. See the Installation Guide for details.
- Disable anonymous authentication and be sure to enable Windows authentication. It might be disabled on default installations of Windows Server 2008
- Configure a specific account for the IIS application as described in the Documentation. On any problems add this account to the group of local administrators before any further troubleshooting. Permission problems constitute in weird error message not directly targeting to this. If the error does not occur after that you need to spent some time on getting the permissions right. I will add some general recommendations to the Installation Guide.
- If you try to configure the Database connections via the Admin – Configuration tab it might take up to a minute to open this page. This should happen only if you have a Database server configured that can’t be reached at that moment. If it doesn’t show anything at all try to open the page http://localhost/YourFrontEndName/Admin/configure (while replacing YourFrontEndName :-) ). This should show you more information on the error happening. So far in most cases where this issue happened, it was due to disabled Windows authentication.
If more common issues arise I will update this post and also place a copy to the Installation Guide in the Online Documentation.
Sorry for any inconvenience caused and I appreciate all the help I got so far troubleshooting these issues.
Comments