>Recently we had an issue where I was applying the latest updates to our test SharePoint server. Unfortunately for one reason or another once I had applied the MOSS Infrastructure Update the installation failed and everytime I ran the hotfix installer it would get all the way to the end and throw an error.

Looking at the event logs there were a number of issues where stored procedures could not be found so we decided to rollback the server to a previous backup using Acronis TrueImage.

Something that I should make clear is that the server is a VMWare ESX Server based virtual machine and is running Windows 2003 R2 64bit. After the C: and database data and logs were restored I snapshotted the machine and then started the process of applying the WSS Infrastructure Update….

The hotfix installed all the binaries ok and so started the SharePoint Configuration Wizard, this got to step2 and threw an error.

An update conflict has occured DiagnosticService is being updated.

Performing a quick google uncovered this little gem from Microsoft, “When updating the alternate access mapping the message – An update conflict has occurred, and you must re-try this action occurs. This Knowledge base article (KB 939308) goes through a process to clear down the configuration cache which is found in c:\documents and settings\all users\application data\microsoft\sharepoint\config\{guid}\

Following the instructions allowed the successfully installation of the Infrastructure Update and got the machine going again.

Hopefully this will help someone in a similar pickle!

Cheers
Simon

>Had an issue today where I wanted to export a site from a live environment to a staging environment. So I thought thats fine, run stsadm -o export -url [yoursiteurl] -filename [backup_filename.bak] -version 3 and then import on the otherside.

However the command run for a while and then threw an exception out of disk space. I check the drive that I was creating the file on and it had 131Gb free.

After some investigation I could see that the c:\ drives free disk space was decreasing as the export command was run again.

To get around this I reset the %temp% and %tmp% variables to point to a temp directory on the disk with free space.

Re-ran the command and worked successfully this time! Something to think about and very dangerous if your disks ran out of space, particularly on the data or log drives! Fortunately the stsadm command seems to stop when there is less than 220Mb on the drive…

Hope thats useful to someone!
Simon