View Complete Post
When try to open a folder in a moss 2007 document library in Explorer View, the folder does not open.
I am using IE7 and the path of the folder does not contains more than 100 characters.
Also it opening on few on the machines which has IE7.
I am attempting to connect to a Microsoft Sharepoint library, via the "Actions -> Open in Windows Explorer" option from the Sharepoint page. When I do so, I get the error message "your client does not support opening this list with windows explorer". In short, I am trying to get the "drag and drop" functionality of a Sharepoint library.
I am running Windows 7 64-bit and IE8. The target Sharepoint environment is a MOSS 2007 EE. My Windows "WebClient" service is running, and I have no problem connecting to this exact library via a Windows XP computer running IE8.
When I click on a pdf document uploaded in a document library it comes up with a blank page.
I guess it's trying to open pdf on the browser. I turned off "Display PDF in browser " option in Adobe Preferences, but it doesn't help, same issue.
I tried other browsers too, it's the same issue.
I am able to open all other pdf files local to my machine fine.
I am using IE 8 on my machine (Windows 7) and the Sharepoint server is MOSS 2007.
When a user, who uses Dragon NaturallySpeaking, says "new" when viewing a Document Library the default content type is selected and the associated application (e.g. Microsoft Word) is launched. This scenario is okay for Content Type selection since
the Microsoft Office applications will prompt for the metadata once the file is saved.
If the user needs to create new folders in the Document Library however they need to expand the "new" dropdown menu.
What is the best way for someone using Dragon NaturallySpeaking to expand the "new" menu for a Document Library in SharePoint?
I am trying to troubleshoot an issue where some users of our SharePoint environment have problems using the open with windows explorer option in a document library.
For some users this works fine...ÃÂ the explorer opens quickly and they can manage the documents.
For other users it takes up to 5 minutes before the explorer view opens.ÃÂ During this time the browser becomes completly unresponsive.
As part of the troubleshooting process I tried taking the UNC path that is shown in the explorer view and tried using the Start -> Run and then entering in the path.ÃÂ ÃÂ ÃÂ This seems to cause the complete desktop to freeze until the explorer window displays.
This is occuring on Windows XP SP Pro SP2 with both IE6 and IE7.ÃÂ ÃÂ The desktops are on the same domain as the SharePoint servers.
Any thoughts on next steps?
I created my own file type. And I have an application to open this specific file
(xml). In SP2010 created a list of documents and have uploaded this file type on my list of specific documents and up
to here everything is working fine.
But when I click the file from the list of documents that he was open with my software or whether it is possible to synchronize
with the file.
My application (WPF Application) is already prepared to receive through "CommandLineArgument" the name and location of the file. If I go to the folder where
my file and make double click, my software starts and open the file.
How do I open t
Hello I have a problem with managed metadata on two different servers and would like to ask you to try it.
I assume you have managed metadata service running.
1, Open some document library in some site
2, Create column - managed metadata type and select some termset and set it as required.
3, Upload a document and fill in metadata when you will be asked.
4, Then edit properties and check, that metadata are there.
5, Save this library as template.
6, Deploy document library from this template and try steps 3+4.
My problem is, you can select metadata, but they are not saved. e.g. when you check document properties managed metadata are not there.
Can you confirm this behavior ?
Thank you very much.
P.S.: one more weird thing. If you do metadata filling using office 2010 compatible application. Metadata remain there, but they are not visible in document library properties.