DotNetNuke Installation

  • Thread starter falconinternetlimited
  • Start date
F

falconinternetlimited

Hi,

Does anyone have experience of installing DotNetNuke? I'm having an issue installing it and could do with just running a couple of questions by someone to make sure I'm not being over stupid.

Thanks a lot,

Rupert
 
F

falconinternetlimited

Hi,

Thanks for your responses. I have now tried to install both core 4 and core 3.3 to no avail. I'll continue with 3.3 because I think it is more likely that I can get that to work.

Anyhow, I have renamed release.config to web.config and amended the database line with the database name, UID and password.

Do I need to do anything else. I thoughts going to the root url would effectively start the installation process?

Thanks again,
Rupert
 
Upvote 0

Spire

Free Member
May 31, 2005
170
0
It's a while since I did it but don't u need to create a empty database in Sql Server
Then ammend the web.config to point at that server and database, I notice from your aboue post u did not mention setting the web.config connection string server address.

The other thing I can think of is that u will need to give the directory where the installation is to go full read/write permmisons during the installation, and ensure that ASp.Net has full read/write permmisons to the directory.

When I tried to install it on my host's servers I had to open a support ticket for them to set the permmisions during installation, then they reset them afterwards.
 
Upvote 0
F

falconinternetlimited

Hi,

Thanks for the response. I have created the MSSQl database, the details of which I put into the connection string within web.config. I have however only changed 1 line in web config. Is there more than 1 line that I need to amend?

Thanks again!

Rupert
 
Upvote 0
Spire said:
The other thing I can think of is that u will need to give the directory where the installation is to go full read/write permmisons during the installation, and ensure that ASp.Net has full read/write permmisons to the directory.

Once you've edited the web.config file thats pretty much it, but as Spire mentioned above, make sure the directory has the correct permissions. Only other thing I can think that could effect things is the Framwework being used by your host, if you have gone for 3.x that should be fine with pretty much all ASP.NET enabled servers as it uses 1.1
 
Upvote 0
F

falconinternetlimited

Hi,

Thanks again for your esponses and help. Things have "moved on" but I am now getting the following error...

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

It seems a bit odd because I'm not upgrading....?

Thanks again,

Rupert
 
Upvote 0

Latest Articles

Join UK Business Forums for free business advice