Felipe Ferreira

MCT, MCITP Database Administrator, MCPD: Web Developer

Sharepoint: ActiveX Error When Trying to View List in Datasheet View

When trying to view a list in datasheet view, sometimes you get the following error:

" 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 browser does not support ActiveX controls, or support for ActiveX controls is disabled. "

Well.. the first thing you should test is if activeX is in fact enabled in your browser.. second thing.. if you’re running the correct version of Office.. to use datasheet view you need access 2003 or 2007 installed on your machine. But, if you’re searching for this here you probably already checked those things.. so let’s go to the next level:

Open regedit and let’s edit windows registry.. first of all, please do a backup of your windows registry! you know that edit this is a dangerous thing, right?
Ok then.. so now that you’ve did your registry backup, delete (or rename) the following entry:

HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\
{65BCBEE4-7728-41A0-97BE-14E1CAE36AAE}

that’s all.. if even this doesn’t work for you, try to register again stslist.dll:

regsvr32.exe stslist.dll

see ya

Posted: Jul 30 2009, 04:11 PM by Felipe Ferreira | with 11 comment(s)
Filed under: ,

Comments

Sharepoint: ActiveX Error When Trying to View List in Datasheet View | ASP Scribe said:

Pingback from  Sharepoint: ActiveX Error When Trying to View List in Datasheet View | ASP Scribe

# July 30, 2009 2:21 PM

Lehanoff said:

OMG! Thank you! I've been waiting long time for this solution!

# August 11, 2009 8:11 AM

Felipe Ferreira said:

glad to know it helped you Lehanoff.

regards

# August 11, 2009 9:06 AM

Wieger vd Burgt said:

Thanks! this worked lovely.

Found this also on MS website. They say it works like design. Arrogance of MS is unbelievable. They cba to fix it i guess.

# August 26, 2009 3:18 AM

Hilvar said:

Great. It worked. Thanks a lot.

# October 14, 2009 11:46 AM

Ted Szczygielski said:

Hi - thanks

I'v been spend a lot of time trying find solution

Since only deleting this registry HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\

{65BCBEE4-7728-41A0-97BE-14E1CAE36AAE}

solve this problem

much obliged

Ted - Poland

# November 5, 2009 4:16 AM

Rudolf said:

Anyone had this issue with Windows 7? Registry seems to be a bit different. There are several entries with 65BCBEE4-7728-41A0-97BE-14E1CAE36AAE. I am not sure which one to remove

# November 9, 2009 10:29 AM

Darren D said:

We solved this issue (Office 2003 SOE with Project 2007) simply by opening Excel 2003 and performing a repair. Excel 2003 > Help > Detect and Repair (may require a restart). This re-instates control of the Office Web Component (runs Datasheet view) from Access 2007 back to Excel 2003. Not one of Microsoft's finest moments on the backward compatibility front.

# November 12, 2009 8:14 PM

Felipe Ferreira said:

Thanks for sharing your solution Darren.

in my case there wasn't office 2007 installed, and even reinstalling office 2003 didn't solved the problem. it was a 1 day headache, that's why I decided to share how I fixed here :)

hope your solution can help others here too

regards

# November 12, 2009 10:00 PM

Ken B. said:

I had the same Datasheet View problem in Share Point using Office 2003 and IE7.  

I did not have the registry path HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\

{65BCBEE4-7728-41A0-97BE-14E1CAE36AAE}.

I also did not have the C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\LAYOUTS\1033\ows.js file.  

So, I searched my registry and found the {65bcbee4-7728-41a0-97be-14e1cae36aae} value under HKEY_Classes_Root\CLSID\...  I had two entries total in my registry and deleted them, after first backing up the registry of course.  Then, I ran the Excel 2003 Detect and Repair.  No more problem.  

Next, I like Darren D's idea and will try to fix the problem by only running the Excel 2003 Detect and Repair to see if the registry hack is even necessary.  

Does anyone know what this registry value {65bcbee4-7728-41a0-97be-14e1cae36aae} does?  

# November 15, 2009 2:09 PM

Ken B. said:

Ahhhh, it is the Datasheet Control GUID {65bcbee4-7728-41a0-97be-14e1cae36aae}

# November 15, 2009 2:13 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)