Hot answers tagged

7

Check the size of your export package. There is a default cab size of about 25Mb - this used to be a limit you had to increase with stsadm by setting a parameter. With the PowerShell Export-SPWeb cmdlet it generates multiple files if you hit the limit. You may need to change this limit using the CompressionSize parameter to set the cab size (up to a maximum ...


5

The hiding / unhiding of menu items is dependant on the settings in the import. Doing an import with RetainObjectIdentity=true keeps the menu items hidden. The relevant code of the CDP APIs are as follows: SPExportSettings exportSettings = new SPExportSettings( new Uri("http://source"), @"c:\temp"); SPExport export = new SPExport(exportSettings); ...


4

A couple of points to consider here: SharePoint isn't designed to have a single package which captures everything. Like most SharePoint 2007 developers, I'd agree with Wictor that WSPBuilder is the way to go for packaging up custom code assets such as assemblies, 12 hive files etc. - these get packaged up into Features and Solutions (.wsp). However this ...


4

If the content is in a content database with no other content, you could backup the content db and move it and then attach it in the new farm. If it is not, you can use the command line stsadm.exe -o backup -url [yoursitecollectionurl] -filename [filename] to back the file up on the current server, then copy the file to the new server and use the command ...


4

Run the stsadm -o enumsolutions command from a command line on the SP server to see where and if this solution was deployed. stsadm -o enumsolutions Thanks. I have had this happen before as well. I ran the following stsadm commands in this order. My goal was to go step by step and remove any aspect of the solution and then slowly place it back into ...


4

The best approach is to use main master page (with only test pages attached) placed in a document library, and track changes to the file made using SPD and if any changes are made - update ghosted master page in file system accordingly, all other master pages are deployed via modules and are ghosted versions of one in files system. After changing file ...


4

I happen to have a great exposure working with the Content Deployment in an authoring and production topology: Authoring and production farm The two-farm topology is a standard Internet site topology, and it is typical of topologies that are used to publish an Internet site. It includes two server farms: one to host the authoring site collection along with ...


3

The best way I've found to do this is to periodically copy the content database itself back down from Production and attach copies of it to each of the environments. This is very simple to do but does have a few potential drawbacks, such as: Any manual changes to the dev/qa environments are wiped out (if you are using features to deploy customizations ...


3

I would think that a 3 stage environment would make a lot of sense if you were developing an internet. The staging environment gives you complete control over the page authoring environment. As you indicated you have a separate set of permissions for the users involved with authoring. In addition, when the pages are approved in the staging environment, ...


3

Yes you can use WSPBuilder to package all your stuff. It's a great tool for that. You should leave the site backup out of though and restore that manually. Regarding your error; make sure that you have installed the same features/templates on the target farm where you restore your site.


3

And how about site template creation approach? This will produce a sandboxed solution (wsp-file), which can be deployed to any other site. Unfortunately, this approach is not always a good solution for localized or deeply customized sites, because it is very static (and maybe some other issues). So, what else can you use: 1. XML modules In SharePoint ...


2

Yes, you're quite right that SharePoint doesn't deal particularly well with this requirement out-of-the-box. If you wish to go beyond separating authoring/reading (typically accomplished with Content Deployment) and use different branding, then the only option is to do a fair amount of custom development. In the end it comes down to using SharePoint mainly ...


2

I found one solution : Microsoft let us modify the XML files used to import data : So what I did : Set the import settings.RetainObjectIdentity to true. Modify the xml files to change the Guids of existing content Right now, there's a lot of hardcoded things, but I think, I will be able to make it more generic. using System; using ...


2

Easiest way would be to open up the xml of the out of box feature which provisions columns in SharePoint site. Got to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\fields. The 3 xml files fieldswss.xml, fieldswss2.xml and fieldswss3.xml contain the definitions of all the OOB columns in SharePoint. You can easily ...


2

I suggest you go back to the business and inform them of the purpose of a staging server. If a production environment has a reliance of staging, then you essentially don't have a staging environment. This might not be entirely helpful as an answer, but do remind the business why you have a staging server, and why it is indeed called 'staging'.


2

Finally, after some brainstorming I found a feasible solution. On Production : Created a custom control to send comment as email to a list at staging. On Staging : Configured the list to receive emails. This will contain comments sent via email. A SPEmailEventReceiver attached to the list process the email (sent from production) and put it to ...


2

Don't be fooled by the "have sufficient free space" message...I think that's just part of a higher level generic error message. I had this same exact error about a month ago and the only way I was able to get around it was going into Central Admin, create a new content database on the web app, and then use the databasename argument on the Restore-SPSite ...


2

Create a job that only runs on demand that will export everything, no matter when it was published previously. Run this manually. It will be good to have it in case this should happen again.


2

I got this to work by creating the destination site collection with the template Custom - Select template later... option, rather than using the template Collaboration - Blank Site. I hope that saves some frustration for someone.


2

I don't know the solution but, have you tried to set feature scope to web, use default module definition and activation of this module on the Suche subsite? <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Module Name="MasterPageModule" Url="_catalogs/masterpage"> <File Url="MasterPage.master" Type="GhostableInLibrary" ...


2

Masterpages and pagelayout can only be deployed to SiteCollections, not sites/subsites. So your feature needs to be Site scoped. You can always in your FeatureReceiver set the masterpage on a specific SPWeb. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Module ...


2

Could you please make sure these things? Are you sure that you're importing to a blank Site Collection template? In other words, destination site collection should be a brand new blank site collection – Don't try to export to a newly created publishing site collection. Having required features not activated will result in CD failure? Also, make sure if ...


2

Luke, First of all never change anything inside a SharePoint Content Database. Concerning the "0" number of site collections it may happen due to permissions and conflict of internal SID for the dbo user for a restored content database. Here is what can you do and it should work just fine provided that your content database is not exceeding 15GB. Take ...


2

The advantages of multiple instances are limited in the scenario you've given. You are correct in what you're implying - that you could simply have one farm, with no content deployment. Editors could see unpublished content, and other users see published. Or, as the document you linked to says, you could have one instances and deploy to a different site ...


2

I would recommend you to deactivate and uninstall the feature using stsadm/PowerShell on destination environment first, the retract and delete the WSP containing the feature. Now, try to add and deploy the WSP containing correct feature version, but DON'T activate/deactivate the feature. In fact let this feature activation/deactivation should be done using ...


2

Refer to the SharePoint Guidance from patterns & practices They have a section on configuration data which would apply, and part of that section includes storing configuration data in a list. The list implementation is much like a hashtable.


1

Don't know if this might help. Seems like IE 8 has some limitations on Base64 encoded images. http://stackoverflow.com/questions/10159500/internet-explorer-and-base64-image-display


1

Sorry if I misunderstood the problem, it's seems like you're talking about the differences between author names of the document right ? My idea may be too easy but it may help to deep further. In SP, the "modified by" name is directly linked to the SP account, but in office document, there's also a native property named "Author", and other properties that ...


1

Solved. Problem was reported to Microsoft Support few days after this thread was created and we finally found the solution - the only thing, that we need to do before CD job is launched is to disable Property Promotion function. Before that, I did not know that such a function exists.


1

Yes, all the Content Deployment jobs can be run at same time (in parallel), but you need to make sure that you don't start another Content Deployment job if previous one is already in "Preparing" mode. I had faced some problems in the past while running different Content Deployment Jobs in parallel especially when Content Deployment jobs are configured with ...



Only top voted, non community-wiki answers of a minimum length are eligible