Changes to the content source cannot be made while it is not idle. Wait for the current action to complete and retry your changes.
If you receive this error make sure you are not crawling anything. Simple, yes, but I spent a few minutes trying to figure out what was going on.
I was seeing this error when trying to create new email address for a Document Library.
When setting up email in SharePoint, make sure your Application Pool account, Timer account, and the account you are using for mail access are all the same.
After updating this, the Server was unable to process request. —> Access is denied. error went away.
In Windows Server 20008 the Application Pools are located here:
Server Manager –> Roles –> Web Server (IIS) –> Internet Information Services
Under the Connections section click on Application Pools
On the right side of the screen you will see Actions. From there click on Advanced Settings…
The value in the Identity field is the same account we use for the Timer Service and the account that has access to Active Directory.
How to check or update the Windows SharePoint Services Timer:
Open Server Manager, in Windows Server 2008 this can be found in the Start Menu (start button) or type Server Manager in the search box in the Start Menu. Once you have this open click on Configuration –> Services then locate Windows SharePoint Services Timer.
From there right click on Windows SharePoint Services Timer and select Properties. Now, click on the Log On tab. The account listed should also be the same as the account you were using in the Application Pool.
Let me know if you have any questions.
I used the following site to configure a dedicated front end server for crawling:
http://technet.microsoft.com/en-us/library/cc261810.aspx
In doing this, the only issue I ran into was this error:
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.
My issue was related to the existing server having a file index location of C:\Index.
Central Administration > Application Management > Manage this Farm’s Shared Services > New Shared Services Provider
Once I created a folder in the same location, on the new server, the error went away.
Only thing I can imagine is SharePoint wanted to move the index from the old server to the new server. SharePoint being SharePoint, it wanted the index folder in the same exact location.
Update:
If you are moving to Windows Server 2008 make sure you read this KB article.
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.(The item was deleted because it was either not found or the crawler was denied access to it.)”
http://support.microsoft.com/kb/896861
I will continue to update this list…
1. Check your new Farm for blocked file types.
Central Administration > Operations > Blocked File Types
2. InfoPath forms. Make sure you check that your forms are working in the new Farm. In my case, the forms had the old URL and wouldn’t work. I had to also update / relink the forms to their corresponding library.
3. PDF icon
http://support.microsoft.com/kb/837849
4. When we created the new Farm we also used all new AD accounts. When I tried to crawl our network I was only able to crawl public folders. Fix? Replace the old crawl account on the domain with the new account or update your new Farm with the old crawl account.
Shared Services Administration: SSP1 > Search Administration > Default content access account
5. BDC. This has turned out to be a big one. I wasn’t able to simply export the BDC definition files from the old Farm and import them into the new Farm. I had to recreate all the BDC files, security, and update all the pages that were using the BDC data. If you are not using BDC Metaman, you need to start!
6. If you are moving to Windows Server 2008 make sure you read this KB article.
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.(The item was deleted because it was either not found or the crawler was denied access to it.)”
http://support.microsoft.com/kb/896861
7. Search Scopes, none, zero, nothing was moved over when we migrated. i’m now in the process of trying to recreate all the search scopes.
8. reapply the Adobe PDF filter to the Farm. This post goes into great detail on how to apply the update.
http://bloggingabout.net/blogs/harold/archive/2008/10/02/index-pdf-documents-on-sharepoint-using-adobe-pdf-ifilter-9.aspx
After our farm migration, we realized that our new domain name and InfoPath didn’t get along. Our old domain name was a simple http://intranet and all the InfoPath Forms were linked to that name. After being asked to re-link several thousand forms (clicking one at a time) I started looking around the web for a solution.
Here is what I found:
1) Open the library. Click Settings –> Form Library Settings –> Relink documents to this Library. Now copy the URL in your address bar.
2) Open this page in SharePoint Designer. File –> Open –> paste the URL in the File name: field and click Open.
3) If you don’t see the split screen layout, complete the following steps. Click on View –> Page –> Split
4) Locate the <FORM> tag within the HTML section of the page and place the following code before the </FORM> tag.
<script type=”text/javascript” language=”javascript”>
function CheckAll(chk)
{
for (i = 0; i < chk.length; i++)
chk[i].checked = true ;
}
</script>
<input type=”button” value=”Check All” onclick=”CheckAll(document.forms.aspnetForm.chkRepair)” >
5) Save, Refresh the page, you should now see a Check All button in the bottom left corner of the page.
Here is what my HTML looks like:
<FORM id=”SubmitRepairDocsForm” method=”POST” action=””>
<INPUT id=”SubmitRepairRedirectList” type=”hidden” name=”SubmitRepairRedirectList” />
<INPUT id=”SubmitRepairRedirectFolder” type=”hidden” name=”SubmitRepairRedirectFolder” />
<INPUT id=”SubmitRepairDocs” type=”hidden” name=”SubmitRepairDocs” />
<SharePoint:FormDigest runat=server ForceRender=”true”/>
<script type=”text/javascript” language=”javascript”>
function CheckAll(chk)
{
for (i = 0; i < chk.length; i++)
chk[i].checked = true ;
}
</script>
<input type=”button” value=”Check All” onclick=”CheckAll(document.aspnetForm.chkRepair)” >
</FORM>
Edit…
If you want to speed up this process, you can also edit the RowLimit property.
Search in the code for RowLimit, by default it’s set to 100, change it to 500.
RowLimit Paged=”TRUE”>500<
An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.
Central Administration > Operations > Timer Job Definitions
Scheduled Approval
Scheduled Page Review
Scheduled Unpublish
Variations Propagate Page Job Definition
Variations Propagate Site Job Definition
First, make sure you have the Office SharePoint Server Publishing Feature enabled.
Home > Site Settings > Site Features
Second, if the Feature is enabled, try to Deactivate then Activate. This should install the Time Jobs in Central Admin.
The My Site of [user name] is scheduled for deletion. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL: http://mysite.sharepointed.com/personal/User_Name
After a manger forwarded me this email, I realized we had a configuration problem in our environment.
The problem was we had our LDAP Active Directory (AD) import configured to import all users regardless of their status. So, when the user was deleted from AD the manager received the email and was unable to see the My Site.
To fix the problem I updated the LDAP Search Filter to:
(&(objectCategory=person)(objectClass=user)( !(userAccountControl:1.2.840.113556.1.4.803:=2)))
Now the import will only grab active users from AD. This is allows plenty of time for the manager to look that users My Site before it is deleted.
In my case, we disable users in AD then sixty days later they are deleted from AD. Once deleted from AD the My Site will be deleted from SharePoint following the next FULL import of user profiles.
Where do I edit the LDAP Search Filter?
Here:
Shared Services Administration: [Your SSP Name] > User Profile and Properties > Manage Connections
When trying to access the Shared Service Provider (SSP) I received the following generic error:
An unexpected error has occurred.
Yes, the detail is overwhelming and pointed me directly at the problem.
To allow the .aspx page to show the detail behind the error I had to make a small change to the web.config file. In my case the web.config file in question was located in the following location:
C:\Inetpub\wwwroot\wss\VirtualDirectories\7788
How did I know where this was located? If you are in Central Administration and hover over the name of your SSP with your mouse, you should see the path at the bottom of the browser windows. If not, right click and select Copy Shortcut and paste it into notepad.
Example:
The 7788 pointed me to the folder that contained the web.config I needed to edit.
Once you have located the needed web.config file make a copy of it. Open the original web.config file and make these two changes.
<SafeMode CallStack=”true“>
<customErrors mode=”Off” />
Save the file.
The page should now show you what is wrong with the file. In my case, there were a ton of “?” all over my web.config. How they got there I will never know.
I was working in a Document Library and the View was missing the New button to allow for folder creation.
Simple fix.
Site Actions > Edit Page > (the web part you want to fix) click edit > Modify Shared Web Part
In the Web Part properties window click on Edit the current view
Now scroll down to until you see Folders.
Select Show items inside folders in Folders or Flat:
Done.
When trying to create a workflow using Internet Explorer I received the following message:
| 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. |
| Click Try Again to attempt to load the form again. If this error persists, contact the support team for the Web site.
Click Close to exit this message. |
This error was then followed up by another error:
This form has been closed.
We have InfoPath forms installed with workflows that have worked seamlessly, sooooo, I was a little perplexed when i started getting this error.
Answer:
stsadm.exe -o unquiescefarm
I tried doing the same thing using Central Admin. with no luck
Central Administration > Operations > Quiesce Farm