Home > An Unexpected > An Unexpected Error Has Occurred. Sharepoint Wss

An Unexpected Error Has Occurred. Sharepoint Wss


We recommend that you use this process only if you really require this process. **Note**  Once again, always always make a backup copy of your web.config before editing it. Grab Fiddler (http://www.fiddler2.com/fiddler2/) and fire it up on a client. Do we need to apply any patch? Go to C:\inetpub\wwwroot\wss\VirtualDirectories\80 Open Web.Config Change share|improve this answer edited Jul 7 at 20:28 BryanC 1203 answered Jan http://lanprolab.net/an-unexpected/an-unexpected-error-has-occurred-in-sharepoint.php

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Database Event ID: 5586 Date:  12/18/2012 Time:  11:15:29 AM User:  You can use a tool such as ULSViewer to facilitate looking at this data and filter out the requests you don’t need to see. Entries (RSS) and Comments (RSS) %d bloggers like this: Sign in Search Microsoft Search Products Templates Support Products Templates Support Support Apps Access Excel OneDrive OneNote Outlook PowerPoint Publisher Word Install How could banks with multiple branches work in a world without quick communication? http://stackoverflow.com/questions/1997803/an-unexpected-error-has-occurred

An Unexpected Error Has Occurred Sharepoint 2010

Sharing knowledge with the global IT community since November 1, 2004 Articles / SharePoint / Tips & Tricks 0 How to Fix the Error "An unexpected error has occurred" When You Are they pointing to any problems that line-up with requests you're making for SharePoint pages? If you're a user having problems with a public website or survey, email or call the company that owns the website and ask them for help.   You can usually find contact information

There is no such thing as "Office Server 2010." There was a Microsoft Office SharePoint Server (MOSS) 2007 but Microsoft SharePoint Server 2010 is not "Office Server 201o."

After I installed Simply, it's a GUID (globally unique identifier) that's automatically generated for every request that the SharePoint server receives. Again this isn't a fix, and certainly the customizations shouldn't lead to errors - but it may at least allow you to continue working. An Unexpected Error Has Occurred Sharepoint 2013 Central Administration Information regarding the origin and location of the exception can be identified using the exception stack trace below Stack Trace: [InvalidCastException: Specified cast is not valid.] Microsoft.Office.Project.PWA.WebParts.TimesheetPart.LoadTimesheetData(GetTSDataModeEnum LoadingMode, Guid resUID,

Because I only needed one of the updates, I didn't need to run the SharePoint Products and Technologies Configuration Wizard to complete the upgrade process. An Unexpected Error Has Occurred Sharepoint 2010 New Site Collection Reply Brian Smith - MSFT says: December 28, 2009 at 12:57 pm Hi Raju, That isn;t really enough to go on. For the Admin, a correlation ID can be used to trace errors, as well as performance problems and other issues. The correlation ID can help find out what happened but doesn't identify what happened.

However when an error occurs, the error message contains the correlation ID that was valid for the request at the time. An Unexpected Error Has Occurred Sharepoint Import Spreadsheet By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Is there an easier way ? -Yes. Any problems and conditions that SharePoint is aware of (internally) should surface through ULS - including many that don't necessarily bubble out to the Windows event logs.

An Unexpected Error Has Occurred Sharepoint 2010 New Site Collection

You will find the instructions on Chaitu Madala's blog much easier to follow. his explanation Send No thanks Thank you for your feedback! × English (United States)‎ Contact Us Privacy & Cookies Terms of use & sale Trademarks Accessibility Legal © 2016 Microsoft apropos .Net Development An Unexpected Error Has Occurred Sharepoint 2010 As an IT Pro or Admin, to figure out what happened, you need to find the ULS logs for the time the event occurred, and search for the Correlation ID in An Unexpected Error Has Occurred Sharepoint 2013 Like this:Like Loading...

Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. http://lanprolab.net/an-unexpected/an-unexpected-error-has-occurred-in-sharepoint-site.php Code2care's mission is to share varied knowledge in technical and non-technical areas gathered during day-to-day learnings and development activities so that our visitors can leverage this portal to find solutions to Best regards, Brian. In other words, you should be able to determine if the problem is just an ASPX page, if it is due to other resources that aren't available on the server, etc. An Unexpected Error Has Occurred Sharepoint 2007

An Admin uses the correlation ID as "breadcrumbs" to retrace a requests or processes in the SharePoint Unified Logging System (ULS) to find what leads up to and causes a problem. SP_Admin, is a member of both the Farm Administrators and the local administrators group on the SharePoint server per this KB article http://support.microsoft.com/kb/981229. In my case solution #11 did the job. check my blog It seems that someone created a CodePlex project that uses the same name as the original ULS Viewer tool - very confusing.

You may have to look across several of the web front ends to find the one that has the correlation ID you’re looking for. Sharepoint An Unexpected Error Has Occurred Web Parts Maintenance Page Announcing Chrome push notifications for the Spiceworks Community Beta Today we are proud to announce we are adding a new way for you to receive the Community updates that you care Reply Sachin Vashishth says: April 12, 2011 at 3:11 am Hi Brian, As you said above "if timesheets are the problem removing some added task lines might help. " so how

I also installed a SQL Server 2008 R2 Standard.

On the File menu, click Exit. I'll cut and paste the last quarter of the log that captures the error... 09/19/2012 16:33:41 1 INF Parsed the command line successfully 09/19/2012 16:33:41 1 INF Privacy statement  © 2016 Microsoft. An Unexpected Error Has Occurred Sharepoint 2010 Central Administration I see an error when I try to open the WSS 3.0 Central Admin...

Best regards, Brian Reply Alexandr says: September 8, 2009 at 5:56 am I do have such error type with PS 2007 SP2. more hot questions question feed default about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Join them; it only takes a minute: Sign up An unexpected error has occurred up vote 1 down vote favorite I have created an asp.net web application on my local machine http://lanprolab.net/an-unexpected/an-unexpected-error-has-occurred-sharepoint-2010.php Ohio 9.

Once those were gone, I was able to open up the problem timesheets. On the Edit menu, click Delete.