Thanks to Dink at Sharepointu.com for this solution:

You can actually achieve this through a simple workflow in SharePoint Designer using a custom list in your SharePoint site.

In your site, create a custom list called “Emails” and add in two columns:

First column called “Body” – type “Multiple lines of text” (this will contain the actually “body” of the email).

Second column called “Date” – type “Date and Time” (this will be used to hold the next date/time the email will be sent).

Additionally, enable versions on the list – choose “Create a version each time you edit an item in this list” (this will be used for tracking how many times the email is sent and serves as a “confirmation” that the workflow did run).

*Additionally, if it doesn’t already exist, create a new group in the site that you will add in all the users who need to receive the monthly email (permissions for this is not important so you can use an existing site group if it already has the users you need).

In SPD, connect to your site and create a new Workflow “File > New > Workflow” called “Email Users” and attach it to the “Emails” list:
Set it to both:
“Automatically start this workflow when a new item is created” and
“Automatically start this workflow whenever an item is changed”.

At first glance, you may be thinking that setting it this way will cause an infinate loop, and you’d be correct – this is intentional.

Click next to create the Workflow steps.

We only need one step so name it “Send Message”.

**In any of the following steps, if you do not see the specified Action listed when you click the “Actions” button, select the “More Actions” option from the bottom of the list to bring up a complete list of all the actions available where you can now find the Action specified.**

Click “Actions” and choose “Pause Until Date”.
Click “this time”, click the “fx” button, then choose “Current Item” and “Date” for the “Source” and “Field” dropdowns, then click “OK”.

Click “Actions” and choose “Send an Email”.
Click “this message”.
Click the address book icon in the “To” field then scroll through the list of site groups to find the *group that your users belong to (this will be the list of users that need to receive the email), select the group then click “Add>>” then “OK”.
Click the “fx” button in the “Subject” field and choose “Current Item” and “Title” in the “Source” and “Field” dropdowns, then click “OK”.
Click the “Add Lookup to Body” button and choose “Current Item” and “Body” for the “Source” and “Field” dropdowns, then click “OK”.
Optionally, you can now add any additional text to the body of the email message by placing your cursor before or after the “[%Emails:Body%]” lookup and type in whatever you want.
Once completed, click “OK”.

Click “Actions” and choose “Add Time to Date”.
Click on “0″ and change it to “1″.
Click on “minutes” and change it to “months”.
Click on”date”, click the “fx” button, then choose “Current Item” and “Date” from the “Source” and “Field” dropdowns, then click “OK”.
Leave the “(Output to “Variable: date)” part as is.

Click “Actions” and choose “Update List Item”.
Click “this list”.
Choose “Current Item” in the “List” dropdown.
Click “Add” and choose “Date” from the “Set this field” dropdown, then click the “fx” button.
Choose “Workflow Data” and “Variable: date” for the “Source” and “Field” dropdowns, then click “OK”.
Click “OK” again, then one more time to close the “Update List Item” screen.

Your workflow should now appear as:

Pause until Emails:Date
then email [Your Group Name Here]
then Add 1 months to Emails:Date (Output to Variable: date)
then Update item in Emails

Click the “Check Workflow” button to verify there are no errors in the Workflow (confirmation box will open – click “OK” to close it), then click the “Finish” button to build the workflow and associate (attach) it to the “Emails” list.

Back on your site, go to the “Emails” list and create a new item.
Give it the “Reminder to Submit Expense Forms” title (or whatever you require) and add to the body the message you want then to read. Choose the next “11th” as the date (obviously the current month if its before the 11th, or the following month if its currently after the 11th), then click “OK” to add the item.

What’s going to happen is that as soon as the item is added to the list, the workflow will start. If the date listed (in the item) is in the future, it will pause until that date, then when the date is reached, it will send out an email to each member of the group with the details of the item as the email (title will be email title – body will be email body). Once it has emailed the message out, the workflow will then add 1 month (not 30 days, but one calendar month) then update the “date” field in the item on the list to reflect this new date. Since we’ve now “modified” the list item, this will again fire off the workflow which has the first step of pausing until the date listed in the item – which is now one month in the future (and will always be on the 11th).

You can now also look through the version history of the item to see an etry of each time the email had been sent (indicated by a new version being listed for each time).

More From pstilgoe

• Import data from CSV and SQL to a SharePoint list
• Creating filtered views in Sharepoint
• Using Sharepoint meeting workspaces with Outlook 2003 / 2007

Ask pstilgoe To Recommend Your Posts

No more fumbling with My Computer or Windows Explorer, wishing you could print information about all your files. Karen’s Directory Printer can print the name of every file on a drive, along with the file’s size, date and time of last modification, and attributes (Read-Only, Hidden, System and Archive)! And now, the list of files can be sorted by name, size, date created, date last modified, or date of last access.

Directory Printer

More From pstilgoe

• How to add Blackberry support for MOSS 2007 & Infopath Forms
• How to delete the Shared Service Provider in MOSS 2007
• How to configure Kerberos for SharePoint / MOSS 2007

Ask pstilgoe To Recommend Your Posts

There seems to be a bug in MOSS 2007 which when grouping by a calculated column in a view you get the following error in your list: <!– #RENDER FAILED –>

So I have created two columns to capture someones first name & lastname, I have then created a calculated column called Fullname =(FirstName & ” ” & LastName).

When you try to group the list by full name you get the error
<!– #RENDER FAILED –> displaying in your list columns.

Not ideal but as a workaround in the short term if you set the group to display expanded the list displays correctly. Hopefully MS will fix this via hotfix or in the next service pack.

More From pstilgoe

• Sharepoint and JQuery
• How to easily move / copy list items from one sharepoint list to another
• Converting a Sharepoint List into XML

Ask pstilgoe To Recommend Your Posts

You have a SharePoint list that contains a date column, you want to create a view that groups all the items by the dates month only.

To do this create a ‘Calculated Column’ and use the following formula:

=TEXT(Date,”yyyy – “)&TEXT(Date,”mm”)&TEXT(Date,” (mmmm”)&TEXT(Date,” yyyy)”)

Now by grouping your list by this column, your list will be grouped by the dates month only.

More From pstilgoe

• Sharepoint calculated column more date / day calculations
• Enable anonymous access on a Sharepoint site
• Displaying the week number using a Sharepoint calculated column

Ask pstilgoe To Recommend Your Posts

Article ID : 946517
Last Review : August 7, 2008
Revision : 4.0

SYMPTOMS

Consider the following scenario. You have a process that has more than one thread. Additionally, the process uses the Internet Information Services (IIS) Active Directory Service Interfaces (ADSI) provider to access IIS. Two threads access IIS at the same time. In this scenario, you may be unable to manage IIS by using Server Manager.

When this problem occurs, you must restart IIS, or you must restart the process that uses the IIS ADSI provider.

This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this problem occurs for the SharePoint Timer service, you may experience the following symptoms:

• In SharePoint Server 2007, tasks that are scheduled do not run.

• On the SharePoint Web front-end server, you see repeated errors in the Application log in Event Viewer. These errors usually include one of the following three events:

• Event ID 6398
• Event ID 6482
• Event ID 7076

For example, you may see an error message that resembles the following:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: (964)
Event ID: 6398
Date: 11/7/2007
Time: 5:45:38
PM User: N/A
Computer: 44MOSSAGRUK
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob
(ID 02b5e3f2-21e3-4552-bf1d-6e152749458a) threw an exception. More information is included below.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

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

• When you try to manage IIS by using Server Manager, you receive a blank page, or you receive the following error message:
the path specified cannot be used at this time

RESOLUTION
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

More From pstilgoe

• SharePoint/MOSS Active Directory Self Service Web Part
• Best Practices Resource Center for SharePoint Server 2007
• How to configure Kerberos for SharePoint / MOSS 2007

Ask pstilgoe To Recommend Your Posts

REMEMBER:

You can restrict number of versions in following ways:
1) You can limit the number of major versions
2) You can limit a number of major version that will have minor versions
3) You CANNOT limit a number of minor versions to keep for a major version

When you reach your version limits the oldest version will be deleted. Remember these are deleted permanently, they are NOT sent to the recycle bin!

More From pstilgoe

• Sharepoint and JQuery
• Microsoft Office SharePoint Server (MOSS) 2007 Limits
• SharePoint Configuration Analyzer v1.0 for Windows SharePoint Services

Ask pstilgoe To Recommend Your Posts

Microsoft Office SharePoint Server 2007 includes features that can help you control access to content. You configure settings for the content control features discussed in this article in document libraries. To share these settings across libraries in your solution, you can create document library templates that include your content control settings; this ensures that new libraries will reflect your content control decisions.

Plan versioning

Versioning is the method by which successive iterations of a document are numbered and saved. Office SharePoint Server 2007 has three versioning options:

None Specifies that no previous versions of documents are saved. When no versioning is in use, previous versions of documents are not retrievable, and document history is also lost because comments that accompany each iteration of a document are not saved. Use this option on document libraries containing unimportant content or content that will never change.

Major versions only Specifies that numbered versions of documents are retained using a simple versioning scheme (such as 1, 2, 3). To control the effect on storage space, you can specify how many previous versions to keep, counting back from the current version.

In major versioning, each time a new version of a document is saved, all users with permissions to the document library will be able to view the content. Use this option when you do not want to differentiate between draft versions of documents and published versions. For example, in a document library that is used by a workgroup in an organization, major versioning is a good choice if everyone on the team needs to be able to view all iterations of each document.

Major and minor versions Specifies that numbered versions of documents are retained by using a major and minor versioning scheme (such as 1.0, 1.1, 1.2, 2.0, 2.1). Versions ending with .0 are major versions and versions ending with non-zero extensions are minor versions. Previous major and minor versions of documents are saved along with current versions. To control the effect on storage space, you can specify how many previous major versions to keep, counting back from the current version. You can also specify for how many major versions minor versions should be kept. For example, if you specify that minor versions should be kept for two major versions and the current major version is 4.0, then all minor versions starting at 3.1 will be kept.

In major and minor versioning, any user with read permissions can view major versions of documents. You can specify which users can view minor versions. Typically, grant users who can edit items permissions to view and work with minor versions, and restrict users with read permissions to viewing only major versions.

Use major and minor versioning when you want to differentiate between published content that can be viewed by an audience and draft content that is not yet ready for publication. For example, on a human resources Web site that describes organizational benefits, use major and minor versioning to restrict employees’ access to benefits descriptions while the descriptions are being revised.

Plan content approval

Content approval is the method by which site members with approver permissions control the publication of content. A document draft awaiting content approval is in the Pending state. When an approver reviews the document and approves the content, it becomes available for viewing by site users with read permissions. A document library owner can enable content approval for a document library and can optionally associate a workflow with the library to run the approval process.

Use content approval to formalize and control the process of making content available to an audience. For example, an enterprise that publishes content as one of its products or services might require a legal review and approval before publishing the content.

The way that documents are submitted for approval varies depending on the versioning settings in the document library:

None If no versioning is in use and changes to a document are saved, the document’s state becomes Pending. Office SharePoint Server 2007 keeps the previous version of the document so users with read permissions can still view it. After the pending changes have been approved, the new version of the document is made available for viewing by users with read permissions and the previous version is discarded.

If no versioning is in use and a new document is uploaded to the document library, it is added to the library in the Pending state and is not viewable by users with read permissions until it is approved.

Major versions only If major versioning is in use and changes to a document are saved, the document’s state becomes Pending and the previous major version of the document is made available for viewing by users with read permissions. After the changes to the document are approved, a new major version of the document is created and made available to site users with read permissions, and the previous version is saved to the document’s history list.

If major versioning is in use and a new document is uploaded to the document library, it is added to the library in the Pending state and is not viewable by users with read permissions until it is approved as version 1.

Major and minor versions If major and minor versioning is in use and changes to a document are saved, the author has the choice of saving a new minor version of the document as a draft or creating a new major version, which changes the document’s state to Pending. After the changes to the document are approved, a new major version of the document is created and made available to site users with read permissions. In major and minor versioning, both major and minor versions of documents are kept in a document’s history list.

If major and minor versioning is in use and a new document is uploaded to the document library, it can be added to the library in the Draft state as version 0.1, or the author can immediately request approval in which case the document’s state becomes Pending.

Plan check-in and check-out

You can require that users check documents in and out of a document library before editing the documents. It is always recommended to do this. The benefits of requiring checking in and out include:

Better control of when document versions are created. When a document is checked out, the author can save the document without checking it in. Other users of the document library will not be able to see these changes and a new version is not created. A new version (visible to other users) is only created when an author checks in a document. This gives the author more flexibility and control.

Better capture of metadata. When a document is checked in, the author can write comments that describe the changes made to the document. This promotes creation of an ongoing historical record of the changes made to the document.

If your solution requires that users check documents in and out when editing them, the 2007 Microsoft Office system client programs include features that support these actions. Users can check documents out, undo check-outs, and check documents in from 2007 Office system client programs.

When a document is checked out, it is saved in the user’s My Documents folder in a subfolder named “SharePoint Drafts.” This folder is displayed in Microsoft Office Outlook 2007. As long as the document is checked out, the user can only save edits to this local folder. When the user is ready to check the document in, the document is saved back to the original server location.

From 2007 Office system client programs, users can optionally choose to leave checked-out documents on the server by changing content editing options.

More From pstilgoe

• Creating a scheduled email reminder using Sharepoint Designer
• Creating filtered views in Sharepoint
• Sharepoint Search – How features work part 1

Ask pstilgoe To Recommend Your Posts

After you identify your content stakeholders, collect information from them that will help you analyze how documents are used in your organization. This is an important part of the planning process because the analysis helps you determine:

How document libraries are structured.

Which site templates to use.

How many sites you will need.

Which information management policies to apply to the sites.

Which physical server topology you will need to implement your solution.

The information to collect includes:

Document type, such as equity research note, employee performance review, internal memo, or product specification.

Purpose of each document type, such as “provides customers with recommendations about equities along with supporting data.”

Author of each document type (listed as roles, not individuals, such as “Financial Analyst,” “Human Resources Specialist,” or “Product Manager”).

Format of the document. If the document is transformed from one format to another, record that information.

Users of each document type, such as “customers” or “team members.”

Other roles that apply to the document’s life cycle, such as “technical reviewer” or “copy editor.”

Location of the document, such as “client computer,” “Web server,” or “file server.” Note that this question could have multiple answers, such as when a document is authored on a client computer and then published to a Web server.

How readers view the document, such as from a Web page or a file share.

Techinal Details:

System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.

at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)

at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)

at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)

at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)

at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)

at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.GetDataSource()

at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)

Resolution:

Grant the following rights in shared services –

Default Content Access Account:Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permissions

Search Service Account: Manage Analytics, Manage Audiences, Manage User Profiles, Personal Features, Personal Site, Set Permission

This error should now be resolved.

More From pstilgoe

• Enable anonymous access on a Sharepoint site
• Using a lookup to return data from a list on a different site
• SSP – Delegate People Management, Profile Import, My Site, Audience Management

Ask pstilgoe To Recommend Your Posts

Current implementation is Windows 2008 server, IIS 7.0 & MOSS 2007, when defining the Shared Service Provider Application Pool Account it is stated that you dont need to grant it any permissions as they will get added automatically upon creation eg:

When each application pool is setup, you must specify an account that will be used for that specific application pool’s identity. This account will be used to access the content databases associated with the web application. It is recommended that a new service account is created for each application pool. This should be a Domain Account with no specific permissions. When the account is specified & SharePoint creates the application pool, it automatically grants the account additional needed permissions.

However in my environment this is not the case as upon creation of this SSP no accounts appear to be able to access the SSP config page. In the short term I have set the App pool account for the SSP as SPadmin (my install / admin account) until I have time to figure out exactly what is causing this & what permissions are required.

More From pstilgoe

• Error: Cannot retrieve the information for application credential key
• SharePoint/MOSS Active Directory Self Service Web Part
• How to delete the Shared Service Provider in MOSS 2007

Ask pstilgoe To Recommend Your Posts

Use the following URL replacing the relevant parts to match your setup:

http://atlas:3092/_admin/deletessp.aspx?sspId=e10f8b2b-11ee-475a-bef3-d576ee90de45

More From pstilgoe

• How to add Blackberry support for MOSS 2007 & Infopath Forms
• SharePoint/MOSS Active Directory Self Service Web Part
• Sharepoint 2010: How to hide the quick launch menu

Ask pstilgoe To Recommend Your Posts

When trying to uninstall MOSS2007 I would run setup & then select remove MOSS 2007 completely, shortly after the status box would just dissappear & MOSS wouldnt uninstall. In my case I was able to runs stsadm -o uninstall from a command prompt & then I could run the MOSS uninstall with no problems.

More From pstilgoe

• How to add Blackberry support for MOSS 2007 & Infopath Forms
• How to delete the Shared Service Provider in MOSS 2007
• How to configure Kerberos for SharePoint / MOSS 2007

Ask pstilgoe To Recommend Your Posts

NOTE: This hotfix appeared to trash my WSS 3.0 SP1 MOSS SP1 & SQL 2005 SP2 implementation on Windows 2008 server so use with caution !

List of issues fixed
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• Consider the following scenario. You create a managed property by using the Windows SharePoint Services 3.0 object model. You add the property to a document, and then you upload the document to a document library on a Windows SharePoint Services 3.0 Web site. After a full crawl or an incremental crawl is performed, you try to search for the document that contains the managed property. When the results of the search are returned, the document that contains the managed property is not found.

• In an e-mail message, you click a hyperlink for an assignment in a Microsoft Office SharePoint Server 2007 site. When you do this, you receive the following error message:
There has been an error while loading the form. Click try again to attempt to load form again. If this error persists, contact the support team for the web site.

The URL URL_path is an unsupported relative URL. Use an absolute URL of prefix with ‘~sitecollection, for a site-collection-relative URL.

• You make a change to the Manager field in the Active Directory directory service. Then, you perform an incremental update or a full update. When you do this, the Manager field in the Windows SharePoint Services 3.0 site is not updated in the profile of the user. However, if another field, such as the Contact Number field, is also updated, both the Contact Number field and the Manager field are updated in the SharePoint Profile database.

• When you use the Advanced search feature in the document library in a Microsoft Office SharePoint Server 2007 portal site to search for a document that contains a space in the file name, the document is not returned in the Search Results page. However, the document is returned in the search results if you specify the first part of the file name as the keyword for the search.

For example, a document that is named “Intranet Migration.doc” may not appear in the Advanced search results. If you use “Intranet” or “Migration” as the keyword for the search, the document is returned in the search results.

This issue occurs because the file name property is stored in the Windows SharePoint Services 3.0 portal library with an encoded “%20.” The file name property is not stored with a space.

New Stsadm.exe tool operation added
Microsoft has added a new operation to the Stsadm.exe command-line tool to change the URL of a host-named site collection to a new URL. This new operation is included in this hotfix package.

For more information about the new operation in the Stsadm.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:
939535 (http://support.microsoft.com/kb/939535/) How to use the new “renamesite” operation to change the URL of a host-named site collection in Windows SharePoint Services 3.0
Back to the top

MORE INFORMATION
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites

There are no prerequisites for installing this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix is not replaced by any later hotfix.This hotfix is not replaced by any later hotfix.
Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
Post-installation information
After you apply this hotfix package, you must run the SharePoint Products and Technologies Configuration Wizard.

To do this, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.
File information
This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
32-bit hotfix package
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download informationFile name File version File size Date Time
Wss-kb939592-fullfile-x86-glb.exe 12.0.6015.5000 16,742,872 29-Jun-2007 10:58 Microsoft Windows Installer .msp file information

More From pstilgoe

• Creating a scheduled email reminder using Sharepoint Designer
• Using Sharepoint meeting workspaces with Outlook 2003 / 2007
• How to submit an InfoPath form to a Windows SharePoint Services document library

Ask pstilgoe To Recommend Your Posts

Search Query
urn:content-class:SPSSearchQuery

News Listing
urn:content-class:SPSListing:News

People
urn:content-class:SPSPeople

Category
urn:content-classes:SPSCategory

Listing
urn:content-classes:SPSListing

Person Listing
urn:content-classes:SPSPersonListing

Text Listing
urn:content-classes:SPSTextListing

Site Listing
urn:content-classes:SPSSiteListing

Site Registry Listing
urn:content-classes:SPSSiteRegistry

Site
STS_Web

List
STS_List

List Item
STS_ListItem

Events
STS_List_Events

Tasks
STS_List_Tasks

Announcements
STS_List_Announcements

Discussions
STS_List_DiscussionBoard

Contacts
STS_List_Contacts

Links
STS_List_Links

Document Library
STS_List_DocumentLibrary

Document Library Items
STS_ListItem_DocumentLibrary

Picture Library
STS_List_PictureLibrary

Picture Library Items
STS_ListItem_PictureLibrary

More From pstilgoe

• Content Type Toolbar Web Part
• Enhanced Content Query Web Part
• SharePoint/MOSS Active Directory Self Service Web Part

Ask pstilgoe To Recommend Your Posts