Zephyr's SharePoint Blog

My Sharepoint world experience notes on day to day basis…..

Archive for the ‘Errors’ Category

The SharePoint site collection size more than 50 GB is not opening

Posted by fillzephyr on June 21, 2012

Issue:

I got a call from a user that they are not able to go to their team sites. I tried to open the site and its thinking, thinking and thinking for about 20 mins and then IE throws error page not found.

Solution:

I tried another Site collection and it opens well. So my SharePoint environment is fine except this team site.

I gone to central admin and check the quota template and find it has about 49 GB data on that site collection.

We have used one DB per Site Collection for Document management.

I have a SQL DB backed up of the troubled SC and I did restore it to Dev. try to open it and it opened straight away without any trouble.

From this I find it’s not a problem with SharePoint it’s something related to DB size.

I check logs and event viewer and couldn’t find anything.

I gone to the timer services status under Operations and here you go I find Database statistics services hang on initialized states on 45% from last 2 nights for one server out of our four server farm.

Google it and find this article:
http://blogs.technet.com/b/patrick_heyde/archive/2010/05/27/advanced-maintenance-for-sharepoint-databases-defrag-update-index.aspx
I read about the smarter way section and Patrick specify about 50 GB limit and it strikes that it conflicts with our back up schedule which makes this time services on hang on state.
I gone to the timer services definition and stop the services for the Web app having this SC and done the following steps.
1. Stop Windows SharePoint Services Timer on Windows Services
2. Go to ‘C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config’ on front-end server
3. Clear xml files from the above folder.
4. Open cache.ini file and restart the number into ‘1’
5. Start Windows SharePoint Services Timer on Windows Services

The above steps clear SharePoint Config cache and allow the timer jobs to run properly. The Database statistics timer job is aborted.
Now I turn on the Database statistics timer job then change the timing for this time service from daily to weekly and from 6 am to 4 pm other than the backup scheduled.

Here are the stsadm cmd to change the timings.

To set the schedule for when database statistics are collected for the Web application http://test, use the following syntax:

stsadm -o setproperty -pn job-database-statistics -pv “daily at 15:00:00” -url http://test

To view the current setting of the job-database-statistics property, use the following syntax:

stsadm -o getproperty -pn job-database-statistics -url http://test

Now the site opens straight away.

Advertisements

Posted in Errors, SharePoint Blogs | Tagged: , , , , | Leave a Comment »

Error 6482 : Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

Posted by fillzephyr on August 6, 2009

Error 6482

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date:  4/15/2009
Time:  3:50:10 PM
User:  N/A
Computer: MOSSPRD
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (0953efa6-baa1-474d-8e4d-58a31fad7a2e).

Reason: The underlying connection was closed: An unexpected error occurred on a send.

Techinal Support Details:
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.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
— End of inner exception stack trace —
at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Resolution:

I am getting this error after my fresh installation in Of Moss Prod with SP1. I am having 64 bit environment.

I had download iis resource kit from Microsoft website.
After downloading on the server I run the selfssl command from :

Then I type the following commands :

( Installs self-signed SSL certificate into IIS.
SELFSSL [/T] [/N:cn] [/K:key size] [/S:site id] [/P:port]

/T               Adds the self-signed certificate to “Trusted Certificates”
list. The local browser will trust the self-signed certificate
if this flag is specified.
/N:cn            Specifies the common name of the certificate. The computer
name is used if not specified.
/K:key size      Specifies the key length. Default is 1024.
/V:validity days Specifies the validity of the certificate. Default is 7 days.
/S:site id       Specifies the id of the site. Default is 1 (Default Site).
/P:port          Specifies the SSL port. Default is 443.
/Q               Quiet mode. You will not be prompted when SSL settings are
overwritten.

The default behaviour is equivalent with:

selfssl.exe /N:CN=MOSSPRD /K:1024 /V:7 /S:1 /P:443 )

C:\Program Files (x86)\IIS Resources\SelfSSL>selfssl /s:951338967 /v:1000
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.

Do you want to replace the SSL settings for site 951338967 (Y/N)?y
The self signed certificate was successfully assigned to site 951338967.

Posted in Errors, IIS, SharePoint Blogs | Tagged: , | Leave a Comment »

Errors 6398, 7076, 6482 on Only One server.

Posted by fillzephyr on August 6, 2009

I have 2 Web Front End  Server A  and Server B
I  ll find the errors  6398, 7076, 6482 on the event viewer of  server Server B  only (Not Server A) OR When I try to look at the web sites listed under IIS of Server B  , I’ll get a dialog box noting “Specific path cannot be used at this time”.
 
To resolve I ll have to just go to the services(Path : Start>Administrative Tools>Services) Open it.
Go to the Windows SharePoint Services Timer and restart it. This error will gone.
 
There are Hot fixes there for it but it happens sometime only and Again its effect to Server B only Not the Server A.
 
The reason for this error is beause “You may be unable to manage IIS by using Server Manager if two threads access IIS at the same time”
 
Thanks.
 

Posted in Errors, SharePoint Blogs | Tagged: , , , | Leave a Comment »

Unable to Delete Share Service Providers (SSP) in SharePoint 2007 (MOSS)

Posted by fillzephyr on June 23, 2009

I am trying to delete two SSP from my environment and I am always getting this error:

An object in the SharePoint administrative framework, “SharedResourceProvider Parent=SPFarm”, could not be deleted because other objects depend on it.  Update all of these dependants to point to null or different objects and retry this operation.  The dependant objects are as follows:

– here I don’t see any dependencies (that’s really makes me wonder what’s happening)

I tried both ways to delete SSPs from central admin as well as using STSADM command:

stsadm –o deletessp –title “SSPName”

When I go to the Manage this Farm’s Shared Services Then my both SSPs are shown as unprovisioning.

I went through this simple way of deleting ssp.

First of all I find the Object id of my SSP. To come out through this I open the SQL Server Management Studio gone to the Objects table.

Under Databases>sharepoint_config_DBName > tables > dbo.Objects

And run the following select query

SELECT * FROM [SharePoint_Config_ DBName].[dbo].[Objects]

where name like ‘SSPName’

and find out the ID of my ssp.

Then I run the following stsadm command:

Stsadm -o deleteconfigurationobject -id “id retrieved from object table”

And still it gives me the same above error.

(In most of the cases after running above cmd when you try to delete SSP it works , but not in my case)

I then try this other way:

I find out that the object status of my ssp is “3” which should be 0 by default, so to convert it to 0 I run the following update query on my objects table

UPDATE [SharePoint_Config_ DBName].[dbo].[Objects]

SET [Status] = 0 WHERE objects.name=’SSPName’

It sets my status to 0.

When I go to the Manage this Farm’s Shared Services and refresh it the unprovisioning warning sign gone.

Now I tried to delete ssp using stsadm still the same error and the ssp shows unprovisioning warning sign again. I check in the object table and it shows me the status update to 3. I again change the status and make it to 0.

Now I want to delete the row with the object id of my ssp as I feel it’s an orphaned. I find the object id running select query.

SELECT * FROM [SharePoint_Config_ DBName].[dbo].[Objects]

where name like ‘SSPName’

then find the dependencies running the following query on dependencies table loacte

Under Databases>sharepoint_config_DBName > tables > dbo. Dependencies

SELECT * FROM [SharePoint_Config_DBName].[dbo].[Dependencies]

where [ObjectId] = ‘EBE75FD3-4EA3-4BF0-BC15-E796A0F7BC21’

check the dependencies.

Then delete it using the following query on dependencies table

Under Databases>sharepoint_config_DBName > tables > dbo. Dependencies

DELETE FROM [SharePoint_Config_ DBName].[dbo].[Dependencies]

WHERE [ObjectId] = ‘EBE75FD3-4EA3-4BF0-BC15-E796A0F7BC21’

Now I try to delete the unnecessay SSP and it is deleted through the Central Admin.

Hope it will help you out in issues of deleting the SSP.

Thanks!!!

Read the rest of this entry »

Posted in Errors, SharePoint Blogs | Tagged: , , , , | 8 Comments »

Solutions Deployment Hungs up on Deploying/retracting in MOSS 2007

Posted by fillzephyr on May 11, 2009

Problem: During the execution of a retraction/deployment the timer job may hang showing ‘Retracting’ or ‘deploying’ and never completes

Cause: This is cause from one of the WFE not being able to finalize the retraction or deployment.

Solution: For each WFE in the farm execute a stsadm.exe -o execadmsvcjobs. I had follow up these two good articles to come out from deploying /retracting status.

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

But what next when I try to deploy/retract the solution again. It hung’s up.  So I tried to figure out whats the problem causing this thing. I checked in my Timer job status (Central Administration>Operations>Timer Job Status) and it show that the Solution is tried to deploy on my one WFE and the index server.   I had not found any deployment on my other WFE So I had executed the command stsadm.exe -o execadmsvcjobs manually on the other WFE server. And it works like a charm the solution deployed/retracted successfully.

Also I had tried to check the time of my servers and my CA web application to confirm that they both are on the same time zone sometime this may also create a problem for deploying/retracting the solutions on the servers. In my case they are on the same time zone. To check the time zone for your CA site just

GO TO

Central Administration>Application Management>Web Application General Settings

Select your central administration web application. In Default Time Zone just checks out the time to match with your servers. If it’s not matched then select the appropriate time zone and click OK.

Thanks.

Feedback appreciated.

refrences :

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.sharepointps.com/blog/?tag=/deployment

Posted in Errors, SharePoint Blogs, Uncategorized, Warnings in MOSS | Tagged: , , , | 4 Comments »

An error occurred accessing a data source. An entry has been added to the Windows event log of the server. Log ID:5566

Posted by fillzephyr on May 3, 2009

I tried to open the InfoPath form from the form library as web-browsable form and I fall on to this error:

An error occurred accessing a data source. An entry has been added to the Windows event log of the server.

Log ID: 5566

The cause of this error is the installation of .net 3.5 SP1. So to resolve this error you have to add key to the registry on all of the servers I have 2 WFE and 1 Application server. I had change the registry key on the entire server and restart the servers. The first server I restart is of course WFE on which my CA resides and the other WFE and then Application server. I think it’s always best to change first in Server on which CA resides.

I had followed these steps on all my servers and it works for me:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
  8. Restart the computer.

Reference: http://support.microsoft.com/kb/926642

Posted in Errors, infopath | Tagged: , | 6 Comments »

The server is currently being taken down for maintenance. Check with your system administrator to see when this server is scheduled to come back online.

Posted by fillzephyr on May 3, 2009

I had setup a new farm with 2 WFE and 1 Application server in an x64 production. I had to move a few site collections from a dev environment to prod environment. I had the farm installed with the MOSS SP1. The dev environment is with the latest February cumulative updates. So when I move the site collections it will give me error that the site is not going to be restoring as the prod environment is not up to date to the dev environment and so I run the February cumulative updates. And then restore the site and it went successfully. After few days I got a task of uploading some InfoPath forms and then I got this error.

picture1-1

The reason for this error is that the Server farm is in a Quiescent Condition.  So I gone to the Operations in CA and then under the the Global Configuration there is an option of Quiesce Farm.

Go to Central Administrator->Operations->Global Configuration-> Quiesce Farm

I click on it and I check the farm conditions and it shows me the status as Quiesced.

As shown below:

cg2521

Set the minutes to 3  min and then click reset farm.

After the farm reset I tried to upload the form and it went well for me.

Refrence :  http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/DispForm.aspx?ID=242

Thanks

Posted in Errors, infopath | Tagged: , , | 1 Comment »

Event ID 5586

Posted by fillzephyr on April 17, 2009

ERROR :

Event Type:     Error

Event Source:   Windows SharePoint Services 3

Event Category: Database

Event ID:       5586

Date:           4/16/2009

Time:           3:52:09 PM

User:           N/A

Computer:       MOSSPRD

Description:

Unknown SQL Exception 515 occured. Additional error information from SQL Server is included below.

Cannot insert the value NULL into column ‘permission path’, table ‘tempdb.dbo.#temp_______________________________________________________________________________________________________________000000000657’; column does not allow nulls. INSERT fails.

The statement has been terminated.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp


Resolution :

I was struggling with this error. I had a colleague who had setup the farm with the service account set to SA for the SQL Server.  After the farm is setup the backend SQL server’s cluster got collapsed. The Database team backup and restore the all databases including the config and all other databases. After restoring database the permission of the Service account is set to DBcreator and DBsecurity. Now when I go and try to create the webapplication from central admin and STSADM. I got this error “Unknown Error” , when i check in event viewer in application i see error of event ID 5586. I had Google about these errors but I can’t find any solution on net. When I discussed with my colleague and then gone to the database team to solve this problem. We had checked everything from the database user mail configuration settings and other stuffs it’s all set to be perfect. Still we are getting this error. At the end when we change the Service Account Permission to the SA and try to create to Webapplication, I am able to create it. Also I tried to create a root site collection and it works perfectly fine. I don’t find the perfect reason what’s creating this error but we can create a web app using Service account as SA. Also to add when I check the config and other database it was seen it was under the person’s name owner who had restore the database, but we had make the service account owner for all the databases related to SharePoint.

Any Feedback appreciated. Also anyone know the reason for these error please let me know.

Thanks

Posted in Errors, SharePoint Blogs | Tagged: , , | 1 Comment »

Errors A theme with the name “THEMENAME 1011” and version already exists on the server.

Posted by fillzephyr on February 3, 2009

Got an error when created a new theme and try to apply it to my sharepoint sites then it will give me an error

A theme with the name “THEMENAME 1011” and version  already exists on the server.

Resolution:

Go into SharePoint Designer and open the subsite. Under the _theme folder, delete the folder for the theme you just created.

then open the site it  . GO to site settings> site theme > select your theme.

wholla it will use this theme now!!!

the issues is of Caching.

Thanks

Posted in Errors, SharePoint Blogs | Tagged: , , | 2 Comments »

Event ID 7888, Event ID 5555

Posted by fillzephyr on November 24, 2008

Category : Office server General

Event Id : 7888

 

 

A runtime exception was detected. Details follow.
Message: A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (
http://xxxxxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.


Technical Details:
Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (
http://xxxxxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.RegisterSitesForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.FlushAdds()
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.Add(T objAdd)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.AddRemoveSites(String strFirstChangeToken, SPChangeToken lastChangeToken)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

 

Category: User Profiles

 

Event Id: 5555

 

 

Failure trying to synch web application xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx , contentDB xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Exception message was A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx(http://xxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm –o preparetomove. If this is the cause the stsadm –o preparetomove command can be used with the –oldcontentdb command line option to resolve this issue.

 

stsadm -o sync -ListOldDatabases 0

stsadm -o sync -deleteolddatabases 0

 

Deleted sync information for DB f112b6ea-4589-4859-b81d-26c9962a0ef0

Deleted sync information for DB 97b34344-77b0-405d-b99c-46bf429b8189

Deleted sync information for DB 61bba9f6-0162-4b51-91b5-68fade5edfe6

Deleted sync information for DB 0e95be0c-cb73-4b4e-8f06-03f07d4e09f7

Deleted sync information for DB fdc41cfd-9ad9-463b-86ee-067d09ecdc50

Deleted sync information for DB 02629f3d-26ae-4e8e-b3ac-06940f098a16

Deleted sync information for DB 25aaf049-afb1-42de-b773-1e854e636c62

Deleted sync information for DB 89b6c448-2d11-4121-9f87-282690b24ed0

Deleted sync information for DB 16746235-41f2-4296-ac9c-29123e17e87a

Deleted sync information for DB 518f7fa4-d7e0-4dd5-86ec-2fb4e2673c04

Deleted sync information for DB 6cae50c9-1e82-4699-849c-42def07acc26

Deleted sync information for DB 16413071-01c5-4dbc-9231-4465befaa8f7

Deleted sync information for DB e9b2fc09-a10e-447a-a4a9-4778b6c933d4

Deleted sync information for DB 0f35bc2b-954b-4bcf-9f71-48a2e9baf511

Deleted sync information for DB 333759c8-832d-4365-92cc-5cebc99b0bb1

Deleted sync information for DB 62c953d9-2a5b-4d7f-9ad2-65cef454fa1f

Deleted sync information for DB 76131bfd-c709-4cfc-a7e0-6c6351f2f89b

Deleted sync information for DB 2cb015f1-47e5-41e0-880d-6d1bf1f6c662

Deleted sync information for DB 17749ae9-8f6c-4bf6-9f04-7545ebc03cb1

Deleted sync information for DB 2ed4aa45-849d-4bcf-bee9-7c2d61b8328d

Deleted sync information for DB 09232a6d-7ea1-4e8e-a003-8248b124ca10

Deleted sync information for DB 9558a565-18d6-4426-9c41-964af8d2619b

Deleted sync information for DB 61b0eb8f-46ab-4454-afa5-abe1a4f4dfb9

Deleted sync information for DB 6f50d830-fc75-41b4-b4d3-c164739a79e5

Deleted sync information for DB a89ceb7d-b1c2-4a41-ac28-d9184e0d082d

Deleted sync information for DB bf31d2b7-ac56-4977-a7bd-d91c49095fe0

Posted in Errors, SharePoint Blogs, Warnings in MOSS | Tagged: , | 3 Comments »