2. ASPRunnerPro General questions
  3. [SOLVED]  Trouble with uploading .docx files
This topic is locked
[SOLVED]

 Trouble with uploading .docx files

 		9/20/2011 2:54:52 PM
ASPRunnerPro General questions
S
 swiersman author

Hi All,
I am using ASPRunner v6.1 and I have a problem when uploading ".docx" files from my ADD.asp form.
The upload function works great and the file is stored in my designated UPLOAD folder.
The problem occurs when i try to open the uploaded file it in my view.asp form. My MS WORD opens up and reports the file may be corrupt.
When I diff the orginal file I uploaded with the one siting in the UPLOAD folder they are not the same. The file in the UPLOAD folder has an additional "0" at the end of the file binary code.
This does not happen when uploading a *.doc file.
Has anyone had this same issue and resolved it?
Thanks,
Scott
jadachDevClub member 9/20/2011

I had the same issue.
You need to add new mime-types to IIS in order to allow the download of new MS Office 2007 files.
S
 		swiersman author 9/21/2011

Thanks,
I did check my MIME registrations and they looked good per MS defintions.
Some sights I have visited mentioned it could be that the ASP download page continues to write output after the Response.BinaryWrite command. Removing the later content, or adding a Response.End afterward, resolved the issue.
Does anyone know where this downoad code exists when using ASPRunner 6.1 so I could give this try?
Thanks,
Scott
Sergey Kornilov admin 9/21/2011

Scott,
my suggestion would be to try ASPRunnerPro 6.3. If there were any issues with upload they were fixed in version 6.3.
If this doesn't help or you cannot upgrade at this moment post your application to Demo Account and open a ticket at http://support.xlinesoft.com sending your Demo Account URL. 'Demo Account' button can be found on the last screen in the program.
jadachDevClub member 9/22/2011

For what it's worth, I have an application built in ASPR 6.3 - and xlsx files do not play nice when retrieving from the database. When I moved the application to another IIS server, the problem went away. So, I'm thinking this is IIS and not ASPR.