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 ...Windows Web Server 2008 RC2Windows Web Server 2008 RC2
Previous
 
Next
New Post
1/27/2011 11:31 AM
 
how does your connection string look like - attachdbfilename is supported by SQL Express only.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/27/2011 2:59 PM
 
Sebastian Leupold wrote:
how does your connection string look like - attachdbfilename is supported by SQL Express only.

 I am using SQL Express on another computer in the domain.

I've tried using the IP address and computer name and it results in the same errors.

Isn't the "connection string" supposed to be generated by the DotNetNuke installer from the results of the "Configure Database Screen?"

My web.config is the same as it was when I extracted the files. I am receiving the error before it writes anything to the web.config therefore it hasn't actually been changed. Could I possible do this manually?

 
New Post
1/27/2011 3:20 PM
 
you may easily configure the connection string manually but need to take care, to keep both uncommented strings in sync.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/27/2011 3:46 PM
 
Thanks for those tips. I was able to get passed the part previously mentioned. Apparently, we are running both SQL Server 2000 and SQL Server 2005 on our server. The database I created was in SQL Server 2005 using SQL Server Management Studio Express. The snag I am getting now is when the script tries to update versions.

"Upgrading Database to Version 05.02.00...FAILURE ERROR: (see 05.02.00.log for more information)"

I've done some Google searches and found that this is an error with SQL Server 2000? However, in my case, I am actually using SQL Server 2005 which should work properly. Any further guidance would be much appreciated.

On another note how do I check these logs?
 
New Post
1/27/2011 3:53 PM
 
If the DB is located on a machine that is a member of a domain, make certain you are providing the correct credentials. and that the file system has the proper permissions.


 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Windows Web Server 2008 RC2Windows Web Server 2008 RC2


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