My MOSS WCM STSADM custom commands have been updated

Just finished updating my custom commands for MOSS WCM Publishing site developers. This update is long overdue... I know... my bad. Most importantly, the PublishAllItems command had bad memory issues. Those have since been resolved. I also had a bunch of other changes I had implemented on PublishAllItem (such as canceling running workflows and fixing the issue where not everything was published), but decided to change some stuff up after seeing how Gary Lapointe wrote his PublishItems command.

As for the other commands GenSiteColumnsXml & GenContentTypesXml, they've been significantly revamped. For both, I'm now using the Field.SchemaXml property instead of manually building the XML. Also, the GenContentTypesXml command now includes the <DocumentTemplate> and <XmlDocuments> sections.

Feel free to see all the updates listed in the change log and go download the latest release: v0.8.7.1029.

Technorati tags: sharepoint, moss, wcm, publishing site, custom stsadm command

posted on Monday, October 29, 2007 10:34 PM

Feedback

re: My MOSS WCM STSADM custom commands have been updated 10/30/2007 11:24 AM Alex Bookless

Hi Andrew,

thanks for this lovely tool... it's really nice - I only had one slight problem with it - the dll included in the latest version seemed to be version 7.0.0.0 rather than the 8.7.1029 which resulted in an error when trying to run it - I got round this by building the source code and copying the dll into the GAC but just thought you might like to know :)

Thanks again,
Alex

# re: My MOSS WCM STSADM custom commands have been updated 10/30/2007 12:15 PM AC [MVP MOSS]

Alex-
THanks... bonehead move on my part. The download has been fixed. The correct version is 0.8.7.1029.

re: My MOSS WCM STSADM custom commands have been updated 11/1/2007 6:41 PM Aaron Powell

Hey Andrew,

I've just installed the latest version but am getting "Assertion Failed" when trying to run the PublishAllItems with options of "Abort, Retry, Ignore".

When choosing "Abort" it exists (as expected), I didn't try the "Retry" option, but I did try "Ignore", stsadm ran and published all pages.

I'm sure its not meant to throw that error...

# re: My MOSS WCM STSADM custom commands have been updated 11/1/2007 8:12 PM AC [MVP MOSS]

Aaron-
Thanks... another bonehead move on my part. I left a Trace.Assert(false) in there which makes it easier to attached the debugger to STSADM.EXE when testing. I accidentally published the debug build, not the release build. Download it again and upgrade the solution to fix this. It worked before, you just got that annoying assertion dialog.

re: My MOSS WCM STSADM custom commands have been updated 11/21/2007 8:04 PM Aaron Powell

Hey Andrew me again,

I'm working on a new MOSS site so I have just downloaded a copy of the StsAdm extensions and installed and tried running them, but I keep getting "Object references not set to an instance of an object".

this is what I'm running:
C:\[..]\bin>STSADM.EXE -o GenSiteColumnsXml -url http://<site-url> -outputFile C:\Columns.xml

Any thoughts on what could be causing the error? I don't really want to have to write the XML myself, its such a pain!

re: My MOSS WCM STSADM custom commands have been updated 11/22/2007 4:47 PM Aaron Powell

Problem solved, turns out that the error wasn't actually caused by Andrew's extensions, but by the user I was running them as.

My user wasn't a SP Server Admin, just a Windows admin. After adding myself to the SP Server Admin I was able to run the commands successfully.

I got directed down this line of through from here: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1257801&SiteID=17

Post Feedback

Title:
Name:
Email:	(email will not be displayed)
Url:
Comments:
Please add 1 and 7 and type the answer here: Remember Me?

All Comments Are Filtered & Moderated
Unfortunately comment spammers are just too effecient and are constantly dirtying up blogs with irrelevant and unwanted comments trying to improve their standing on search engines. All comments on this blog are moderated. I do not censor comments, but I don't approve comments with vulger language or those soliciting products. Most of the time comments are approved within a few hours of being submitted with the only exception when I'm traveling.

Why are you asking for my email address?
The only reason I'm asking for your email address, which isn't required to submit a comment, is to provide a gravatar if you've created an account for yourself and associated your email address with a small image. If you have a gravatar created for the email address you submit, it will appear next to your comment. Otherwise nothing will appear.

What is a gravatar?
A gravatar is a "globally recognized avatar." You can get more information about gravatars, as well as create your own for free, at www.gravatar.com. You can also view my gravatar here.

This work is licensed under a Creative Commons License
Site design by Heather Solomon.