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 ...SQL 2005 connectionSQL 2005 connection
Previous
 
Next
New Post
5/30/2007 6:45 AM
 
Yes, i forgot because i dont have any idea about what objectQualifier i have to put here.

defaultProvider="SqlDataProvider">


name="SqlDataProvider"
type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
connectionStringName="SiteSqlServer"
upgradeConnectionString=""
providerPath="~\Providers\DataProviders\SqlDataProvider\"
objectQualifier=""
databaseOwner="dbo"/>



any clue?
Best
 
New Post
5/30/2007 7:42 AM
 

When your opening your database (e.g  with the Microsoft SQL Server Management Studio) you will see it.

Example: Searching for the table "Portals" (it's responsible what portals are running on your DNN installation)
When the table is called "dbo.Portals" then the databaseOwner is dbo and no objectQualifier
When the table is called "dbo.dnn_Portals" then the databaseOwner is dbo and 
objectQualifier is dnn_

When you started your installation with a objectQualifier then you must continue with it for the future versions or you can't do an update!

 
New Post
5/30/2007 8:03 AM
 
Ok, i undertand. I dont have objectQualifier.
I change the databaseOwner="dbo" for "qce374" and the installation starts but now i have another diferent errors: (I dont have db_owner permissions in my hosting server.)

Installing DotNetNuke

Version: 04.03.07



Installation Status Report

00:00:00.078 - Installing Version: 3.1.0
00:00:00.078 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.187 - Installing Script: DotNetNuke.Schema.SqlDataProvider Error! (seeD:\XVRT\noticiasdelmundo.es\Html\Providers\DataProviders\SqlDataProvider\DotNetNuke.Schema.log for more information)
00:00:03.562 - Installing Script: DotNetNuke.Data.SqlDataProvider Error! (seeD:\XVRT\noticiasdelmundo.es\Html\Providers\DataProviders\SqlDataProvider\DotNetNuke.Data.log for more information)
00:00:10.406 - Installing MemberRole Provider:
00:00:10.406 - Executing InstallCommon.sql
00:00:11.922 - Executing InstallMembership.sql
00:00:12.500 - Executing InstallProfile.sql
00:00:12.797 - Executing InstallRoles.sql
Error!
00:00:13.266 - Upgrading to Version: 3.1.1 Success
00:00:15.609 - Upgrading to Version: 3.2.0 Success
00:00:15.813 - Upgrading to Version: 3.2.1 Success
00:00:15.969 - Upgrading to Version: 3.2.2 Success
00:00:16.047 - Upgrading to Version: 3.2.3 Error! (seeD:\XVRT\noticiasdelmundo.es\Html\Providers\DataProviders\SqlDataProvider\03.02.03.log for more information)
00:00:18.360 - Upgrading to Version: 3.2.4 Success
00:00:18.453 - Upgrading to Version: 3.2.5 Success
00:00:18.500 - Upgrading to Version: 3.2.6 Success
00:00:18.610 - Upgrading to Version: 3.2.7 Success
00:00:18.656 - Upgrading to Version: 3.3.0 Success
00:00:18.750 - Upgrading to Version: 3.3.1 Success
00:00:18.860 - Upgrading to Version: 3.3.2 Success
00:00:19.016 - Upgrading to Version: 3.3.3 Success
00:00:19.297 - Upgrading to Version: 4.0.0 Error! (seeD:\XVRT\noticiasdelmundo.es\Html\Providers\DataProviders\SqlDataProvider\04.00.00.log for more information)
00:00:19.625 - Upgrading to Version: 4.0.1 Success
00:00:19.735 - Upgrading to Version: 4.0.2 Success
00:00:19.766 - Upgrading to Version: 4.0.3 Success
00:00:19.813 - Upgrading to Version: 4.0.4 Success
00:00:21.282 - Upgrading to Version: 4.0.5 Success
00:00:21.297 - Upgrading to Version: 4.0.6 Success
00:00:21.328 - Upgrading to Version: 4.0.7 Success
00:00:21.344 - Upgrading to Version: 4.3.0 Success
00:00:21.391 - Upgrading to Version: 4.3.1 Success
00:00:21.438 - Upgrading to Version: 4.3.2 Success
00:00:21.563 - Upgrading to Version: 4.3.3 Success
00:00:21.735 - Upgrading to Version: 4.3.4 Success
00:00:21.782 - Upgrading to Version: 4.3.5 Success
00:00:22.172 - Upgrading to Version: 4.3.6 Success
00:00:22.485 - Upgrading to Version: 4.3.7 Success
00:00:22.578 - Performing General Upgrades


Server Error in '/' Application.

El nombre de columna 'PageQuota' no es válido.
El nombre de columna 'UserQuota' no es válido.
No se pudo usar la vista o función 'vw_Portals' debido a errores de enlace.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: El nombre de columna 'PageQuota' no es válido.
El nombre de columna 'UserQuota' no es válido.
No se pudo usar la vista o función 'vw_Portals' debido a errores de enlace.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:







Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[SqlException (0x80131904): El nombre de columna 'PageQuota' no es válido.
El nombre de columna 'UserQuota' no es válido.
No se pudo usar la vista o función 'vw_Portals' debido a errores de enlace.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857434
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735046
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +31
System.Data.SqlClient.SqlDataReader.get_MetaData() +62
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +886
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +122
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +62
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +499
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +201
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText) +40
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +262
DotNetNuke.Data.SqlDataProvider.GetPortals() +47
DotNetNuke.Entities.Portals.PortalController.GetPortals() +19
DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, String strDatabaseVersion) +1533
DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +1284
DotNetNuke.Framework.Install.InstallApplication() +1171
DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +274
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
 
New Post
5/30/2007 2:47 PM
 

Returning to 4.5, this time trying 4.5.2 as it's avaialable now.

I'm using windows authentication. I can connect to the database.mdf in VS Express, attach then detach the file in management studio  but when I run the install wizard I get this:

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 15350
Message: An attempt to attach an auto-named database for file D:\Documents and Settings\Jeff Mowatt\My Documents\Visual Studio 2005\WebSites\DNN452\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Jeff

 

 
New Post
5/30/2007 4:00 PM
 

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL 2005 connectionSQL 2005 connection


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