Dear Gurus of Sharepoint. I updated .NET 3.0 as per the instructions at on KB article 932394 http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B932394 and am now trying to set the Sharepoint timer interval as following for one of my web applications. C:\Documents and Settings\-svc-ifp-spfarmdev>F:\SharepointMigrations\stsadm -o setproperty -propertyname "job-workflow" -propertyvalue "every 5 minutes between 0 and 59" -url http://istdev.bpweb.bp.com I get the following result, much to my disappointment. The server administration programs and the Windows SharePoint Services Web applications on this Web server are not compatible. Ensure that the administration program is the same version as the Web application. Help is gratefully accepted from anyone and everyone. What am I doing wrong!??? We have made no modifications for STSADM since its installation. Was I supposed to? Many thank, RB

I am getting the same message. On one web application setting the timer worked, on the other it does not.

I'm getting the same error message while trying to add a timer service using:stsadm.exe -o setproperty -url http://my_server/site-pn alerts-enabled -pv truehas anyone found a solution for this?

I thought i'd bump this up to see if anyone has any suggestions. Since i've been working this problem, i've installed two hotfixes (kb941422 and kb948945) and i've also ran the command:stsadm -o upgrade -inplace -forceupgrade ..... Nothing has worked. when I try to run the command to set the timer job (stsadm.exe -o setproperty -url http://my.server.... -pn alerts-enabled -pv true) I still get the error message listed above.If anyone has any suggestions, i'm all ears....thanks.

When I ran into this problem it turned out I had the wrong URL. Once I put in the right URL everything worked fine. James

Thank you... I was about to panic and start using four letter words.... Check your URL (including protocol HTTP vs HTTPS)Once again thanks

Hello,I've checked my URL including protocoll and get this error again and again. All of my other webapplication are fine. But only one is failing by execute following command "stsadm -o getproperty -pn job-immediate-alerts -url http..". I couldn't find out any differents between my webapplications and there versions.All of them have same versions. What is cause of my issue and how can I resolve it?greetings Danny

I have same issueBasically the stsadm command works for some url but not the others.For example, all next web applications are hosted on my serverurl1.company.comurl2.company.comurl3.company.comThe command works for url1.company.comC:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>STSADM.EXE -o getproperty -url http://url1.company.com -pn alerts-enabled <Property Exist="Yes" Value="yes" />but not for url2.company.com, it will returnThe server administration programs and the Windows SharePoint Services Web applications on this Web server are not compatible. Ensure that the administration program is the same version as the Web application.A simliar issue with Alert, all alert works from url1.company.com but not from url2.company.com

My issue with this, boiled down to running two different versions of Sharepoint on one server. I have a SBS2003 installation, which requires that you install WSS3 side-by-side, so as not to disrupt the WSS2 services that are an integral part of SBS2003. As a result, the first time I attempted to set a property using STSADM (in my case I was trying to get rid of the "New!" tags) I ran into the same error. The command I used was this: stsadm.exe -o setproperty -pn days-to-show-new-icon -pv 0 -url http://intranet whilst located in \Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN. I tried changing to \60\BIN (I assume this STSADM belongs to WSS2?) and it still didn't work. It took me a few seconds to realise, that although I was using the correct STSADM for my WSS3 site configuration, I was in fact pointing the URL argument to http:\\intranet, which will resolve to my WSS2 default site - which is running on port 80 on the server - and that, regardless of the fact that I had put in my host header information correctly (intranet), STSADM wasn't able to just "know" that I mean the server on the WSS3 configured port. As a result, the solution to my problem was in fact to ensure I used the following command: stsadm.exe -o setproperty -pn days-to-show-new-icon -pv 0 -url http://intranet:2010 which thankfully worked perfectly. I hope this information is of use to someone who ends up here from Google, like I did :) Ben.

Hi Ethand I was having the exact same problem. I've been checking SMTP'server, versions relay settings. All to find out that there are two places that you set the outbound email settings. The first place is under the operations tab. The second is under the "Applications tab - Settings for outbound e-mail in webapplications". Here you need to make sure that the right server is selected. That solved my issue. /Ulrich