I'm getting an error on upload. The upload appears to be working though (but one at a time).
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 7/3/2008
Time: 12:06:32 PM
User: N/A
Computer: www
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/3/2008 12:06:32 PM
Event time (UTC): 7/3/2008 4:06:32 PM
Event ID: e96fefd368214ca9973c81fb359a60f4
Event sequence: 27
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1515208653/Root-1-128595745316037805
Trust level: Full
Application Virtual Path: /
Application Path: D:\InetPub\filevistaroot\
Machine name: www
Process information:
Process ID: 3004
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
Request information:
Request URL: http://files.mathxl.com/FileVistaControl/upload.aspx?rootFolderID=0&relativePath=mmt&ASP.NET_SessionId=jlqzya45excc0fzenrelmx3j&FT.Active=1&FT.OverrideProvider=1&FT.UploadID=&groupID=12151011910154981&groupOrder=first
Request path: /FileVistaControl/upload.aspx
User host address: 192.234.246.209
User: pe
Is authenticated: True
Authentication Type:
Thread account name: DM\www1
Thread information:
Thread ID: 8
Thread account name: DM\www1
Is impersonating: True
Stack trace: at GleamTech.Web.FileTransfer.UploadHttpModule.a(HttpResponse A_0)
at GleamTech.Web.FileTransfer.UploadHttpModule.a(Object A_0, EventArgs A_1)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Alec
7/3/2008 9:12 AM
FYI, we fixed this issue in v3.2.2.
The problem occured in Flash upload mode when uploading more than one file at once. The error was occuring when one of the files took long time to finish, causing a timeout and stopping the overall upload with an error message.
Cem Alacayir
7/3/2008 8:11 PM
What's the best way to upgrade from v3.1? I'm using the SQL Server database with accounts/etc all setup.
Alec
7/7/2008 1:52 PM
1. Download the trial copy of version 3.2:
2. It is recommended that you make a backup copy of your current FileVista folder and SQL Server database so that you can roll back if anything goes wrong.
3. Copy file FileVista\App_Data\FileVista.config to a separate location. You will NOT need to unlock the trial version again as your license key is kept in your current database.
If you prepared a custom language file in FileVista\languages subfolder than keep a copy of it too, you will need to add new strings to your language file for version 3.2 though.
4. Depending on your previous installation method:
•If you previously installed FileVista via the MSI setup file than uninstall it from Add/Remove programs. If any files or subfolders are still left under the uninstalled FileVista folder, delete all.
•If you previously installed it manually than delete all files and subfolders under your FileVista folder.
5. Depending on the new installation method you choose:
•Run FileVista.msi which is found in the FileVista-v3.2-trial.zip and install the application to the same folder as your previous installation.
•Manual: Copy all the files and subfolders from FileVista folder in the FileVista-v3.2-trial.zip to your existing FileVista folder.
6. Put FileVista.config that you made a copy of in step 3 to the same place under your newly installed FileVista folder,
i.e. overwrite the file with the same name: FileVista\App_Data\FileVista.config.
7. Run update.aspx and choose your current version (range) correctly (3.0 till 3.2). Complete the update wizard, close your browser and restart the application.
Cem Alacayir
7/7/2008 3:12 PM
Thanks that worked. One thing though I forgot to change my impersonation after overwriting web.config and I got an error and it appeared the upgrade was left in a half finished state because it complained about inserting the same key into configuration twice when I ran it again. I rolled it back and got it working, but I would suggest some sort of transaction for the upgrade process just to avoid that. Thanks.
Alec
7/13/2008 4:01 PM