Thursday, April 26, 2012

Can't browse to an SSL-secured Office SharePoint Server 2007 site or to the Search Settings page for a SSP Site


Changed Indexer from SERVER- A to SERVER-B for SSP1 and while launching the SSP,
I got below error:-
Could not connect to server for application 'SharedServices1'. This error might occur if the server is not responding to client requests, the firewall or proxy configuration is preventing the server from being contacted, or the search administration Web service is not running on the server

Checked the ULS logs:-
Exception caught in Search Admin web-service proxy (client). System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.     at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)     at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)     at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)     at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)     at System.Net.Security.SslState.ForceAuthentication

Steps taken to fix the issue:-

  1. Installed the IIS 6.0 Resource Kit on the index server (SERVER-B).
  2. Assigned a new SSL certificate to the Office SharePoint Server Web Services site on the index server using the selfssl tool from the resource kit.
    1. Selfssl /s:(IIS ID of the Office Server Web Services site) /v:(length of validity for the certificate in days)
    2. Selfssl /s:1720207907 /v:99999
Replaced the existing certificate with the newly created SelfSSL certificate and Search Settings now worked.

Tuesday, February 14, 2012


Unable to edit List items in SharePoint
For existing list, please follow the below steps to resolve the issue.
1. Download “SharePoint Manager”
2.Launch “SharePoint Manager” from SharePoint App Server by logging with Farm Admin account.





















3. Expend the respective site and then list.


4. Scroll down and select the field value.






5. Click on the button in front of (Collection) text.
















6. Scroll down and select the "Effective Permission Mask" and "SxchemaXml".
7. Copy the "SchemaXml" value.







8. Add the value RenderXMLUsingPattern="TRUE"








9. Overwrite the value and click OK.
10. Now you should able to edit the items in the list.







Tuesday, October 4, 2011


Issue
Unable to upgrade ‘MOSS 2007 SP1 + Dec 2008 CU (12.0.0.6335)’ to ‘MOSS 2007 SP2 + Aug 2011 CU (12.0.0.6565)’.  It was getting failed on 8th – 9th step while running the ‘SharePoint Products and Technologies Configuration Wizard’ with below error message.

SearchSP2AnchorTextDatabaseAction.Upgrade on database SPDBP\SPDBP:SharedServices1_Search_DB
Action 12.2.506.0 of Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence failed.
The statistics 'LinkId' is dependent on column 'LinkID'.

Cause
The statistics for ‘LinkID’ and ‘BatchID’ were dependent on column ‘LinkID’ and ‘BatchID’ in ‘SharedServices1_Search_DB’ database and it failed because one or more objects access this column. In order to get this done, dropped and re-created the statistics.

Steps taken to resolve the issue.
·         Drop the statistics for ‘LinkID’ (script attached) and tried to attempt but it got failed on the same step (8th-9th) with below error message.
SearchQFE21038DatabaseAction.Upgrade: Changing MSSBatchHistory column BatchID type to bigint on database SPDBP\SPDBP:SharedServices1_Search_DB
Action 12.2.508.0 of Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence failed.
The statistics 'BatchID' is dependent on column 'BatchID'.
·         Drop the statistics for ‘BatchID’ (script attached) then tried to attempt and again it got failed on the same step (8th-9th) with ASP.Net error message.
Action 3.0.3.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed.
InstallAspNet 1785161557 failed.
·         Re-register the ASP.Net component by running the command ‘aspnet_regiis –u’ and ‘aspnet_regiis –I’
·         Attempt to run ‘SharePoint Products and Technologies Configuration Wizard’ and this time MOSS 2007+SP2 got updated successfully.
·         Next steps to install Aug CU 2011, binary got installed on all servers successfully but when we tried to run ‘SharePoint Products and Technologies Configuration Wizard’ then again it got failed on the same step (8th-9th) with time out error message.
Action 12.2.508.0 of Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence failed to commit.
Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
·         Restarted the SQL services and SharePoint servers then tried to attempt ‘SharePoint Products and Technologies Configuration Wizard’ and it got completed successfully.
·         Re-created the statistics for ‘LinkID’ and ‘BatchID’ (script attached).
·         Verified the version (12.0.0.6565) from Central Administration -> Operations -> Servers in farm.

Script to drop statistics
/****** Object:  Statistic [LinkId]    ******/
USE [SharedServices1_Search_DB]
GO

if  exists (select * from sys.stats where name = N'LinkId' and object_id = object_id(N'[dbo].[MSSAnchorText]'))
DROP STATISTICS [dbo].[MSSAnchorText].[LinkId]
GO

/****** Object:  Statistic [BatchId]    ******/
USE [SharedServices1_Search_DB]
Go
if  exists (select * from sys.stats where name = N'BatchID' and object_id = object_id(N'[dbo].[MSSBatchHistory]'))
DROP STATISTICS [dbo].[MSSBatchHistory].[BatchID]
GO

Script to create statistics
USE [SharedServices1_Search_DB]
GO
/****** Object:  Statistic [BatchID]    
CREATE STATISTICS [BatchID] ON [dbo].[MSSBatchHistory]([LinkId])
GO
/****** Object:  Statistic [LinkId]    
CREATE STATISTICS [LinkId] ON [dbo].[MSSAnchorText]([LinkId])
GO






Friday, March 6, 2009

PDF Icon does not show in the document library while uploading the pdf file.


Steps Taken for resolution
1. Copy the PDF.GIF file to “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images”
2. Edit the file C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML
1. Add an entry for the .pdf extension.
2. Reset the IIS
3. After that we were able to view the pdf icon in your document library.


Unable to open few Links on SSP Site.

Steps for resolution

1. Unable to open Search Settings page on SSP Site.

Error :- Access Denied C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES\Menu.css

Solution:-
Added the WSS_ADMIN_WPG Group on the 12 Folder (Security & Groups).

2. Also unable to open User Profiles and My Sites.
Error:- HTTP 403 Page not found.

Solution:-
Checked the event viewer and ntlm authentication was failing.
And we run the below command
stsadm -o authentication -type windows -usewindowsintegrated -exclusivelyusentlm -enableclientintegration -url http://abcxyz:8080

Issue resolved.

Friday, December 19, 2008

Slow performance of SharePoint Site

Problem:
========================================
SharePoint site takes 25-40 seconds to load initial web page when accessed from overseas sites.
SPS Web server in Toronto is accessed quickly when the client is local, but takes a long time when accessed from Australia, for instance.

Solution:========================================
Traces have been taken from client and server, and we intermittently see a substantial delay between client sending an HTTP GET and server responding, as well as a delay in establishing the initial session. However, there is no way to determine where exactly in the path between the machines the delays are introduced.
The traffic flow is as follows:
Client----->Internal Switches-----> Certeon Application Accelerator-----> Router-----> MPLS Cloud-----> Router-----> Certeon Application Accelerator-----> Internal Switches-----> Web Server

Also of note is that after the initial delay in loading the website, further navigation of the site is done with acceptable performance.
Local Toronto clients do not access the site through the Certeon, but go direct via LAN, and see no delays. So this should eliminate the server config as an issue.
All remote clients experience the delays, some greater than others, generally corresponding to how far away the client is. For instance, clients in Perth see about a 28 second delay in loading the site, while clients in Salt Lake City see a delay of about 15 seconds. This leads us to suspect that the MPLS cloud routing and infrastructure is introducing the delay, but we need to trace on both sides of the
Certeon to eliminate it as the cause.
The Certeon translates the IP address of the client, and also alters the port on which the connection is made to the server, and so it is not possible to correlate packet for packet the communication between client and server captured in the traces.
In order to remove the Certeon devices from the environment, we disabled its functionality on both sides of the connection, effectively allowing all traffic to pass through the devices unaltered. This now allows us to see the full communication between client and server with correct port assignments and IP addresses, and we see that there are actually no intermittent long delays recorded
at all, and the full download of the site legitimately takes a full 28 seconds based on the amount of data over the latency of the connection.


Thursday, August 28, 2008

Unable to browse CentralAdminSite. It keeps ask the user name & password.

DESCRIPTION: Unable to browse Central Admin Site. Every time It asks the user name & password while we were putting the right credentials for central admin site.
SYMPTOMS: Every time Central Admin Site asks the user name & password while we are putting the correct credentials.
ERROR MESSAGE: We get the pop-up screen (User Logon Box) for entering the user name and password.
RESOLUTION: Run the command psconfig -cmd adminvs -provision -port 45576 -windowsauthprovider -onlyusentlm
Fixed the issue.