thekid.me.uk

You the Man! Good One!

i am doing this edit web.config file but can not solution Please again send some solution and send my email. "Debugging SharePoint can be problematic at times, it does like to hide debugging information from you. The bain of my life recently has been “An unexpected error has occurred” with nothing written to log files, trace or the event log. Normally I can debug the problem with a little commenting & narrowing down of the problem, but today I have managed to get rid of that error screen completely. The solution is to change a single entry in web.config, by modifying the line… <SafeMode MaxControls=“200“ CallStack=“false“… to… <SafeMode MaxControls=“200“ CallStack=“true“… You will also need to set custom errors to 'Off' . <customErrors mode=“Off“/> You will no longer see the “An unexpected error has occurred” error page and instead you get a lovely ’standard ASP.Net error page’ with the stack trace and everything…development has got that little bit easier!!"

Thanks for this tip

Thanks for this info...

You rock! This will save our development team so much time and aggrivation...we were about going crazy from the "unexpected error" message! Thanks!

Two quick edits in the config file and i can now debug the problem, How do you know these things??? But most of all thanks for posting this, saved me a lot of time.

Two quick edits in the config file and i can now debug the problem, How do you know these things??? But most of all thanks for posting this, saved me a lot of time.

I just did some drilling into this problem and found a solution. After you have enabled the detailed error reporting, you will see a new error when you click on "My Tasks" similar to "StatusingDataAccess.GetDataForTask could not find pre-cached data. Attempted to load Guid - 9eb1c3c5-59ee-41fb-8b84-d386b89dd0f7". What I did was perform a manual search on the Database table for a Task that has a GUID equal to the GUID reported on the error screen. I performed this query on the dbo.MSP_TASKS table: SELECT * FROM dbo.MSP_TASKS WHERE TASK_UID='7e514b0c-cd40-4663-b6e5-2454f1668289'; The query returned 1 result for the task that has the error. I removed the user from the resources for that task, and then the user was able to open "My Tasks" again.

You are Great...You saved my time.

Thanks for the post, this was a huge help.

Thanx a lot mate! You are my saviour.

Thanks man! No to figure out "Extender controls may not be registered before PreRender."

Thanks for this!

Hi Iam getting a error "copying to the destination did not completed successfully" when i send a document to record center. Does it requires any customisation in officialfile.aspx.... Iam really confused.... Can any one help me Thanks Ganesh

Awesome find. The error reporting (lack of) in SharePoint was driving me nuts until now. Thanks again.

Hi you saved my day, thanks

Thanks sir.. this is great help for me to get the exact issue.

Hello, I believe i edited the wrong web.config file. And now i get a runtime error when accessing my portal. I changed back the settings and still get error. Do you know how i can resolve this. Here is the error Server Error in '/' Application. -------------------------------------------------------------------------------- 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>

Thanks for this wonderful tip! My life will be a lot easier from now on :).

A precious hint indeed! I've got 5 MOSS 2007 development books - but none of them contains such crucial tips like this one... Thanks a lot

I had used SmartPart (return version 1.3) in my WSS 3.0 iam able to install properly & add my UC , when i need to modify I clicked on Modify > Webpart shows error : An unexpected error has occurred” error page Webpart Manintance page :if you have permission , you can use this page

Very helpfull tip

This is really great help. thanks

Hi Vincent Rothwell, You are the best. Thanks for your help. As a IT guys we need learn how to provide that kind of info to improve the business. Marcello Ramos Brazil

Thanks for this - helps a lot when debugging custom WebParts!

Thanks a lot for the wonderful tip !!!

many thanks, this is going to save me a lot of time

BIG help. Thanks a lot!

When I search for web.config, I get a slew of files and quite a few for SharePoint. I found one that had the fields you said needed to be changed, changed them and it did not change anything. Is there a specific web.config file I should be looking for. Thanks.

Bob, Your web.config is in the root of your web application. By default these will be in the C:\Inetpub\wwwroot\wss\VirtualDirectories folder. Generally the name of the folder for your site will be either the machine name with a number or the host header with a number. This can be different if the person who created the web application chose a different folder name. You can also find out the folder from within the IIS manager. HTH

Thanks. WSe now see the code. We have a unique situation here where I installed and set up the application and someone else is adding and modifying sites. Twice now the main site that person is working on has come up with an unexpected error - the first time we killed the site and it was then recreated. This is the second time it has happened, and we want to know what is behind these errors - the activity prior to each was not the same. What we hope to learn is how to fix whatever went wrong without having to rebuild the site. If we cannot discover what caused the fatal error, we will have to kill it again and from this point forward, back up the site after each action is successful so we have a point in time to go back to with a healthy site in place.

That is stunningly awesome! Thank you so much!

hi thanks for yr help.. using this method i have solved my problem

This is a great piece of information. It really saves a lot of time of a Sharepoint developer to find where the problem is. I had a similar issue, with one of my webparts (based on something similar to smartpart), i followed the steps and i could see the trace information and figure out the problem was with the path of .ascx user contol file. thanks a lot

Amazing tip man! I have been skinning Sharepoint portals for some time now, but was never really taught. I've just been learning on my own (doing quite well if I might say so), but I had run into this "Unexpected error" while editing my default.master page. After setting up these debug tips, Sharepoint opened up to me and told me EXACTLY what it was looking for and couldn't find. Two seconds later I fixed the problem. Your site is going in my list of treasured bookmarks for sure. Thanks again!

Thank you very much. Very useful inforation, otherwise it is difficult to figureout the exact problem. Thanks Mahesh

thank you thank you!!! thank you thank you!!! thank you thank you!!!

Gr8 Tip!!!

Thanks a lot for saving my time.

Hi thanks for the info! Do you happen to know how to do this in MOSS running in a load balanced server? Thanks!

I followed your post and am still getting the error and not an asp page. Any ideas?

After making changes to web.config file, I think we need to do iisreset, otherwise, you may get server error in "/" application.

You are the man!! You're truly my personal hero!! I love you mate!!!

Hi Thanks for solution.This saves lot of time for developers

Also bear in mind that the _layouts virtual directory has it's own web.config, you'll need to edit this too to get stack dumps from pages under the _layouts directory. -Gsvin

thanks, man, it helps me a lot today to find out the problem and fixed it.

Exactly which web.config file do you modify? I see like 10 of them on here for the sharepoint setup I have...?

Thanks boss u made my day

Thanks boss u made my day

Gavin, Iam looking for correct web.config to modify myself. I found this info: In a Microsoft® Windows® SharePoint™ Services deployment, web.config files are contained in the following folders within the file system: Local_Drive:\Inetpub\wwwroot — The web.config file of the top-level content root folder that defines configuration settings for the virtual server of the default Web site in the Windows SharePoint Services deployment. In addition, the content root folder includes a \wpresources folder that contains a web.config file used in Web Part resources. Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources — A web.config file that is used in Web Part resources for the Global Assembly Cache (GAC). Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\CONFIG — The web.config file and other .config files that together define configuration settings for extending other virtual servers. Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\ISAPI — The web.config file that defines configuration settings for the /_vti_bin virtual directory. Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\LAYOUTS — The web.config file that defines configuration settings for the /_layouts virtual directory. Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\ADMIN\Locale_ID — The web.config file that defines configuration settings for pages used in SharePoint Central Administration. Also previouly was posted by Vince: Your web.config is in the root of your web application. By default these will be in the C:\Inetpub\wwwroot\wss\VirtualDirectories folder. Generally the name of the folder for your site will be either the machine name with a number or the host header with a number. This can be different if the person who created the web application chose a different folder name. You can also find out the folder from within the IIS manager. Good Luck! :o)

Excellent tip! It saved lot of my time in development. Thank you very much!

Thank you...

Thanks

thanks

Thanks alot, really a big help.

Thanks bro... It works....

thanks

thanks...saved me a lot of time...

OMG, I love you man!!! You really helped! I was so frustrated with "unexpected shit occurred" and finally I saw this post. Man, you rock!!!!

THANKS FOR THIS GREAT INFO.

very useful tip

Don't you hate it when something like this is such a simple solution. Thanks.

thank you very much

Amazing. Thanks so much.

thank you my friends.

thank you very much

thankss youu

thank you admin.

Thank You...

thx a lot .....

thank you cano..

thank you kanka

thank you seoking..

thank you kral

thank you mcks

thanks admin sagol

thank s admin

This is owesome. I had spent 3 days to figure the problem but just couple of changes to Web.Config saved me

thank you babacan

thank you very good brother

you are my desire..

thank you seoking..

thank you

thank you kanka

thank youu

thanks kanka

Thank You

thank you

thanks

thank you.

turkish justin tv..

thank you

thank you

Ok, I see all the thank you's and you're a life saver etc etc... But what I still don't see is what caused the error in the first place. Everyone that reads these boards are not developers, so even if I looked at the web.config file and made these changes, it still doesn't tell me what the heck caused this in the first place. Thats the answer i'm looking for. A plain and simple answer...

Thank you...

You saved my life.... :)

You made my day! Thanks for this!

Thank You Admin

hallo i wish you verry succes operator

Really a thankful solution. Thanks a lot!!!![:)]

Thanks a lot :)

Thank You

thank

Thank You Admin

hallo i wish you verry succes operator

hallo dear friends thanks a lot for your workshop

hallo i wish you verry succes operator

The purpose of not provided detailed error reports surrounds security. This is fine in a dev evnironment but I wouldn't recommend it in production. Your trace logs set to verbose should provide all the detail you need. That being said, I believe there's a way to get detailed errors being displayed when accessing the site while directly on a WFE but still provide the clumsy custom error to end users.

hello ! thanks !

Thank You page admin

thank you kanka

Thaan you erkan kanka:D

Saol un beyler

thank you for your help!!!

thank you very much my friends..

thank you very much my friends..

Thank you ... very much

I am grateful to you for this great content.

hallo dear friends thanks a lot for your workshop

Thanks very much...

Great thread, at least now I have a point to start searching for what is wrong... thanks to all of you

good post thank you

many thanks!

I tried your method, it works fine with most... But there is still a page in my environment is still giving me 'unexpected error has occured' even after the settings are configured...other pages can display the error message fine though. any idea?

Thank you

And any one help me..one the web.config file has been updated as above..i been facing with / application error as..where we need to change this code.?

Good Saved me Thanks again :)

And any one help me..one the web.config file has been updated as above..i been facing with / application error as..where we need to change this code.?

Good Saved me Thanks again :)

You Saved us!!!

Thank youss Saved

tnk you sohbet odaları

tnk you mirc indir

tnk you sohbet

tnkyou

thank you veRRy good :))

Thank you sooo much :)

2+ years later, a BIG THANKS to you. =)

tnlyou

thanks you admin

chat rooms turkish thank you very much..

Really a thankful solution. Thanks a lot!!!!

WOW . East or west you are the best. Sai

Callstack

You just saved me a lot of time, Thanks!

Thanks for the info!!!!

lez sohbet odaları thnk you

lez sohbet odaları thnk you

Veramente un bel casino tutta questa storia. Non è che ho capito proprio tutto, ma semnbra davero interessante.

Brilliant Tip! Changed the file, refreshed the page and it said SQL Logon error! Reset the SQL services and all now fine and dandy!

Thanks 1,000,000!

thanks for nice ı love site

Thanks verry good

very useful informations

Nice post, thanks for

nice..Thank you...

it's great

very useful. i'ts great. thank's. ...

Thank you, we happy we made these shares are

Good stuff Thanks

very useful informations

Veramente un bel casino tutta questa storia. Non è che ho capito proprio tutto, ma semnbra davero interessante.

admin sys gel git gel bir daha git

thank you good informations

Amended the web.config file as noted at the top of this post and now getting the follow stack error. Help, can someone point me in the right direction to work out what I need to do next? Stack Trace: [SPUpgradeException: An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177] Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility() +1805 Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) +61 Microsoft.SharePoint.SPWeb.InitializeSPRequest() +291 Microsoft.SharePoint.SPWeb.EnsureSPRequest() +58 Microsoft.SharePoint.SPWeb.get_Request() +54 Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) +400 Microsoft.SharePoint.WebControls.SPControl.GetContextWeb(HttpContext context) +31 Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object oSender, EventArgs ea) +385 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75