iPhone 3G – I’ve finally upgraded

31 07 2009

white-iphone Well I’ve finally upgraded my trusty 2G iPhone to a 3G one – I couldn’t justify the price of the 3GS so went with a 3G 16GB one in white as you don’t see as many of these as the black ones.

I opted to buy the phone outright and use my o2 simplicity sim card as I think the prices for the iPhone contracts are just crazy!

I’ve been using it for about a week so far and I love it! The best thing is the sheer increase in speed over my old 2G one which was so slow browsing the web etc on GPRS or EDGE. I prefer the screen on the 3G iPhone and the flush headphone socket so I can use normal headphones and not just the apple ones.

As I’ve installed lots of apps since I’ve started using the new 3G device, I thought I would share a list of top rated ones:

reqall_icon_5121-150x150 reQall –For managing tasks/notes etc

original myPhone –Syncing facebook pictures/birthday’s with your iPhone contacts

Flight_control_app_iconFlight Control –So simple yet so addictive, in this game you have to land as many aircraft as possible by drawing routes on the screen to the runway

Let me know what you think of the above apps and the iPhone 3G in general 🙂

Alerts not working after WSS Backup/Restore

24 07 2009

Recently we had a problem with our WSS environment when we tried to move the databases from one SQL server to another. I used the standard stsadm restore option to restore the individual web applications &  site collections.

Everything appeared to work great and I re-deployed our .wsp’s until one of the users notified me that their alerts didn’t seem to work. I double checked their alerts on the site and they were set up ok – ‘Immediate’ alerts on a documents list.

When I tried to subscribe myself a new alert, I would receive the initial subscription email but not the actual alert.

I did a bit of digging around and it turns out there that there is a known bug when using stsadm or the GUI to restore a web application – the Timer Jobs don’t get restored! When I check the timer job definitions page in central admin I could only see timer jobs for those web applications that were created since the restore.

This is well document in Dave Wollerman’s blog –

See here:


or here:


Now it seems there is a Post-SP1 hotfix available here that will fix the issue (KB941922) – http://support.microsoft.com/kb/941422

I cannot confirm however if that hotfix works as I manually created the web applications again keeping the IIS sites & content databases, this then recreated the missing timer job definitions and hey presto the alerts stopped working!

Hope this helps anyone with similar issues!

WSS – OWSTimer error when performing Web Application restore

15 07 2009

I had to rebuild our WSS farm recently and create a new configuration database so I needed to restore our web applications. I had taken a backup of the entire farm and decided to restore each web app individually.

When I used the GUI (Central Administration) to do the restore I received the following error:

Error: Object WSS_Intranet (89) (previous name: IntranetDev (80)) failed in event OnRestore. For more information, see the error log located in the backup directory.
SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=WSS_Intranet (89) Parent=SPWebService is being updated by svc_moss_sql, in the OWSTIMER process, on machine **Machine Name**. View the tracing log for more information about the conflict.

Looking in the error logs and event viewer didn’t yield any more information so I did some research on the internet. It turns out to fix it you need to temporarily stop the OWSTimer (WSS Timer) service. Unfortunately if you do this it means you cannot use the GUI to restore as this uses a timer job, so you will need to restore using the STSADM restore command:

e.g. STSADM –o restore –directory “\\servername\backupfolder” –restoremethod new –item “Farm\Windows SharePoint Services Web Application\Intranet”

In this case ‘item’ is the path in the backup tree to the web application you wish to restore – have a look in the central admin GUI to help find the correct path.

Once you run the command you should see the web application being restored, once it has been restored you can start the OWSTimer service again.

I got this info from Tom Meskens blog, see the original post here – http://ph-tom.blogspot.com/2009/06/owstimer-error-when-restoring.html, thanks Tom!!

Note: Be careful if you are doing this on a live/production server, be sure you know the effects of stopping the OWSTimer service as this will affect any running timer jobs including custom ones.

Hope this helps! 🙂

A WSS Nightmare!

10 07 2009

Thought I’d blog post about the problems I encountered last night whilst trying to move our WSS databases to another SQL server, what I thought would take about an hour max turned into a 6 hour job!

I ran the PSConfig wizard and disconnected the server from the farm, I then gave the thumbs up to our DBA to move the config and content databases.

After these were moved I went to reattach the server to the farm again by running PSConfig, after fixing a few problems with SQL permissions I thought everything would be ok. Was I wrong or was I wrong!? I kept getting an error when the wizard was ‘Securing the SharePoint resources’ that it couldn’t copy some files to the folder ‘D:\Web Server Extensions\12’, in Particular the ‘Data’ Folder.

That got me totally flummoxed, the D: drive?? I couldn’t understand why SharePoint would try to copy its 12 hive to the D partition, we always had the 12 hive in the normal place on the C (System) partition. As it turns out, some IIS sites had been migrated from another server and the IIS files placed on the D partition so we had two inetpub folders (one on C and the other on D).

It seems that this is why SharePoint was trying to copy the folders to the other partition. After searching the registry I found lots of references to the folder D:\Web Server Extensions and attempted to change this to the normal 12 Hive. This did not work however and only caused more issues – so how did I fix it I hear you ask??

Well in the end I opted to totally uninstall WSS and re-install from scratch, upgraded to SP1 then reconnected to the farm. Hey presto all our sites were back and I just need to redeploy the solutions (wsp) packages again.

Lessons learned? – don’t migrate IIS settings/sites from other servers while WSS is installed, at least if you don’t know the consequences.

Hope this helps someone if you have the same problem :p