RSS

Category Archives: Office Integration

WebClient service hang in the Stopping State

One of my customer had reported that she could not open the SharePoint document library folder from the shortcut. Actually, she created a shortcut for the document library explorer view. Some reasons she could not open the document library explorer view from the shortcut but she can able to access the site and able to open the explorer view from the URL.

After I digg into her machine and found out that WebClient Service was hang in the stopping state. I could not even stop/start the service using net command. Finally, I had to kill the process associated with the webclient service to stop the service and restart it afterwards.

Here is the command, I have used to kill the process associated with the webclient service.

taskkill /fi “imagename eq svchost.exe” /fi “Services eq WebClient” /F

Once I killed the process, I have restarted the service using net command.

Net start webclient

The issue has been resolved after I killed the process associated with WebClient and restarted the WebClient Service.

 

SYMPTOMS: 

User not able to access the SharePoint Explorer View or Shortcut created on top of SharePoint Explorer View.

CAUSE:

WebClient Service might be stopped or hang in the stopping state

RESOLUTION:

1. Kill the process associated with the WebClient Service

taskkill /fi “imagename eq svchost.exe” /fi “Services eq WebClient” /F

2. Restart the WebClient

Net start webclient

 

Hope this helps.

Advertisements
 
2 Comments

Posted by on August 8, 2012 in Office Integration, Sharepoint

 

DATASHEET ISSUE WITH SHAREPOINT

SYMPTOMS:

When attempting to create/open a document in a SharePoint list or view a list in Datasheet view, you receive one of the messages below:

1. The list cannot be displayed in Datasheet view for one or more of 
the following reasons:
 - A datasheet component compatible with Windows SharePoint Services 
is not installed.
 - Your Web Browser does not support ActiveX controls.
 - Support for ActiveX controls is disabled.
-OR-
 The list is displayed in Standard view. It cannot be displayed in 
Datasheet view for one or more of the following reasons: A datasheet 
component compatible with Microsoft SharePoint Foundation is not 
installed, your browser does not support ActiveX controls, a component is 
not properly configured for 32-bit or 64-bit support, or support for 
ActiveX controls is disabled. 2. The document could not be created. The required application 
may not be installed properly, or the template for this document library 
cannot be opened. 3. The document could not be opened for editing. A Windows SharePoint 
Services compatible application could not be found to edit the document.

CAUSE:

There are several possible causes for any of the error message listed above.  Some possible causes are;

1) Incompatibility issues specific to the version of Microsoft Office installed on your computer,

2) The SharePoint Support component or Windows SharePoint Services Support (as appropriate to your version of MS Office) is not installed on your computer,

3) The Owssupp.dll file is not registered correctly in Microsoft Windows and/or is corrupt due to installation of Office 2003 professional, and any of Office 2007 Products

4) You are using Microsoft Office 2010 and do not have a 64-bit version of ActiveX Control installed on your computer.

RESOLUTION:

It is recommended that you consult your Site Administrator before performing any of the resolution options listed below.

Repair a Corrupt Owssupp.dll: Running a Microsoft Office diagnostic tool can repair a corrupt .DLL file.  Below are the instructions to run the diagnostic tool.

1. Navigate to C:\Program Files\Microsoft Office\Office12
2. Delete the OWSSUPP.DLL file from this directory.
3. Click Start.
4. Click All Programs.
5. Click Microsoft Office.
6. Click Microsoft Office Tools.
7. Run Microsoft Office Diagnostic.

8. Repair office installation using below instructions

If Office 2003 is installed on the computer:
1. Click Start, and then click Control Panel.
2. Click Add or Remove Programs.
3. In the list of currently installed programs, click Microsoft Office 2003, and then click Change.
4. Click Add or Remove Features, and then click Next.
5. Click to select the Choose advanced customization of application check box, and then click Next.
6. In the Choose update options for applications and tools box, expand Office Tools, click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer.
7. Click Update.


 
Leave a comment

Posted by on July 1, 2011 in Office Integration, Sharepoint

 

SharePoint 2007: Word was unable to read this document. It may be corrupt

SYMPTOMS:

When user try to open a document from SharePoint document library, the document does not open, and they receive the following error message:
“Word was unable to read this document. It may be corrupt.
Try one or more of the following:
* Open and Repair the file.
* Open the file with the Text Recovery converter.
(\…\test.doc)”

RESOLUTION:

We have been trying to troubleshoot this above mentioned issue by applying HOTFIX from Microsoft, but no luck!

We would like to dig more information about this issue to find out a proper solution, so we gathered the information like HTTP Trace, Network Trace, ULS Log etc. We have noticed after we analyzed the ULS log, this issue appears only one web application and other web application works correctly without any issue and we could not find any entries for problematic web application.

Similarly, we could not find any useful information from Network Trace analysis however we have found out the root cause of this issue by analyzing the HTTP Trace.  HTTP Trace shows a couple of redirection(“HTTP STATUS CODE: 307”) calls when user opening a document from the SharePoint document library.

We dig into more on why it is redirecting/omitting the HTTP calls when user opening a document from document library, finally we have found out that culprit (“Proxy pac file exception”). We did not added the exception for problematic Web application url in the proxy pac file.

After we added the exception entry in the IE proxy pac file, the issue has been resolved!

 
3 Comments

Posted by on July 1, 2011 in Office Integration, Sharepoint

 

Tags: