dashCommerce

I been trying all damn nite to get this thing work and it refuses.  this is my set up i am running  BlogEngine.net in the root folder of my site i then created a SQL server db in my hosting control panel. i created a folder called commerce and gave it app root. the i built the site in VS08 then ftped the files to the server. i typed mydomain.com/commerce/install/install.aspx and i get this error

Configuration Error

Line 54: 			<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
Line 55: 		</httpModules>
Line 56: 		<siteMap enabled="false" defaultProvider="AdminXmlSiteMapProvider">
Line 57: 			<providers>

 Line 58: 				<clear/>

Thanks 

 Well BlogEngine is my main app and it took me three days before i got it to work with godaddy so i really don't want to mess with it an move it to another directory. is there any other way? i been looking into hosting companies and other that the lack of control they offer the best plan for the least amount.

Since my first post what i did was created a virtual directory in the root folder  but now i have another error. this seems to becoming from the web.conf from the root.

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'BlogEngine.Core' or one of its dependencies. The system cannot find the file specified. (d:\hosting\wolfman2k1\web.config line 79)

Source Error:

[No relevant source lines]

Source File: d:\hosting\wolfman2k1\web.config    Line: 79

do i have to modify that config file in some way? also i have already created a database on my server for this app can i modify the connection string to use that database  and which one these strings do i use?

• ODBC:
• Driver={SQL Server}; Server=p3swhsql-v07.shr.phx3.secureserver.net; Database=commerce_admin; Uid=commerce_admin; Pwd='your password';

• OLE DB, OleDbConnection (.NET):
• Provider=sqloledb; Data Source=p3swhsql-v07.shr.phx3.secureserver.net; Initial Catalog=commerce_admin; User ID=commerce_admin; Password='your password';

• SqlConnection (.NET):
• Data Source=p3swhsql-v07.shr.phx3.secureserver.net; Initial Catalog=commerce_admin; User ID=commerce_admin; Password='your password';

• Publishing Wizard Connection:
• URL: https://p3mssqlpub.secureserver.net
  What are the Database Publishing Service and Database Publishing Wizard?

 or better yet is there a way i can manually configure the app to run on my server without running the install application?

here is the web.config for the root

<?xml version="1.0"?>
<configuration>

  <configSections>
    <sectionGroup name="BlogEngine">
      <section name="blogProvider" requirePermission="false" type="BlogEngine.Core.Providers.BlogProviderSection, BlogEngine.Core" allowDefinition="MachineToApplication" restartOnExternalChanges="true"/>
    </sectionGroup>
  </configSections>

  <BlogEngine>
    <blogProvider defaultProvider="MSSQLBlogProvider">
      <providers>
        <add name="XmlBlogProvider" type="BlogEngine.Core.Providers.XmlBlogProvider, BlogEngine.Core"/>
        <add name="MSSQLBlogProvider" type="BlogEngine.Core.Providers.MSSQLBlogProvider, BlogEngine.Core"/>
      </providers>
    </blogProvider>
  </BlogEngine>


    <connectionStrings configSource="sql.config" />


  <appSettings>
    <add key="BlogEngine.FileExtension" value=".aspx" />
    <!-- You can e.g. use "~/blog/" if BlogEngine.NET is not located in the root of the application -->
    <add key="BlogEngine.VirtualPath" value="~/" />
    <!-- The regex used to identify mobile devices so a different theme can be shown -->
    <add key="BlogEngine.MobileDevices" value="(nokia|sonyericsson|blackberry|samsung|sec-|windows ce|motorola|mot-|up.b)" />
  </appSettings>
 
  <system.web>
   
    <compilation debug="true" />
    <globalization requestEncoding="utf-8" responseEncoding="utf-8" culture="auto" uiCulture="auto" />
    <httpRuntime enableVersionHeader="false" useFullyQualifiedRedirectUrl="true" maxRequestLength="16384" executionTimeout="3600" requestLengthDiskThreshold="16384" />

    <machineKey
      validationKey="D9F7287EFDE8DF4CAFF79011D5308643D8F62AE10CDF30DAB640B7399BF6C57B0269D60A23FBCCC736FC2487ED695512BA95044DE4C58DC02C2BA0C4A266454C"
      decryptionKey="BDAAF7E00B69BA47B37EEAC328929A06A6647D4C89FED3A7D5C52B12B23680F4"
      validation="SHA1" decryption="AES"
    />

    <authentication mode="Forms">
      <forms timeout="129600" name=".AUXBLOGENGINE" protection="All" slidingExpiration="true" loginUrl="~/login.aspx" cookieless="UseCookies" />
    </authentication>

    <pages enableSessionState="false" enableViewStateMac="true" enableEventValidation="true">
      <controls>
        <add namespace="Controls" tagPrefix="blog"/>
      </controls>
    </pages>

    <customErrors mode="RemoteOnly">
      <error statusCode="404" redirect="~/error404.aspx" />
    </customErrors>

    <membership defaultProvider="XmlMembershipProvider" >
      <providers>
        <clear />
        <add name="XmlMembershipProvider" type="BlogEngine.Core.Providers.XmlMembershipProvider, BlogEngine.Core" description="XML membership provider" xmlFileName="~/App_Data/users.xml"/>
      </providers>
    </membership>

    <roleManager defaultProvider="XmlRoleProvider" enabled="true" cacheRolesInCookie="true" cookieName=".BLOGENGINEROLES">
      <providers>
        <clear />
        <add name="XmlRoleProvider" type="BlogEngine.Core.Providers.XmlRoleProvider, BlogEngine.Core" description="XML role provider" xmlFileName="~/App_Data/roles.xml"/>
      </providers>
    </roleManager>

    <siteMap defaultProvider="PageSiteMap" enabled="true" >
      <providers>
        <add name="PageSiteMap" description="The site map provider that reads in the .sitemap XML files." type="BlogEngine.Core.Web.Controls.PageSiteMap, BlogEngine.Core"/>
        <add name="SecuritySiteMap" description="Used for authenticated users." type="System.Web.XmlSiteMapProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" securityTrimmingEnabled="true" siteMapFile="Web.sitemap" />
      </providers>
    </siteMap>
   
    <httpModules>
      <add name="WwwSubDomainModule" type="BlogEngine.Core.Web.HttpModules.WwwSubDomainModule, BlogEngine.Core"/>
      <add name="UrlRewrite" type="BlogEngine.Core.Web.HttpModules.UrlRewrite, BlogEngine.Core"/>
      <add name="CompressionModule" type="BlogEngine.Core.Web.HttpModules.CompressionModule, BlogEngine.Core"/>
      <add name="ReferrerModule" type="BlogEngine.Core.Web.HttpModules.ReferrerModule, BlogEngine.Core"/>
      <!--The CleanPageModule below removes whitespace which makes the page load faster in IE. Enable at own risk -->
      <!--<add name="CleanPageModule" type="BlogEngine.Core.Web.HttpModules.CleanPageModule, BlogEngine.Core"/>-->
     
      <!--Remove the default ASP.NET modules we don't need-->
      <remove name="PassportAuthentication" />
      <remove name="Profile" />
      <remove name="AnonymousIdentification" />
    </httpModules>

    <httpHandlers>
      <add verb="*" path="file.axd" type="BlogEngine.Core.Web.HttpHandlers.FileHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="image.axd" type="BlogEngine.Core.Web.HttpHandlers.ImageHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="syndication.axd" type="BlogEngine.Core.Web.HttpHandlers.SyndicationHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="sitemap.axd" type="BlogEngine.Core.Web.HttpHandlers.SiteMap, BlogEngine.Core" validate="false"/>
      <add verb="*" path="trackback.axd" type="BlogEngine.Core.Web.HttpHandlers.TrackbackHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="pingback.axd" type="BlogEngine.Core.Web.HttpHandlers.PingbackHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="opensearch.axd" type="BlogEngine.Core.Web.HttpHandlers.OpenSearchHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="metaweblog.axd" type="BlogEngine.Core.API.MetaWeblog.MetaWeblogHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="rsd.axd" type="BlogEngine.Core.Web.HttpHandlers.RsdHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="css.axd" type="BlogEngine.Core.Web.HttpHandlers.CssHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="js.axd" type="BlogEngine.Core.Web.HttpHandlers.JavaScriptHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="rating.axd" type="BlogEngine.Core.Web.HttpHandlers.RatingHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="opml.axd" type="BlogEngine.Core.Web.HttpHandlers.OpmlHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="monster.axd" type="BlogEngine.Core.Web.HttpHandlers.MonsterHandler, BlogEngine.Core" validate="false"/>
      <add verb="*" path="blogml.axd" type="BlogEngine.Core.Web.HttpHandlers.BlogMLExportHandler, BlogEngine.Core" validate="false"/>
    </httpHandlers>
 
  </system.web>
</configuration>

Are you sure you have correctly created the Vdir in IIS? If yes it seems to be a misconfiguration of IIS. Try going to IIS Manager and look if your application is running on aspnet 1.1 or aspnet 2.0 (required).

 In order to do that you have to go to property of your application, ASPNET tab.

faccipieri:

Are you sure you have correctly created the Vdir in IIS? If yes it seems to be a misconfiguration of IIS. Try going to IIS Manager and look if your application is running on aspnet 1.1 or aspnet 2.0 (required).

 In order to do that you have to go to property of your application, ASPNET tab.

 

Well it's hard to do that because i use shared hosting and until i start making money from my site i can't use dedicated servers. so we the limited access to that i have over the asp control panel its rather hard to tell by basuc option when i creat a vd is whether it has read write privilidges and set as application root. but to answer your other part of the question it's asp 2.0 because thats what blogengine requires. dont know what else it could be 

I did not have much success with go daddy. I use http://terrasite.com/. I have good luck with them and they give me lots of control.

I am working on getting Dash Commerce implemented in my GoDaddy account. I am having problems with the web.config. I manually created the database using the GoDaddy's Web Interface for creating SQL databases. I also used their connection string in my web.config. My current error is is with SubSonic. I have not used SubSonic before so I'm not sure how to interpret this error message:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: SubSonic.ELib2DataProvider..ctor()

Source Error:

Line 44: 	<SubSonicService defaultProvider="ELib2DataProvider">
Line 45: 		<providers>
Line 46: 			<add name="ELib2DataProvider" type="SubSonic.ELib2DataProvider, SubSonic" connectionStringName="CommerceTemplate"/>
Line 47: 		</providers>
Line 48: 	</SubSonicService>

First, thank you for such a quick reply and the amount of posting you do and help you provide in the forums.

Based on the directory structure, I'm going to say I have 2.2.0 installed.

Strange, here's what my web.config looks like:

<SubSonicService defaultProvider="dashCommerceProvider">
    <providers>
      <clear />
      <add name="dashCommerceProvider" connectionStringName="dashCommerce" type="SubSonic.SqlDataProvider, SubSonic" />
    </providers>
  </SubSonicService>

...and that's down around line 145.

I'm on GoDaddy as well, and all I had to do was make sure that the folder that contains dashCommerce is set as a Virtual Directory.  So, from the Hosting Control Center, select "Content > IIS Settings".  Then click the "Create" button, and type in the directory name that dashCommerce is under.  You'll also want to select the "Set Application Root" checkbox.  That's all I had to do.

Once you get that going, however, you'll notice that you run into another problem... setting up the database!  From what I can tell there's no way to setup a FullText catalog on any of the tables once you've created the database.

Has anybody else been able to do this on GoDaddy??  If so, please, spill the beans - I even talked to their support last night, and they had to elevate it because they couldn't figure it out either.  Will dashCommerce work without a FullText catalog?  I might give that a shot.

Chad 

Unless you made some modifications, that looks like a snippet from 3.0 versoin of DC. Is that correct? Also, I confirmed that my directory is marked as a Virtual Directory and that it is a root.

So my question is basically, what version are you referring to, Chad?

Thanks,

Phillip

Ah, right you are... sorry about that, I was bit quick to post a response - and didn't even think about what version I was using.  Yes, I'm using 3.0. 

Well last night, after several hours of not being able to get 2.0 to work, I began uploading 3.0.

Should I abort the deployment of 3.0 on GoDaddy? It sounds like even if I get it installed it won't work due to the Full Text indexing requirement.

Can you describe the problems you are encountering? This will help me plan my course of action. I need to figure this out ASAP, because one I have the site in place I have severl modifications I need to make to it for a project.

Thanks.

Basically, GoDaddy does NOT support Full text indexing on MS SQL databases... and since that's what dashCommerce needs - the whole install process (under install/install.aspx) fails.

If you can wait a few hours - I'm working on a fix for this - because I'm in the same boat you are.  I found that there's really only one stored procedure that uses the full text search - so I'm just re-writing it so that it doesn't need the full text catalog there.  I'll respond with the procedures to take as soon as I'm able to confirm that my change works.

Chad 

So does that mean you are using the built-in installation procedure? Are you saying that the Full-Text is required for only the installation and no other part of the App? If so, then why not manually install the database and type the connectoin string in the web.config file?

I am open to the possibility that my question does not compute because of things I might not be aware of....