MOSS 2007 SP2 and WSS3.0 SP2 Support has ended

According to MS Product Life Cycle , Microsoft Office SharePoint Server (MOSS) Service Pack 2 and Windows SharePoint Service (WSS) SP2   supports has ended yesterday.If you do not upgrade your MOSS 2007 and WSS 3 server to SP3 level than you may not get fully support from Microsoft Support.
the minimal supported version is WSS 3.0 SP3 and MOSS SP3
http://support.microsoft.com/lifecycle/default.aspx?LN=en-us&p1=14414&x=11&y=11
http://support.microsoft.com/lifecycle/default.aspx?LN=en-gb&p1=12200&x=11&y=6

Advertisements

WSS3.0 Service Pack 3 and MOSS2007 Service Pack 3 has been released.

For WSS 3.0 Service Pack 3:
http://support.microsoft.com/kb/2526305

For MOSS2007 Service Pack 3:
http://support.microsoft.com/kb/2526299

Installation Order:

Install WSS Service Pack 3
Install MOSS Service Pack 3

Install needed Language service packs:
Install Service Pack 3 for Windows SharePoint Services 3.0 Turkish
Install Service Pack 3 for Windows SharePoint Services 3.0 Arabic

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.

Important! . As you know at same time october CU 2011 has already released. There is some problems upgrade both SP3 and October CU 2011. Microsoft has working on it. So your options now install sp3 or install october CU. Not upgrade together. I will inform you when it is fixed.

 

Problem with Security Update for Windows SharePoint Services 2007 (KB2493987), 64-bit Edition

After  kb2493987 installed unable to connect sharepoint sites getting error Service Unavailable.
Unable to run IIS application pools getting error.

Application pools stop when a request arrives with the following error in the system logs:
A process serving application pool terminated unexpectedly process exit code was 0xffffffff
Checked the IIS file versions and there are a lot of DLLs do not match SP2 version.
I have asked customer to re-install SP2 and it solved the issue.

After IIS working correctly this time sharepoint site getting error of  404 not found error.
First check DisableLoopbackCheck issue.

Don’t forget when a security updates patched  need to run configuration wizard until not to do so.

CAUSE
===================
kb2493987 Automatically instaled windows update.

SOLUTION
====================
net stop MSSQL$MICROSOFT##SSEE
net start MSSQL$MICROSOFT##SSEE
psconfig -cmd upgrade -inplace b2b -wait -force

For More Information:
http://support.microsoft.com/kb/2493987
http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx
http://support.microsoft.com/kb/944267

How to enable verbose log mode on Moss 2007

First Method: Using Central Administration

1) Open your Central Administration web page and Click “Operations”
2) Click Diagnostic Logging link

3) For enabling verbose mode for all categories:
Select and set “Select a Category” combobox value to “All
Select and set “Least critical event to report to the event log” combobox value to “Warning
Select and set “Least critical event to report to the trace log” combobox value to “Verbose

4) Click OK.Its done.
Important!:Please don’t forget change mode to default after collecting needed verbose mode logging. Because in verbose mode log files grows rapidly and if you are not enough storage your sharepoint server would be crashed

Important!:Before enabling verbose mode ensure you have enough hdd space on ALL your servers. Because this is a farm configuration and all servers has been affected by this change.

For restoring default values.
Select and set “Select a Category” combobox value to “All
Select and set “Least critical event to report to the event log” combobox value to “Error
Select and set “Least critical event to report to the trace log” combobox value to “Medium
and click OK button.


Second Method: Using stsadm command

1) Open a command prompt
2) Redirect to path drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentions\12\Bin
3) Be sure that you have enough hardisk space for collecting verbose mode logging.
4) Run stsadm command:

Syntax
stsadm.exe -o setlogginglevel
[-category < [CategoryName | Manager:CategoryName [;…]] >]
{-default |
-tracelevel < trace level setting>
[-windowslogginglevel] <Windows event log level setting>}

For set all categories to verbose use this command:
exp:
stsadm -o setlogginglevel  -tracelevel verbose -windowslogginglevel warning

For set all logs level to default use this command:
exp:
stsadm -o setlogginglevel -default

Important!:Please don’t forget change mode to default after collecting needed verbose mode logging. Because in verbose mode log files grows rapidly and if you are not enough storage your sharepoint server would be crashed.

If you want to learn current logging level run bellowed command:
Exp:
stsadm.exe -o listlogginglevels

for more information.
http://technet.microsoft.com/en-us/library/cc261740(office.12).aspx

You can find Sharepoint logs in folder: (Default folder)
Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentions\12\LOGS
NOTE: If you need to transfer these files to Microsoft File Services , please compress files in zip file. If zip file size is bigger than  5GB please spearate multiple files that lower than 5GB.

Hhave nice day …

Backup Error on Moss2007: Object Shared Search Index failed in event OnPrepareBackup, The current operation timed-out after 3600 seconds

If you getting error in spbackup.log file when getting backup like:
Error: Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.
WebException: The current operation timed-out after 3600 seconds
Debug: at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPrepareBackup(Object sender, SPBackupInformation args) at Microsoft.SharePoint.Administration.Backup.SPBackup.RunPrepareBackup(SPBackupRestoreObject node)

Cause:
When performing a backup of a search application, sometimes the operation for pausing the search application fails. In this case, the backup of the search index cannot continue. In that case, the SSP backup is virtually useless. Pre-SP2, the process of backing up the search database will continue. Post-SP2, the failure to pause the search application during a backup process will also result in failure of backing up the search databases, and the search databases will be marked with the same error as the search index component.
For More info:
http://download.microsoft.com/download/4/1/F/41F3A698-55E8-40B4-A306-AD6CF1F95394/2007%20Office%20Servers%20Service%20Pack%202%20Changes.xlsx

Resolution:
Upgrade to Moss 2007 SP2

Moss 2007 web enabled Infopath form timeout troubleshooting

This is an old problem but lastly i handle a case and fallowed below troubleshooting.

1) Check the InfoPath service timeout configuration. Central Administration -> (InforPath Form Services Section) Configure Infopath forms service.
Check “Data Connection Timeouts” as milliseconds.

Check “Form Session State” Active session should be terminated after option

2) Check your web application timeouts from IIS by open IIS mmc and right click your sharepoint site.

3) Check your sharepoint web.config file for HttpRuntime.executionTimeout value :

<httpruntime maxRequestLength=”51200″ executionTimeout=”7200” />

Optional Int32 attribute.
Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET.This time-out applies only if the debug attribute in the compilation element is False. If the debug attribute is True, to help avoiding application shut-down while you are debugging, do not set this time-out to a large value.The default is 110. In the .NET Framework 1.0 and 1.1, the default is 90 seconds.