Issue: Error message when you install an InfoPath 2007 Client Form Template (i.e. a non browser-enabled form) on a Windows Vista or higher computer: “Cannot create InfoPath.ExternalApplication object. Error code = 0×80080005”
Resolution: To work around this issue simply:
Issue: “A runtime exception was detected. Details follow. Message: Access Denied! Only site admin can access Data Source object from user profile DB.”
Resolution: Grant the search account access to the SP2007 user profile store
Question: How to find all ContentByQuery web parts for a Farm?
Answer:
If you add a web part to a page and it wasn’t written correctly you may experience an issue where the whole page doesn’t load.
When this happens, the simplest way to solve the issue is to perform the following steps:
If you’re ever working with a site that just won’t load and you don’t know it’s structure, you can (if it isn’t severely busted) still attempt to access other pages by manually navigating to the “View All Site Content” page, by adding _layouts/viewlsts.aspx to the end of the site URL.
E.g. http://intranet/_layouts/viewlsts.aspx
If you still have troubles with the site, then you can attempt to navigate to the site settings page and modify the settings that might be causing the issue by adding _layouts/viewlsts.aspx to the end of the site URL:
E.g. http://intranet/_layouts/settings.aspx
Have you ever wanted to remove the annoying “Powered by InfoPath” logo that users see when accessing InfoPath forms in the browser?
The good news is that this is pretty straightforward. Just follow these simple steps:
Enjoy!
On SharePoint 2007 every now and then you may have a need to delete the SSP so that you can then recreate it.
The trouble is that deleting it through the UI isn’t very reliable. However, it is reasonably straightforward to do so using stsadm, using the following command line syntax: stsadm -o deletessp -title “[SSP Title]” -force -deletedatabases
For example: stsadm -o deletessp -title “SSP01″ -force -deletedatabases
As a best practice, SharePoint should be installed using a SQL alias.
Think of a SQL alias like a DNS record, but also being able to refer to a specific SQL instance name.
If you need to upgrade database servers in the future, you will usually be keeping the existing DB server in place, and creating a separate DB server environment (e.g. SQL 2005 vs SQL 2008). If you had your SharePoint installation configured with the server name details of the SQL 2005 environment, then now you have to undertake a long and arduous process to move to 2008.
If you configured the environment with a SQL alias – then you can just go and update the alias on each of the SharePoint servers to point at the new SQL 2008 environment. Much simpler!!
Note: When installing SharePoint with a SQL alias, you need to make sure that you set up the alias on EACH and EVERY SharePoint server. Miss one and the box won’t be able to connect to the required database server(s).
The command to bring up the SQL Alias Client Config Utility is: cliconfg
Issue: Can’t change VM settings (e.g. memory, add another disk) in VPC
Cause: The machine may be closed and in saved state, but it needs to be fully shut down to add more memory or another disk.
Resolution: Shut down the machine completely, then attempt to change the settings again.