DotNetNuke

Re: File Manager cannot handle large website sizes.

dhardie — Tue, 08 Nov 2005 05:58:05 GMT

I am trying to rebuild the source, but i can't get rid of the 105 odd build errors. And then when i do i am faced with this problem
Can someone please help with it? I really need this fixed.

I also tried it on release 3.2 but the problem has not been resolved. If someone could help me on that too that would be great.

Re: File Manager cannot handle large website sizes.

cathal — Fri, 04 Nov 2005 20:49:40 GMT

someone had the same problem and posted his fix here

Cathal

Re: File Manager cannot handle large website sizes.

dhardie — Fri, 04 Nov 2005 01:54:19 GMT

I hate to be annoying about this, but it really needs to be resolved soon. My site does not function properly with this problem. I have posted it on Gemini so hopefully it can be resolved within the next release.

Re: File Manager cannot handle large website sizes.

aus_nexxus — Fri, 04 Nov 2005 01:40:41 GMT

To open DNN you will need to have the web dev components installed. Just grab your DVD of VS2003 and rerun the install and make sure you select the web components.

Good pick up on the file manager though.

Re: File Manager cannot handle large website sizes.

dhardie — Thu, 03 Nov 2005 23:40:19 GMT

I have run into another problem as a result of this annoying issue. I cannot assign permissions to folders if the file manager is not working. Is there another way to assign folder permissions.
I tried to open the DNN source project in VS2003 and i have not been successful i am confronted with a dialog box that says to install Web Developers Components. Is there a special way to open DNN in order to edit it?

Re: File Manager cannot handle large website sizes.

Ronald.Ward — Fri, 21 Oct 2005 04:50:40 GMT

dhardie,

Since this piece of code resides on a code behind page, it is compiled into the designated .dll. If you want to make changes to this you will need to recompile the source (which you have if you see the vb files) yourself and create a new .dll after making the changes.

It is really just the front end pages that you can modify, save and then hit refresh to see changes. These will be the .ascx and .aspx pages.

Although I have not tested it with 9GB, I have used successfully the Speerio File Manager Pro in lieu of the DNN built in File Manager that had about 5GB of files in the Portals directory. IT is pretty snappy and handles large files easy. It has even become a somewhat viable alternative to FTP for some people due to it's simplicity to implement vs. a full blown locked down FTP server.

-Ronald

Re: File Manager cannot handle large website sizes.

dhardie — Fri, 21 Oct 2005 02:21:39 GMT

Here is another stupid question, how do i know if it is reading the newly changed code? Do i need to do anything special to IIS or compile it? Or is it a simple matter of just changing the line of code and then browsing to that page?

Re: File Manager cannot handle large website sizes.

cathal — Fri, 21 Oct 2005 00:18:45 GMT

no, it's not stupid at all. The 32/64 just indicates the size of the type. An Int32 is a 32bit signed integer, so can go to 2,147,483,647 (or 2GB), whereas Int64 is a 64bit signed integer so can go to 9,223,372,036,854,775,807 (too big to matter :)). Both of them are fine on a 32bit system.

Cathal

Re: File Manager cannot handle large website sizes.

dhardie — Fri, 21 Oct 2005 00:05:38 GMT

I don't know if this is a stupid question or not, but does assigning an Int32 to an Int64 require the server to be 64-bit or can it still work on a 32-bit system?

Re: File Manager cannot handle large website sizes.

cathal — Thu, 20 Oct 2005 23:35:11 GMT

Hhhm, it looks like theres an overflow error in the filemanager. The GetPortalSpaceUsed function is used in a number of locations, as well as referencing a sproc of the same name, so it may not be a trivial change. Please log it at the public issuelog @
http://support.dotnetnuke.com/project/Project.aspx?PROJID=23 so it can be worked on for a future version.

Note: I haven't tried this yet, but I suspect the problem is in GetFileTable in FileManager.ascx.vb (the highlighted line)
myColumns = New DataColumn
            myColumns.DataType = System.Type.GetType("System.Int32")
            myColumns.ColumnName = "IntFileSize"
            tblFiles.Columns.Add(myColumns)

You could try changing it to be System.Int64 to see if the overflow is just on the filesize

Cathal

File Manager cannot handle large website sizes.

dhardie — Tue, 18 Oct 2005 00:59:05 GMT

I am currently working with an Intranet site that is over 9Gb in size. When i try to access the File Manager i get a "An error has occurred. Error: File Manager is currently unavailable", looking at the Log Viewer i find this:

InnerException: Value was either too large or too small for an Int32.
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Value was either too large or too small for an Int32. ---> System.OverflowException: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at DotNetNuke.Entities.Portals.PortalController.GetPortalSpaceUsed(Int32 PortalId) at DotNetNuke.Modules.Admin.FileSystem.FileManager.UpdateSpaceUsed() at DotNetNuke.Modules.Admin.FileSystem.FileManager.BindFileList() at DotNetNuke.Modules.Admin.FileSystem.FileManager.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Is there anyway i can change this so that the File Manager can be operational once again?