Important Security Hotfix MS07-059

Techy News Blog » Important Security Hotfix MS07-059

Techy News Blog » Important Security Hotfix MS07-059 — Tue, 09 Oct 2007 10:24:59 GMT

PingBack from http://www.artofbam.com/wordpress/?p=6335

re: Important Security Hotfix MS07-059

joelo — Tue, 09 Oct 2007 10:35:15 GMT

Note, a couple of these links still aren't live yet as of 12:30am Pacific time on Oct 9. I wanted to give you a heads up on this as early as I could knowing that these links would be live later. I hope this doesn't cause confusion.

Joel

WSS v3: Important Security Hotfix MS07-059

Wes Preston — Tue, 09 Oct 2007 16:56:49 GMT

Be sure to check out this hotfix for WSS v3 as posted on the SharePoint Team Blog: http://blogs.msdn.com/sharepoint/archive/2007/10/09/important-security-hotfix-ms07-059.aspx

WSS 2.0 SP3 and SPS 2003 SP3

Joel Oleson's SharePoint Land — Tue, 09 Oct 2007 21:02:14 GMT

You may not have heard about these updates, they may not have hit your radar is you're already running

no se tarden

Haaron Gonzalez — Wed, 10 Oct 2007 02:50:02 GMT

Tienes implementado SharePoint en tu empresa? o implementaste sharepoint para tus clientes? Bueno, en

no se tarden

Haaron Gonzalez — Wed, 10 Oct 2007 02:50:25 GMT

Tienes implementado SharePoint en tu empresa? o implementaste sharepoint para tus clientes? Bueno, en

re: Important Security Hotfix MS07-059

joelo — Wed, 10 Oct 2007 03:38:32 GMT

Note the links have been updated and they are now all live.

More Harm then Good

Chris Kuntz — Wed, 10 Oct 2007 18:32:37 GMT

I read through the fix, the known issues and what could happen should I install the patch. From that it sounds like the cure is worse than the illness. I really like the fact that after the patch is installed in CANNOT be uninstalled and several fix will break when we apply SP1 for WSS3. So unti MS can make it less dangerous to install patchins for WSS3, I will live with the vulnerbility.

re: Important Security Hotfix MS07-059

Tim — Wed, 10 Oct 2007 20:02:37 GMT

Joel, can you give us any release dates for WSS 3.0 SP1?

re: Important Security Hotfix MS07-059

Aaron K — Wed, 10 Oct 2007 21:28:28 GMT

Joel, does this hotfix address the item level permissions issue that results in an permanently broken list - SQL error "Invalid syntax near the keyword 'SET'"?

Support has stated this has been fixed in SP1, but does not know its status in a hotfix. It has broken multiple production lists and really causes the product to be unusable.

re: Important Security Hotfix MS07-059

joelo — Thu, 11 Oct 2007 00:12:28 GMT

I have added the download links to make it easier to get and more accessible. Still, be sure to read all the information before installing/deploying the hotfix.

re: Important Security Hotfix MS07-059

joelo — Thu, 11 Oct 2007 00:13:27 GMT

Sorry I can't provide any dates for SP1. It is still in beta with a select set of customers.

WSS HotFix Trashed My SharePoint Server

Daniel Barton — Thu, 11 Oct 2007 00:14:51 GMT

I was able to install the SharePoint hotfix without any errors, but when I then went to install the WSS hotfix it failed during the SharePoint Wizard. The upgrade.log file indicates that "CanUpgrade" failed for my databases.

Unfortunately now I can't get my server back to normal. I made a farm backup of the server before I started and restored it after the failure, but no luck. The restore completed successfully but my web sites aren't up.

If I try to rerun the patches it says they are already installed. If I try to run the SharePoint Wizard it says that the database has been upgraded and I need to install the patch.

Where do I go next? The only thing I can think of is to uninstall SharePoint completely and start over.

If anyone has suggestions you can reach me at daniel.barton@pgnmail.com.

re: Important Security Hotfix MS07-059

Jan Avramov — Fri, 12 Oct 2007 11:53:41 GMT

After applying this fix we are not able to start WSS Admin service. Anyone knows how to fix this?

Thanks

re: Important Security Hotfix MS07-059

One more crash — Fri, 12 Oct 2007 13:26:53 GMT

I had the same kind of crash, something to do with SQL tables missing, I know that this is not the support forum, but MOSS team should be aware of the "quality" of this patch... not good...

re: Important Security Hotfix MS07-059

joelo — Sat, 13 Oct 2007 01:47:28 GMT

I've forwarded your comments to support. I'll respond either on the blog or in the comments when I get any answers.

re: Important Security Hotfix MS07-059

joelo — Sat, 13 Oct 2007 04:18:41 GMT

If you ran into a problem installing this, you should contact support for the quickest resolution. Due to the nature of this, I'd like to share a couple of soltuions and will try to track down a couple over the comments if I can get copies of the upgrade logs and explanations of your environment and what you did. Email me at joelo at microsoft.com

FYI. The WSS Admin problem is likely fixed by the GroupBoard KB article: http://support.microsoft.com/?id=941678

Also make sure you have already tried the solutions recommended on this post.

http://blogs.msdn.com/joelo/archive/2007/09/26/hotfixes-service-packs-and-password-resets.aspx

specifically try the:

psconfig –cmd upgrade –inplace b2b –wait –force

and then if that doesn't work try:

stsadm -o upgrade -inplace -forceupgrade

re: Important Security Hotfix MS07-059

Paul Buckle — Mon, 15 Oct 2007 13:57:04 GMT

We also can't start WSS Admin service after applying this hot"fix". This is not good.

The psconfig command doesn't work either - it says something about -cmd being invalid. I haven't tried the stsadm fix as I am looking elsewhere for a solution at the moment.

re: Important Security Hotfix MS07-059

Tronn Carson — Mon, 15 Oct 2007 15:40:55 GMT

I’ve applied the hotfix several times with clean installs on two development servers using “complete” installation and one staging farm of two WFEs and one application server with Central Administration. I’ve run the installs with and without dropping content databases first. When I do not drop the content databases I always have to start the indexing manually at Step 9. I’ve also tried manually forcing software upgrade as you recommended.

Either way when I run the verification steps I get these results:

• Central admin reports version 12.0.0.6039

• SELECT * FROM VERSIONS reports 12.0.0.6039 (not 12.0. 6035 as expected)

• Upgrade.log reports 0 errors and 0 warnings

• Microsoft.SharePoint.dll version is now 12.0.6039.5000

• Microsoft.Office.Server.dll version is 12.0.4518.1014 not 12.0.6036

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\OSERVER\DisplayVersion reports 12.0.4518.1016 not 12.0.6036

• Windows Update is still reporting WSS and Office Server hotfixes need to be applied

Any advice appreciated.

Re: After applying this fix we are not able to start WSS Admin service

Pavel Shilov — Mon, 15 Oct 2007 20:21:55 GMT

I get "Cannot start service SPAdmin on computer '.'.

System.InvalidOperationException: Cannot start service SPAdmin on computer" in PSDiagnostic log file and hotfix doesn't finish installation.

Workaround that help my:

use this command after installing the binary files with SPFarm admin user account:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>psconfig.exe -cmd upgrade inplace b2b wait force

SharePoint FAQ on DST and October 9th Public Update

Joel Oleson's SharePoint Land — Wed, 17 Oct 2007 00:41:44 GMT

I've gotten some questions asked on the hotfix and public update I wanted to address here. Q. Do I need

re: Important Security Hotfix MS07-059

joelo — Wed, 17 Oct 2007 00:55:00 GMT

You should look at this post in an FAQ. I've tried to address a lot of these questions.

http://blogs.msdn.com/joelo/archive/2007/10/16/sharepoint-faq-on-dst-and-october-9th-public-update.aspx

re: Important Security Hotfix MS07-059

Todd Walker — Wed, 07 Nov 2007 00:48:41 GMT

Anyone know if the other hotfixes such the May 8 hotfix package (KB936867 and KB936877) are also included in this package? When I try to install the May 8 hotfixes after this update it claims the hotfix is already installed, but I am not convinced.

Addendum to the SharePoint Deployment Daylight Savings patch issue

Aaron Robertson-Hodders SharePoint Blog — Fri, 09 Nov 2007 02:53:01 GMT

There has been much written about the issue (in particular Joel's Q&A ) with Deploying Solutions

Addendum to the SharePoint Deployment Daylight Savings patch issue

SHAREPOINTBlogs.com Mirror — Fri, 09 Nov 2007 03:35:08 GMT

There has been much written about the issue (in particular Joel's Q&A ) with Deploying Solutions

re: Important Security Hotfix MS07-059

Amol Ghanwat — Tue, 13 Nov 2007 20:09:22 GMT

Hi Everyone,

My name is Amol and i have been working upon cases where you get issues after you install the update 934525. This is a security update and so, after installing such a hotfix might cause sharepoint to stop working if your server or your configuration has some things missing. So, you need to troubleshoot the issue first and then try to find out why the upgrade of Sharepoint Technologies Wizard is failing.

Now, when you install the hotfix and then try to run the Products and Technologies Wizard, it should get completed if you do not have any things missing. But unfortunately if it fails, then you can try the following steps.

- Run the Products and Technologies Wizard and take a note at what step the wizard if failing. [It should ideally fail at step 2 or 8 or 9.]

- If the wizard fails at Step 8 or 9 then take look at the PSCDiagnostic_<id>.txt file located under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs

- Open that file in notepad and Search for "ERR" and do a match case for it.

- Take a note of the error message.

- Run the following command on the Sharepoint server:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin > psconfig -cmd upgrade -inplace b2b -force -wait

- If this command failes then open the following file : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\upgrade.log

- Search for "[ERROR]" (excluding the quotes) and do a match case for that. Look at the error message and take a note of it.

- Now you are ready with the basics that you need to troubleshoot the issue.

- The upgrade.log file should give you clear messages that should help you identify the problem. If you are not able to find out the problem, please paste the error messages in this blog and i will take a look at them.

Thank You,

Amol Ghanwat

Cannot start Windows Sharepoint Services Administration

Peter — Tue, 13 Nov 2007 20:32:46 GMT

I finished installing the security patches to WSS and MOSS after I ran psconfig –cmd upgrade –inplace b2b –wait –force. But now Windows Sharepoint Services Administration is stopped although it's set to automatic. I tried starting it manually by going to the services console, but it won't start. I get error 1053: The service did not respond to the start or control request in a timely fashion.

How do I fix this?

re: Important Security Hotfix MS07-059

birixiote — Mon, 10 Dec 2007 03:46:16 GMT

We are having no luck installing the updates as we are getting the following error: “The expected version is not found in the system”. The version of SharePoint we have running is 12.0.0.4518.

Do we need install any other fixes before we install the latest one to get the versions up-to-date? Any help will be greatly appreciated.

re: Important Security Hotfix MS07-059

Tom C — Thu, 10 Jan 2008 00:05:34 GMT

I'm also havintg the same problem as birixiote. I'm getting "The expected version of the product was not found on the system" error when trying to install KB937832. I have MOSS 12.0.4518.1015 with SQL Server 2005 SP2 back end.

Daylight savings issue with MOSS 2007 deployments pre SP1

Merrick Chaffer's Blog — Wed, 02 Apr 2008 18:33:40 GMT

Daylight savings time. http://blogs.msdn.com/sharepoint/archive/2007/10/09/important-security-hotfix-ms07-059.aspx

Daylight savings times messes up WSP solutions

Nick's SharePoint Blog — Mon, 07 Apr 2008 14:03:20 GMT

Last week I encountered something strange here on the servers. Retracting a solution file (*.wsp) took