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
Written by peter.stilgoe on August 26th, 2008 with no comments.
Read more articles on Windows / Active Directory and Moss / Sharepoint / WSS and Document Management.
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.
Written by peter.stilgoe on August 22nd, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS.
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.
Written by peter.stilgoe on August 21st, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS.
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.
Written by peter.stilgoe on August 18th, 2008 with no comments.
Read more articles on Windows / Active Directory and Windows Vista and Moss / Sharepoint / WSS and Windows Server 2008.
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!
Written by peter.stilgoe on August 13th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS and Document Management.
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.
Written by peter.stilgoe on August 13th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS and Document Management.
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.
Written by peter.stilgoe on August 13th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS and Document Management.
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.
Written by peter.stilgoe on August 13th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS and Windows Server 2008.
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.
Written by peter.stilgoe on August 13th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS and Windows Server 2008.
Use the following URL replacing the relevant parts to match your setup:
http://atlas:3092/_admin/deletessp.aspx?sspId=e10f8b2b-11ee-475a-bef3-d576ee90de45
Written by peter.stilgoe on August 11th, 2008 with no comments.
Read more articles on Moss / Sharepoint / WSS.
« Older articles
No newer articles
