Hi

I've signed up to a hosting package with SeekDotNet.com, I installed DNN and it was working fine.  I then tried to make some admendments to the 'profile.ascx.resx file for some extra field descriptions I'd added in for user registration,  It all went wrong after this.  I could log in fine but when I went to the admin menu and select any option I get a runtime error. As shown below.

I'm just waiting to get the friendly error message option switched on to get a better idea on whats causing this. 

I have tried to reinstall DNN a couple of times, as have SeekDotNet but still get same problem.  I have also dumped all IE cookies etc.....

Has anyone else come across this problem?

I would like to add that SeekDotNet have been excellent in helping to look into this problem, and I'm very impressed with their overall service and speed so far.  I'm just looking for a 2nd opinion/voice on what might be causing this.

  Any help welcome.  Thanks DanDescription: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Server Error in '/admin' Application.

---

Runtime Error

Hi Gabriel

I posted this with several sites that I visit for help, but seemed to draw a blank everywhere....

My providers worked very hard to solve it but even they seemed stumped.  They ended up moving my domain and database to a different server, and then reinstalled DNN again to the latest version.  That did solve the problem.

From my own workings I tired to address each error in the config file, but it always got replaced by another...I wonder if the version of DNN I was using has a bug in it, that  leads to problems when you install it onto your hosting space more than once...

I'm not really an expert, sorry I can't help further.

Dan