Explorer view not opening in windows vista

Your client does not support opening this list with Windows Explorer.

I think, we are very much familiar with this error message and know what exactly needs to be done if such issue occurs. But this issue varies if operating system changes from XP to Windows Vista.

FYI- this is a known issue with windows vista OS and we have a Microsoft KB for this: http://support.microsoft.com/kb/841215

Before we can go ahead and concludes on to above mentioned KB, make sure to check the following points:

1)    Web client service should be started

2)    You can also get the error if the URL to the document library is 100 characters long

3)    If you are using Internet Explorer 6 you will get the error. You know it’s time to upgrade

It would be a good question as what exactly this KB suggest?

Please refer the following info:
1. Click Start
2. Type regedit.exe in the Start Search box
3. Locate and expand the list and navigate to the following location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameter
4. Locate the value BasicAuthLevel
--Right click the value and choose Modify.
--In the Value data box, type 2, and then click OK.
5. Exit Registry Editor, and then restart the computer.

  

If it’s a Windows Server 2008 OS then please check the following:
1. Open up the Windows Server Manager.
2. Click Features in the left hand menu
3. Click Add Features, in the main window.
4. Select the Desktop Experience feature, and then click Next.
5. Click Install.
6. Click Close when the Add Features wizard is done.
7. Choose to reboot when done.

       

If it’s a Windows Server 2003 OS then please check the following:

Download and install the Microsoft Hot fix

Windows Office needs a Web Client update to work properly with WebDAV.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than HAPPY to HELP you as well as RESOLVES your issues, Thank you

restrictions on file names, folders, and URLs

SharePoint is always tricky but if we know how to use, what to use and where to use then it will be very easy. Today i am going to share some basic details which are very common but extremely useful.

URL Restrictions:

The maximum length for a URL in Windows SharePoint is 260 characters. However, I suggest you do not use URLs longer than 256 so users can include the links in the links list, as mentioned in Miscellaneous section below.

Some additional details (Just for reference):

Site Restrictions

- You cannot use the characters ” # % & * : < > ? \ / { | } ~ in a site name.

- You cannot start a site name with an underscore. For example, _MySharepointSite is not a valid name for a site or a subsite.

- Periods are not allowed consecutively in the middle of a site name. For example, My..SharepointSite is not a valid name.

- You cannot start or end a site name with a period. For example, .MySharepointSite and MySharepointSite. are both invalid names.

Document Libraries

- If you use one of the following characters in a Document Library they will be removed: Comma, hyphen, period, left and right parenthesis ().

Miscellaneous Tips

- Do not use underscores in a site name. Although allowed, Microsoft discourages it.

- Link list items cannot be more than 256 characters

File & Folder Restrictions

- You cannot use the characters ” # % & * : < > ? \ / { | } ~ in a file or folder name.

- A file or folder name in a URL cannot contain more than 128 characters in Windows sharepoint services 2.0/3.0 and MOSS.

- You cannot start or end a file name or folder with a period. For example, .Mysharepoint.docx and Mysharepoint2007.docx. are both invalid names.

- Periods are not allowed consecutively in the middle of a file or folder name. For example, My..sharepoint2007.file is not a valid name.

If you have any queries/questions regarding the mentioned information then please let me know.

I would be more than HAPPY to HELP you as well as RESOLVES your issues, Thank you

You cannot type some Polish letters in the Rich Text Editor

Working on one SharePoint issue in which the user is not able to use some polish letters.

Problem Description: Users with polish keyboards cannot input some data in the Rich text Editor of the Content editor web part or the Wiki pages

Did research and found the Microsoft KB article which states that:

Polish has letters in addition to the 26 letters that are used in English. However, you cannot type some of these additional letters in the Rich Text Editor. For example, this issue occurs when you try to type some Polish letters in a blog or in a custom list that uses the Rich Text Editor.

We need to run the STSADM utility to enable this fix. Use the following command:
stsadm.exe -o setproperty -url http://portal -pn “richtexteditorshortcutenabled” -pv “no”
This has to run on the portal which contains the site collection.

Reference article:

http://support.microsoft.com/kb/942388

One more thing is that i would like to highlight here: if you are not able to execute the above mentioned command then what you will do ?? Don't worry-Here is the workaround for this:

Enter Polish characters not with ALT, but with SHIFT, ~, release keys and then l for ł etc.

I hope the above mentioned information will be useful to all of you and helps you to resolve the issue in an efficient manner. If you have any queries/questions regarding the mentioned information then please let me know. I would be more than HAPPY to HELP you as well as RESOLVES your issues...

How to Fix PDF Previews in Explorer on 64-bit Windows

When I try to preview a PDF in Outlook, I get the message as mentioned below:
 “This file cannot be previewed because of an error with the following previewer: PDF Preview Handler for Vista”.

Resolution:

Just download the Adobe Reader preview handler x64 fixer by Leo Davidson, click the Apply Fix button…

Download the Adobe PDF Preview Fixer

Resolution by using Registry modification:

1)      Close all the other applications which are currently running on your machine

2)      Start

3)      Regedit.exe

4)      Browsed to the following location

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\
CLSID\{DC6EFB56-9CFA-464D-8880-44885D7DC193}

5)      Change the AppID to the following

{534A1E02-D58F-44f0-B58B-36CBED287C7C}

That’s it-Done

If you have any queries/questions regarding the above mentioned information then please let me know... I would be more than HAPPY 2 HELP you as well as RESOLVES UR Issues, Thank you

Refferences:

-http://www.sevenforums.com/general-discussion/34348-file-cant-previewed.html

-http://office-watch.com/t/n.aspx?a=1350

-http://www.edbott.com/weblog/2009/09/finally-a-fix-for-the-pdf-preview-bug-in-64-bit-windows/

You do not have the necessary permissions to use the 'ListName' object. Have your system administrator or the person who created this object establish the appropriate permissions for you.

Team-today I worked on one issue and would like to share the resolution details with all of you so that we can efficiently resolve any forthcoming issues based on the same type.

Problem description:

When You try to add an existing sharepoint list to a Microsoft Office Access 2007 database then you receive an error message that resembles the following:

Error message: 
You do not have the necessary permissions to use the '<ListName>' object. Have your system administrator or the person who created this object establish the appropriate permissions for you.

Action Taken:

1) Checked the number of groups which are present on the site and user permissions on the site as well as for the specific list that we trying to connect

2) User has Full control on the site as well as for the list also so problem is not from sharepoint end

3) Checked the office application installed on the system and found multiple version which consist of office 2003 as well as office 2007

4) Checked the access version and found out it belongs to Office 2007 suite

5) Checked on my machine to reproduced the same and we are able to reproduced it so the problem is not from the Office suite

6) User conveyed that its working on one of the sharepoint site and compare both the sites and found out some differences in terms of columns and characters but to make sure did research and found the Microsoft KB: http://support.microsoft.com/kb/924739

Microsoft KB states that it’s a known issue. Details as follows:

Cause: This problem occurs because the Access 2007 database engine disallows columns that have names that contain more than 64 characters.

Workaround: To work around this problem, use only column names that contain less than 64 characters in SharePoint lists.

Resolution for this issue: there was one column which has more than 64 characters, we shorten the column name and tried connecting the list to access and it works without any issues.

If you have any queries|questions|doubts regarding above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, thank you J