SHAREPOINTBlogs.com Mirror

The secret lists of SharePoint

Here are some lists that are hidden in SharePoint but can be useful for different scenarios: Content Deployment Content Deployment Jobs: http://CA/Lists/Content%20Deployment%20Jobs/AllItems.aspx Job Reports: http://CA/Lists/Job%20Reports/AllItems.aspx Quick Deploy Items: http://site/Quick%20Deploy%20Items/AllItems.aspx Variations Relationships List http://site/Relationships%20List/AllItems.aspx Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

MOSS 2007 Content Deployment - Problem

I have trouble with a staging environment that I recently set up. I went through the error logs and finally got the staging environment functioning without errors, but previous to working through those errors, we successfully made a content deployment path and job and ran it. Now, the Destination central Admin is giving permissions issues. I changed and restarted some services and some component services.. Are there any specific things I should check related specifically to content deployment as far as services on the server? Either the URL for the destination Web application is not valid, or you do not have permissions to the Central Administration site on the destination server farm. Error details: The remote Web service request failed with this message : 'Exception has been thrown by the target of an invocation.'. You have specified a URL that begins with http://. Communication to this URL will not be secure and can be intercepted by malicious users. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Musings on MOSS 2007 Content Deployment

So a few days ago I started playing with and testing the MOSS content deployment feature. From my previous readings, it seemed easy enough. My approach was to go at it from scratch so that I could understand what works and what doesn't. I got quite Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

MOSS 2007 Content Deployment Topologies

As you all may know, content deployment is a powerful feature in MOSS 2007 (this concept has been brought over from CMS 2002). With almost any site, you need authors to actually create and edit the content that the target users will see. If the site is Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Using the SharePoint Content Deployment Wizard

So if you've read the earlier posts about the tool ( Introducing the SharePoint Content Deployment Wizard and When to use the SharePoint Content Deployment Wizard ) and figure this is a useful tool, let's go onto the next level of detail. Generally Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

When to use the SharePoint Content Deployment Wizard

Following my introduction to the tool last time, today I want to try to help position the tool for people who aren't sure if it could be useful to them or for what scenarios - if you only take one thing away from my postings on the Content Deployment Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Introducing the SharePoint Content Deployment Wizard

Regular readers might have spotted I've been slightly quieter than usual over the past few weeks - actually I've not been slacking, but working on a tool which you might find useful from time to time. As I've discussed in numerous posts, deployment Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Violation of PRIMARY KEY constraint 'PK__#ExportObjects____XXXXXXXX'

Not a nice title, not a nice error as well... I encountered this error while trying export/import a file through the object model. Searching the net I found some posts suggesting this could be caused by the versioning in the Style Library. As soon as you've checked-in multiple major versions of a file the error 'could' occur. But that had to do with Incremental deployments. MS has a hotfix for that case: http://support.microsoft.com/kb/936867 . But I was not doing any Incremental deployments, I just wanted to export one single file from a site. Also, I did not have the time to request, wait and install the Hotfix so I tried something else: Delete all content from the Style Library , and it worked. Just a cut-and-paste everything to your local machine, refresh the browser (just in case) and put everything back in place. Of course you will lose any version data, but thats a fair trade-off. The issue is also related to the Site Image gallery and other site-level-galleries, so you might want to try resetting them as well. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

STSADM export, Content Deployment, Content Migration API, Features/Solutions - deployment options compared

Back in May I wrote a post titled SharePoint deployment options : Features or Content Deployment? , which discussed some thoughts on what was the "right" way to move assets from development to production (and perhaps environments in between Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Deployment using STSADM export or content migration API

Having focused on deployment using Features for several articles, back in May I wrote an article titled SharePoint deployment options : Features or Content Deployment? , which explored some of the decisions around deployment strategies for SharePoint Read More......( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks