Diagnose Missing. Web. Part and Missing. Assembly issues from the Share. Scalable Fabric task management system. A central focus area, defined by you, contains windows that behave in the traditional way. When you drag a window. A popular multifunction virtualizer for Windows and Linux. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/65/88/metablogapi/6560.image_718C5176.png' alt='Cara Install Sql Server 2008 Management Studio Express' title='Cara Install Sql Server 2008 Management Studio Express' />Point Health Analyzer using Power. Shell. After posting articles on diagnosing Missing. Feature and Missing. Setup. File errors in the Share. HP needs 68 weeks to ship additional TouchPads, according to a leaked email sent to customers. HP is prepping one last run for its defunct tablet. Download the free trial version below to get started. Doubleclick the downloaded file to install the software. Phil, Thank you so much for this series of posts this and 2 others. To anyone having trouble getting the PowerShell scripts to run, you can just hijack Phils SQL. Point 2. 01. 0 Health Analyzer and Test SPContent. Database operation, I have become slightly obsessed with doing the same for other errors, too. I have also had my fair share of them on migration projects recently, so I cant be the only one experiencing them at the moment. In this article I am going to focus on Missing. Web. Part and Missing. Assembly errors. As stated in previous articles, there is no silver bullet to solving these errors in all cases, but the scripts offered here will allow you troubleshoot the errors further to find exactly where they are happening in the content database. Once you know this, you have a fighting chance of being able to solve the problem. Missing. Web. Part Error. In this example, I have received the following error whilst running a Test SPContent. Mz87v8fpr4U/hqdefault.jpg' alt='Cara Install Sql Server 2008 Management Studio Express' title='Cara Install Sql Server 2008 Management Studio Express' />Database operation after a content database migration from Share. Point 2. 00. 7 to 2. It also appears in the Share. Point Health Analyzer under the Configuration category with the title Missing server side dependencies Category Missing. Web. Part. Error True. Upgrade. Blocking False. Message Web. Part class 4. 57. SP2. 01. 0Content, but is not installed on the current farm. Please install any featuresolution which contains this web part. Remedy One or more web parts are referenced in the database SP2. Content, but are not installed on the current farm. MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/81/88/metablogapi/1665.image_32EBCB1A.png' alt='Cara Install Sql Server 2008 Management Studio Express' title='Cara Install Sql Server 2008 Management Studio Express' />Please install any feature or solution which contains these web parts. As you can see, the error gives you a Web. Part class GUID, the name of the content database, and how many times it is referenced in the database, but little else. What we need to find out here is either the name of the web part or on which pages it is referenced in the database. For this I am going to reuse the Run SQLQuery Power. Shell script that I introduced in my article on Missing. Setup. File errors function Run SQLQuery Sql. Server, Sql. Database, Sql. Issuu is a digital publishing platform that makes it simple to publish magazines, catalogs, newspapers, books, and more online. Easily share your publications and get. Tabtight professional, free when you need it, VPN service. You have not yet voted on this site If you have already visited the site, please help us classify the good from the bad by voting on this site. QuerySql. Connection New Object System. Data. Sql. Client. Sql. ConnectionSql. Connection. Connection. String Server Sql. Server Database Sql. Database Integrated Security TrueSql. Cmd New Object System. Data. Sql. Client. Sql. CommandSql. Cmd. Command. Text Sql. QuerySql. Cmd. Connection Sql. ConnectionSql. Adapter New Object System. Data. Sql. Client. Sql. Data. AdapterSql. Adapter. Select. Command Sql. CmdData. Set New Object System. Data. Data. SetSql. Adapter. FillData. SetSql. Connection. CloseData. Set. Tables0Once you have loaded the function in a Power. Shell console, you can run it by using the Run SQLQuery command with the options relevant to your deployment. For Missing. Web. Part errors, you need to run a SQL SELECT query on the All. Docs table in the content database exhibiting the problem, joining to the All. Web. Parts table in order to find details about the missing web part. For example, you would type the following command to find details of the web part with the class ID 4. Run SQLQuery Sql. Server SQLSERVER Sql. Database SP2. 01. Content Sql. Query SELECT from All. Docs inner join All. Web. Parts on All. Docs. Id All. Web. Parts. tpPage. Url. ID where All. Web. Parts. tpWeb. Part. Type. ID 4. 57. Id, Site. Id, Dir. Name, Leaf. Name, Web. Id, List. Id, tpZone. ID, tpDisplay. Name Format List. Yes, it is a pretty long command, but it will produce a very useful output, as shown in this example Id 6ab. Site. Id 3. Dir. Name NewsPages. Leaf. Name Article. List. aspx. Web. Id dcc. List. Id 7e. Zone. ID BodytpDisplay. Name Id b. Site. Id 3. Dir. Name Pages. Leaf. Name Welcome. Web. Id 2ae. List. Id d. Zone. ID Right. Column. ZonetpDisplay. Name This tells us that the web part has been found on two pages the references mentioned in the Missing. Web. Part error. Site. Id tells us the site collection and Web. Id the site where the pages are located. We also have a Dir. Name showing the relative path and the page name itself against the Leaf. Name property. If youre lucky, you might get the display name of the web part against the tpDisplay. Name property, but if not, you should at least be able to tell which zone the web part has been added to by looking at the tpZone. ID property. Easily the best way of resolving these issues is to do as the error suggests and install the missing feature or solution containing the web part, but if this is not possible or feasible to do in your scenario, we can discover the site collection URL from the GUIDs using Power. Shell and then remove the offending web parts from the pages specified. To find the site collection URL using the information output from the query, type the following command site Get SPSite Limit all where. Id eq 3. 37c. 57. Url. One you have the site collection URL, you can use the relative path specified by the Dir. Name property to find the location of the file. To remove the web part from the page, type the page URL in the browser and add For example, to open the web part maintenance page for the Article. List. aspx page specified in the output, type the following URL in the browser http portalnewspagesarticlelist. You can then highlight the offending web part normally called Error. Web. Part for Missing. Web. Part errors by ticking the box and clicking Delete. The screenshot below shows a web part maintenance page to give you an idea of the UI, but not an example of an Error. Web. Part as I had already removed them Note If you remove an Error. Web. Part from a publishing page with versioning switched on, you may have to delete all earlier versions of the page before the error disappears from the Share. Point Health Analyzer or Test SPContent. Database report. This is because the web part will still be referenced from these versions, even though you removed it from the currently published page. Missing. Assembly Error. Missing. Assembly errors look similar to this one Category Missing. Assembly. Error True. Upgrade. Blocking False. Emulator Iphone. Message Assembly PAC. Share. Point. Tagging, Version1. Cultureneutral, Public. Key. Tokenb. 50. SP2. Content, but is not installed on the current farm. Please install any featuresolution which contains this assembly. Remedy One or more assemblies are referenced in the database SP2. Content, but are not installed on the current farm. Please install any feature or solution which contains these assemblies. I normally find Missing. Assembly errors appear as the result of an event receiver, which is still registered on a list or library but part of a featuresolution no longer present on the farm. In most cases, you may be able to look at the assembly name reported in this error and know what the problem is straight away. As before, the best way of resolving this is to reinstall the missing solution file. However, if you are not able to install the solution e. Share. Point 2. 00. To troubleshoot this issue we can re use the Run SQLQuery function used to help find missing web parts above. The table we need to look at this time though is called Event.