Greetings all,

Go easy on me, it's my first post.

So a little background. Looking at doing a migration of content and such
from one MOSS install to another as part of an initial release. Both
servers are running MOSS 2007, service packed and good to go.

For this migration, I'm using:

stsadm -o export -url http://moss -filename
c:\temp\bulkexport.cab -overwrite -versions 4 -includeusersecurity -cabsize
300

and the corresponding import after setup at the other end. For this I get no
errors and just one warning related to a Web Part issue I'm currently
investigating (likely not related to the below issue, as it's a single Web
Part).
I've succeeded in testing the migration with only a few small issues.

1. We're getting an error on some pages similar to the following:

Unable to display this Web Part. To troubleshoot the problem, open this Web
page in a Windows SharePoint Services-compatible HTML editor such as
Microsoft Office SharePoint Designer. If the problem persists, contact your
Web server administrator.

This is because some of the data lists are using XSLT transforms, therefore
are using webparts. The code for these is similar to the following (it's a
little way down, apologies in advance, not easy to read). The problem is,
that when these pages are migrated, the GUIDs have to be manually
"realigned" in Sharepoint Designer on the destination MOSS server as they
don't match up correctly to the GUIDs of the lists. From the looks of this
url:

http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-part.html

this seems to be a bug with Sharepoint Designer, but what I'm unsure of is
how this is still a problem after migration. Only thing I can suggest (I'm
yet to test this theory out) is that it's possible from reading that the
GUIDs aren't aligned because of the missing braces? I'm going to do some
more investigation into this, but wondering if anyone had ideas. Note the
example below is *after* the GUIDs have been changed and enclosed with {}.
The fix stated on this blog post definately works in this case however.

<WebPartPages:WebPartZone runat="server" AllowPersonalization="false"
FrameType="TitleBarOnly" ID="TopZone"
Title="<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation="Vertical"
QuickAdd-GroupNames="Default"
QuickAdd-ShowListsAndLibraries="false"><ZoneTemplate>
<WebPartPages:DataFormWebPart runat="server"
SuppressWebPartChrome="False" Description="" PartImageSmall=""
DataSourceID="" MissingAssembly="Cannot import this Web Part."
FrameType="Default" ConnectionID="00000000-0000-0000-0000-000000000000"
DetailLink="/subdir/Lists/Archive/AllItems.aspx"
ExportControlledProperties="True" IsVisible="True" AllowRemove="True"
AllowEdit="True" ID="g_4008a0e8_872c_4b1c_976e_b17e55de1c40" Dir="Default"
FrameState="Normal" ViewContentTypeId="" AllowConnect="True" PageSize="-1"
AllowMinimize="True" IsIncludedFilter=""
TitleUrl="/subdir/Lists/Archive/AllItems.aspx" ShowWithSampleData="False"
HelpMode="Modeless" ExportMode="All" ViewFlag="0" Title="Recent Items"
HelpLink="" AllowHide="True" AllowZoneChange="True" PartOrder="1"
UseSQLDataSourcePaging="True" PartImageLarge="" IsIncluded="True"
NoDefaultStyle="TRUE" __MarkupType="vsattributemarkup"
__WebPartId="{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
__AllowXSLTEditing="true" WebPart="true" Height="" Width=""><DataSources>
<SharePoint:SPDataSource runat="server" DataSourceMode="List"
SelectCommand="&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
Name=&quot;Category&quot;
Ascending=&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/View&gt;"
UseInternalName="True"
ID="Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormParameter
ParameterKey="ListID" PropertyName="ParameterValues"
DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParameter
ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/subdir/"
Name="WebURL"></WebPartPages:DataFormParameter>
</SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
ParameterKey="ListID" PropertyName="ParameterValues"
DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParameter
ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/subdir/"
Name="WebURL"></WebPartPages:DataFormParameter>
</UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
ParameterKey="ListID" PropertyName="ParameterValues"
DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParameter
ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/subdir/"
Name="WebURL"></WebPartPages:DataFormParameter>
</InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
ParameterKey="ListID" PropertyName="ParameterValues"
DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParameter
ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/subdir/"
Name="WebURL"></WebPartPages:DataFormParameter>
</DeleteParameters>
</SharePoint:SPDataSource>
</DataSources>

2. After migration, hidden state of navigation items is not persisted. This
specific site has two levels of nav, so this is a bit of a pain. To fix
this, got to go into

Site Actions -> Site Settings -> Modify Navigation

for each nav area and hide the nav items as appropriate. Is there a better
way to go about migrating navigation items, so that their state (hidden or
not) is preserved? Am I missing something on export that would correct this
issue?

Thanks in advance, and hope I've explained everything legibly.

Cheers,
Gavin Jones
Developer
Enlighten Designs

Re: MOSS stsadm migration niggles by KZ

KZ
Wed Jun 11 15:16:38 CDT 2008

On 11 Jun, 07:28, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Greetings all,
>
> Go easy on me, it's my first post.
>
> So a little background. =A0Looking at doing a migration of content and suc=
h
> from one MOSS install to another as part of an initial release. =A0Both
> servers are running MOSS 2007, service packed and good to go.
>
> For this migration, I'm using:
>
> stsadm -o export -urlhttp://moss-filename
> c:\temp\bulkexport.cab -overwrite -versions 4 -includeusersecurity -cabsiz=
e
> 300
>
> and the corresponding import after setup at the other end. For this I get =
no
> errors and just one warning related to a Web Part issue I'm currently
> investigating (likely not related to the below issue, as it's a single Web=

> Part).
> I've succeeded in testing the migration with only a few small issues.
>
> 1. We're getting an error on some pages similar to the following:
>
> Unable to display this Web Part. To troubleshoot the problem, open this We=
b
> page in a Windows SharePoint Services-compatible HTML editor such as
> Microsoft Office SharePoint Designer. If the problem persists, contact you=
r
> Web server administrator.
>
> This is because some of the data lists are using XSLT transforms, therefor=
e
> are using webparts. =A0The code for these is similar to the following (it'=
s a
> little way down, apologies in advance, not easy to read). =A0The problem i=
s,
> that when these pages are migrated, the GUIDs have to be manually
> "realigned" in Sharepoint Designer on the destination MOSS server as they
> don't match up correctly to the GUIDs of the lists. =A0From the looks of t=
his
> url:
>
> http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-par...
>
> this seems to be a bug with Sharepoint Designer, but what I'm unsure of is=

> how this is still a problem after migration. =A0Only thing I can suggest (=
I'm
> yet to test this theory out) is that it's possible from reading that the
> GUIDs aren't aligned because of the missing braces? I'm going to do some
> more investigation into this, but wondering if anyone had ideas. =A0Note t=
he
> example below is *after* the GUIDs have been changed and enclosed with {}.=

> The fix stated on this blog post definately works in this case however.
>
> <WebPartPages:WebPartZone runat=3D"server" AllowPersonalization=3D"false"
> FrameType=3D"TitleBarOnly" ID=3D"TopZone"
> Title=3D"<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation=3D"Vertica=
l"
> QuickAdd-GroupNames=3D"Default"
> QuickAdd-ShowListsAndLibraries=3D"false"><ZoneTemplate>
> =A0 =A0 =A0 <WebPartPages:DataFormWebPart runat=3D"server"
> SuppressWebPartChrome=3D"False" Description=3D"" PartImageSmall=3D""
> DataSourceID=3D"" MissingAssembly=3D"Cannot import this Web Part."
> FrameType=3D"Default" ConnectionID=3D"00000000-0000-0000-0000-000000000000=
"
> DetailLink=3D"/subdir/Lists/Archive/AllItems.aspx"
> ExportControlledProperties=3D"True" IsVisible=3D"True" AllowRemove=3D"True=
"
> AllowEdit=3D"True" ID=3D"g_4008a0e8_872c_4b1c_976e_b17e55de1c40" Dir=3D"De=
fault"
> FrameState=3D"Normal" ViewContentTypeId=3D"" AllowConnect=3D"True" PageSiz=
e=3D"-1"
> AllowMinimize=3D"True" IsIncludedFilter=3D""
> TitleUrl=3D"/subdir/Lists/Archive/AllItems.aspx" ShowWithSampleData=3D"Fal=
se"
> HelpMode=3D"Modeless" ExportMode=3D"All" ViewFlag=3D"0" Title=3D"Recent It=
ems"
> HelpLink=3D"" AllowHide=3D"True" AllowZoneChange=3D"True" PartOrder=3D"1"
> UseSQLDataSourcePaging=3D"True" PartImageLarge=3D"" IsIncluded=3D"True"
> NoDefaultStyle=3D"TRUE" __MarkupType=3D"vsattributemarkup"
> __WebPartId=3D"{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
> __AllowXSLTEditing=3D"true" WebPart=3D"true" Height=3D"" Width=3D""><DataS=
ources>
> <SharePoint:SPDataSource runat=3D"server" DataSourceMode=3D"List"
> SelectCommand=3D"&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
> Name=3D&quot;Category&quot;
> Ascending=3D&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/View&g=
t;"
> UseInternalName=3D"True"
> ID=3D"Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormParame=
ter
> ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormPar=
ame=ADter
> ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues" DefaultValue=3D"/=
subdir/"
> Name=3D"WebURL"></WebPartPages:DataFormParameter>
> </SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
> ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormPar=
ame=ADter
> ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues" DefaultValue=3D"/=
subdir/"
> Name=3D"WebURL"></WebPartPages:DataFormParameter>
> </UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
> ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormPar=
ame=ADter
> ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues" DefaultValue=3D"/=
subdir/"
> Name=3D"WebURL"></WebPartPages:DataFormParameter>
> </InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
> ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormPar=
ame=ADter
> ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues" DefaultValue=3D"/=
subdir/"
> Name=3D"WebURL"></WebPartPages:DataFormParameter>
> </DeleteParameters>
> </SharePoint:SPDataSource>
> </DataSources>
>
> 2. After migration, hidden state of navigation items is not persisted. =A0=
This
> specific site has two levels of nav, so this is a bit of a pain. =A0To fix=

> this, got to go into
>
> Site Actions -> Site Settings -> Modify Navigation
>
> for each nav area and hide the nav items as appropriate. =A0Is there a bet=
ter
> way to go about migrating navigation items, so that their state (hidden or=

> not) is preserved? =A0Am I missing something on export that would correct =
this
> issue?
>
> Thanks in advance, and hope I've explained everything legibly.
>
> Cheers,
> Gavin Jones
> Developer
> Enlighten Designs

Thinking of the basics first, could you not use the deployment
schedules for this? Or, stsadm the site collection across (stsadm -o
backup -url <sourceurl> -filename <filename>) and then (stsadm -o
restore -url <targeturl> -filename <filename>)?

Re: MOSS stsadm migration niggles by Gavin

Gavin
Wed Jun 11 16:14:38 CDT 2008

Hey KZ, thanks for your time.

I'm still relatively new to this, so I'll do my best to explain.

By deployment schedules, are you meaning the content deployment interface
within the Central Administration section? If so, the two servers are
detached/isolated and hence I was looking into deployment in a detatched
fashion. Does this method include deployment of lists and navigation
components/settings? I'm gathering that detatched migrations are not common
or not recommended in this case?

As far as stsadm and backup vs export goes, I can give this a try.
Everything I've looked into discusses the use of "export" and "import" as
being the recommended approach for migration, so that's what I was using.

Cheers,
Gavin

----- Original Message -----
From: "KZ" <kezoe@screaming.net>
Newsgroups: microsoft.public.sharepoint.portalserver
Sent: Thursday, June 12, 2008 8:16 AM
Subject: Re: MOSS stsadm migration niggles

Thinking of the basics first, could you not use the deployment
schedules for this? Or, stsadm the site collection across (stsadm -o
backup -url <sourceurl> -filename <filename>) and then (stsadm -o
restore -url <targeturl> -filename <filename>)?

On 11 Jun, 07:28, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Greetings all,
>
> Go easy on me, it's my first post.
>
> So a little background. Looking at doing a migration of content and such
> from one MOSS install to another as part of an initial release. Both
> servers are running MOSS 2007, service packed and good to go.
>
> For this migration, I'm using:
>
> stsadm -o export -urlhttp://moss-filename
> c:\temp\bulkexport.cab -overwrite -versions
> 4 -includeusersecurity -cabsize
> 300
>
> and the corresponding import after setup at the other end. For this I get
> no
> errors and just one warning related to a Web Part issue I'm currently
> investigating (likely not related to the below issue, as it's a single Web
> Part).
> I've succeeded in testing the migration with only a few small issues.
>
> 1. We're getting an error on some pages similar to the following:
>
> Unable to display this Web Part. To troubleshoot the problem, open this
> Web
> page in a Windows SharePoint Services-compatible HTML editor such as
> Microsoft Office SharePoint Designer. If the problem persists, contact
> your
> Web server administrator.
>
> This is because some of the data lists are using XSLT transforms,
> therefore
> are using webparts. The code for these is similar to the following (it's a
> little way down, apologies in advance, not easy to read). The problem is,
> that when these pages are migrated, the GUIDs have to be manually
> "realigned" in Sharepoint Designer on the destination MOSS server as they
> don't match up correctly to the GUIDs of the lists. From the looks of this
> url:
>
> http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-par...
>
> this seems to be a bug with Sharepoint Designer, but what I'm unsure of is
> how this is still a problem after migration. Only thing I can suggest (I'm
> yet to test this theory out) is that it's possible from reading that the
> GUIDs aren't aligned because of the missing braces? I'm going to do some
> more investigation into this, but wondering if anyone had ideas. Note the
> example below is *after* the GUIDs have been changed and enclosed with {}.
> The fix stated on this blog post definately works in this case however.
>
> <WebPartPages:WebPartZone runat="server" AllowPersonalization="false"
> FrameType="TitleBarOnly" ID="TopZone"
> Title="<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation="Vertical"
> QuickAdd-GroupNames="Default"
> QuickAdd-ShowListsAndLibraries="false"><ZoneTemplate>
> <WebPartPages:DataFormWebPart runat="server"
> SuppressWebPartChrome="False" Description="" PartImageSmall=""
> DataSourceID="" MissingAssembly="Cannot import this Web Part."
> FrameType="Default" ConnectionID="00000000-0000-0000-0000-000000000000"
> DetailLink="/subdir/Lists/Archive/AllItems.aspx"
> ExportControlledProperties="True" IsVisible="True" AllowRemove="True"
> AllowEdit="True" ID="g_4008a0e8_872c_4b1c_976e_b17e55de1c40" Dir="Default"
> FrameState="Normal" ViewContentTypeId="" AllowConnect="True" PageSize="-1"
> AllowMinimize="True" IsIncludedFilter=""
> TitleUrl="/subdir/Lists/Archive/AllItems.aspx" ShowWithSampleData="False"
> HelpMode="Modeless" ExportMode="All" ViewFlag="0" Title="Recent Items"
> HelpLink="" AllowHide="True" AllowZoneChange="True" PartOrder="1"
> UseSQLDataSourcePaging="True" PartImageLarge="" IsIncluded="True"
> NoDefaultStyle="TRUE" __MarkupType="vsattributemarkup"
> __WebPartId="{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
> __AllowXSLTEditing="true" WebPart="true" Height="" Width=""><DataSources>
> <SharePoint:SPDataSource runat="server" DataSourceMode="List"
> SelectCommand="&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
> Name=&quot;Category&quot;
> Ascending=&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/View&gt;"
> UseInternalName="True"
> ID="Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormParameter
> ParameterKey="ListID" PropertyName="ParameterValues"
> DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­ter
> ParameterKey="WebURL" PropertyName="ParameterValues"
> DefaultValue="/subdir/"
> Name="WebURL"></WebPartPages:DataFormParameter>
> </SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
> ParameterKey="ListID" PropertyName="ParameterValues"
> DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­ter
> ParameterKey="WebURL" PropertyName="ParameterValues"
> DefaultValue="/subdir/"
> Name="WebURL"></WebPartPages:DataFormParameter>
> </UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
> ParameterKey="ListID" PropertyName="ParameterValues"
> DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­ter
> ParameterKey="WebURL" PropertyName="ParameterValues"
> DefaultValue="/subdir/"
> Name="WebURL"></WebPartPages:DataFormParameter>
> </InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
> ParameterKey="ListID" PropertyName="ParameterValues"
> DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­ter
> ParameterKey="WebURL" PropertyName="ParameterValues"
> DefaultValue="/subdir/"
> Name="WebURL"></WebPartPages:DataFormParameter>
> </DeleteParameters>
> </SharePoint:SPDataSource>
> </DataSources>
>
> 2. After migration, hidden state of navigation items is not persisted.
> This
> specific site has two levels of nav, so this is a bit of a pain. To fix
> this, got to go into
>
> Site Actions -> Site Settings -> Modify Navigation
>
> for each nav area and hide the nav items as appropriate. Is there a better
> way to go about migrating navigation items, so that their state (hidden or
> not) is preserved? Am I missing something on export that would correct
> this
> issue?
>
> Thanks in advance, and hope I've explained everything legibly.
>
> Cheers,
> Gavin Jones
> Developer
> Enlighten Designs




Re: MOSS stsadm migration niggles by KZ

KZ
Fri Jun 13 07:48:24 CDT 2008

On 11 Jun, 22:14, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Hey KZ, thanks for your time.
>
> I'm still relatively new to this, so I'll do my best to explain.
>
> By deployment schedules, are you meaning the content deployment interface
> within the Central Administration section? =A0If so, the two servers are
> detached/isolated and hence I was looking into deployment in a detatched
> fashion. =A0Does this method include deployment of lists and navigation
> components/settings? =A0I'm gathering that detatched migrations are not co=
mmon
> or not recommended in this case?
>
> As far as stsadm and backup vs export goes, I can give this a try.
> Everything I've looked into discusses the use of "export" and "import" as
> being the recommended approach for migration, so that's what I was using.
>
> Cheers,
> Gavin
>
>
>
> ----- Original Message -----
> From: "KZ" <ke...@screaming.net>
>
> Newsgroups: microsoft.public.sharepoint.portalserver
> Sent: Thursday, June 12, 2008 8:16 AM
> Subject: Re: MOSS stsadm migration niggles
>
> Thinking of the basics first, could you not use the deployment
> schedules for this? Or, stsadm the site collection across (stsadm -o
> backup -url <sourceurl> -filename <filename>) and then (stsadm -o
> restore -url <targeturl> -filename <filename>)?
>
> On 11 Jun, 07:28, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> > Greetings all,
>
> > Go easy on me, it's my first post.
>
> > So a little background. Looking at doing a migration of content and such=

> > from one MOSS install to another as part of an initial release. Both
> > servers are running MOSS 2007, service packed and good to go.
>
> > For this migration, I'm using:
>
> > stsadm -o export -urlhttp://moss-filename
> > c:\temp\bulkexport.cab -overwrite -versions
> > 4 -includeusersecurity -cabsize
> > 300
>
> > and the corresponding import after setup at the other end. For this I ge=
t
> > no
> > errors and just one warning related to a Web Part issue I'm currently
> > investigating (likely not related to the below issue, as it's a single W=
eb
> > Part).
> > I've succeeded in testing the migration with only a few small issues.
>
> > 1. We're getting an error on some pages similar to the following:
>
> > Unable to display this Web Part. To troubleshoot the problem, open this
> > Web
> > page in a Windows SharePoint Services-compatible HTML editor such as
> > Microsoft Office SharePoint Designer. If the problem persists, contact
> > your
> > Web server administrator.
>
> > This is because some of the data lists are using XSLT transforms,
> > therefore
> > are using webparts. The code for these is similar to the following (it's=
a
> > little way down, apologies in advance, not easy to read). The problem is=
,
> > that when these pages are migrated, the GUIDs have to be manually
> > "realigned" in Sharepoint Designer on the destination MOSS server as the=
y
> > don't match up correctly to the GUIDs of the lists. From the looks of th=
is
> > url:
>
> >http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-par...
>
> > this seems to be a bug with Sharepoint Designer, but what I'm unsure of =
is
> > how this is still a problem after migration. Only thing I can suggest (I=
'm
> > yet to test this theory out) is that it's possible from reading that the=

> > GUIDs aren't aligned because of the missing braces? I'm going to do some=

> > more investigation into this, but wondering if anyone had ideas. Note th=
e
> > example below is *after* the GUIDs have been changed and enclosed with {=
}.
> > The fix stated on this blog post definately works in this case however.
>
> > <WebPartPages:WebPartZone runat=3D"server" AllowPersonalization=3D"false=
"
> > FrameType=3D"TitleBarOnly" ID=3D"TopZone"
> > Title=3D"<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation=3D"Verti=
cal"
> > QuickAdd-GroupNames=3D"Default"
> > QuickAdd-ShowListsAndLibraries=3D"false"><ZoneTemplate>
> > <WebPartPages:DataFormWebPart runat=3D"server"
> > SuppressWebPartChrome=3D"False" Description=3D"" PartImageSmall=3D""
> > DataSourceID=3D"" MissingAssembly=3D"Cannot import this Web Part."
> > FrameType=3D"Default" ConnectionID=3D"00000000-0000-0000-0000-0000000000=
00"
> > DetailLink=3D"/subdir/Lists/Archive/AllItems.aspx"
> > ExportControlledProperties=3D"True" IsVisible=3D"True" AllowRemove=3D"Tr=
ue"
> > AllowEdit=3D"True" ID=3D"g_4008a0e8_872c_4b1c_976e_b17e55de1c40" Dir=3D"=
Default"
> > FrameState=3D"Normal" ViewContentTypeId=3D"" AllowConnect=3D"True" PageS=
ize=3D"-1"
> > AllowMinimize=3D"True" IsIncludedFilter=3D""
> > TitleUrl=3D"/subdir/Lists/Archive/AllItems.aspx" ShowWithSampleData=3D"F=
alse"
> > HelpMode=3D"Modeless" ExportMode=3D"All" ViewFlag=3D"0" Title=3D"Recent =
Items"
> > HelpLink=3D"" AllowHide=3D"True" AllowZoneChange=3D"True" PartOrder=3D"1=
"
> > UseSQLDataSourcePaging=3D"True" PartImageLarge=3D"" IsIncluded=3D"True"
> > NoDefaultStyle=3D"TRUE" __MarkupType=3D"vsattributemarkup"
> > __WebPartId=3D"{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
> > __AllowXSLTEditing=3D"true" WebPart=3D"true" Height=3D"" Width=3D""><Dat=
aSources>
> > <SharePoint:SPDataSource runat=3D"server" DataSourceMode=3D"List"
> > SelectCommand=3D"&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
> > Name=3D&quot;Category&quot;
> > Ascending=3D&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/View=
&gt;"
> > UseInternalName=3D"True"
> > ID=3D"Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormPara=
meter
> > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormP=
arame=AD=ADter
> > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"/subdir/"
> > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > </SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
> > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormP=
arame=AD=ADter
> > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"/subdir/"
> > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > </UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
> > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormP=
arame=AD=ADter
> > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"/subdir/"
> > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > </InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
> > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormP=
arame=AD=ADter
> > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > DefaultValue=3D"/subdir/"
> > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > </DeleteParameters>
> > </SharePoint:SPDataSource>
> > </DataSources>
>
> > 2. After migration, hidden state of navigation items is not persisted.
> > This
> > specific site has two levels of nav, so this is a bit of a pain. To fix
> > this, got to go into
>
> > Site Actions -> Site Settings -> Modify Navigation
>
> > for each nav area and hide the nav items as appropriate. Is there a bett=
er
> > way to go about migrating navigation items, so that their state (hidden =
or
> > not) is preserved? Am I missing something on export that would correct
> > this
> > issue?
>
> > Thanks in advance, and hope I've explained everything legibly.
>
> > Cheers,
> > Gavin Jones
> > Developer
> > Enlighten Designs- Hide quoted text -
>
> - Show quoted text -

Yes, the central admin interface is what I mean. You will need to
enable the target farm to receive incoming deployment jobs. Check
under the necessary sections in central admin (deployment settings).
Their is additional load on the box when this runs at it essentially
receives cab files and must unpack them. Make sure there is sufficient
disk space to do this. I do not know about the navigation elements but
if your doing it on a site by site basis I don't see why that would
not be swept up.

The stsadm command I specified moves entire site collections. Keep
this in mind because you may be wanting to move a sub sites
information whilst leaving another sub site or top level site
untouched. If in doubt, take a backup of the target site first.

Re: MOSS stsadm migration niggles by Gavin

Gavin
Sat Jun 14 00:31:16 CDT 2008

Hey KZ

I went with the Central Admin idea, works very well locally and on test
environs and doesn't have the other issues.
Have this working successfully between a test server and a VM with no issues
at all.

However because the deployment path is through a VPN, I've had some trouble
getting the deployment to work. Essentially, worked many of the gotchyas
you've mentioned in this email myself, ended up with the following issue:

Publishing: Content deployment job failed. Error:
'System.NotSupportedException: The stream does not support concurrent IO
read or write operations.
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer,
Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at
Microsoft.SharePoint.Publishing.Internal.Administration.HttpDataTransfer.UploadFile(String
sourceFilePath, String postToUrl, String& responseXml)
at
Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.UploadFilesToRemoteServer(Guid
remoteJobId, String adminPortUrl)
at
Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServerToServer()
at
Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob()
at
Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean
runAsynchronously)
at
Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid
targetInstanceId)'

From what I've read this is an issue trying to push the CABs over to the
destination machine, and people have mentioned lowering the "FileMaxSize"
property to 2MB:

http://blogs.msdn.com/maximeb/archive/2008/02/19/debugging-content-deployment-issues.aspx

however this particular config option isn't available anywhere in the UI
(nor under the Content Deployment lists). I'm assuming to get this to work
it's expected that a custom deployment job would be created (eg coded up)?
Is there any way I can copy these CABs manually and kick off the import at
the other end? Or is this likely to be more trouble than it's worth?

Cheers,
Gavin

----- Original Message -----
From: "KZ" <kezoe@screaming.net>
Newsgroups: microsoft.public.sharepoint.portalserver
Sent: Saturday, June 14, 2008 12:48 AM
Subject: Re: MOSS stsadm migration niggles


On 11 Jun, 22:14, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Hey KZ, thanks for your time.
>
> I'm still relatively new to this, so I'll do my best to explain.
>
> By deployment schedules, are you meaning the content deployment interface
> within the Central Administration section? If so, the two servers are
> detached/isolated and hence I was looking into deployment in a detatched
> fashion. Does this method include deployment of lists and navigation
> components/settings? I'm gathering that detatched migrations are not
> common
> or not recommended in this case?
>
> As far as stsadm and backup vs export goes, I can give this a try.
> Everything I've looked into discusses the use of "export" and "import" as
> being the recommended approach for migration, so that's what I was using.
>
> Cheers,
> Gavin
>
>
>
> ----- Original Message -----
> From: "KZ" <ke...@screaming.net>
>
> Newsgroups: microsoft.public.sharepoint.portalserver
> Sent: Thursday, June 12, 2008 8:16 AM
> Subject: Re: MOSS stsadm migration niggles
>
> Thinking of the basics first, could you not use the deployment
> schedules for this? Or, stsadm the site collection across (stsadm -o
> backup -url <sourceurl> -filename <filename>) and then (stsadm -o
> restore -url <targeturl> -filename <filename>)?
>
> On 11 Jun, 07:28, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> > Greetings all,
>
> > Go easy on me, it's my first post.
>
> > So a little background. Looking at doing a migration of content and such
> > from one MOSS install to another as part of an initial release. Both
> > servers are running MOSS 2007, service packed and good to go.
>
> > For this migration, I'm using:
>
> > stsadm -o export -urlhttp://moss-filename
> > c:\temp\bulkexport.cab -overwrite -versions
> > 4 -includeusersecurity -cabsize
> > 300
>
> > and the corresponding import after setup at the other end. For this I
> > get
> > no
> > errors and just one warning related to a Web Part issue I'm currently
> > investigating (likely not related to the below issue, as it's a single
> > Web
> > Part).
> > I've succeeded in testing the migration with only a few small issues.
>
> > 1. We're getting an error on some pages similar to the following:
>
> > Unable to display this Web Part. To troubleshoot the problem, open this
> > Web
> > page in a Windows SharePoint Services-compatible HTML editor such as
> > Microsoft Office SharePoint Designer. If the problem persists, contact
> > your
> > Web server administrator.
>
> > This is because some of the data lists are using XSLT transforms,
> > therefore
> > are using webparts. The code for these is similar to the following (it's
> > a
> > little way down, apologies in advance, not easy to read). The problem
> > is,
> > that when these pages are migrated, the GUIDs have to be manually
> > "realigned" in Sharepoint Designer on the destination MOSS server as
> > they
> > don't match up correctly to the GUIDs of the lists. From the looks of
> > this
> > url:
>
> >http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-par...
>
> > this seems to be a bug with Sharepoint Designer, but what I'm unsure of
> > is
> > how this is still a problem after migration. Only thing I can suggest
> > (I'm
> > yet to test this theory out) is that it's possible from reading that the
> > GUIDs aren't aligned because of the missing braces? I'm going to do some
> > more investigation into this, but wondering if anyone had ideas. Note
> > the
> > example below is *after* the GUIDs have been changed and enclosed with
> > {}.
> > The fix stated on this blog post definately works in this case however.
>
> > <WebPartPages:WebPartZone runat="server" AllowPersonalization="false"
> > FrameType="TitleBarOnly" ID="TopZone"
> > Title="<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation="Vertical"
> > QuickAdd-GroupNames="Default"
> > QuickAdd-ShowListsAndLibraries="false"><ZoneTemplate>
> > <WebPartPages:DataFormWebPart runat="server"
> > SuppressWebPartChrome="False" Description="" PartImageSmall=""
> > DataSourceID="" MissingAssembly="Cannot import this Web Part."
> > FrameType="Default" ConnectionID="00000000-0000-0000-0000-000000000000"
> > DetailLink="/subdir/Lists/Archive/AllItems.aspx"
> > ExportControlledProperties="True" IsVisible="True" AllowRemove="True"
> > AllowEdit="True" ID="g_4008a0e8_872c_4b1c_976e_b17e55de1c40"
> > Dir="Default"
> > FrameState="Normal" ViewContentTypeId="" AllowConnect="True"
> > PageSize="-1"
> > AllowMinimize="True" IsIncludedFilter=""
> > TitleUrl="/subdir/Lists/Archive/AllItems.aspx"
> > ShowWithSampleData="False"
> > HelpMode="Modeless" ExportMode="All" ViewFlag="0" Title="Recent Items"
> > HelpLink="" AllowHide="True" AllowZoneChange="True" PartOrder="1"
> > UseSQLDataSourcePaging="True" PartImageLarge="" IsIncluded="True"
> > NoDefaultStyle="TRUE" __MarkupType="vsattributemarkup"
> > __WebPartId="{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
> > __AllowXSLTEditing="true" WebPart="true" Height=""
> > Width=""><DataSources>
> > <SharePoint:SPDataSource runat="server" DataSourceMode="List"
> > SelectCommand="&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
> > Name=&quot;Category&quot;
> > Ascending=&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/View&gt;"
> > UseInternalName="True"
> > ID="Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormParameter
> > ParameterKey="ListID" PropertyName="ParameterValues"
> > DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­­ter
> > ParameterKey="WebURL" PropertyName="ParameterValues"
> > DefaultValue="/subdir/"
> > Name="WebURL"></WebPartPages:DataFormParameter>
> > </SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
> > ParameterKey="ListID" PropertyName="ParameterValues"
> > DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­­ter
> > ParameterKey="WebURL" PropertyName="ParameterValues"
> > DefaultValue="/subdir/"
> > Name="WebURL"></WebPartPages:DataFormParameter>
> > </UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
> > ParameterKey="ListID" PropertyName="ParameterValues"
> > DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­­ter
> > ParameterKey="WebURL" PropertyName="ParameterValues"
> > DefaultValue="/subdir/"
> > Name="WebURL"></WebPartPages:DataFormParameter>
> > </InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
> > ParameterKey="ListID" PropertyName="ParameterValues"
> > DefaultValue="{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > Name="ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFormParame­­ter
> > ParameterKey="WebURL" PropertyName="ParameterValues"
> > DefaultValue="/subdir/"
> > Name="WebURL"></WebPartPages:DataFormParameter>
> > </DeleteParameters>
> > </SharePoint:SPDataSource>
> > </DataSources>
>
> > 2. After migration, hidden state of navigation items is not persisted.
> > This
> > specific site has two levels of nav, so this is a bit of a pain. To fix
> > this, got to go into
>
> > Site Actions -> Site Settings -> Modify Navigation
>
> > for each nav area and hide the nav items as appropriate. Is there a
> > better
> > way to go about migrating navigation items, so that their state (hidden
> > or
> > not) is preserved? Am I missing something on export that would correct
> > this
> > issue?
>
> > Thanks in advance, and hope I've explained everything legibly.
>
> > Cheers,
> > Gavin Jones
> > Developer
> > Enlighten Designs- Hide quoted text -
>
> - Show quoted text -

Yes, the central admin interface is what I mean. You will need to
enable the target farm to receive incoming deployment jobs. Check
under the necessary sections in central admin (deployment settings).
Their is additional load on the box when this runs at it essentially
receives cab files and must unpack them. Make sure there is sufficient
disk space to do this. I do not know about the navigation elements but
if your doing it on a site by site basis I don't see why that would
not be swept up.

The stsadm command I specified moves entire site collections. Keep
this in mind because you may be wanting to move a sub sites
information whilst leaving another sub site or top level site
untouched. If in doubt, take a backup of the target site first.



Re: MOSS stsadm migration niggles by KZ

KZ
Tue Jun 17 11:37:36 CDT 2008

On 14 Jun, 06:31, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Hey KZ
>
> I went with the Central Admin idea, works very well locally and on test
> environs and doesn't have the other issues.
> Have this working successfully between a test server and a VM with no issu=
es
> at all.
>
> However because the deployment path is through a VPN, I've had some troubl=
e
> getting the deployment to work. =A0Essentially, worked many of the gotchya=
s
> you've mentioned in this email myself, ended up with the following issue:
>
> Publishing: Content deployment job failed. Error:
> 'System.NotSupportedException: The stream does not support concurrent IO
> read or write operations.
> =A0 =A0at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buf=
fer,
> Int32 offset, Int32 size, AsyncCallback callback, Object state)
> =A0 =A0at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int3=
2
> size)
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Internal.Administration.HttpDataTransfer.U=
p=ADloadFile(String
> sourceFilePath, String postToUrl, String& responseXml)
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Upload=
F=ADilesToRemoteServer(Guid
> remoteJobId, String adminPortUrl)
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServ=
e=ADrToServer()
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Execut=
e=ADJob()
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Bo=
o=ADlean
> runAsynchronously)
> =A0 =A0at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinit=
i=ADon.Execute(Guid
> targetInstanceId)'
>
> From what I've read this is an issue trying to push the CABs over to the
> destination machine, and people have mentioned lowering the "FileMaxSize"
> property to 2MB:
>
> http://blogs.msdn.com/maximeb/archive/2008/02/19/debugging-content-de...
>
> however this particular config option isn't available anywhere in the UI
> (nor under the Content Deployment lists). =A0I'm assuming to get this to w=
ork
> it's expected that a custom deployment job would be created (eg coded up)?=

> Is there any way I can copy these CABs manually and kick off the import at=

> the other end? Or is this likely to be more trouble than it's worth?
>
> Cheers,
> Gavin
>
>
>
> ----- Original Message -----
> From: "KZ" <ke...@screaming.net>
>
> Newsgroups: microsoft.public.sharepoint.portalserver
> Sent: Saturday, June 14, 2008 12:48 AM
> Subject: Re: MOSS stsadm migration niggles
>
> On 11 Jun, 22:14, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> > Hey KZ, thanks for your time.
>
> > I'm still relatively new to this, so I'll do my best to explain.
>
> > By deployment schedules, are you meaning the content deployment interfac=
e
> > within the Central Administration section? If so, the two servers are
> > detached/isolated and hence I was looking into deployment in a detatched=

> > fashion. Does this method include deployment of lists and navigation
> > components/settings? I'm gathering that detatched migrations are not
> > common
> > or not recommended in this case?
>
> > As far as stsadm and backup vs export goes, I can give this a try.
> > Everything I've looked into discusses the use of "export" and "import" a=
s
> > being the recommended approach for migration, so that's what I was using=
.
>
> > Cheers,
> > Gavin
>
> > ----- Original Message -----
> > From: "KZ" <ke...@screaming.net>
>
> > Newsgroups: microsoft.public.sharepoint.portalserver
> > Sent: Thursday, June 12, 2008 8:16 AM
> > Subject: Re: MOSS stsadm migration niggles
>
> > Thinking of the basics first, could you not use the deployment
> > schedules for this? Or, stsadm the site collection across (stsadm -o
> > backup -url <sourceurl> -filename <filename>) and then (stsadm -o
> > restore -url <targeturl> -filename <filename>)?
>
> > On 11 Jun, 07:28, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> > > Greetings all,
>
> > > Go easy on me, it's my first post.
>
> > > So a little background. Looking at doing a migration of content and su=
ch
> > > from one MOSS install to another as part of an initial release. Both
> > > servers are running MOSS 2007, service packed and good to go.
>
> > > For this migration, I'm using:
>
> > > stsadm -o export -urlhttp://moss-filename
> > > c:\temp\bulkexport.cab -overwrite -versions
> > > 4 -includeusersecurity -cabsize
> > > 300
>
> > > and the corresponding import after setup at the other end. For this I
> > > get
> > > no
> > > errors and just one warning related to a Web Part issue I'm currently
> > > investigating (likely not related to the below issue, as it's a single=

> > > Web
> > > Part).
> > > I've succeeded in testing the migration with only a few small issues.
>
> > > 1. We're getting an error on some pages similar to the following:
>
> > > Unable to display this Web Part. To troubleshoot the problem, open thi=
s
> > > Web
> > > page in a Windows SharePoint Services-compatible HTML editor such as
> > > Microsoft Office SharePoint Designer. If the problem persists, contact=

> > > your
> > > Web server administrator.
>
> > > This is because some of the data lists are using XSLT transforms,
> > > therefore
> > > are using webparts. The code for these is similar to the following (it=
's
> > > a
> > > little way down, apologies in advance, not easy to read). The problem
> > > is,
> > > that when these pages are migrated, the GUIDs have to be manually
> > > "realigned" in Sharepoint Designer on the destination MOSS server as
> > > they
> > > don't match up correctly to the GUIDs of the lists. From the looks of
> > > this
> > > url:
>
> > >http://webborg.blogspot.com/2007/08/resolving-to-display-this-web-par..=
.
>
> > > this seems to be a bug with Sharepoint Designer, but what I'm unsure o=
f
> > > is
> > > how this is still a problem after migration. Only thing I can suggest
> > > (I'm
> > > yet to test this theory out) is that it's possible from reading that t=
he
> > > GUIDs aren't aligned because of the missing braces? I'm going to do so=
me
> > > more investigation into this, but wondering if anyone had ideas. Note
> > > the
> > > example below is *after* the GUIDs have been changed and enclosed with=

> > > {}.
> > > The fix stated on this blog post definately works in this case however=
.
>
> > > <WebPartPages:WebPartZone runat=3D"server" AllowPersonalization=3D"fal=
se"
> > > FrameType=3D"TitleBarOnly" ID=3D"TopZone"
> > > Title=3D"<%$Resources:sps,LayoutPageZone_TopZone%>" Orientation=3D"Ver=
tical"
> > > QuickAdd-GroupNames=3D"Default"
> > > QuickAdd-ShowListsAndLibraries=3D"false"><ZoneTemplate>
> > > <WebPartPages:DataFormWebPart runat=3D"server"
> > > SuppressWebPartChrome=3D"False" Description=3D"" PartImageSmall=3D""
> > > DataSourceID=3D"" MissingAssembly=3D"Cannot import this Web Part."
> > > FrameType=3D"Default" ConnectionID=3D"00000000-0000-0000-0000-00000000=
0000"
> > > DetailLink=3D"/subdir/Lists/Archive/AllItems.aspx"
> > > ExportControlledProperties=3D"True" IsVisible=3D"True" AllowRemove=3D"=
True"
> > > AllowEdit=3D"True" ID=3D"g_4008a0e8_872c_4b1c_976e_b17e55de1c40"
> > > Dir=3D"Default"
> > > FrameState=3D"Normal" ViewContentTypeId=3D"" AllowConnect=3D"True"
> > > PageSize=3D"-1"
> > > AllowMinimize=3D"True" IsIncludedFilter=3D""
> > > TitleUrl=3D"/subdir/Lists/Archive/AllItems.aspx"
> > > ShowWithSampleData=3D"False"
> > > HelpMode=3D"Modeless" ExportMode=3D"All" ViewFlag=3D"0" Title=3D"Recen=
t Items"
> > > HelpLink=3D"" AllowHide=3D"True" AllowZoneChange=3D"True" PartOrder=3D=
"1"
> > > UseSQLDataSourcePaging=3D"True" PartImageLarge=3D"" IsIncluded=3D"True=
"
> > > NoDefaultStyle=3D"TRUE" __MarkupType=3D"vsattributemarkup"
> > > __WebPartId=3D"{4008A0E8-872C-4B1C-976E-B17E55DE1C40}"
> > > __AllowXSLTEditing=3D"true" WebPart=3D"true" Height=3D""
> > > Width=3D""><DataSources>
> > > <SharePoint:SPDataSource runat=3D"server" DataSourceMode=3D"List"
> > > SelectCommand=3D"&lt;View&gt;&lt;Query&gt;&lt;OrderBy&gt;&lt;FieldRef
> > > Name=3D&quot;Category&quot;
> > > Ascending=3D&quot;TRUE&quot;/&gt;&lt;/OrderBy&gt;&lt;/Query&gt;&lt;/Vi=
ew&gt;"
> > > UseInternalName=3D"True"
> > > ID=3D"Panui_x0020_Archive3"><SelectParameters><WebPartPages:DataFormPa=
rameter
> > > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFor=
mParame=AD=AD=ADter
> > > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"/subdir/"
> > > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > > </SelectParameters><UpdateParameters><WebPartPages:DataFormParameter
> > > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFor=
mParame=AD=AD=ADter
> > > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"/subdir/"
> > > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > > </UpdateParameters><InsertParameters><WebPartPages:DataFormParameter
> > > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFor=
mParame=AD=AD=ADter
> > > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"/subdir/"
> > > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > > </InsertParameters><DeleteParameters><WebPartPages:DataFormParameter
> > > ParameterKey=3D"ListID" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"{3384D330-C313-47EE-B61D-F2E6609A677B}"
> > > Name=3D"ListID"></WebPartPages:DataFormParameter><WebPartPages:DataFor=
mParame=AD=AD=ADter
> > > ParameterKey=3D"WebURL" PropertyName=3D"ParameterValues"
> > > DefaultValue=3D"/subdir/"
> > > Name=3D"WebURL"></WebPartPages:DataFormParameter>
> > > </DeleteParameters>
> > > </SharePoint:SPDataSource>
> > > </DataSources>
>
> > > 2. After migration, hidden state of navigation items is not persisted.=

> > > This
> > > specific site has two levels of nav, so this is a bit of a pain. To fi=
x
> > > this, got to go into
>
> > > Site Actions -> Site Settings -> Modify Navigation
>
> > > for each nav area and hide the nav items as appropriate. Is there a
> > > better
> > > way to go about migrating navigation items, so that their state (hidde=
n
> > > or
> > > not) is preserved? Am I missing something on export that would correct=

> > > this
> > > issue?
>
> > > Thanks in advance, and hope I've explained everything legibly.
>
> > > Cheers,
> > > Gavin Jones
>
> ...
>
> read more =BB- Hide quoted text -
>
> - Show quoted text -

More trouble than its worth I'd go for. To be honest your outside my
expertise with this now. You need advice from a MOSS developer for the
setting mentioned I suspect. I don't suppose you could create multiple
jobs to lower the mb size?

Re: MOSS stsadm migration niggles by Gavin

Gavin
Mon Jun 23 21:04:05 CDT 2008


"KZ" <kezoe@screaming.net> wrote in message
news:e3c945a4-0cdd-4923-8ca7-64dc2511affe@j22g2000hsf.googlegroups.com...
On 14 Jun, 06:31, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> Hey KZ
>
> I went with the Central Admin idea, works very well locally and on test
> environs and doesn't have the other issues.
> Have this working successfully between a test server and a VM with no
> issues
> at all.
>
> However because the deployment path is through a VPN, I've had some
> trouble
> getting the deployment to work. Essentially, worked many of the gotchyas
> you've mentioned in this email myself, ended up with the following issue:
>
> Publishing: Content deployment job failed. Error:
> 'System.NotSupportedException: The stream does not support concurrent IO
> read or write operations.
> at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer,
> Int32 offset, Int32 size, AsyncCallback callback, Object state)
> at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32
> size)
> at
> Microsoft.SharePoint.Publishing.Internal.Administration.HttpDataTransfer.Up­loadFile(String
> sourceFilePath, String postToUrl, String& responseXml)
> at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.UploadF­ilesToRemoteServer(Guid
> remoteJobId, String adminPortUrl)
> at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServe­rToServer()
> at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Execute­Job()
> at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boo­lean
> runAsynchronously)
> at
> Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefiniti­on.Execute(Guid
> targetInstanceId)'
>
> From what I've read this is an issue trying to push the CABs over to the
> destination machine, and people have mentioned lowering the "FileMaxSize"
> property to 2MB:
>
> http://blogs.msdn.com/maximeb/archive/2008/02/19/debugging-content-de...
>
> however this particular config option isn't available anywhere in the UI
> (nor under the Content Deployment lists). I'm assuming to get this to work
> it's expected that a custom deployment job would be created (eg coded up)?
> Is there any way I can copy these CABs manually and kick off the import at
> the other end? Or is this likely to be more trouble than it's worth?
>
> Cheers,
> Gavin

>> More trouble than its worth I'd go for. To be honest your outside my
>> expertise with this now. You need advice from a MOSS developer for the
>> setting mentioned I suspect. I don't suppose you could create multiple
>> jobs to lower the mb size?

Turns out it's a piece of cake. Made up a simple little program in VS.NET,
Imported reference to the Sharepoint.Publishing DLL, and added code similar
to the following

ContentDeploymentConfiguration config =
ContentDeploymentConfiguration.GetInstance();

if (CustomConfig.Default.FileMaxSize > 0)
{
config.FileMaxSize = CustomConfig.Default.FileMaxSize;
Console.WriteLine("config.FileMaxSize: " +
CustomConfig.Default.FileMaxSize);
}

Doesn't reduce it to the exact amount requested (often 2-10MB, a few files
were 19-20MB) but it made the deployment proceed successfully.
Obviously need to run as the Farm Admin to get this to work.

Hope this might help someone.

Cheers,
Gavin



Re: MOSS stsadm migration niggles by rbonecrusher

rbonecrusher
Tue Jun 24 15:23:01 CDT 2008



"Gavin Jones" wrote:

>
> "KZ" <kezoe@screaming.net> wrote in message
> news:e3c945a4-0cdd-4923-8ca7-64dc2511affe@j22g2000hsf.googlegroups.com...
> On 14 Jun, 06:31, "Gavin Jones" <enligh...@newsgroups.nospam> wrote:
> > Hey KZ
> >
> > I went with the Central Admin idea, works very well locally and on test
> > environs and doesn't have the other issues.
> > Have this working successfully between a test server and a VM with no
> > issues
> > at all.
> >
> > However because the deployment path is through a VPN, I've had some
> > trouble
> > getting the deployment to work. Essentially, worked many of the gotchyas
> > you've mentioned in this email myself, ended up with the following issue:
> >
> > Publishing: Content deployment job failed. Error:
> > 'System.NotSupportedException: The stream does not support concurrent IO
> > read or write operations.
> > at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer,
> > Int32 offset, Int32 size, AsyncCallback callback, Object state)
> > at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32
> > size)
> > at
> > Microsoft.SharePoint.Publishing.Internal.Administration.HttpDataTransfer.Up­loadFile(String
> > sourceFilePath, String postToUrl, String& responseXml)
> > at
> > Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.UploadF­ilesToRemoteServer(Guid
> > remoteJobId, String adminPortUrl)
> > at
> > Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoServe­rToServer()
> > at
> > Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Execute­Job()
> > at
> > Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boo­lean
> > runAsynchronously)
> > at
> > Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefiniti­on.Execute(Guid
> > targetInstanceId)'
> >
> > From what I've read this is an issue trying to push the CABs over to the
> > destination machine, and people have mentioned lowering the "FileMaxSize"
> > property to 2MB:
> >
> > http://blogs.msdn.com/maximeb/archive/2008/02/19/debugging-content-de...
> >
> > however this particular config option isn't available anywhere in the UI
> > (nor under the Content Deployment lists). I'm assuming to get this to work
> > it's expected that a custom deployment job would be created (eg coded up)?
> > Is there any way I can copy these CABs manually and kick off the import at
> > the other end? Or is this likely to be more trouble than it's worth?
> >
> > Cheers,
> > Gavin
>
> >> More trouble than its worth I'd go for. To be honest your outside my
> >> expertise with this now. You need advice from a MOSS developer for the
> >> setting mentioned I suspect. I don't suppose you could create multiple
> >> jobs to lower the mb size?
>
> Turns out it's a piece of cake. Made up a simple little program in VS.NET,
> Imported reference to the Sharepoint.Publishing DLL, and added code similar
> to the following
>
> ContentDeploymentConfiguration config =
> ContentDeploymentConfiguration.GetInstance();
>
> if (CustomConfig.Default.FileMaxSize > 0)
> {
> config.FileMaxSize = CustomConfig.Default.FileMaxSize;
> Console.WriteLine("config.FileMaxSize: " +
> CustomConfig.Default.FileMaxSize);
> }
>
> Doesn't reduce it to the exact amount requested (often 2-10MB, a few files
> were 19-20MB) but it made the deployment proceed successfully.
> Obviously need to run as the Farm Admin to get this to work.
>
> Hope this might help someone.
>
> Cheers,
> Gavin
>
>
>

Did you ever find a resolution to your second issue: Hidden navigation items
not being persisted with a content deployment? I'm having the same issue and
I'm beating my head against the wall over it. It's not just the "hidden"
setting, either, it's all navigation settings.