Microsoft Sharepoint Services

Seems like the contacts that are created by SharePoint in Exchange 2007, does not update the properties of the contact as per the requirements of Exchange 2007. Following is the repro of the issue and I am figuring out where exactly thep roblem lies. Will update the blog as soon as I get the solution.

Should be able to resolve the SharePoint contact information by clicking Ctrl + K while sending e-mails to List library
Created one new web application on port 80 and the site URL as http://site-url and we configured the incoming and outgoing e-mails as mentioned in fig 1.1 and fig 1.2

Fig 1.1

Fig 1.2

Browse the site http://site-url and create one document library name as “Incoming Email”. Went to document library settings of that particular document library as shown in fig 1.3

Fig 1.3

And configured the incoming e-mail settings and given the e-mail address as documents@serverSMTP.domain.com as mentioned in fig 1.4

Fig 1.4

And we went to to the Active directory there we can see that the contact has been created and we went to Start——>All Programs—–>Microsoft Exchange server 2007—–>Exchange Management Console there we can see the document library contact is created as shown below

And right click on that contact and selected property but we are getting error as shown below as customer is getting the same

And we tried to resolve the display name by clicking Ctrl+K but we are getting error

Present Behavior : Not able to resolve the document library contact by clicking the Ctrl+ K as we are able to do for normal Active Directory Contacts as shown below

Expected: Need to resolve the document library contacts by clicking Ctrl + K and able to send an e-mail to that particular document library

• Install October Cumulative Update for WSS Global KB957691

• Install October Cumulative Update for MOSS Global KB957693

• Install October Cumulative Update for MOSS language specific KB958567

• Install October Cumulative Update for MOSS Global Workflow KB958569

Now, you need to be sure if you have installed any pre-requisites for these hot-fixes. You can find them in the kb articles mentioned. I am installing the October updates on my lab and will write down if I come across any issues.

Consider the following scenario:

- We have a document library with the following settings:
o Name – Major and Minor Version – Alert Issue
o Permission – Unique Permissions. We have broken the permissions and the library no longer inherits the permissions from the top level site collection.

- We now add a user to the top level site with Read Permissions
- The same user is added to the document library with Read permissions
- For a better clarification, following is the versioning settings for the document library:

- Now the user with Read permission logs on to the site and subscribe for an Alert for the document library. The user gets the initial alert email about the alert being created for the Document Library.
- To distinguish, I have the site admin logged in to the document library and create a alert for him. The site admin now uploads a new document to the document library.
- We see that the user with Read only permissions does not get a subsequent alert, but the site admin does.

Conclusion:
If the user has Read permissions over a document library and if the document library has “Major and Minor” versioning turned on, then the user with the read permission will not get an alert.
This is a by-design issue.

Work-Arounds:
- Turn Off Major and Minor versioning and either keep Major versioning on or Minor versioning on, but not both.
- Give the user edit permission over the document library. This can be done either by assigning Contribute permission to the user or by editing the permission levels for the site.

Reason:
The user only has read permission and not edit permission over the library and its items. When a new item is inserted, the document is saved as draft and now published on the site. Thus, the document is not final. Thus, the user will not get an alert. But for the user who has edit permission, can approve the document and thus need to be notified about the document change so that the user can approve/reject the draft version.

This is one of the issue that made me go crazy when dealing with it. I have a document library and a folder in it. I have many items in the document library and also some sub-folders in it. When I try to click on the folder or  open the folder and click on the item inside the sub-folder, i get an error :
“Cannot complete this action”

The problem here was that I do not get any errors in the Event Viewer. All I see is some warning messages related to .NET CLR and that probably might be because there are some registry entries or .dlls that are not functioning properly.

Getting to the point again, I installed the August Cumulative hotfix on my SharePoint Server and that resolved the issue. I see that the error message was there in one of the kb articles mentioned for the cumulative hot-fixes and thought of giving it a try. The kb articles are :

Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008
http://support.microsoft.com/kb/957109

Description of the Windows SharePoint Services 3.0 hotfix package: August 26, 2008
http://support.microsoft.com/kb/956057

Description of the SharePoint Server 2007 hotfix package: August 26, 2008
http://support.microsoft.com/kb/956056/

Make sure that you go through the Technet Article about how to install the hot-fix on your SharePoint Servers, else it will hell lot of pain to revert back or get the issues resolved.

Deploy software updates for Windows SharePoint Services 3.0
http://technet.microsoft.com/en-us/library/cc288269.aspx

Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

Note:
One more issue that I see gets resolved using the cumulative hot-fix is as follow

Symptoms :
When we upgrade the site from WSS2 – WSS3 or MOSS, the default.aspx page doesnot come up.
Error: HTTP 500 Internal Error

When we try to open the page in SharePoint Designer, we get an error
“Cannot open the page”

If we go to a subsite, everything works fine. Also, all the new web apps that we create work great. 
In this sscenario, try the cumulative hot-fixes mentioned above. Your issue should be resolved.

I am in the process of implementing SSO on my SharePoint development environment and was searching was a starting point, where I can get some information. Here is what I found :

http://www.decatec.it/blogs/2007/05/16/MOSS+SSO+Single+Sign+On.aspx

http://blogs.msdn.com/sharepointdesigner/archive/2007/08/27/an-introduction-to-single-sign-on-sso-with-data-views.aspx

http://www.theserverside.net/tt/articles/showarticle.tss?id=ImplementingSSO

http://blogs.msdn.com/arpans/archive/2008/05/09/sharepoint-end-user-security.aspx

Hope this helps.

Administration jobs means the timer jobs that are executed on regular basis on the SharePoint Server. They range from Alert processing, Synchronization, etc. To get the complete timer job list for the farm, browse to Central Administration -> Operations -> Timer jobs

If you see any failed job in the timer jobs status, the first thing that you might try is running the following command on all the servers :

stsadm -o execadmsvcjobs

The above command will try and execute the timer jobs that are stuck/scheduled for the specific time when you run that command. There are possibilities like the stsadm command is stuck and shows “Executing….” in the command prompt after you attempt to run the above command.

To run the above command successfully, follow the below troubleshooting steps :

• Open Central Admin -> Operations -> Diagnostic Logging
• Select “All” under the jobs and set the Error logging to Verbose.
• Try to execute the execadmsvcjobs command.
• Open the log file under “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs” . This is the default log directory. It might be possible that the logs directory is changed by the administrator who has set up SharePoint. We can check the logs settings from Central Administration -> Operations -> Diagnostic logging.
• Open the file in MS Excel -> Apply filters for the columns -> Under the Levels column, select “high” and “verbose”. Under the category column, select “Timer” and “Unified Logging Service”
• Check for any errors that you get there.
• Based upon errors, we need to further troubleshoot the issue.
• The possible errors that you might get are :
  • The previous instance of the timer job ‘Application Server Administration Service Timer Job’, id ‘{12403D5C-D18B-4D06-9E2F-C2855E30385C}’ for service ‘{83A518CA-9139-4A50-999B-6C35E4D42A34}’ is still running, so the current instance will be skipped.  Consider increasing the interval between jobs
  • Error during Encrypting Decrypting

If you get the above two errors, they probably are related. This issue normally occurs where you have multiple server farm configuration. The first error says that there is an admin jobs that is not getting executed. As the job is stuck, we need to remove that job from the config so that other jobs can be executed. Run the following two commands to check if it is a ssp timer jobs or a admin timer job that is listed :

stsadm -o deletessptimerjob -id “12403D5C-D18B-4D06-9E2F-C2855E30385C”

If the above command says that there is no ssp timer jobs listed with the above ID, run the following command to delete the object with that id :

stsadm -o deleteconfigurationobject -id “12403D5C-D18B-4D06-9E2F-C2855E30385C”

This will remove the timer job that was stuck. Now try and execute stsadm -o execadmsvcjobs on the other servers and you might get the second error that I have listed above. The Encryption/Decryption error states that for some reason, the password used by the timer service on that server is not valid.

Open Services.msc on the server where you are getting the error and re-enter the log on credentials for the “Windows SharePoint Services Timer”. Run the following command to update the username and password for the timer service account :

stsadm -o updatefarmcredentials -userlogin “domain\username” -password “xxxxxxx” -local

NOTE: For the complete list for updating the farm credentials follow this kb :http://support.microsoft.com/kb/934838/en-us

Run the stsadm -o execadmsvcjobs on the server where you were getting the errors and this time it will run succesfully. If you face any further problems, or other error messages, please leave a comment and I should get back to you soon.