Sharepoint 2003 sites migrated to MOSS don't have Visitors, Members, Owners Groups

It's important to MOSS and Office navigation that a sharepoint site has the Members group. Without it the site will not show up under "My Sharepoint Sites" in office packages.

To create these groups:
1) go to People and Groups
2) Settings
3) Choose "Set Up Groups- Set member, visitor, owner groups for this site"

Personalizing your pages with Google Widgets

I needed to change my homepage from igoogle to my Sharepoint team site. :( But there's one widget I really needed...my family calendar. So I added it to my personal view of my team site.

Here's how to do it:

Grab the link for the widget you'd like to use

Click "about this gadget"

Then on the right side click "view source"

click "get code" button

Now go back to your sharepoint page...

When on the site, click the drop down menu next to your name on the top right. Then choose "Personalize this page"

Add the "Content editor web part"

Edit the webpart and click "source editor" button

Paste in link gathered from google gadget

More Google Gadgets: http://www.google.com/ig/directory?num=24&synd=open

You're all set.

Managing "My Sites"

First add your Farm Admin Account as a site collection admin to the My site you need to manage:

http://servername:port/_admin/owners.aspx?

Click Shares Services
User Profiles and properties
View User Profiles
Select down arrow for account you want to manage

"Edit" allows you to change their profile information(ie picture)
choose "Manage Personal Site"

"The search request was unable to connect to the Search Service." message when searching

For server farm with seperate index server
1)In CA stop both searches Office SharePoint Server Search Windows SharePoint Services Search
2)On application/index server stop Windows SharePoint Services Timer Service
3) Clear sharepoint cache (directions in another post)
4) Restart Timer Service
5) Start Windows SharePoint Services Search in CA
6) Office SharePoint Server Search

Note: Query and Indexing
Check Use this server for indexing content
Use this server for serving search queries

How to Change a User's My Site Profile Picture

Reference: http://www.dlocc.com/component/fireboard/?func=view&catid=15&id=9

Goto your MOSS Central Administration Site
Click on Shared Services Administrations: SharedService1 (yours may be named differently)
Click on User Profiles and Properties
Click View User Profiles
Locate the account name you wish to edit
Hover over the name and select Edit in the dropdown
Swap the Picture URL for the one pointing to the image you would like as the avatar.

Failure trying to synch site... Event ID 5553 & 7888

These two event errors showed up this morning. It was due to moving a site between web applications. It seems the site keeps record of its GUID, so if you move it to another web application that shoud have a seperate GUID it creates a conflict when it attempts to sync. I was lucky because I knew which application it had to be.

To fix it I did the following:
Detach Content Database. This will not delete your database only break the association.
stsadm -o preparetomove -contentdb SQLserver:DB_NAME -site http://websitestsadm -o deletecontentdb -url http://website -databaseserver SQLserver -databasename

DB_NAMEReattach Content Database.stsadm -o addcontentdb -url http://website -databasename DB_NAME -databaseserver SQLserver

Further info can be found at: http://monthlymoss.blogspot.com/2007/11/here-is-issue-that-i-came-across-that.html

Lesson learned: Never move a site between web applications on the same farm w/o doing a preparetomove command.

Login Failed for User 'SQL service account'.

An object of the type Microsoft.SharePoint.Administration.SPWebApplicationProvisioningJobDefinition named "Provisioning...

Fix: Go into Timer Job definitions, then find a job definition called Provisioning or Unprovisioning Web Application (it will have your web app name in brackets) and delete it. You should then be able to save the Authentication Provider settings.

Clearing MOSS Config Cache

This can be really helpful if you're having any isues with timer jobs stalling or services not starting. Do this at your own risk and during non-production hours. This is one of those procedures you don't do if you're having any issues with your timer service.

1. Reset timer service (This is just to make sure that it's working okay)

• Click Start, point to Administrative Tools, and then click Services.
  
• Right-click Windows SharePoint Services Timer, and then click Stop.
  
• Close the Services console.
  Everything ok?
  

2. Go to: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID

3. Open guid

4. Back up the Cache.ini file.

5. Open cache.ini with notepad

6. Set number to "1" then save

7. Then delete all xml files making sure to exclude cache.ini

8. Then reset windows sharepoint timer service.

You'll notice that soon after the service reset that the xml files will start to reappear and the number that was originally in the cache.ini file will return.

Trouble publishing Infopath Form to Browser...

When you attempt to publish your Infopath form to the browser you get the following message and the "Enable this form to be filled out by using a browser" button is greyed out.

"The server is running infopath forms services, but the compatibility setting for this form template is infopath only"

You must set the forms compatibility settings in Infopath in order to publish to the browser.

Setting browser-compatibility up front

When you first open the InfoPath client application you are presented with the Design a Form Template dialog box. You can check the Enable browser-compatible features only checkbox to make a form template browser-compatible.

What this means is that the InfoPath designer will only present you with those features of InfoPath that are supported in both the InfoPath editor as well as the browser.

Setting browser-compatibility afterwards

You can set browser-compatibility after you have designed your form template by going to the Tools menu, and selecting the Form Options menu item to open the Form Options dialog box, and then clicking on the Compatibility category.

Thanks Charlotte Price and Martha Davis.

Error Opening New InfoPath form in MOSS...

When attempting to open a new infopath form in a forms library on sharepoint, you receive the following error message:

The document could not be created. The required application may not be installed properly, or the template for this document library cannot be opened...

Fix:
Open infopath,Click Help/Office Diagnostics

Submitted by Brad Palmer

Solution Stuck Deploying

When going to deploy a soluting the soluction gets stuck saying "Deploying". You can go the the Timer Job definitions and delete the one associated with the stuck deployment.