Hello together,
as usual, the Kudos are going to Joergsi 😉
The June cumulative update packages are available.
NOTE!! This update makes the security patch (MS10-039 or KB 983444) from June obsolete!
Please see also my other post for the Known issues with this fix!
WSS:
983311 The full server package for WSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;983311
MOSS:
983310 The full server package for MOSS
http://support.microsoft.com/default.aspx?scid=kb;EN-US;983310
Download and installation information:
- NOTE!! Install SP2 for WSS and MOSS SP2 and Language Packs if not yet happened.
- Do you need more information about the SP2 update?
Please check out my post on “All about updating WSSv3 and MOSS 2007” - Download full server package for WSS: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=983311&kbln=en-us
- Download full server package for MOSS: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=983310&kbln=en-us
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed.
SharePoint mysteries and more... 
We are experiencing the same error as Brian C did after installing the hotfixes. It surfaces when a user, who has appropriate permissions in the document library, tries to check out a document from an Enterprise SharePoint 2007 document library.
Does anyone have any pointers for a fix for the fix?
The log file entry is as follows:
Unexpected query execution failure, error code 8144. Additional error information from SQL Server is included below. "Procedure or function proc_FetchDocForRead has too many arguments specified." Query text (if available): "{?=call proc_FetchDocForRead(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"
LikeLike
Hi Steve,
are there any known workflow related issues as a result of installing the June 2010 CU for WSS and MOSS?
I have 2 lists with 1 SPD worklfow on each list that i use to update each other in a 6 hourly cycle. The workflows run fine for a few days and then fail on some of the items (approx 30 items in each list with varying numbers failing at any given time). There does not appear to be a regular interval at which they fail. I tried using stsadm to increase the workflow thresholds etc. to no avail.
No events are shown in the Event Logs and none are shown in the ULS logs.
I installed the June 2010 CU to try and fix the issue described above and now i can no longer open a workflow in SPD. I continually get the error "Server Error: Unable to complete this operation" or "Failed to load the workflow" when i use the File->Open Workflow option.
I have tried clearing out my Designer cache to no avail. I can replicate this error 100% from different PCs, with different users, even from the WFE itself so I dont believe it is a permissions of .NET issue. I have no problem opening workflows in all my other farms that are all MOSS SP2. All farms have the codeplex workflow actions installed. I have uninstalled and reinstalled the custom actions. I have ensured the necessary changes are in place in the web.config.
I have create a new workflow with no actions or conditions and am unable to go back and open it. I am also unable to delete any workflows. I can disassociate them from a list from not delete them
There are no events shown in the Event Logs but it seems to trigger the following event in the ULS logs:
w3wp.exe (0x157C) 0x0120 Windows SharePoint Services Database 6f8g Unexpected Unexpected query execution failure, error code 8144. Additional error information from SQL Server is included below. "Procedure or function proc_FetchDocForRead has too many arguments specified." Query text (if available): "{?=call proc_FetchDocForRead(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"
Any help you might have would be gratefully appreciated. I am contemplating deploying the August CU just to see if i can resolve these errors as i am running out of ideas.
Regards,
Brian
LikeLike
Hi Jeff,
I'm very sorry about that and I'm still not aware of such regressions caused by the June CU. But if there would be any, then they might be fixed with the august CU. As already posted to Brian, please try to install the august CU also and check whether you can repro the issue.
For download, click here: blogs.technet.com/…/august-cu-for-moss-2007-and-sharepoint-2010.aspx
And finally, if you still have your problems after applying the august CU, then please open a service request at MS Support!
LikeLike
Hi Brian,
I would agree to first try to install the august CU. I'm currently not aware of any known regressions with the June CU. from the log entry, the stored procedure proc_FetchDocForRead fails for some reason.
What does the event log says according to it?
DId you turned on the verbose logging for ULS?
What, if you create a new web app and retry to repro your issue there? Same result?
Also a profiler trace on SQL server might bring some more light on it.
If after applying august CU you still have this issue / can repro it on a new web app, you should call MS Support to open a case.
Hopefully you'll resolve it after patching 😉
greets, Steve
LikeLike