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.
Related
I am trying to publish sharepoint2016 website including Power View reports which created by SQL server services service (SSRS). there is top level site and bi center as sub-site; both are working fine but problem is that when I try to view the report it said the error:
"the web application at [url] could not be found. verify that you have typed the url correctly. if the url should be serving existing content, the system administrator may need to add a new request url mapping to the intended application."I search about the error but It does not reach my target.
https://forums.asp.net/t/1970799.aspx?SQL+Reporting+Service+Runtime+Error+The+item+reports+Report1+cannot+be+found+rsItemNotFound+
note that the whole site is working fine in domain.
Please help...
Thanks...
Sorry for late guys...
i found that Power shell of SP cannot execute any command related to SSRS
it just need to reinstall SSRS service compatible with SP2016. then every thing is fine.
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.
This question may be a dublicate, but no recent post leads to a working answer for my case.
I have a Sharepoint 2013 running on a Windows Server 2012. Following issue appeared:
I made a new Site-Collection as wiki. Everything (links,...) works fine on the server but when I want to access the wiki from outside (not localhost) the server runs in a 404 Not found error.
http://localhost/sites/wiki/Pages/Home.aspx - works fine(localhost)
http://10.38.0.15/sites/wiki/Pages/Home.aspx - doesn't work.
I checked the IIS settings, all servers are up and running. The log file has no errors in it.
Does anyone know, how to solve this problem?
thx
Jürgen
The most common cause for this is that you don't have the IIS host header configured correctly. The 404 will appear because you are hitting a different IIS web site and not the one you intended to.
If you go into IIS Manager and click on "Sites" in the right hand pane there will be a column called bindings and a column called ID.
IIS will check in the order of ID for the first site that matches. Make sure the default site is stopped. If you see bindings that look like the following:
ID 1: Bindings: *:80
ID 2: Bindings: www.yoursite.com:80
www.othersite.com will match ID 1. Any other site that doesn't specify a port or https: will be directed to ID 2. You need to ensure that the site you are trying to access matches your bindings. The "www.yoursite.com" is added to the site via "New Web Application" in SharePoint. There is a field called Host: in Central Administration. This should match what you are typing from inside and outside the server. If you need the site to respond to multiple names, you need to extend the web application.
Assuming you used the default of claims authentication, here are the instructions for that:
http://technet.microsoft.com/en-us/library/gg276325.aspx
I am not sure if this is still required in Server 2012, but disabling the loopback check might also help, although this usually results in a 401, and repeated attempts to log in. Here are the instructions for that.
http://support.microsoft.com/kb/896861
Сheck the alternate access mapping in SharePoint administrator.
It should be something like this:
http://yourservername default
http://10.10.1.30:80 internet
http:// so on ..
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 was given a dotnetnuke v4.9.5.5 database (sql-express about 300MB) and I am trying to get it up and running on a different server. I have tried:
Installing the 4.9 version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page...)
installing the 5.x version and
loading the database into the app_data folder
loading the database through the SQL page under the host login (forwards to 404 page... again..)
All of which fail. I cannot find any support on this topic at all. What is the correct way to go about this?
EDIT: wrong info please close..
Here is a good blog on the topic HOW TO: Move a DotNetNuke installation .
The basics are:
Copy all the files and the database, the two are closely tied together.
Update the connection string in the web.config.
Update the portal alias' in the PortalAlias table.
If you don't have the rest of the site files, it may be very difficult. While the database will contain most of the site content, you may be missing some important pieces like skin files, module files, and content files.
So, the first thing you should do is see if you can get the files zipped up and sent to you. If so, it should be fairly easy to get the site up and running. You may have to update the ConnectionStrings in the web.config but otherwise it should run as it.
If you can't get the original files, you could try installing version 4.9.5 of DotNetNuke and replacing the supplied database with the database you were given. You'll need to post the error messages you get if it doesn't work out or consult someone with solid DotNetNuke experience.