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 ...Important: DNN Developers please read: Installation issues 4.4.0 error - Discussion and findingsImportant: DNN Developers please read: Installation issues 4.4.0 error - Discussion and findings
Previous
 
Next
New Post
11/27/2007 10:40 AM
 

Yes, it should not be this hard.  But think about it from our perspective.  We only have your limited problem description to try and identify the issue and correct it, whereas you have access to the actual server.  While I can play 20 questions to try and narrow down the problem, this is a crude way to do troubleshooting at best.  At the same time, think about the complexities of all the possible database configurations and what the testing regime would need to look like just to test the database installation.  This is why in Open Source projects we must rely on the community to help identify issues. 

Even once an issue has been identified, like lack of support for Case Sensitive collations, the correct solution is not always available.  I could easily make the changes to make DNN work in case sensitive environments.  It would take less than a week worth of work to make the actual changes but I would likely break every existing module and DotNetNuke website in the process.  Most modules are not coded and tested to work in a case sensitive environment.  Clearly that is a decision that should not be made lightly.  We have to weigh the benefits to a few users  versus the disruption to the broad community.  This is certainly a candidate for inclusion in the next major breaking release which may well be in the Cambrian timeframe.


Joe Brinkman
DNN Corp.
 
New Post
11/27/2007 11:23 AM
 

Solyad wrote

Did further testing.

Correction on my first post. I finally found out the overall collation of the server I was working on - its Latin1_General_BIN.
Seems this is case sensitive and is the route of my problems.  

I can not install onto this box and as its the main development machine for our group this is a major issue. It also can be an issue deploying third party.

You should be able to create a new database and set the appropriate collation w/o issues.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/28/2007 9:57 AM
 

Understood Joe

What would be great is if you mention this restriction somewhere nice and clear on the site as I had no idea what the cryptic errors were and a quick google search shows Im not the only one.

Is it listed as part of a "Systems Requirment" anywhere because it really needs to be.

A simple note saying the Sql Server db must be case insensitive.

 

Now I understand the limitation I can try seek ways around it re: seeking a 3rd party hoster or internal resources..

Also Sebastion you mentioned setting an individual db on the Latin1_General_Bin server to a case insenstive collation but Im still running into issues. Im going to keep digging to see if I come up with anything.

If I do Ill post back in case its useful to ye.

 

 

 
New Post
12/8/2007 2:07 PM
 

I guess your remark about c# means that Dotnetnuke is a acse sensitive environment despite a remark earlier from Joe Brinkman.

My issue now is if io should continue and stay at 4.3 or find other platforms where i don'meet these issues. This is determined by the movement of solving this. I am hung up to a provider (Webstekker) which apparantly has issues of case sensitivity. It should also always be neatly programmed since we have to rely on Microsoftplatforms. It is not uncommon that issues like this appear when going to next versions. I always try to respect case issues, if not only for readability.

Do you know if someone is solving this by rewriting the code?

Rgds,

Jerry

 
New Post
4/10/2008 11:37 AM
 

I've read through the posts.  Has anyone figured out what needs to be changed and can let us know?  I am not a programmer, and have limited experience.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Important: DNN Developers please read: Installation issues 4.4.0 error - Discussion and findingsImportant: DNN Developers please read: Installation issues 4.4.0 error - Discussion and findings


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