MOSS 2007 RTM bug : Content Deployment : Strange Characters : Revisited

Another content deployment post revisited. This problem, as i mentioned in my previous post, was confirmed as a bug with MOSS 2007 RTM and due to be fixed in SP1.

Peter Hoplar, however, continued his hunt for the encoding problem and has written a 2 part post in great detail;

'Hunting the encoding problem in content deployment' - Part1 and Part2

Content Deployment Problem : Violation of PRIMARY KEY constraint : Revisited

In a previous article i blogged on how to get around a 'Violation of PRIMARY KEY constraint' error that i had cropping up in a Content Deployment Routine. This unfortunately doesn't mean that you won't see the error again! I've had this error return so some further research lead me to comments posted on Ton Stegman's content deployment blog by Ryan Steeno.

To summarise Ryans comments, after some extensive tracing (understatement) he ascertained that having the versioning settings of any of the Site Collection Libraries (Images/Documents/Style) set to Allow Multiple Only seemed to resolve the issue.

Note : There are also reports of this error using the stsadm utility import/export operations which Peter Holpar has managed to resolve.

MOSS 2007 RTM bug : Content Deployment : Strange Characters

I've been experiencing some problems with strange characters appearing in deployed content pages on a WCM site.

So far i've found that if my RichHTML field contains a ' ' (in the HTML code view) once it has been deployed to my target server it gets rendered as an Â.

I've also noticed that the apostrophe and quote marks pasted in from word result in ’ and “ (begin quote) / ” (end quote) once the content deployment job has run.

Microsoft have confirmed that this is a bug with MOSS2007 RTM and have promised a fix in SP1.

In the meantime, this can be worked around by a bit of fiddling in the source content. Open up the page in edit mode and using the RichHTML editor replace word pasted apostrophes and speech marks.

technorati tags:MOSS, 2007, Bug, Content, Deployment, Strange, Characters, Â, ’, “

Blogged with Flock

SPS 2003 Upgrade to MOSS 2007 : /_layouts/mngsubwebs.aspx

I've come across a permission problem which has tripped me up after what i thought was a successful upgrade from an SPS2003 site to MOSS 2007.

In my old SPS2003 site every site (approx 50) uses a 'Links' web part at the top of the landing page that contains a link to '/_layouts/1033/mngsubwebs.aspx'. If i browse my old SPS2003 site with just read access then no problem. However, i try the same links on the upgraded MOSS 2007 site using a read only account and im confronted with 'Access Denied' messages.

The workaround i came up with was to change the link to :

'/_layouts/viewlsts.aspx?ShowSites=1'

The shows a similar view.

technorati tags:MOSS, 2007, Upgrade, mngsubwebs.aspx, access denied

Blogged with Flock