Mountain View 1600, CA 94043
+1 650-253-0000
name@example.com
Web
Site
Search
Register
Login
DNN Home
Services
-
DotNetNuke Support
-
CRM Systems
DNN
-
DotNetNuke Modules
-
Module Downloads
-
Module Upgrade Policy
DNN Support
-
Module Update News
-
Knowledge Base
-
License Management
-
Invoice History
Module Downloads
Blog
Store
Contact Us
-
About Us
Search
Home
1
2
3
4
5
Home
Support
Feedback Design...
Critical Error Path or File Name Too Long...?
Previous
Next
4/3/2007 9:45 AM
Joined: 1/1/0001
Posts: 0
Critical Error Path or File Name Too Long...?
(United States)
I get the following message when I try to configure Feedback Designer:
A critical error has occurred.
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.
I'm wondering, is this referring to the local path name? as in c:\filepath or the
http://filepath
name? The http path is less than 100 characters.
I am running dotnetnuke on my local computer for testing before moving any final edits to the website. I am running the website through Visual Web Developer Express and the ASP.Net Development Server. The local location of the website is "C:\Documents and Settings\Rick\My Documents\Visual Studio 2005\WebSites\DotNetNuke Website3\" and that doesn't appear to be too long of a name either at 92 characters.
Is this module just incompatible with the .Net Development Server and VWD? or is there something I'm missing. It installed without any error messages. I uninstalled deleting the files, and then reinstalled. Same problem.
I'm stumped.
Any help is greatly appreciated,
Rick
4/3/2007 9:48 AM
Joined: 1/1/0001
Posts: 0
Re: Critical Error Path or File Name Too Long...?
(United States)
I forgot to mention that I'm running DotNetNuke 4.4.1 on Windows XP SP2 and also SQL Express 2005, loads of memory and paging file space.
Rick
4/3/2007 9:57 AM
Joined: 1/1/0001
Posts: 0
Re: Critical Error Path or File Name Too Long...?
(Australia)
I have not come across this error before, development for this module is tested on iis rather than the personal web server that visual studio comes with...perhaps this may be causing some problems.
Where exactly is the error showing up?
4/3/2007 10:52 AM
Joined: 1/1/0001
Posts: 0
Re: Critical Error Path or File Name Too Long...?
(United States)
The message was appearing above the "Feedback Designer" module, so I think this was an error produced by DNN since it was not within the module box itself. I went ahead and loaded the module on to the live website and it is working fine there with no problems. I've just made it viewable only by admin for now until it is configured the way I want it.
So, I guess maybe it had something to do with either the directory name length where it was on my local machine, or it was just not working with the ASP.Net Development Server. First time that has happened with a module, but I've only been using DNN for a few weeks and still learning. This module and others and DNN in general will make it so easy for my friend to moderate her own website once I have it all set up for her. I think I should have charged her more than a lunch and $150 for all this from domain name registration through to completion of website, but she is just getting started with her business and I'm glad to help.
I may try the module again for fun on a local web to see if it was the directory name or the Dev Server that was the problem. Will let you know the outcome if I do...
Thank,
Rick
4/3/2007 11:02 AM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Critical Error Path or File Name Too Long...?
(Australia)
Thanks for the info. Glad it is all worked out.
4/3/2007 11:47 AM
Joined: 1/1/0001
Posts: 0
Re: Critical Error Path or File Name Too Long...?
(Australia)
Yes, glad to hear in production all worked out well.
4/16/2007 12:58 PM
Joined: 1/1/0001
Posts: 0
Re: Critical Error Path or File Name Too Long...?
(United States)
I'm not sure what the problem was before, but I tried it again in the Visual Web Developer Express 2005 Development Server, and it worked just fine. So, it was not a problem with your software, it was a problem with something in my settings on that particular website, just not sure what...
Rick
4/16/2007 2:27 PM
DNN Module Support
Joined: 8/28/2006
Posts: 2065
Re: Critical Error Path or File Name Too Long...?
(Australia)
Thanks for the feedback we feel vindicated!
Page 1 of 1
Previous
Next
Home
Support
Feedback Design...
Critical Error Path or File Name Too Long...?