Monday, November 22, 2010

Timeout expired. The timeout period elapsed prior to completion of operation or the server is not responding

Last weekend our SQL servers are rebooted. This had the instance of NW2007 configuration DB. on mondya morning  the Pending Tasks and the New Tasks are not able to be viewed by the concerned approvers. When approvers clicking on the Tasks they are getting unexpected error. In the event viewer it says "Cannot find a corresponding human workflow task id for this task".

Event Type: Error

Event Source: Windows SharePoint Services 3
Event Category: None
Event ID: 0
Date: 11/22/2010
Time: 9:41:40 AM
User: N/A
Computer: COMPUTERNAME
Description:
Nintex Workflow; Build: 11100 (http://DOMAINNAME/_layouts/NintexWorkflow/ApproveReject.aspx?List=27d20a40-c30f-4a8c-978d-f9a1d772f02f&ID=937&Source=http://DOMAINNAME/AllItems.aspx)
Cannot find a corresponding human workflow task id for this task.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
Then we disabled custom error mode to get the detailed error message. Below is the error page information.
 

It seems like the connection between the Web front ends and the Databases of the Nintex workflow DB is missing.

Nintex suggested to check the connection settings between Web Front End and the server runnning the Nintex Workflow DB. We did the following things to get the issue reolved.
 
a) Go to SharePoint Central Administratioin --> Application Management
b) Under the Nintex Workflow Management click on "Database setup".
c) EDIT the Configuration Database that is already setup.
d) Following are the settings that has already setup
   Database Server, Database Name, ("Connect to an exisiting Database" checked)Database Authentication
   is "Windows Authentication".
e) Clicked on "Ok" at the end of the page.
 
That's it. The magic is it reset the connection between the Web Front End and the Server connecting the Nintex Worklfow database.
Everything is working fine now.
Thanks to the Nintex support for asking to check the connectivity.

Saturday, August 28, 2010

How do i change the Host File Information

In Windows XP the host file information is setup in the following path by default
c:\windows\system32\drivers\etc\host

You can edit this file using the note pad and can give the IP names and the host header information there so that it redirects you to the remote sites that are hosted by the servers.

for instance i had the following requirement
156.81.248.28 http://testwip.mycompany.pvt/

If you add this host information in your host file it will redirect you to that location.

Friday, March 5, 2010

A required previlige is not held by the client

The remote shutdown option is always safer option to restart the server. This is ideal option when the server is virtual because when you restart the server from the server itself some times server fails to start up.

Syntax: shutdown -r -f -m MachineName

r - restart
f - force
m - machine

But sometimesThe remote shutdown cannot run sometime due to lack of previliges. We can check the following things
Start --> Run gpedit.msc
Go to
Computer Configuration --> Windows Settings--> Security Settings --> Local Policies --> User Rights Assignment
Double Click on "Shut Down the System"

Check if the following groups are listed

Administrators
Backup Operators
Power Users
Users

If any of them are missing, add them.

Monday, March 1, 2010

Server Out Of Memory

Server Out of Memory

There is no memory on the server to run your program. Please contact your administrator with this problem.

I have got the above exception when trying to downlaod a large flash file to local drive.which is about 198 MB. After following some blogs and IISRESET on the server caused to get rid of the exception.

Start --> Run --> IISRESET

I believe IISRESET causes to clean up the temporary file storage and also cleans up the application pool which get rids of the Out Of Memory exception and also the server that we had has POC server which is very old.

Please feel free to comment on this post so that i can update this post effectively.

Cheers,

Vinay.

Thursday, February 4, 2010

There are no page layout files available in the master page library of the top-level site. Add one or more page layouts to this library before you create a page or set page properties

I created the blank site and activated the publishing features. After this i have migrated the content frm one site to other site using SharePoint content Deployment wizard tool. Then tried to create the page. Here is the error i got when i ctried to create page.

There are no page layout files available in the master page library of the top-level site. Add one or more page layouts to this library before you create a page or set page properties.

Below are the steps i followed
1) Navigate to the master page gallery (Site Actions --> Site Settings --> Modify All Site Settings)
2) Under the galleries section go to "Master pages and page layouts".
3) In the "Master Pages abd page layouts" library click on "document Library settings"
4) Then go to "Advanced settings".
5) Here go to "Allow management of content types" is equal to "Yes".
6) Then "document library settings" page under the "content types" section click "change new button order and default content type".
7) Check the first two and modify the order. Then click Ok.

That fixed this issue. Will be updating the reasons for this error in next post.

Please post your ideas.

Friday, December 4, 2009

Task 'SharePoint' reported error (0x8000FFFF): 'An error occured in the outlook or SharePoint. Contact the SharePoint site Administrator. HTTP 415'

When synchronizing the SharePoint calendar to the to the outlook i am getting "Send/Receive Error" in the Outlook

Task 'SharePoint' reported error (0x8000FFFF): 'An error occured in the outlook or SharePoint. Contact the SharePoint site Administrator. HTTP 415'

Possible Reasons:
1) While synchronizing the SharePoint calendar to the outlook it may have failed to sync the permissions.

Steps that possibly reslove this issue:

Note: Make sure that Outlook 2007 is installed in the local machine

1)Try stop and start the event notification and try synchronzing the SharePoint
Calendar to the outlook again.
- to stop the event notification, from the command prompt type 'net stop sens'.
- to start the event notification, from the command prompt type 'net start sens'.

2) If the above option does not work then try the other approach below:
- From the outlook, Go to Tools ---> Account Settings ---> SharePoint Lists
and remove all the items from that. Then try synchronizing the SharePoint
Calendar again.

Saturday, November 21, 2009

The search service is currently offline. visit services on the server page in sharepoint central administration to verify whether the service......

ISSUE:

The search service is currently offline. visit the services on server page in sharepoint central administration to verify whether the service is enabled. this might also be because an indexer move is in progress.

Reasons: there might be couple of reasons
1) Index file is corrupted. The index file is generally located at d:\Program Files\Microsoft Office
Servers\12.0\Data\Office\Server\Applications.
2) Your account that is used for search might not have access to the content source.
3) Your indexer might be in move as stated in the error message.

Here are some of the error messages that i have seen in the event viewer.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6483
Date: 11/12/2009
Time: 10:43:2009
User: N/A
Computer: SERVERNAME
Description:
Application synchronization failed for Microsoft.Office.Server.Search.Administration.SearchService

Reason: Cannot open database "Sharedservices1_Search_DB_36fea12f-9bf5-4286-81c8-942e5509bf57" requested by the login. The login failed.

Login failed for the user "SEARCH SERVICE ACCOUNT"

Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10030
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Error importing registry hive from the configuration database and into the registry.

Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'

Details:
Access is denied. (0x80070005)

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

Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10046
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
The database connection string is not available.

Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10032
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Could not create a database session.

Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'

Here are the steps i followed to fix the search issue:

1) Stop the Office SharePoint search through "Central Adminsitration"
- From Central Administration go to Operations --> Services running on the server. Then
look for the "Office SharePoint Server Search". Then click on "stop".
2) This de-configures the search service and deletes all the indexed content permanently.
Note: when click on "stop" you might be getting a warning message asking "Are you sure you
want to uninstall the Office SharePoint Server Search from this server?"
Click on "Ok"
3) Now click on "start"
Note: in the "Service Account"(used for search service) section make sure that account has
access to the search data-base.
4) Then click "Shared Services Administration" hover over the failing SSP and select edit.
5) Now you will notice that the indexer is not configured for this Shared ServiceProvider. Select
it from drop-down.
Note: If you are using stand alone server the only the server name will be appearing in the
dropdown.
6) In the "SSP Service Credentials Section" make sure that the account has access to the Search
data-base.
7) Here is the important part. The index server you have selected is probably that you have
used before. If it is, go to the server and locate the indexer files. It is in the text box right
below the dropdown you just used. The path of the index file is written at beginning.
8) In there you will find a folder with GUID name. At the end of the folder add "_Old".
9) Now go back to SSP settings and click "Ok". Wait for one minute the indexer will create the
new GUID folder.
10) Now start the full crawl from the Shared Services Search Administartion,

Conclusion: In this case the service account that is used for search does not have access to the Search data-base. The service account will be given at Shared Services "SSP Credentials" section. And the indexer file is corrupted, By following all the above ten steps i got the Search issue fixed. Hope this post might help to others who have similar/same issue.

References:
http://vspug.com/jasonmedero/2008/09/15/moss-2007-error-when-moving-indexing-role-the-search-service-is-currently-offline-visit-the-services-on-server-page/

http://social.technet.microsoft.com/Forums/en/sharepointsearch/thread/22af594f-10d7-4672-b1f9-472f9aebd3f6

http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/02/24/the-search-service-is-currently-offline-visit-the-services-on-server-page-in-sharepoint-central-administration-to-verify-whether-the-service-is-enabled-this-might-also-be-because-an-indexer-move-is-in-progress.aspx