i am new to dnn. i downloaded the 4.0.2 version. i have .net framework 2.0 on my system. i unzipped the zip file for dnn into c:\dotnetnuke and followed the steps in the "read.me" file. encountered 2 problems right off the bat: first, the instructions instructed
me to create a virtual directory in iis and point it at the directoy which contained the .vbproj file. only problem was.....i did a search on the entire file structure and that file wasn't in it. 2nd problem is that i can NOT get the web.config file set up
correctly. it's just not clear to me what i need to do.
is there a STEP BY STEP "for dummies" manual somewhere which i could use to get this thing going - one which doesn't "skip implied steps"?
also.....i loaded the app in visual web developer 2005 express and every page has about 100 errors. stuff like:
"could not find the schema information for attribute such-and-such"
There is an assumption of base knowledge that you may not have. To start, the Virdtual Directory points to where you unzipped the files. I have no idea what "can NOT get the web.config file set up correctly" actually means. Did you have trouble with the
connection string? If so, what?
I have set this up at least 10 times on multiple machines. Any problems I had were because one machine did not have enough memory. you need at least 512Megs of Ram.
Also, you can see how to set it up using the Source version here:
Make sure you have done the following settings correctly.
In SQL Server Enterprise Manger, navigate to your machine.
Under Security->Logins, select the user to whom the permission should be given for the DotNetNuke database. If you have not created the user yet, create one.
Make sure you have selected the DotNetNuke database access option for that user.
Make sure you have give public and db_owner roles permit for that user to the DotNetNuke database.
Open Web.config file
Under <appsettings> section, update the database and user parameters in SiteSqlServer key. It should look similar to this line. <add key="SiteSqlServer" value="Server={database server};Database={DNN User};uid=DNN;pwd={DNN User Password};" />
I have faced similar error on installation. The above checks allowed me to solve it.
Now I always use SQL server logons rather than Integrated Security so I don't have a database set-up that way that I can use as an example. However I seem to remember that when I did have it set up that way that I had to give ASPNET access to the database.
my memory is fizzy.
Can you set your SQL server to use "Mixed Mode" so you can use a connection like in my example?
threeo
Participant
1156 Points
539 Posts
why is this so difficult?
Dec 28, 2005 01:49 AM|LINK
i am new to dnn. i downloaded the 4.0.2 version. i have .net framework 2.0 on my system. i unzipped the zip file for dnn into c:\dotnetnuke and followed the steps in the "read.me" file. encountered 2 problems right off the bat: first, the instructions instructed me to create a virtual directory in iis and point it at the directoy which contained the .vbproj file. only problem was.....i did a search on the entire file structure and that file wasn't in it. 2nd problem is that i can NOT get the web.config file set up correctly. it's just not clear to me what i need to do.
is there a STEP BY STEP "for dummies" manual somewhere which i could use to get this thing going - one which doesn't "skip implied steps"?
also.....i loaded the app in visual web developer 2005 express and every page has about 100 errors. stuff like:
"could not find the schema information for attribute such-and-such"
why is that?
threeo
jeff@zina.co...
All-Star
87677 Points
11637 Posts
Moderator
Re: why is this so difficult?
Dec 28, 2005 09:15 PM|LINK
There is an assumption of base knowledge that you may not have. To start, the Virdtual Directory points to where you unzipped the files. I have no idea what "can NOT get the web.config file set up correctly" actually means. Did you have trouble with the connection string? If so, what?
Jeff
Sponge_Bob
Member
435 Points
87 Posts
Re: why is this so difficult?
Dec 28, 2005 10:13 PM|LINK
adefwebserve...
Contributor
5912 Points
1207 Posts
MVP
Re: why is this so difficult?
Dec 28, 2005 10:39 PM|LINK
This is what you are looking for:
http://forums.asp.net/1114393/ShowPost.aspx
I have set this up at least 10 times on multiple machines. Any problems I had were because one machine did not have enough memory. you need at least 512Megs of Ram.
Also, you can see how to set it up using the Source version here:
http://forums.asp.net/1123229/ShowPost.aspx
Open Light Group
LightSwitchHelpWebsite.com | ADefWebserver.com
threeo
Participant
1156 Points
539 Posts
Re: why is this so difficult?
Dec 29, 2005 12:23 AM|LINK
FINALLY
thank you man....
threeo
Participant
1156 Points
539 Posts
Re: why is this so difficult?
Dec 29, 2005 02:27 AM|LINK
i am so frustratingly close......
i have gotten all the way to where it is building the app....
but i run into a problem: i am trying to use a sql server database rather than the default sql express
all i ever get is:
DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )
ERROR: Could not connect to database.
Login failed for user 'sqlservice'.
now...2 things i don't get:
1) on the right hand side of visual web developer express i have 2 tabs:
solution explorer and database explorer
i have used database explorer to set up a connection to my sql server database and it works fine
how do i tell the app to use it? the app uses the web.config which sets up the database connection all over again (and fails)
2) why does the database explorer connection work but, using the exact same connection string inserted into web.config......the login fails?
grrrrrrr
rajkumarn
Member
165 Points
33 Posts
Re: why is this so difficult?
Dec 29, 2005 01:01 PM|LINK
I have faced similar error on installation. The above checks allowed me to solve it.
Write - Share - Earn
adefwebserve...
Contributor
5912 Points
1207 Posts
MVP
Re: why is this so difficult?
Dec 29, 2005 01:15 PM|LINK
The Server explorer in Web Develper Express is only for development not for Application settings.
You need to alter the Web.config to comment out the SQL express connection string (using "<!-- " and "-->" and uncomment the SQL part. For example:
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express
<add
name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" /> -->
<!-- Connection String for SQL Server 2000/2005 -->
<add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke4;uid=sqlservice;pwd=password;" providerName="System.Data.SqlClient"/>
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/> -->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke4;uid=sqlservice;pwd=password;"/>
Open Light Group
LightSwitchHelpWebsite.com | ADefWebserver.com
threeo
Participant
1156 Points
539 Posts
Re: why is this so difficult?
Dec 29, 2005 03:50 PM|LINK
yes i had already done that:
<
connectionStrings><!--
Connection String for SQL Server 2005 Express<add
name="DotNetNuke"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />
--><!--
Connection String for SQL Server 2000/2005 --><
add name="DotNetNuke" connectionString="Data Source=DEV1;Initial Catalog=DotNetNuke;Persist Security Info=True;User ID=sqlservice" providerName="System.Data.SqlClient" /></
connectionStrings><
appSettings><!--
Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules<add key="DotNetNuke" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
--><!--
Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules --><
add key="DotNetNuke" value="Data Source=DEV1;Initial Catalog=DotNetNuke;Persist Security Info=True;User ID=sqlservice"/><
add key="InstallTemplate" value="DotNetNuke.install.config" /><!--
Alternative Install Templates (included in package)<add key="InstallTemplate" value="Club.install.config" />
<add key="InstallTemplate" value="Personal.install.config" />
<add key="InstallTemplate" value="SmallBusiness.install.config" />
--><
add key="AutoUpgrade" value="true" /><
add key="InstallMemberRole" value="true" /><
add key="ShowMissingKeys" value="false" /><
add key="EnableWebFarmSupport" value="false" /><
add key="EnableCachePersistence" value="false"/></
appSettings>adefwebserve...
Contributor
5912 Points
1207 Posts
MVP
Re: why is this so difficult?
Dec 29, 2005 04:03 PM|LINK
Now I always use SQL server logons rather than Integrated Security so I don't have a database set-up that way that I can use as an example. However I seem to remember that when I did have it set up that way that I had to give ASPNET access to the database. my memory is fizzy.
Can you set your SQL server to use "Mixed Mode" so you can use a connection like in my example?
Open Light Group
LightSwitchHelpWebsite.com | ADefWebserver.com