Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...web.config settings for Sql 2005 Express and DNN4  - HELP!!!!!!!!web.config settings for Sql 2005 Express and DNN4 - HELP!!!!!!!!
Previous
 
Next
New Post
12/2/2006 6:19 PM
 
sm --

Looks like you have an XML tagging error in your web.config . You need to move two dashes, and a right-facing arrow.

I have posted a photo of this for you on my site at:
http://www.commonmancomputing.com/xml_001.jpg

Then try that.

Thanks,
Travis
 
New Post
12/3/2006 9:22 AM
 

That did it! 

I'm currently using notepad to edit my files.  I don't really use Visual Studio, but would it have caught this?  What other editors would you recommend for this type of stuff for non-programmers like myself.

Thank you for your help!

- Mark

 
New Post
12/3/2006 1:31 PM
 
Mike,

I use Notepad for all my editing as well. I don't know the first thing about Visual Studio, and in fact, I only learned to look for that particular XML tagging error five minutes before I posted the fix which eventually worked for you. Heck, I didn't even know to call it an "XML tagging error" and in fact my use of that term may not be correct.

My biggest criticism of DNN is that it is not immediately friendly to the non-programmer (like myself, and you). An example would be your posts. I've noticed 12+ hour long wait times for your (smsolutions') posts to be approved, so that I could read them, and reply to them. I can see that you have replied, but the actual content of your reply isn't visible until a moderator approves it. Generally I have to go to sleep and wake up the next day before I can read such posts.

Thanks,
Travis
 
New Post
12/3/2006 3:44 PM
 

I thank you for your help none the less, it saved the day.  I was very impressed with the "XML tagging error" defination you used, especially now that I know you're a non-programmer   We non-programmers need to stick together!

I have to agree with you on your comments about both post approval times ever since the forums were moved into the site and general friendliness of the product.  It seems, IMHO, ever since the 3x and 4x split came about the focus on end user ease-of-use just isn't there as much as it used to be, the developers are focusing on the technical aspects of the code - and there's nothing wrong with that, as you need a strong framework - but the ease of use of the product has suffered.   I always found better support - and don't even get me going on the searching - in the ASP.NET forums and while I understand why the core would want to move everything over to their own forums engine, I think they're forgetting the fact that they are providing the framework which allows 3rd solutions to be built upon.  It should be a compliment, and not a threat, to them that there are other rock solid forum engines out there that would much better suit the community.  (Heck, let's see if this post even makes it.).  But I digress...

I used to be a die-hard DNN evangelist.  Today, however, not so much anymore. 

Thanks again for your help, it's much appreciated.  If you ever want to throw ideas back and forth you can always reach me through portals.smsolutions.com.

- Mark

 
New Post
12/3/2006 5:46 PM
 
Actually, now you have 2 SiteSQLServer settings under connection settings, and the .Net is just using the last setting.  In reality all you had to do was to make a simple change to you SQL Express connection string.  Instead of using the Initial Catalog, use Database instead.  This makes it similar to the connection string you are now using except for the use of (local) as the DataSource.  If I were you I'd change it to be .\SLQExpress (or whatever the SQL Server name is on your computer.  There are some instances that (local) does not work and there have been many post about it.

<add
     name="SiteSqlServer"
     connectionString="Data Source=.\SQLEXPRESS;Database=dnnDB;uid=dnnUser;pwd=dnnUserPassword;"
 providerName="System.Data.SqlClient" />

At the very least you should do the following

1) Make sure the extra connection string under <connectionString> section is commented out.

2) Make sure you are using the same connectionstring that you are using in <connectionString> section is being used in the <appSettings> section.  This is more for consistancy.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...web.config settings for Sql 2005 Express and DNN4  - HELP!!!!!!!!web.config settings for Sql 2005 Express and DNN4 - HELP!!!!!!!!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out