tag:blogger.com,1999:blog-4702950152327976706.post7346321028275691071..comments2024-03-27T19:28:01.524-07:00Comments on Just geeks: Resolving Missing References when upgrading to SharePoint 2010Brent Vhttp://www.blogger.com/profile/15891142062380248367noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4702950152327976706.post-34339474777766239262016-01-18T01:42:00.717-07:002016-01-18T01:42:00.717-07:00Ditto to the other posts - just what I needed to k...Ditto to the other posts - just what I needed to know. Perfect :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-73813767727255035692014-11-11T11:30:41.487-07:002014-11-11T11:30:41.487-07:00This was so helpful, thanks a million.This was so helpful, thanks a million.Drewhttps://www.blogger.com/profile/01918705800589662683noreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-11329374631937073142014-09-03T12:13:02.314-07:002014-09-03T12:13:02.314-07:00Hi Brent. This is a great post and I need the info...Hi Brent. This is a great post and I need the information, but in step 1 you say that "In my case, I deleted the site since it was not used and had not children sites" but you don't say how you did this. Can you tell me how you did it?<br /><br />Thanks a bunch.Christine Lisihttps://www.blogger.com/profile/10956275677211783219noreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-81749852961771870762013-02-21T08:45:34.447-07:002013-02-21T08:45:34.447-07:00Anonymous,
It could be a clean up issue if the it...Anonymous,<br /><br />It could be a clean up issue if the item is not needed anymore, or it could be that if you still need and use the functionality that you need to include a reference to the missing item. In your case, I am guessing that the workflow solution was not there and had to be re-installed (redeployed) to fix the problem. If you moved servers, changed environment, etc this would not unexpected, but if you have not changed anything I would not expect to get the errors. In general something has to have changed without SharePoint knowing about it before you will get this error. <br /><br />Hope that helps some...<br /><br />Thank you,<br /><br />BrentBrent Vhttps://www.blogger.com/profile/15891142062380248367noreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-69720208294596690462013-02-20T04:34:50.674-07:002013-02-20T04:34:50.674-07:00Is there any reason why we get these errors/warnin...Is there any reason why we get these errors/warnings? Or is it just a lack of cleanup that SharePoint shows and that should be fixed manually by us?<br /><br />I get this error on custom workflow solutions I've built with Visual Studio. All I do is update my code in Visual Studio, then run a deploy. Am I missing something that causes these messages to pop up?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-47407707527362979722013-01-30T13:54:41.847-07:002013-01-30T13:54:41.847-07:00Very helpful, thanksVery helpful, thanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4702950152327976706.post-36177603417710006852012-09-21T05:21:37.564-07:002012-09-21T05:21:37.564-07:00Kudo's. Thanks very much. I had a terrible tim...Kudo's. Thanks very much. I had a terrible time with custom templates missing. For one we had taken the time to follow this advice:<br />http://sptechpoint.wordpress.com/2009/12/23/creating-a-custom-site-definition-with-a-custom-master-page/<br />But we didn't have the original WEBTEMPcustom.xml correct. I simply followed your advice to set the webs webtemplate to something we had - 1, re-export and import and it worked. Thanks again.<br />-TomAnonymoushttps://www.blogger.com/profile/15435522712178438286noreply@blogger.com