'An unexpected error has occurred' on upload after changing limit
Hi,
I recently changed the max upload size for attachments to TFS work items on our SharePoint site. I did this by going to the
http://tfsserver1:8080/tfs/ProductCollection/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx?op=SetMaxAttachmentSize URL and entering the new size in bytes.
This worked a treat, but not I cannot upload any documents to another site on the same server.
I can open and save documents that are already there, but when I click the 'Upload' button it gives a white page with 'An unexpected error has occurred.' on it.
Is there something else I have to set when I increase the upload limit for work items?
Regards,
Isobel
August 16th, 2010 10:25am
Hi there.
Can you please take a look in the SharePoint log files and see what error message is logged there when this happens, and share with us?
Regards,
MagnusMy blog: InsomniacGeek.com
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2010 11:19am
Hi Magnus,
I can't see anything obvious in the log as I'm still a SharePoint novice. I have pasted the log events from the latest attempt below. I think the last line is the actual error because the other lines appear in the log when I just view the
site, but it makes no sense to me.
08/16/2010 13:15:05.38 w3wp.exe (0x2298) 0x2174 Windows SharePoint Services General
0 Medium Entering MRU trim routine.
08/16/2010 13:15:05.38 w3wp.exe (0x2298) 0x2174 Windows SharePoint Services General
0 Medium Initial table size: 16501694 in 81 entries
08/16/2010 13:15:05.38 w3wp.exe (0x2298) 0x2174 Windows SharePoint Services General
0 Medium Final table size: 16501694 in 81 entries
08/16/2010 13:15:05.38 w3wp.exe (0x2298) 0x2174 Windows SharePoint Services General
0 Medium Exiting MRU trim routine.
08/16/2010 13:15:05.38 w3wp.exe (0x0458) 0x1DE4 Windows SharePoint Services General
0 Medium Entering MRU trim routine.
08/16/2010 13:15:05.38 w3wp.exe (0x0458) 0x1DE4 Windows SharePoint Services General
0 Medium Initial table size: 34050615 in 127 entries
08/16/2010 13:15:05.38 w3wp.exe (0x0458) 0x1DE4 Windows SharePoint Services General
0 Medium Final table size: 34050615 in 127 entries
08/16/2010 13:15:05.38 w3wp.exe (0x0458) 0x1DE4 Windows SharePoint Services General
0 Medium Exiting MRU trim routine.
08/16/2010 13:15:05.55 OWSTIMER.EXE (0x0A68) 0x021C Windows SharePoint Services General
0 Medium Entering MRU trim routine.
08/16/2010 13:15:05.55 OWSTIMER.EXE (0x0A68) 0x021C Windows SharePoint Services General
0 Medium Initial table size: 0 in 0 entries
08/16/2010 13:15:05.55 OWSTIMER.EXE (0x0A68) 0x021C Windows SharePoint Services General
0 Medium Final table size: 0 in 0 entries
08/16/2010 13:15:05.55 OWSTIMER.EXE (0x0A68) 0x021C Windows SharePoint Services General
0 Medium Exiting MRU trim routine.
08/16/2010 13:15:06.16 wmiprvse.exe (0x1E9C) 0x099C ULS Logging
Unified Logging Service 8wsw High Now terminating ULS (wmiprvse.exe, onetnative.dll)
I also cannot see anything in the Event Viewer, but I may be looking in the wrong place.
Any ideas?
Isobel
August 16th, 2010 3:17pm
Hi Stanfford,
I have tried those steps and I still get the following error:
Runtime Error
Description:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running
on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root
directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to
a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
The above is the result from my machine. Below is the result from the server on which SharePoint is running.
Runtime Error
Description:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application.
This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to
a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Regards,
Isobel
Free Windows Admin Tool Kit Click here and download it now
August 17th, 2010 2:28pm
Hi Savoeurn,
Thank you for your suggestions. I haven't been able to test them yet but I will do as soon as possible (hopefull) today and let you know if it helps.
Isobel
August 25th, 2010 10:10am
Hi Savoeurn,
You fixed it!! Thank you so much. It's been annoying me for weeks.
The problem was that I had a line in the web.config that looked like this
<httpRuntime maxRequestLength="52428800" />
However the value could not be that high so I changed it to <httpRuntime maxRequestLength="2097151" />.
I found this out becasuse your post helped me turn off custom errors by doing the following:
- open file 'C:\inetpub\wwwroot\wss\VirtualDirectories\37475\web.config'.
- Find 'callStack'.
- Set to "true".
- Save file.
- Open file 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS'.
- Find 'customError'.
- Set to "Off".
- Save file.
Thanks again,
Isobel
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2010 11:08am