Hello, I was wondering if anyone could shed some light on why it is that when I export a MP via the GUI, a slew of superfluous, unneeded references are added (to Manifest\References) which, when subsequently removed with a text editor, cause no grief when attempting to import the MP afterwards (proving that the references were indeed unneeded). Thanks, Larry

What are the superfluous, unneeded references that were removed?HTH, Jonathan Almquist - MSFT

Hi, I am writing to check if there is any update regarding this issue.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Larry - these were not added when exporting. Exporting adds no references. These were always there - and were added (likely by mistake) when some component in the MP made reference to the remote objects in other MP's. If these objects (such as a group or an override) are removed - then the reference remains in the manifest section, even though there are no objects left in the MP which require it. This is by design - there is no requirement in XML that you cannot have a reference even if unused - sometimes this is advantageous when you want to create references during the MP design stage because you want to create workflows that will use or reference other datasources or object types in remote MP's. Kevin Holman

Hello Jonathan, Below are the references that appear to get added. To be clear, I export the MP, manually update it by removing the unneeded referrences, and re-import it. When I subsequently re-export the MP, the references are once again added! <Reference Alias="MicrosoftSystemCenterInteropHPOVOConnector6170430"> <ID>Microsoft.SystemCenter.Interop.HPOVO.Connector</ID> <Version>6.1.7043.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftWindowsInternetInformationServicesCommonLibrary6066580"> <ID>Microsoft.Windows.InternetInformationServices.CommonLibrary</ID> <Version>6.0.6658.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftWindows2008ClusterManagementMonitoring6067200"> <ID>Microsoft.Windows.2008.Cluster.Management.Monitoring</ID> <Version>6.0.6720.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftSystemCenterOperationsManager20076176720"> <ID>Microsoft.SystemCenter.OperationsManager.2007</ID> <Version>6.1.7672.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftUnixViews617000256"> <ID>Microsoft.Unix.Views</ID> <Version>6.1.7000.256</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftSystemCenterInternal6172210"> <ID>Microsoft.SystemCenter.Internal</ID> <Version>6.1.7221.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftWindows2003ClusterManagementLibrary6067200"> <ID>Microsoft.Windows.2003.Cluster.Management.Library</ID> <Version>6.0.6720.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftWindowsClientLibrary6062780"> <ID>Microsoft.Windows.Client.Library</ID> <Version>6.0.6278.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="QuestSpotlightADAMMP11014"> <ID>Quest.Spotlight.ADAM.MP</ID> <Version>1.1.0.14</Version> <PublicKeyToken>a88189d7c4e196c5</PublicKeyToken> </Reference> <Reference Alias="SecureVantageSecurityGPAMonitoring402339"> <ID>SecureVantage.Security.GPA.Monitoring</ID> <Version>4.0.2.339</Version> <PublicKeyToken>60b527b13d975a39</PublicKeyToken> </Reference> <Reference Alias="MicrosoftSystemCenterOperationsManagerInternal6172210"> <ID>Microsoft.SystemCenter.OperationsManager.Internal</ID> <Version>6.1.7221.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="MicrosoftWindowsServerLibrary6067940"> <ID>Microsoft.Windows.Server.Library</ID> <Version>6.0.6794.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> <Reference Alias="SecureVantageSecurityGPADiscovery402339"> <ID>SecureVantage.Security.GPA.Discovery</ID> <Version>4.0.2.339</Version> <PublicKeyToken>60b527b13d975a39</PublicKeyToken> </Reference> <Reference Alias="SecureVantageSecurityBaseLibrary402339"> <ID>SecureVantage.Security.Base.Library</ID> <Version>4.0.2.339</Version> <PublicKeyToken>60b527b13d975a39</PublicKeyToken> </Reference> Thanks, Larry

Hello Kevin, I appreciate your taking the time to answer! As mentioned in my reply to Jonathan above, I export the MP, edit it by removing the unnecessary references, and re-import it back into the MG. When I subsequently re-export the MP, the references are once again added! Hmmm, or at least they appear to be added! Is it possible that importing the cleaned MP didn't really crush the unneeded references?!? Thanks, Larry

i've seen this on numerous occasions as well when creating a new mp, create 1 one rule it in and then export it for further editing in the authoring console or something. instead of having 3-4 references it has like all references to all mp's in my mg. They were definitely unneeded as i removed them, signed the mp and imported the mp also on several occasions.Rob Korving http://jama00.wordpress.com/

There are some standard references that are always added to a MP by default, but I haven't seen this before where several other MP references were added (and possibly all MP's in MG were referenced). Can you tell me what exactly is in your MP that continues to have this problem with references being added? Also, do you notice this happening with any of your other MP's, or just this one?HTH, Jonathan Almquist - MSFT

I have seen this also on our test environment. Created an MP and all management packs were included in the reference section. It appeared to me that during the creation some time-out occurs and as a solution all management packs are included in the reference section ???Regards, Marc Klaver http://jama00.wordpress.com/

For those that are observing this behavior, can you share what version and CU you are running in these environments? I haven't noticed this problem, and I'm not seeing this in my lab environments either. Thanks.HTH, Jonathan Almquist - MSFT

r2 cu3, but i'm pretty sure we observed this behaviour in cu1 as well (we skipped cu2).Rob Korving http://jama00.wordpress.com/

Jonathan, We are running R2 CU2. Thanks, Larry

Jonathan, I examined a newly created MP and the exported version is clean. It is certainly a problem with the MP in question (a SQL Server overrides MP)! Kevin's explanation would explain the behaviour (though not the cause), as re-importing a cleaned version of the MP does not appear to actually remove the unneeded references. If this is the case, then how do I clean this mess up? Larry

It does seem to be a nuisance and a perplexing problem, but this shouldn't effect you operationally anyway... If you popped this MP up on a file share somewhere, I could take a look at it. Maybe import into my lab and see if I get similar results. Suppose that's the best I can do from here.HTH, Jonathan Almquist - MSFT

Unless you update (increment) the MP version, on re-import, no changes will be recognized. Try your test after updating the version. Since these are MP's from different vendors, the "these are probably standard" is highly unlikely. Further, many of them seem to be override MP's, so they weren't even commercial MPs.Microsoft Corporation

Unless you update (increment) the MP version, on re-import, no changes will be recognized. Try your test after updating the version. Since these are MP's from different vendors, the "these are probably standard" is highly unlikely. Further, many of them seem to be override MP's, so they weren't even commercial MPs. Microsoft Corporation That sounds like a logical next step. Does this work for you, Larry?HTH, Jonathan Almquist - MSFT

Hello, Based on Dan's response, a light had clicked! We have not yet implemented any versionning in our overrides MPs, as updates to unsealed MPs do not require an updated version # (I have testing this countless times)! Having said this, I proceeded to test Dan's suggestion, and I now find myself unable to reproduce the problem! It seems that the problem has disappeared since the recent changes that made! :( Larry P.S. I'll see if I can re-produce the problem with other override MPs...