Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...install wizardinstall wizard
Previous
 
Next
New Post
6/11/2007 4:40 PM
 
Patrik

Joined: 6/8/2007
Posts: 2

Hi guys, i'm new to dnn and I have a question. when i start the installation process I get this error

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See C:\DotNetNuke\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See C:DotNetNukeProviders" to type 'Integer' is not valid.

Any one knows how to fix it?
 
New Post
6/11/2007 4:45 PM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

check C:\DotNetNuke\Providers\DataProviders\SqlDataProvider\04.04.00.log for details of the error

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/12/2007 11:23 PM
 
Jeff

Joined: 2/28/2007
Posts: 3

I just tried to upgrade from 4.4.1 to 4.5.3 and am getting the same exact FAILURE 400 error that dozens of others have already reported.

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See D:\DotNetNuke\Website\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See D:DotNetNukeWebsitePr" to type 'Integer' is not valid.

The log files to which your response refers do not exist. The log files that do exist are empty. Note the following--they are 2 bytes in size:

D:\DotNetNuke\Website\Providers\DataProviders\SqlDataProvider>dir *.log
 Volume in drive D is Data
 Volume Serial Number is 603F-54A6
 Directory of D:\DotNetNuke\Website\Providers\DataProviders\SqlDataProvider
06/12/2007  08:01 PM                 2 04.04.01.log
06/12/2007  08:01 PM                 2 04.05.00.log
06/12/2007  08:01 PM                 2 04.05.01.log
06/12/2007  08:01 PM                 2 04.05.02.log
06/12/2007  08:01 PM                 2 04.05.03.log
06/12/2007  09:26 PM           210,002 DotNetNuke.Data.log
06/12/2007  09:26 PM             5,205 DotNetNuke.Schema.log
06/12/2007  09:26 PM                 2 DotNetNuke.SetUp.log
               8 File(s)        215,219 bytes
               0 Dir(s)  168,922,578,944 bytes free

The DotNetNuke.*.log files don't appear to be of much help. The only mention of an error is in the DATA version; the first few lines of which are:

System.Data.SqlClient.SqlException: 'FK_EventLogConfig_EventLogTypes' is not a constraint.
Could not drop constraint. See previous errors.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)

Finally, I did a clean install of 4.5.3 on a laptop and it works like a champ. My BETA server is now a paper weight however...

Any guidance would be most appreciated.
 
New Post
6/12/2007 11:34 PM
 
Jeff

Joined: 2/28/2007
Posts: 3

Having seen another post about the web.config file being molested, I checked mine. Seems the machine keys were changed. I changed them back to the values in my backed up web.config. Then went to my host site (localhost/DotNetNuke) and the scrips ran without error. So I clicked on the GO TO SITE link and now I get this:

DotNetNuke Error: - Version 04.05.03

 

Domain Name localhost/dotnetnuke Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:

  1. Web Server Processing
    • When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
    • Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
    • The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.
  2. HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
    • The Request URL is parsed based on the "/" character
    • A Domain Name is constructed using each of the relevant parsed URL segments.

      Examples:

      URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
      URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
      URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
      URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
      URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory
    • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.

      Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.

      Example:

      URL: http://localhost/DotNetNuke/default.aspx
      URL: http://MACHINENAME/DotNetNuke/default.aspx
      URL: http://209.32.134.65/DotNetNuke/default.aspx
      PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke

      Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.

There is no PortalAlias field in the Portals table. But there is a PortalAlias table in which all of my aliases are found.
 
New Post
6/13/2007 12:27 AM
 
Jeff

Joined: 2/28/2007
Posts: 3

I JUST DISCOVERED A SOLUTION!

Seems previous versions of the installer added the dnn_ prefix to all of the tables in the database. The 4.5.3 installer does not. The upgrade documentation does not suggest that this setting in web.config be moved, but perhaps it should.

SO, after getting the error situation about a zillion times, I restored my database, re-ran the installer, and this type supplied the dnn_ object prefix on the database connection page. The installer still threw the same error as before -- FAILURE 400 -- but I closed my browser, started a new one, navigated to the site, and the DB scripts then ran without failure.

At this point, the GO TO SITE link actually took me back to my fully-functional site!

Therefore, prior to upgrading, make sure that the ObjectQualifier setting is also moved from your old web.config to the new one. This value is found near the end of the web.config (at least on mine) in a section that looks something like the following:

  <data defaultProvider="SqlDataProvider">
   <providers>
    <clear />
    <add name="SqlDataProvider"
     type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
     connectionStringName="SiteSqlServer"
     upgradeConnectionString=""
     providerPath="~\Providers\DataProviders\SqlDataProvider\"
     objectQualifier="dnn_"
     databaseOwner="dbo" />
   </providers>
  </data>

Good luck!
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...install wizardinstall wizard


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