DotNetNuke

Re: Installation on Win 2003 Dedicated Server

IcthusTech — Tue, 04 May 2004 12:54:29 GMT

Problem Solved....
When using the control panel to create a site, the CP created a virtual alias to /admin. Any calls from DNN to the /admin location were going to the CP /admin. Changing the CP to use "WebAdmin" fixes the problem.

Re: Installation on Win 2003 Dedicated Server

AZweb — Mon, 03 May 2004 16:38:58 GMT

I have not tried 2.04 yet but I know 1.0.9 & 10 and 2.03 all run without a hitch on 2003.
They all setup in minutes on the first try for me anyway.

See my quick step by step I made up at DNNFAQ's new site under constuction at DNNFAQ. Sorry about the colors, I have been working with my new skin layout.

Try clearing your cache and cookies or at least find the ones for the sites you setup. They may be messing with changes to your web config settings. This has happened to many other before if you search the forums for addition posts on this subject.

Keep trying...

Tom

Re: Installation on Win 2003 Dedicated Server

IcthusTech — Mon, 03 May 2004 16:29:24 GMT

Thanks Chris, I have not. I will need some direction for that.

Re: Installation on Win 2003 Dedicated Server

cjsmitty — Mon, 03 May 2004 16:19:03 GMT

I have over a dozen different web sites running on W2K3 without any events.

It would appear from your error that the portal table is not being updated on the initial DB creation. Have you tried to access it or create the initial instance via your IP address?

Re: Installation on Win 2003 Dedicated Server

IcthusTech — Mon, 03 May 2004 16:09:17 GMT

I have tried a few other installs using sub-domains, new db's etc. This is not a db connection issue, each time the db tables and sprocs are created, but after that process I am returned with the same error as above.

Does anyone else have DNN 2.04 running on win 2003 server have any ideas?

Re: Installation on Win 2003 Dedicated Server

IcthusTech — Mon, 03 May 2004 13:31:59 GMT

Nik..
-This is a fresh install of 2.04
-The webconfig db strings must be correct because it does populate the db.
-mysite.com is there for illustration purpose only the url is resolving correctly.
-There are no skins
-As this is a fresh install there is nothing being loaded becasue I can't get past this point.

Thanks

Re: Installation on Win 2003 Dedicated Server

cniknet — Mon, 03 May 2004 13:28:31 GMT

Is this DNN 1.x or 2.x?

Some things to check:

- You did not make any mention of web.config changes. Did you change the default provider to SQL?
- Is http://mysite.com the URL used for installation? Does your "control panel" update the alias field for the portal with the URL you are using?
- Is DNN2.x - are you using a skin? There might be a problem with the skin.
- Are there any modules on the tab? One of them may be producing the error.

Nik

Installation on Win 2003 Dedicated Server

IcthusTech — Mon, 03 May 2004 13:00:20 GMT

I would like to install several DNN sites onto a dedicated Win 2003 Server. The sites and directory structure are created using a control panel. After creating a new site with the cp, I go in and edit the permissions for the www (root) folder of the site to allow full control of User "Network Service", create the SQL db and give the userid dbo permissions.
After navigating to the default.aspx page the database is created but once the site tries to open I receive the following in my browser window:

An unhandled error has occurred.

The address string in the address bar is as follows:

http://mysite.com/Default.aspx?tabid=1&error=Value+cannot+be+null.%0d%0aParameter+name%3a+child&content=0

Can anyone point me in the right direction?

Thanks for your help!