Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreProblems with installing 02.01.00 on DNN 441 SiteProblems with installing 02.01.00 on DNN 441 Site
Previous
 
Next
New Post
10/17/2007 12:29 PM
 

Hi,

I've updated the store module on a DNN 441 site install to 02.01.00.  When I try to put the module on the page I get the following error.  Does anyone know how to correct this?

Thanks

Jerry

AssemblyVersion: 04.04.01
PortalID: 0
PortalName: Deb Wilson DotNetNuke Training Site
UserID: 1
UserName: host
ActiveTabID: 314
ActiveTabName: STORE MODULE
RawURL: /elementary/training/deb/HOME/STOREMODULE/tabid/314/Default.aspx
AbsoluteURL: /ELEMENTARY/TRAINING/DEB/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.40607; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 5f5f662f-1678-4819-ba79-52eaa49c8a43
InnerException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.IO.Path.NormalizePathFast
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck) at System.IO.Path.GetFullPathInternal(String path) at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath) at System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[] str, Boolean needFullPath) at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList) at System.Web.InternalSecurityPermissions.PathDiscovery(String path) at System.Web.Caching.CacheDependency.Init(Boolean isPublic, String[] filenamesArg, String[] cachekeysArg, CacheDependency dependency, DateTime utcStart) at System.Web.Caching.CacheDependency..ctor(String[] filenames, String[] cachekeys, CacheDependency dependency) at DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider.Insert(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration, Boolean PersistAppRestart) at DotNetNuke.Common.Utilities.DataCache.SetCache(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration, Boolean PersistAppRestart) at DotNetNuke.Common.Utilities.DataCache.SetCache(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration) at DotNetNuke.Services.Localization.Localization.LoadResource(Hashtable target, String language, String cacheKey, String ResourceFile, CustomizedLocale CheckCustomCulture, PortalSettings objPortalSettings) at DotNetNuke.Services.Localization.Localization.GetResource(String ResourceFileRoot, PortalSettings objPortalSettings, String strLanguage) at DotNetNuke.Services.Localization.Localization.GetString(String name, String ResourceFileRoot, PortalSettings objPortalSettings, String strLanguage, Boolean disableShowMissingKeys) at DotNetNuke.Services.Localization.Localization.GetString(String name, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.ProcessControl(Control c, ArrayList affectedControls, Boolean includeChildren, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.IterateControls(ControlCollection controls, ArrayList affectedControls, String ResourceFileRoot) at DotNetNuke.Framework.PageBase.Render(HtmlTextWriter writer) at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Control.RenderControl(HtmlTextWriter writer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

 
New Post
10/17/2007 9:04 PM
 

This is something that is turning out to be a real problem everywhere... file and folder paths are limited in length and everything breaks just because of a few characters too many. It's a ridiculous situation to be in in the year 2007.

The "/elementary/training/deb/HOME etc" bits are making the paths too long. The safest way to use DNN is to install it as near as possible or in your domain root (and add that to your training schedule too).

At least that's what I'm reading from the error... perhaps  someone else knows a tricky way around these issues.

Rob

 
New Post
10/18/2007 4:13 AM
 

Hi Jerry,

I agree with the Rob's comments. Every .net software have this problem on all Windows versions! It's a legacy problem with Win32 API. You can read here the offical Microsoft comment from the BCL Team.

The only workaround is to install your dnn instance near than the root disk, like C:\DNN. I will try to use shorter names in the future but this will not solve all cases. Because if your dnn is installed on C:\Inetpub\www\DotNetNukeFrameworkV462\MyLongCompanyName\MyLongProjectName this path use more than 70 characters on 248!

Gilles


We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.
 
New Post
10/18/2007 9:30 AM
 

Thanks for your help...I tried what you said on another installation where the portal was installed closer to the root.  It appears to work, but now when  I add a module, it adds two instances to the page.  For example I add the Store Catalog, it puts it on there twice.  I installed it on a 441 portal and the previous version of the store modules were there.  I also have the modules marked as premium, but I've given the portal rights to use the store modules.  Do you have any ideas on what maybe causing this?  Should I uninstall the modules and try again?

Jerry

 
New Post
10/18/2007 8:04 PM
 

Hi Jerry,

You can try to uninstall, but I do not believe that's correct the problem. I never seen this before. I will try to install it tomorow as a premium module for mimic your config.

Gilles


We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreProblems with installing 02.01.00 on DNN 441 SiteProblems with installing 02.01.00 on DNN 441 Site


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