Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 2 down vote favorite
1

When doing any sort of development/testing work against SharePoint Online, there are bound to be some errors. Some errors manifest in the form of exceptions, which can be logged to a special-purpose SharePoint list for error details. Other errors, though, cannot be caught as exceptions. For instance:

Error 
Sandboxed code execution request failed. 

Troubleshoot issues with Microsoft SharePoint Foundation. 

Correlation ID: 9cde387c-b460-4731-9681-450a7c890310 

Date and Time: 5/16/2012 4:42:13 AM

On the server version, I would check the logs for the correlation ID to get a detailed stack trace, conditions around the error, etc. Is there any way to get this log information in SharePoint Online?

share|improve this question

1 Answer

up vote 4 down vote accepted

You best chance is to try at least four things while debugging:

  • Use logging library "SharePoint Sandbox Logging" to log errors on feature activation, as you probably know logging capabilities on Sandbox are limited.
  • Have Correlation Id with your error? contact Microsoft support
  • Review SharePoint logs for on-premises Sandbox to check for any errors, warnings that appear during activation
  • Try Literal Debugging
share|improve this answer
Thanks. I'm assuming your third point means testing in a local farm before deployment to SharePoint Online? The problem is there often seem to pop up problems in SharePoint Online which don't manifest in the local sandbox. That "Literal debugging" link is priceless, by the way. Very retro. – Geir Smestad May 16 '12 at 12:35
Yup, on-premises stands for you local Sandbox solution, really, worth a try – Falak Mahmood May 16 '12 at 12:55

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.