I am trying to download setup DotNetNuke on my development PC, which contains IIS7 and SQL Server 2008. I have followed the instructions here: http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/19/View/Details/How-To-Install-DotNetNuke-On-Your-Computer.aspx.
When I navigate to localhost nothing happens. When I navigate to this page in Firefox it says: Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
I have looked at lots of post entries and tried different things. This looked promising but did not help: http://www.dotnetnuke.com/Resources/Forums/forumid/107/threadid/180233/scope/posts.aspx.
Most of the suggestions seem to be for developers that are upgrading websites. Is there a log file anywhere that can tell me exactly what the problem is?
The logs can be found in /Portals/_default/Logs .
You can increase the log sensitivity by editing DotNetNuke.log4net.config. Use
<level value="All" />
for the most detailed log messages.
<level value="Error" />
may also work if All provides too much info.
Related
A weblogic application which is working fine, But on redeploying the .EAR file an error arises mentioning that .EAR file are already existing. On viewing weblogic console menu deployed, It shows no deployed .EAR.
Missing EAR File from Console Menu
This is peculiar, according to you, the application is working fine if that's the case then there should be something deployed on the server, but from the pic, I can't see anything.
This could probably because of the customize table option, it could be possible that you wouldn't have selected any of the available options.
If this problem arises after redeploying, then there is something wrong with the redeployed .ear. If by redeploying, you have just updated the .ear then it's mostly a problem with your .ear, if you have deleted and re-installed the .ear then you should probably check your config.xml file before and after the redeploy. And do check for your server logs when you are redeploying the .ear, that in itself should give a great deal of info.
Please do update your question with the server logs so that it would be easy for me (or others) to debug and help you out, and give an appropriate answer.
I am configuring my Production Version DNN on other machine, but it is always redirecting to the installation wizard page.
I have googled over it and tried below mentioned solutions.
re-checked database connection
re-checked database is not corrupt.
tried to change below settings to false. by doing so, its redirecting to Install/UnderConstruction.htm page.
Can anybody help me to find solution for this issue?
If you navigate to /install/install.aspx what displays on that page?
I would be willing to bet money that it says the database connection fails, there is something you are missing in your DB setup, or connection string, that isn't working properly.
I'm having an white screen of death when trying to debug my silverlight application. The problem is that I don't know what causes it and I don't get any type of information from either Visual Studio or the browser itself (IE9). Breakpoints won't be hit as App() in the App.xml.cs doesn't get fired either.
The application works fine on my own laptop, but I'm trying to make final adjustments to it on the server which will host the application once it's done. The problem occures on this server.
Would there be any way to get information about what's causing it or did someone experience simulair issues?
hit F12 in IE and go to network and start capturing. You should see your error there if something went wrong downloading and also if there was a problem with the Silverlight plugin (check Console or Script tag).
There could be a number of reasons for this including problems with database connectivity, WCF services, and many other factors. One thing that might help you get some information is a product called Fiddler. If you are able to download and install that on your development machine, you can have it running when you try and access your application on the server. It will give you messages for every step of your application initialization, including database authentication, service authentication, the xap file transfer, etc.
My problem was related to init params not loading up from the web project's .aspx page, try having a look at this if you are having "white death screen" issues.
I'm running into this problem and its driving me crazy.
Also, we are not allowed to update the version of IIS.
The content on the server (asmx files holding WCF webmethods called via SOAP) exists and I can freely browse in inetmgr to the virtual directory that contains this data. The files all exist all on the file system and the virtual directories all point to the correct spot and have the correct ACLS, but when I go to their URLs all I get is a 404 message.
I have reset IIS, I have rebooted the server, and I have done everything I can think of.
The IIS logs simple return "404 - -" as the entire line contents, with no other data in the line.
The event logs show nothing, and ASPNET is not dying or anything like that.
With no event logs, and minimal logs in IIS , I have no idea what to do and was hoping that others had run into this before.
In IIS logs there should some codes along side the 404 error which will help find the issue.
Check IIS has the correct version of .Net installed using aspnet_regiis command line tool. Also check that ASMX extensions are mapped to the .Net ISAPI filter as they are with ASPX pages.
I hosted one DotNetNUke Application to my production server, and locally it works perfectly. But, when browsing it redirects to the error page.
How do I set the default.aspx as my application default page? I am getting the error as below:
DotNetNuke Error
--------------------------------------------------------------------------------
Windows Vista
Return to Site
Can anyone can help me, please? Will be appreciated.
UPDATE:
Hi, I changed the Path in the PortalAlias table to the server url and default.aspx as the starting page, but it displays the error.aspx as default page.
Please help me resolve this problem..
So, the application works perfectly locally, but not when you put it on the server. Is that correct?
Make sure that your portal alias is valid. If the site is hosted at
http://www.mysite.com
then www.mysite.com needs to be listed in the PortalAlias table
If you open that table in SQL Mgmt Studio, you'll probably see an entry attaching the portal to your local DotNetNuke folder (ie. localhost). Just add a new entry that points to the same PortalID, but with the correct URL for your production server.
Assuming your DNN installation is at "mysite.com", if you navigate to
http://www.mysite.com/default.aspx
do you still get the error page? If so is any error listed?
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have to correct machine key and connection strings. This is my last resort something is really strange procedure.