Publishing: Variation Hierarchy creation fails when the variation root's Pages library is set to not require checkout
- Clearly this is a bug, and I know the workaround but where can I log this as an issue? Connect has no way to submit issues back to the sharepoint team. The affected product is MOSS Enterprise SP2 (no CUs applied)
Repro:
- Create a site collection with publishing template (e.g. at /)
- Create variation labels (e.g. english/french)
- Modify the root /Pages library (which will eventually host the VariationRoot.aspx page) to NOT require checkout for editing files (via settings > versions)
- Attempt to create hierarchy
Failed
Result from LRO log:
<error><message>The file "Pages/VariationRoot.aspx" is not checked out.</message><full>Microsoft.SharePoint.SPException: The file "Pages/VariationRoot.aspx" is not checked out. ---> System.Runtime.InteropServices.COMException (0x8107090F): The file "Pages/VariationRoot.aspx" is not checked out.
at Microsoft.SharePoint.Library.SPRequestInternalClass.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
at Microsoft.SharePoint.Library.SPRequest.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.CheckInFile(String bstrUrl, String bstrWebRelativeUrl, Int32 iCheckinType, String bstrCheckinComment, Boolean bIsMigrate, Int32 iEditorId)
at Microsoft.SharePoint.SPFile.CheckIn(String comment, SPCheckinType checkInType, Boolean bIsMigrate, SPUser modifiedBy)
at Microsoft.SharePoint.SPFile.CheckIn(String comment, SPCheckinType checkInType)
at Microsoft.SharePoint.Publishing.Internal.VariationSettings.CreateVariationRootPage(PublishingWeb area)
at Microsoft.SharePoint.Publishing.Internal.VariationSettings.CreateHierarchies(LongRunningOperationJob lroLogger, List`1 errors)
at Microsoft.SharePoint.Publishing.Internal.WebControls.CreateVariationHierarchiesLro.CreateVariationHierarchies()</full><customData>The file "Pages/VariationRoot.aspx" is not checked out.</customData></error>
Cleary the answer is to leave the root Pages library alone, however, it took us a long long time to find this issue because we were using a custom feature to create the variations hierarchy in a custom site definition (ONET.xml) - lots of mud in the way.
So, where can we log these things?
-Oisin- Edited byMike Walsh MVPMVP, ModeratorFriday, November 06, 2009 4:59 AMUnnecessary Caps removed from Title
- Edited byOisin GrehanMVPFriday, November 06, 2009 4:11 PM"fix" -> "workaround"
Answers
Hi Oisin,
I understand your concern, if this is a bug, then you could request a refund and there is no charge for bugs.
Please understand I could not confirm this is a bug or not because it is beyond my authority.
I agree with you on the following factors:
1) Setting the Pages library to not require checkout is a valid and legal operation
2) Creating a variation hierarchy is a valid and legal operation
However, I am not sure whether it is true that “3) Operations 1) and 2) are independent and unrelated operations”.
That is why I suggest you to contact premier support, and they could help you to check the internal logic then give you a proper answer which I can’t.
Based on my understanding, Variations use in planning phrase. During the planning, I seldom change the SharePoint settings. If possible, I would like to ask you to create you custom solution based on default SharePoint settings.
Last but not the least, in connect.microsoft.com, you could submit your feedback at:
https://connect.microsoft.com/feedback/default.aspx?SiteID=428
Lambert Qin
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact mtngfb@microsoft.com
Sincerely,Lambert QinPosting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byOisin GrehanMVPMonday, November 09, 2009 3:24 PM
All Replies
Hi Oisin,
I would reproduce your issue in my local, and I could not find any information logged in our internal database.
It is hard for me to say this is a bug because:
1. An simple solution is that to leave the root Pages library alone as you said.
2. I do not have the authority to view the source code.
If you really need to confirm this, I suggest you to contact Microsoft Customer Support Services (CSS) via telephone so that a dedicated Support Professional can assist you in a more efficient manner.
Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Sorry for your inconvenience.
Lambert Qin
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact mtngfb@microsoft.com
Sincerely,Lambert QinPosting is provided "AS IS" with no warranties, and confers no rights.- Hi Lambert,
So you're telling me:
- You can reproduce the issue
- You can't find it in your internal bugs database
- You can't examine the source
- You want me to pay $$$ to report the bug to someone who can actually verify it
It is a bug because:
1) Setting the Pages library to not require checkout is a valid and legal operation
2) Creating a variation hierachy is a valid and legal operation
and finally:
3) Operations 1) and 2) are independent and unrelated operations
The variation creation code throwing an unhandled exception and failing to create the variation hierarchy is not an expected result from performing step 2.
Please advise.
-Oisin
update: Lambert, please do not take this personally - I just wish SharePoint would have a proper site on connect.microsoft.com- Edited byOisin GrehanMVPFriday, November 06, 2009 4:10 PMtypo
- Edited byOisin GrehanMVPFriday, November 06, 2009 11:09 PMnote to support guy
Hi Oisin,
I understand your concern, if this is a bug, then you could request a refund and there is no charge for bugs.
Please understand I could not confirm this is a bug or not because it is beyond my authority.
I agree with you on the following factors:
1) Setting the Pages library to not require checkout is a valid and legal operation
2) Creating a variation hierarchy is a valid and legal operation
However, I am not sure whether it is true that “3) Operations 1) and 2) are independent and unrelated operations”.
That is why I suggest you to contact premier support, and they could help you to check the internal logic then give you a proper answer which I can’t.
Based on my understanding, Variations use in planning phrase. During the planning, I seldom change the SharePoint settings. If possible, I would like to ask you to create you custom solution based on default SharePoint settings.
Last but not the least, in connect.microsoft.com, you could submit your feedback at:
https://connect.microsoft.com/feedback/default.aspx?SiteID=428
Lambert Qin
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact mtngfb@microsoft.com
Sincerely,Lambert QinPosting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byOisin GrehanMVPMonday, November 09, 2009 3:24 PM
- Hi Oisin,
Thanks for reporting the issue. I am from SharePoint product team. We have confirmed this is a known issue. The fix is part of SharePoint 2010 Beta.
Sincerely,
Clement Yau
This posting is provided "AS IS" with no warranties, and confers no rights.
