Problem:
A DNN site is running ok in production. If a copy of the database is used to run the DNN site locally (on a local url) the site will continue to redirect to the production url.
Solution:
Update the DNN portal alias to use the new local url. Update the HTTPAlias field in the PortalAlias table and restart the website (e.g. touch the web.config).
Interprise Suite Version 6.x
Problem:
A topic is defined in IS but is not showing up in ISE as expected.
Solution:
In IS, edit the topic and ensure the checkbox “Show On Web” is checked.
Version: Interprise Suite 6.x
Problem:
The following error is generated when viewing a page in ISE.
Server Error in 'xxx' Application.
Value cannot be null.
Parameter name: child
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.ArgumentNullException: Value cannot be null.
Parameter name: child
Source Error:
Line 260: this.Controls.Clear();
Line 261: // set the template user control to be owned by this page:
Line 262: this.Controls.Add(m_Template);
Line 263:
Line 264: //register the ScriptManager before loading controls or the ComponentArt menu won't work with AJAX pages
Source File: d:\Program Files (x86)\Interprise Solutions\HipsAndCurves\ISE\Web\App_Code\SkinBase.cs Line: 262
Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: child]
System.Web.UI.ControlCollection.Add(Control child) +8828139
InterpriseSuiteEcommerce.SkinBase.OnPreInit(EventArgs e) in d:\Program Files (x86)\Interprise Solutions\HipsAndCurves\ISE\Web\App_Code\SkinBase.cs:262
System.Web.UI.Page.PerformPreInit() +31
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +328
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
Solution:
Typically, it points to a problem with the skin template file e.g. template.ascx. Run the page with a default (out-of-the-box) template. Typically, the page will load which confirms that it’s a problem with the customized template file. Look for functionality on the template file that is missing e.g. missing custom supporting file in the bin folder.
It can also be caused by a user control on the template page that has a compilation (or other error). Look for user controls in the template file with a squiggly line.
Version: Interprise Suite 6.x
Problem:
After a fresh install of Interprise Suite (IS) and Interprise Suite Ecommerce (ISE), connecting to IS via web services produces the error below. Also clicking the web option tab –> images tab causes the same error.
Note that the storefrontservice.asmx url resolves correctly (without errors).
Error:
Connection failed! WSE032: There was an error loading the microsoft.web.services3 configuration sections.
Solution:
Unblock the following files by right clicking each file, select the General tab, click the unblock button.
InterpriseSuite.exe
InterpriseSuite.exe.config
If needed, use the stream util to unblock all files: http://technet.microsoft.com/en-us/sysinternals/bb897440.aspx
Ideally, unblock the zip file prior to unzipping. All unzipped files will then be unblocked.
Version: Interprise Suite 6.0.x.x
Problem:
Can’t login to ISE admin.
Solution:
Make sure you login with user name: webadmin
Trying to login using another “admin” IS account does not work.
Version: Interprise Suite 6.x
Problem:
When trying to upgrade an IS database using the Interprise Database Management Console, a license error is generated as follows:
[5/23/2012 5:41:42 PM] Upgrade database 'your database name' started...
[5/23/2012 5:41:42 PM] Validating database license...
[5/23/2012 5:41:44 PM] Unable to upgrade 'your database name’.
Expired license on x/x/xxxx.
Solution:
Register the database using the Interprise Database Management Console by selecting the database and clicking the Register Product button on the toolbar. Full instructions can be found here:
http://support.interprisesolutions.com/index.php?/Knowledgebase/Article/View/38/0/how-to-register-your-company-database. One the database registered, try upgrading the database again.
Problem:
Magento site displays content but no styling, javascript etc. Stylesheets, javascript, and all other included files are missing a slash.
e.g. http://mywebsite.comjs/prototype/prototype.js
Solution:
In core_config_data table ensure entries with path = web/unsecure/base_url and web/secure/base_url have a trailing slash.
AspDotNetStorefront Version: 8.x
Problem:
When placing an order (in a live environment) there is a long delay (up to 60 seconds) after clicking the Place Order button i.e. the final step a customer takes when placing an order.
Solution:
The delay is caused by the email server not responding and the ASPDNSF SendMail routine waiting until it times out. Check that email is setup and functioning. In admin, in the main menu, go to Configuration –> Email. Ensure settings are correct and the email sent test is successful.
