Office SharePoint Server Publishing Infrastructure – Access Denied

Failed to provision the scheduling job definitions. Page scheduling will not succeed.
office sharepoint server publishing infrastructure – Access Denied

If you see the above errors while Activating the Office SharePoint Server Publishing Infrastructure either in the application event log or the web page respectively, then the solution is to elevate the permissions for the application pool corresponding to that web application. As a short cut solution, just change the App Pool for the web application to point to the Central Admin’s App Pool which has enough rights/permissions. After IISRESET, Acticate the Publishing Infrastructure feature and then revert back the web application app pool to its original pool. This solution is from this blog post.

Excel Services Charts, Spreadsheets & Worksheets in SharePoint – Issues

You do not have permissions to open this file on excel services.

Make sure that the file is in an Excel Services trusted location and that you have access to the file.

If you are troubled with the above errors in SharePoint while publishing and viewing the excel services forms in browser then I believe you are in the right place. I am not sure if my guidelines will solve your problem but at least it solved my issues.

1. In central admin site, in operations page, under services in the server farm enable the Excel Services.
2. Open up the Shared Services Admin site. Under “Excel Services settings” section, open the ‘Edit Excel Services settings ‘. Set the File Access Method to Process Account. In the same page under the ‘External Data’ section assign the appropriate user.
3. Back to SSP Admin site. Open the “Excel Services Trusted File Locations”. Give the URL Address of the location where you publish your excel workbooks. Potentially this will be the document library of type excel services. If it’s a document library make sure not to put the complete URL i.e DON’T PUT something like http://server:5050/doclibraryname/Forms/AllItems.aspx, instead put it like http://server:5050/doclibraryname. In my case this is the main reason which showed the above error. If I use full URL I get those errors and no site mentions this after spending hours searching on google.
4. In the same page under the ‘External Data’ select the Trusted data connection libraries and embedded or just the Trusted data connection libraries.

Domain User Account Not Found or Invalid Password Problem

While I was trying to setup MOSS 2007 on a single server box I had this problem of Invalid Password or User Account not found problem when I try to start the Windows SharePoint Search Service.

I have a user account something like: aifsmoss\searchspccontentaccessusr which I was trying to use while setting up the WSS search service using the Central Administration. Even though I give the correct user name and password it shoots back saying invalid password or account. After a couple of days of troubleshooting I was able to figure out that in the Active Directory, in the user account properties the pre-windows 2000 account name is truncated and it looks something like: aifsmoss\searchspccontentacce

so basically the length of the user account name is the problem and it is truncated. I created another user account and it worked just fine.

Below is the screen shot of the user account properties.

Shared Service Provider Setup Issues

Provisioning failed: Windows NT user or group domain\username not found. Check the name again.

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.

If you are seeing the above errors while setting up Shared Service Provider and or with Search Settingsand looking for a solution you are in the right place. I had similar problems setting up a single server sharepoint 2007 server. I found the below steps from here. Below I am reproducing the same steps with a minor correction in step# 8.

1. In the Component Services snap-in, expand Computers, expand My Computer, and double-click DCOM Config.
2. Locate application OSearch.
3. Right-click the program name, and then select Properties.
4. On the Security tab, in the Launch and Activation Permissions group box, select Customize, and then click Edit.
5. Add the user Network Services and grant permissions Local Launch and Local Activation.
6. Restart the computer.
7. Go to Central Administration. Under Application management, go to Manage Search Service under Search column. There, under the “Query and Index Servers” group, click on the Search Service(Clickable link).
8. Fill all necessary details. Select PREDEFINED option for “Select an account for this component” field and select Network Service in the following list box. This page clearly mentions not to use Network Service or any other inbuilt accounts. So give the domain\username which it says it didnt found in the above error. It works fine.
9. Perform iisreset command.
10. Check if SSP is working now.