Last post Mar 01, 2006 07:31 PM by BugInfested
Jun 16, 2005 10:36 AM|travislaborde|LINK
Jun 16, 2005 12:28 PM|michealobrien|LINK
Jun 16, 2005 01:30 PM|travislaborde|LINK
Thanks for the reply, but.... How can I "login?" Perpahs I failed to mention that the site won't "come up" because of the localhost reference. The server has many domains loaded, and localhost may not be pointing at "this" one.
Jun 17, 2005 05:49 AM|michealobrien|LINK
Jun 17, 2005 06:12 AM|sonapappu|LINK
Jun 17, 2005 06:27 AM|aaava|LINK
Jun 17, 2005 07:27 AM|travislaborde|LINK
Jun 17, 2005 07:54 AM|michealobrien|LINK
Jun 17, 2005 08:01 AM|aaava|LINK
Jun 17, 2005 09:35 AM|travislaborde|LINK
Yep, that's exactly what I did. "Normal" ASP.NET deployment. I never imagined that this sort of thing would happen. I mean, heck, isn't one of the reasons we write web based software because of ease of deployment? Copy the stuff to the server. As long
as you have a virtual directory, and your code can find the database, you're set.
This just seems to be so unfriendly to the "development machine", "testing machine", "production machine" process. I wonder if you can "trick" the process with some creative entries in the hostnames file :) Ugh, did I even say that?
Thanks for all the help!
Jun 17, 2005 10:05 AM|jbrinkman|LINK
Make the entries in your local version of the Database and go through the backup/restore steps you took to install the site the first time.
One of the best things people can do when working with DNN is to try and understand the database. It is pretty straightforward for many cases and I have found that a lot of problems that get posted to the forums can be solved with a simple DB script. Sometimes
it is corrupt data, sometimes a feature is not working right in the software and sometimes it is just easier to make the entry in the db rather than try to find a way to accomplish the feat in the UI.
Jun 17, 2005 10:10 AM|J7Mitch|LINK
Jun 23, 2005 10:09 AM|travislaborde|LINK
Mar 01, 2006 11:51 AM|BugInfested|LINK
I've installed DNN 4.0.2 on my localhost, but created the SQL Server database on the remote server. Everthing worked good.
I copied all of my DNN files using Visual Studio 2005's "copy website" to the remote server (because when I try to build/compile, it failed due to HTML and other errors).
I added "mydomain.com" as a Portal Alias. However, when I try mydomain.com on the browser, I'm redirected to localhost. Does anybody know why this is happening?
I've also used SQL Server Management Studio to reverse the order of the aliases. (put "mydomain.com" into PortalAliasID 1's record and put "localhost" into PortalAliasID 4's record). When I try to access mydomain.com on the browser, it hangs. There is
no response from the remote server.
When I delete the alias and only have "mydomain.com" in PortalAliasID 1 (PortalID 0), it still hangs on the browser when I try to access mydomain.com.
Does anybody know why this is happening?
Mar 01, 2006 07:31 PM|BugInfested|LINK
Please disregard my last post.
I created a new domain through my ISP (hoster)'s control panel when I deployed my DotNetNuke.
I just found out from my ISP that the .Net application had to be re-added for this new domain.
I did what my ISP told me to do and now it works fine.