We have a user who receives the following error message when attempting to open 2 specific custom views within Service Manager 2010.

Error message detail:

Date: 8/05/2014 7:20:14 AM
Application: System Center Service Manager Console
Application Version: 7.0.6555.0
Severity: Error
Message: An error occurred while loading the items.

Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportException: The Full adapter threw an exception. See the FullUpdate property to see the exception.
   at Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportAdapter.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)
   at Microsoft.EnterpriseManagement.UI.DataModel.QueryQueue.StartExecuteQuery(Object sender, ConsoleJobEventArgs e)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

We have seen the fixes in regards to this issue - which involves changing the code of management packs, however changing the management pack would mean that it would change for all department staff instead of this one particular user who has this issue. 

We are hesitant in doing this as it may cause an error for the rest of the staff who are not receiving the error.

Has anyone dealt with a similar situation before?

Any advice would be helpful.

Hi,

Wow - SCSM 2010! Time to upgrade? :)

Have you tried removing the Service Manager temporary files in his User Profile? / Do the same user have the exact same error from another computer?

Regards
//Anders

So this type of error "Full adapter threw an exception" relates to the view engine in the console which still happens in 2012 & R2, but much more rarely. This is actually a large class of view rendering & data acquisition bugs that all have to be shot down independently (much like how "cancer" is a class of hundreds of unique DNA coding errors that all cause similar, but variable, overgrowth behavior in different malfunctioning cell types, rather then a single monolithic disease).

Anders' certainly has a point, later versions are much better about this then earlier, but in-place upgrades are not as easy as they should be sometimes. if you do plan to upgrade, i recommend cloning your existing production environment into a isolated lab, upgrading the lab, figuring out what breaks, and using that to plan for your production upgrade. 

Thanks..... sorry for the late reply...... the user ended up leaving our department (not because of this issue haha)

So events have resolved the issue.

P.S we have now upgraded to SCSM 2012, we are sorting through just as many bugs with that now.........sigh....