**Urgent** New Edit in Datasheet error occurring on proven WSS2 sy
gocat2005
Today when users try to Edit in Datasheet using Office 2003 or 2007 Pro this
error is displayed:
"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 Windows SharePoint Services is not installed, your browser
does not support ActiveX controls, or support for ActiveX controls is
disabled."
We have loads of users screaming about this. Is it to do with Office 2003 SP3?
Mike Walsh
This is possibly caused by them having a mix of Office 2003 and Office
2007 level apps on their client and a security fix has caused the wrong
DLL to be used.
It would help with questions if you say up-front which SharePoint
product you are asking about. I'm assuming WSS 2.0 as you posted here
and it has been in use for 2 years.
Mike Walsh
WSS FAQ http://www.wssfaq.com
no private e-mail questions please
gocat2005
Yeah it says WSS2 in the subject.
What shall I do?
Regards
Graham
Mike Walsh
is) ...
I think this might be one of the things that can be fixed by making sure
you have the correct version of OWSSUPP.DLL for your Office version that
controls the Datasheet function.
In Office 2003 this was controlled Excel 2003. In Office 2007 I'm unsure
whet her it is still Excel (2007) or another product but even there it
IS one of the main Office products so with the mix I mentioned before
you need to look at which 2003 or 2007 main Office products they have
installed.
Mike Walsh
Mike Walsh
Office 2003 main products are in use try Repairing that (or all Office
2003). That should replace any incorrect .dlls (etc.?).
(I'm not sure whether the one I mentioned before is the right one or not)
Mike Walsh
gocat2005
use is FrontPage
I'm trying to re-register owssupp.dll but Vista won't let me - even using
Powershell running as Administrator
I'm doing
cd "c:\program files\microsoft office\office12"
regsvr32 owssupp.dll
Returns error 0x80070716 - which means I don't have permission to register
the dll
arrrrgh!
gocat2005
happens
Mike Walsh
it could possibly screw up your Office 2007 apps.
For that reason I have one PC running Office 2003 and FP 2003 and
another one running Office 2007 (and that's where I'd add SPD 2007 if I
wanted it on a client).
Sorry but no suggestions beyond the try to Repair Office 2007 I
mentioned before.
Mike Walsh
gocat2005
I have been running Office 2007 including SPD and FP2003 together on my
Vista laptop for months no probs.
This issue appeared today and on several systems in different companies.
Some are WinXP + Office 2003 and some on WinXP with Office 2007. Some like me
are Vista + Office 2003 and 2007.
I fired up a PC which has not been updated for a month - all OK.
So the problem must be the latest Windows update.
We'll see what PSS recommend.
QC
Since SP3 was a microsoft update that can't be removed, I am out of ideas.
gocat2005
I don't think this is a server issue. It appears to be caused by the latest
automatic updates to the client PCs.
If I try to access the SharePoint site with a PC which hasn't been updated
since last month, it works fine.
Regards
Graham
QC
client machines.
I booted up a Win XP office 2003 machine that had earlier updated back to
8/17/2007 and it still didn't work.
taso...@gmail.com
all with the same after the SP3 update.
gocat2005
Stay tuned...
Regards
Graham
gocat2005
According to KB http://support.microsoft.com/kb/938814 the issue is caused
by poorly written COM components that use the QueryInterface() method when an
Office 2003 program is started.
This means the Datasheet View Component must be poorly written doesn’t it?
Therefore what we need is a well written Datasheet View Component and quick...
Also, I see note that on my WSS2 SharePoint Server which is a standard
install on Windows Server 2003, Windows Update has downloaded Office 2003 SP3
which is ready to install.
When I look in Add-Remove Programs on the server, sure enough Office 2003
Web Components are there, which is why the Update has been downloaded.
This is not good, right?
gocat2005
I also did a system restore to before the time of the latest updates
released on September 19th 2007 but this problem still occurred.
So I tried Delete Temporary Internet Files in Internet Explorer - the issue
disappeared.
What was all that about then ????
Brett
Brett
ar...@p-talk.nl
> Any word yet, gocat? We are having the sameproblemon 3 of our portals.
>
> Brett
I have this problem as well, and just deleting the browser cache is
not fixing anything.
On the 17th SP3 was released, does this automatic client update have
anything to do with SP3 as well?
gocat2005
This worked in 3 different corporations in different locations who have
experienced this problem since the Office 2003 SP3 update was released on
19th September 2007.
Microsoft advice is: Do not install Office 2003 SP3 on server machines yet
If clearing the browser cache does not fix your problem then try the
documented issues for SP3 (supplied by Microsoft Product Support):-
http://support.microsoft.com/kb/923618 , specially the section ‘Known issues
after you install the service pack’
You can refer to KB http://support.microsoft.com/kb/938814 . The issue is
documented there and there is a resolution/workaround is mentioned.
B-Admin
we are experiencing the same problem when a user tries to use the datasheet
view:
"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 Windows SharePoint Services is not installed, your browser
does not support ActiveX controls, or support for ActiveX controls is
disabled."
But no one of them has SP3 of Office 2003 installed, only SP2. And I also
deleted their temporary internet files. It has worked now for 3 yeas but
since we installed SP3 for v2 of our Sharepoint Server, we have this problem
on every computer. I thought that at the beginning of this thread this was
also the opinion of some people. Did they find a solution?
Canda@discussions.microsoft.com Zoltan Canda
We are using Intranet build on MS Sharepoint Portal Server 2003 SP2 and
Sharepoint Services SP2.
We have the same problem as mentioned before. After instalation of Windows
Sharepoint Services SP3, we have experienced problems with displaying Graphs
in our intranet and we can´t use Edit in Datasheet. If I make a new graph,
then Explorer displays it without errors.
I consulted disfunctional graps with Microsoft Support. Their advice:
Install SP3 to Sharepoint Portal Server. After update, graphs are still not
working. MS only solution is to back to SP2 or make all intranet graphs again.
We found, that this problem occures after installing KB924424. Before this
update everything was working fine. This KB is included in SP3 and can´t be
uninstalled separetely.
I don´t want to reinstall Intranet and I don´t want to remake all graphs in
our intranet.
Can you please help me?
Stewart@discussions.microsoft.com Dan Stewart
know of any other way to resolve this issue?
Thanks
Dan Stewart
Cortland71
datasheet view. I'm Running Office 2007 and Vista. I deleted the Temporary
Internet files as suggested and all is fine again.
Thanks for your help. This was driving me crazy!
dantist
wrote:
> I had the same problem. All of a sudden I couldn't open lists in the
> datasheet view. I'm Running Office 2007 and Vista. I deleted the Temporary
> Internet files as suggested and all is fine again.
>
> Thanks for your help. This was driving me crazy!
>
>
>
> "gocat2005" wrote:
> > The solution was Delete Temporary Internet Files on client machines.
>
> > This worked in 3 different corporations in different locations who have
> > experienced this problem since the Office 2003 SP3 update was released on
> > 19th September 2007.
>
> > Microsoft advice is: Do not install Office 2003 SP3 on server machines yet
>
> > If clearing the browser cache does not fix your problem then try the
> > documented issues for SP3 (supplied by Microsoft Product Support):-
>
> > after you install the service pack'
>
> > documented there and there is a resolution/workaround is mentioned.- -
>
> - -
I have the same problem
after install the Windows SharePoint Services service pack 3 i cannot
view a list in Datasheet view !
anyone have any ideas ?
bsr1031
company. We ended up doing a repair of the WSS2 installation and then an
uninstall and reinstall of the .Net Frameworks. After that the datagrid was
working fine again. Some clients had to delete their temporary internet
files afterwards, others did not. Hope this helps those who are still having
issues.
"gocat2005" wrote:
> Our Sharepoint system has been in use for 2 years - fine.
>
> Today when users try to Edit in Datasheet using Office 2003 or 2007 Pro this
> error is displayed:
>
> "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 Windows SharePoint Services is not installed, your browser
> does not support ActiveX controls, or support for ActiveX controls is
> disabled."
>
bsr1031
recreate the issue in a couple of test environments as well. The datagrid
functionality works fine until WSS SP3 is applied to the server.
"Mike Walsh" wrote:
> Do you know whether in your case the SP3 was applied to clients; servers
> (the WSS 2.0 server); or both ?
>
> Mike Walsh
Mike Walsh
(the WSS 2.0 server); or both ?
Mike Walsh
james....@nov.com
SP2003 server --> Go to C:\Program Files\Common Files\Microsoft Shared
\web server extensions\60\TEMPLATE\LAYOUTS\1033
Open OWS.js in an editor, Find "PortalPinToMyPage"
OWS Code Snip:
function PortalPinToMyPage(eForm, portalUrl, instanceID)
{
eForm.action = portalUrl + '_vti_bin/portalapi.aspx?
Cmd=PinToMyPage';
eForm.ReturnUrl.value = window.location.href;
eForm.ListViewUrl.value =
MakeMtgInstanceUrl(eForm.ListViewUrl.value, instanceID);
eForm.submit();
}
----Start copy here----
function RenderActiveX(str)
{
document.write(str);
}
----End copy here----
var L_CutToolTip_TEXT = "Cut";
Save, Do an IISRESET, Clear your browser cache, and Life should be
good...
Arthur Pounder
This issue has been reported by several organisaitons. As I understand it,
Microsoft are working on a fix for this issue.
A
B-Admin
datasheet back. Thank you very much James!
Jack_Feeman
I had a problem with SPD 2007 being used with Office 2203 and WSS2.0. The
answer I got worked fine and solved the issue.
So if your issue is caused by this incompatibility, try this solution
provided by Cornelius J. van Dyk:
http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=103
Thanks Jack
rookie
wrote:
> I didn't see any resolution yet for this issue, so....
>
> I had a problem with SPD 2007 being used with Office 2203 and WSS2.0. The
> answer I got worked fine and solved the issue.
>
> So if your issue is caused by this incompatibility, try this solution
> provided by Cornelius J. van Dyk:
>
> http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=103
>
> Thanks Jack
>
>
>
> "Arthur Pounder" wrote:
> > Hello,
> > This issue has been reported by several organisaitons. As I understand it,
> > Microsoft are working on a fix for this issue.
>
> > A
>
> > "bsr1031" wrote:
>
> > > recreate the issue in a couple of test environments as well. The datagrid
>
> > > "Mike Walsh" wrote:
>
> > > > Do you know whether in your case theSP3was applied to clients; servers
>
> > > > Mike Walsh
>
> > > > bsr1031 wrote:
> > > > > We've beenfollowingthis thread and have finally fixed the problem at our
> > > > > company. We ended up doing a repair of the WSS2 installation and then an
> > > > > uninstall and reinstall of the .Net Frameworks. After that the datagrid was
> > > > > working fine again. Some clients had to delete their temporary internet
> > > > > files afterwards, others did not. Hope this helps those who are still having
> > > > > issues.
>
> > > > > "gocat2005" wrote:
>
> > > > >> Our Sharepoint system has been in use for 2 years - fine.
>
> > > > >> error isdisplayed:
>
> > > > >> "Thelistisdisplayedin Standardview. ItcannotbedisplayedinDatasheet
> > > > >>viewforoneormoreof thefollowingreasons: Adatasheetcomponent
> > > > >> compatible with Windows SharePoint Services is not installed, your browser
> > > > >> does not support ActiveX controls, or support for ActiveX controls is
> > > > >> disabled."
>
>
> - Show quoted text -
Since we rarely log on to our WSS 2.0, I just installed SP3 yesterday
and am having the same complaints from users, that they can no longer
"Edit in Datasheet". I checked in the OWS file that Dan mentions
above and we already have that RenderActiveX function included. Has
there been any update from Microsoft or any other resolution that
anybody has found? Any help is greatly appreciated as our users are
freaking out ...
Thanks!
JonathanD
and am having the same complaints from users, that they can no longer
"Edit in Datasheet". I checked in the OWS file that Dan mentions
above and we already have that RenderActiveX function included. Has
there been any update from Microsoft or any other resolution that
anybody has found? Any help is greatly appreciated as our users are
freaking out ...
Thanks!
Jack_Feeman
experiencing the datasheet lockout. We do not have that problem but we have
not installed SP3 yet either (and I do not think we will.....yet). Can you
use system restore to back out of the SP3 on a machine to see if that
restores the datasheet functionality?
Thanks Jack
JonathanD
client machines running Office 2K3. Since we only have a few people that use
the functionality I decided to attempt some client-based fixes. Last night
we found that if you upgrade to Office 2K7 the issue is no longer there. So
as our temporary fix, this is our solution ...
Jack_Feeman
near future since the user experience will change quite extensively, we will
need to train the userbase first. However, we will be upgrading to WSS v3 so
hopefully we wont run into that issue.
top_...@hotmail.com
wrote:
> The solution was Delete Temporary Internet Files on client machines.
>
> This worked in 3 different corporations in different locations who have
> experienced this problem since the Office 2003 SP3 update was released on
> 19th September 2007.
>
> Microsoft advice is: Do not install Office 2003 SP3 on server machines yet
>
> If clearing the browser cache does not fix your problem then try the
> documented issues for SP3 (supplied by Microsoft Product Support):-
>
> after you install the service pack'
>
> documented there and there is a resolution/workaround is mentioned.
Hey thanks GoCat,
Deleting Temporary Internet Files worked for our XP machines with
Office2003.
It was giving me a real headache as some machines worked fine but many
couldn't edit the sharepoint datasheet.
cheers,
Alan.
TagDEN!!
Bear in mind that you might have to edit the OWS.JS file in more than just
the ...\1033 Directory depending on languages installed.
I had to edit both the ...\1033 and the ...\1030 dir's.
But otherwise everything was dandy. :-)
Thank you.
jam...@wsu.edu
Thanks James,
James
Luis Fernández
in some of them (those upgraded with Office 2K3 SP3), but not in others.
I think upgrading WSS to V3 won't be a solution to the problem, since it
depends of Office 2003 client configurations and upgrade level.
Regards
Luis Fernández
1 - Upgrade Office 2003 clients to SP3 (update of rest of sw pieces
recommended).
2 - Delete registry subkey (folder):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX
Compatibility\{65BCBEE4-7728-41A0-97BE-14E1CAE36AAE}
in each Office 2003 client.
It's a "googled" solution. This prevents IE to check some ActiveX COM
interface compliance for Office 2003 component for displaying WSS datasheets.
Surprisingly, it does not meets COM interface requirements for Office 2003.
Regards,
Luis
costabella
> (I've deleted the Urgent - urgent questions go to Microsoft)
>
> This is possibly caused by them having a mix of Office 2003 and Office
> 2007 level apps on their client and a security fix has caused the wrong
> DLL to be used.
>
> It would help with questions if you say up-front which SharePoint
> product you are asking about. I'm assuming WSS 2.0 as you posted here
> and it has been in use for 2 years.
>
> Mike Walsh
> WSS FAQhttp://www.wssfaq.com
> no private e-mail questions please
>
>
>
> gocat2005 wrote:
> > Our Sharepoint system has been in use for 2 years - fine.
>
> > error is displayed:
>
> > "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
> > does not support ActiveX controls, or support for ActiveX controls is
> > disabled."
>
>
> - Show quoted text -
I have a similar problem. We have never had "Edit in Datasheet" when
we had SharePoint 2003 (WSS 2.0) and Office2003 standard. Now, we've
moved to SP2007 (WSS 3.0). People who have office 2003 still can't use
"Edit in Datasheet". "Edit in Datasheet" works fine for people who
have Office 2007 standard. Can anyone clarify what combinations work,
or what active X controls need to be enabled, etc.?
Eric
Can anyone clarify wh
neuling700
do you have an solution now ? I have the same problem wit WSS 3.0 and Office
2003.
If you have a solution please post it here. Thanks for your help.
Best regards
neuling700
"gocat2005" wrote:
> Microsoft have promised to call me within 24-48 hours!
>
> Stay tuned...
>
> Regards
> Graham
>
> "taso...@gmail.com" wrote:
>
> > Is there any solution to this problem yet? I have 4 sbs2003 networks
> > all with the same after the SP3 update.
> >
> >
neuling700
if you have an solution, please post it here. I have the same problem wit
wss3.0 and office 2003 clients.
Best regards
Neuling700
Monty
Office 2003 machines.
> Alan.- Hide quoted text -
ssfpridav
> ----Start copy here----
> function RenderActiveX(str)
> {
> document.write(str);}
>
> ----End copy here----
> var L_CutToolTip_TEXT = "Cut";
>
> Save, Do an IISRESET, Clear your browser cache, and Life should be
> good...
Life is good again. Thanks for the solution!
Leon Baudewijns
Bernat Recasens
None of the other solutions worked for us, but this yes!
Thank you very much Luis Fernández.
Bernat
Lele
and all the english sites have the problem. We have the Italian language pack
installed, and all the italian sites are ok!
All the clients runs Office 2003.
"QC" wrote:
> We are having the same issue. our server was updated to WSS 2.0 SP3.
>
> Since SP3 was a microsoft update that can't be removed, I am out of ideas.
>
> "gocat2005" wrote:
>
> > I have logged a support incident with Microsoft and will let you know what
> > happens
> >
> > "gocat2005" wrote:
> >
> > > Our Sharepoint system has been in use for 2 years - fine.
> > >
> > > Today when users try to Edit in Datasheet using Office 2003 or 2007 Pro this
> > > error is displayed:
> > >
> > > "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
Edwin
> > > > We have loads of users screaming about this. Is it to do with Office 2003 SP3?- Hide quoted text -
Lele
Thank you very much, James.
Lele
Tomas
We experinced same problem with brand new clients runing Office 2007 SP1
(but ok with some "older" Office 2007 (not SP1) clients!!).
I tested your work around and it worked perfect. A BIG thanks
/Tomas
caty
Thx a lot
Marc (St Pete, Fl)
James and Mike do you know if Microsoft is aware of this aspect of the fix?
Have they made any comments or is this a closed issue to them?
I think one of the things that made this a confusing discussion is that
there are multiple causes to the same error message. It looks like some
applied SP3 to MS Office to get here and others applied SP3 to SharePoint
2003 to get to the problem. My environment included MS Office SP2 and when we
applied SharePoint 2003 services/server SP3 – we got the error.
RogerN
Couldn't have fixed this without you!!
/Roger
lnghrnhou
Champ@discussions.microsoft.com SKi Champ
Thanks
"james....@nov.com" wrote:
> Here's the fix that worked in my Production environment.
>
> >
danny...@gmail.com
and I was seeing some users on Vista able to access the view and
others who could not. I added the site to the trusted sites under IE
and restarted IE and it worked like a champ. Most of us are using IE7
and it turns out that ActiveX controls are not implicitly turned on by
default, however IE will use ActiveX on trusted sites implicitly. Hope
this helps.
cpw
(a workaround is to set an Identifier in the Registry to set Pro Version
Information, but this is only for testing)
Windows SharePoint List data support:
You can only edit Windows SharePoint list data by using Web forms in the
Windows SharePoint Services interface. Editing SharePoint lists in Excel 2003
is only available with Office Professional Edition 2003.
http://office.microsoft.com/en-us/suites/HA102126571033.aspx
WebHst_Support
has tried this fix for Windows Vista running IE7 and Office 2K7?
mike
Sharepoint 2003 after installing SP3!
blizz
little confused as to the exact context that needs to be added. Can you
clarify what needs to be copied were? Is Start Copy here and end copy her
part of the code? Sorry for being a newbie. Any help is appreciated. All
enteries I have entered have lead to page finishing with errors.
Thanks
"james....@nov.com" wrote:
> Here's the fix that worked in my Production environment.
>
> SP2003 server --> Go to C:\Program Files\Common Files\Microsoft Shared
> \web server extensions\60\TEMPLATE\LAYOUTS\1033
>
> Open OWS.js in an editor, Find "PortalPinToMyPage"
>
>
> OWS Code Snip:
>
> function PortalPinToMyPage(eForm, portalUrl, instanceID)
> {
> eForm.action = portalUrl + '_vti_bin/portalapi.aspx?
> Cmd=PinToMyPage';
> eForm.ReturnUrl.value = window.location.href;
> eForm.ListViewUrl.value =
> MakeMtgInstanceUrl(eForm.ListViewUrl.value, instanceID);
> eForm.submit();
> }
> ----Start copy here----
> function RenderActiveX(str)
> {
> document.write(str);
> }
> ----End copy here----
> var L_CutToolTip_TEXT = "Cut";
>
DESE
JayvardhanPune
facing this problem.
There are many solutions that worked for them and there are many of them for
who nothing worked actually.
There are some possible solutions that work. These are not found by me. I'm
just trying to put them at one place.
http://codeforfuture.com/2009/04/22/solutions-sharepoint-datasheet-view-doesnt-work/