I am new to DotNetNuke and we are attempting our first site. So it is very possible I am missing something obvious. When I login using my superadmin account, the super admin menu bar that is supposed to show at the top (according to the videos) is not there. I have a drop down box with edit, layout and view, but that is it.

Any thoughts?

TC

Which version of DotNetNuke are you using?

Is this newly installed?

Did you notice any error messages during the installation process?

If the site is on the internet, would you be willing to share the URL?

Yes, it is a brand new installation. I just went through the godaddy install process again, thinking it may have gone south the first time. But, the second time around I am getting the same issue. The new install is located at www.business2mobile.com/app.

Also tried logging in on three different PCs, using IE 8 and 9, Opera and Safari, and using the administrator account thinking I may have mixed up the login credentials. Same deal.

Thank you,
TC

If you'd like to send me the host username and password, I'll see if there is anything that I can see. To do that, use the Contact form at patapscorg.com. Please don't post it.

Okay, I sent the details via the contact form on patapscorg.com.

There are other things missing. The text "Manage" on the floating menus isn't there. Some other text is missing.

Interestingly you can get to Host.aspx and Admin.aspx if you enter the URLs manually.

I think that there is an update button missing on the Host Settings page. There may be more.



So ... the next question is: how did you install this?

This was done via the application manager interface provided by GoDaddy.

I would recommend that you check with GoDaddy's support department. There's definitely something wrong with the installation, but it's difficult to diagnose without access to the web directory and/or database. They should be able to check it out.

After loggin in, I notice that the site opens in the login window rather than closing an reopening the site in the main window. That's something else that should not be happening.

If you have ftp acccess to the root directory of the application, you could try comparing the directory/file contents with the install package. That might help you see if anything really is missing.

I would normally also suggest looking for file permission errors, but I don't see any errors being logged in the Event Log, so I don't think that is a problem

Here is a wild guess at something to check: please check your web.config and make sure debug is set to false (theres a known issue in 6.0 caused if it is set to true - this has been resolved in 6.0.1)

Debug is set to false. I also consulted with godaddy again but to no avail. I have opted for a manual install using the install package from the dnn site. So I have created a new database folder and using the existing web.config file, configured the connection strings on the new web.config file. When I go to the site, I get an error stating:

Runtime Error

Description: 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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

This post is stripping out the rest, so to see there error, simply visit: http://business2mobile.com/dnn/

I have looked through every line in the web.config file and cannot find that code. Where is it located? Is it something I need to add? At least that way I can see what the problem is.

Seriously... thank you for trying to help here. I dont think godaddy should offer an install package if it is defective.

TC

When you do the manual install, you do not have to do any edits to web.config. Just create a new empty database, and browse to the site. The installer will start and prompt you for database credentials. It's much easier and less prone to error that way.

So, my recommendation is that you start again.

To fix the error you are having, search for "customerrors."