Troubleshoot

English: During the operation of our Reporting Service Server, one of our clients reported accidental reports unavailability. Following is the screen capture on his browser : Accoding to server maintenance history, there was no action performed on that server. So, what can caused this sudden unavailability?  To investigate the issue, we activate ASP.NET debuging in web.config, and browse to the report page. And now we have more precise information that Microsoft.

[Mike]( “mike70@hotmail.com”) - Feb 0, 2013 Hi and thanks for good info. I also found this great article on how to do it automartically: http://blog.viitaila.fi/2013/01/28/changing-the-product-key-of-windows-from-mak-to-kms-with-a-powershell-script/ [cakriwut]( “cakriwut@gmail.com”) - Feb 4, 2013 Thanks for the info.

English: As MSDN Ultimate subscriber, we may have access to volume license installer. In order to activate volume license, one can use MAK (Multiple Activation Key) or KMS (Key Management Service). You can imagine MAK as out-premise activation Microsoft’s and KMS as in-premise activation; both requires Administrator authorization. When VL activation is unsuccessful you can identify the reason by looking at the Activation Error Codes and find the description in Microsoft website.

English: During PowerPivot integration, I have found some issue which requires troubleshoot. Following are some errors and troubleshoot I have made Problem Error message during test connection procedure “A connection cannot be made. Ensure that the server is running.”. Description Error raised when you press “Test connection” during creation of new connection type. Resolution Make sure that you have associated web application and correct service application proxy. A different connection type may be served by different service application proxy.

English Today, for the first time after installing the latest version of 2010 families, I encounter this error “Cannot start service SPUserCodeV4”. This error message comes when I tried to deploy – sandboxed solution. Try to Google what would be the issue, I’ve found some blog here: http://littletalk.wordpress.com/2010/05/05/cannot-start-service-spusercodev4-when-deploy-sharepoint-webpart-in-vs-2010/ http://blog.dennus.net/2009/11/18/sp2010-spusercodev4-your-new-web-part-project-isnt-deploying/ However, in my case it is not “Microsoft SharePoint Foundation User Code Service”. It is “Microsoft SharePoint Foundation Sandboxed Code Service” instead.

Dimitri - Nov 5, 2009 Thanks, this really saved my day! :) prostonut - Mar 2, 2010 Hi there Just one correction about SQL: the SQL order is not right. You have to delete from Object tables first and after that delete it from Classes cakriwut - Mar 1, 2010 Thanks for the correction. [Felisha Orielly]( “Gloston27@yahoo.com”) - May 4, 2012 Thx for information.

Dimitri - Nov 5, 2009 Thanks, this really saved my day! :) prostonut - Mar 2, 2010 Hi there Just one correction about SQL: the SQL order is not right. You have to delete from Object tables first and after that delete it from Classes cakriwut - Mar 1, 2010 Thanks for the correction. [Felisha Orielly]( “Gloston27@yahoo.com”) - May 4, 2012 Thx for information.

English: In SharePoint, there is SPPropertyBag which can stores arbitrary key-and-value pairs into configuration database. And this is very good location compared with web.config. Moreover we can also create our custom class from SPPersistedObject to persist it state in a permanent store and retrieve it for later usage. (see MSDN refence SPPersistedObject) But don’t be so happy – the SPPropertyBag can only store primitive types such as strings, integers, and GUID; and collection of above.

English: In SharePoint, there is SPPropertyBag which can stores arbitrary key-and-value pairs into configuration database. And this is very good location compared with web.config. Moreover we can also create our custom class from SPPersistedObject to persist it state in a permanent store and retrieve it for later usage. (see MSDN refence SPPersistedObject) But don’t be so happy – the SPPropertyBag can only store primitive types such as strings, integers, and GUID; and collection of above.