Tuesday, September 30, 2008

Event ID 6482,7076,6398,27745

For past few days I have noticed errors in my event logs on the MOSS server. The errors were related to event ids 6482,7076,6398,27745. The description was:

Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: General Event ID: 27745Date: 30/09/2008Time: 3:23:52 AMUser: N/AComputer: AUYXUAP310WBC32Description:The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on SharePointSQLServer_Dev. Check the database connection information and make sure that the database server is running..

Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: Timer Event ID: 6398Date: 30/09/2008Time: 3:23:52 AMUser: N/AComputer: AUYXUAP310WBC32Description:The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 4dbd717a-6f8a-4595-8d03-6e21a6551257) threw an exception. More information is included below.
Not enough storage is available to complete this operation.

And similar errors regarding insufficient memory. There are many other suggestions on web but the one that fixed the errors for me was:

-For errors related to Event IDs 6482,7076,6398, I have to install hotfix 923028 available here:http://support.microsoft.com/kb/923028

-For error related to Event ID 27745, I have to stop and start the Windows SharePoint Services Timer service with following command:

net stop “Windows SharePoint Services Timer”
net start “Windows SharePoint Services Timer”

Saturday, September 27, 2008

Error When starting Windows SharePoint Search service

Last week I got stuck with few errors when starting WSS Search Service. Below are few errors that were thrown:



Error1:
Event ID: 10036
A database error occurred.
Source: Microsoft OLE DB Provider for SQL Server
Code: 6 occurred 1 time(s)
Description: [DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found.

Error2:
Error Description: Could not access the Search service configuration database.


Few tips to avoid this kind of error:


  • Make sure the search service account has got DBCreator role on DB server. You can remove this role once the service is started.

  • Offcourse your normal Farm Admin service account also needs DbCreator and SecurityAdmin role.

  • I have read someone saying to use Named Pipes for remote connection. But this is not true it should work with TCP/IP connection as well. So in your SQL server make sure that your remote connection is enabled for either TCP/IP or Named Pipes or for both.

  • Make sure the DB Server name in your connection string is consistent in your farm for all other webapps, admin content config database etc etc..

  • Finally the solution that worked for me was that I was using "DB server name\Instance, port" as the connection string and this format of connection string uses Named Pipes. Unfortunately Named Pipes was disabled so I have to use an Alias of the DB server to use the TCP/IP connection. Also once the alias is setup for you by the DBA's you have to set it up on the MOSS server under SQL Server Client Configuration settings. You can also use server name if you are using default instance for TCP/IP.

I hope that makes sense. If anybody has any more suggestions or corrections to my suggestions then please do leave a comment.

Cheers,

Kunal

SharePoint Capacity Planning Tool

Not sure if some of you have already come across this tool. So instead of reading the whole capacity-planning documentation, you can get a rough idea of your hardware needs and farm topology design. Just enter information such as the number of users, locations, bandwidth and network topology, preferred hardware, and usage profiles. After you provide the tool with basic information about your organization, the tool provides a first approximation of the topology your organization needs.

Good tool for infrastructre guys!

Download Here or follow the link:

http://www.microsoft.com/downloadS/details.aspx?familyid=DBEE0227-D4F7-48F8-85F0-E71493B2FD87&displaylang=en

Sunday, September 14, 2008

Create Databases before deploying MOSS

In many organizatons there are certain policies and procedures where only DBA's can create databases. Now when installing MOSS 2007, the install creates the databases automatically that means they need to give the service account permissions to create database on DB server. This kind of breaks the organizational policy. Do you agree guys? No? Yes? Anyways these are the policies set by organization and we have to abide by them. So what do we do in these situations? Luckily there is a procedure where we can deploy MOSS using DBA-created databases. TechNet provides us with steps where DBA's can create databases on DB servers and Farm Administrators can configure them separately. Have a look at this TechNet article:

http://technet.microsoft.com/en-us/library/cc262869.aspx