Learn from my stupid mistakes

I’ve been playing around with scripted installed for SharePoint 2010.  Given the install process is lengthy, tedious and very easy to bugger up, having a script that performs a least-privilege install automatically is pretty attractive.

Over at Codeplex they’ve got AustoSPInstaller, which is on v2 of the 2010 script.   This takes an XML config file with your service account passwords and so on and goes through all the punishment of a manual install in your behalf.

Great!  Except the powershell script kept getting access denied errors.  That’s odd.  I opened up regedit and had a look at the permissions.  OK script is running as me, I’m in the local domain user’s group, admins have full rights.  WTF?

Now, it’s been a while since I’ve done anything with scripts other than fool around with the filesystem, AD or a compliant SharePoint install, and I’ve only worked on this machine once before.  Luckily I’ve banged my head against this particular wall before.

I’m an administrator… but I still need to ‘run as administrator’ the script.

Much better now.

Of course, on the first run the script found the development database server is full and punched out.  Oh well.


MOSS/SharePoint Upload fails with file error 0x80070021

More upload nonsense!  Now we can upload large files, and all is well until a user turns up trying to upload a 173MB video file off a DVD-R.  It keeps failing and I assume it’s the DVD but it copies to my machine OK, but fails to upload to the document library.

OK, I open up the library in explorer view and drag and drop.  That gives a file locking error with the code 0x80070021.  Goggling didn’t do much good as this error apparently pops up most frequently with Outlook *.pst files.
Luckily my colleague is a SharePoint veteran and I asked him if he’d seen this error before.  Within a few minutes he’d concluded that the database was full.  As it turned out, truncating the log file did the trick.
Here’s the script to do that:
BACKUP LOG wss_content_go_snap_undp_org WITH TRUNCATE_ONLY

Fixing SharePoint/MOSS uploads

Sometimes our users want to upload video to document libraries, which is understandable as there’s no fileshare for them to use. The trouble has been in the past that the upload limit is set to 50MB. This being the 21st century I thought I’d make life a little more rational and change it to 200MB or so. So! Into Central Admin, find the max upload and we’re away.

Except, of course, we’re not because it didn’t work.

Consulting the Google oracle I found this:

Which lead me to:

Now, with all the changes made to web.config, and I’m still getting an error saying the file is larger than allowed. Uh oh. Back to Central Admin, back to the setting, which is under Application Management->Web Application General Settings. Turns out I had the wrong web application selected.

Oh well. Stupid errors caused by stupid oversights again.

a day at the park

My mother gave me a video camera for Christmas, with a heavy hint that I should be taping my kids and sending her the results, as we live on different continents.

My mother gave me a video camera for Christmas, with a heavy hint that I should be taping my kids and sending her the results, as we live on different continents.

I haven’t done much so far because, while I feel I’m a better cameraman than most, editing takes a very long time and is quite tedious, even though I’m using the very basic Windows Live Moviemaker.  You also have to get intimately familiar with your footage, so every camera shake or duff pan gets viewed a zillion times.

Anyway, the result is below.  You’ll probably find it quite dull unless you’re in it or just find children adorable.