Flakey Sharepoint Integration

[David McKenzie]

I posted this to the Sharepoint group.
Microsoft (in the personal of Wei-Dong Xu) referenced
http://support.microsoft.com/?id=840024
and suggested that I should post this issue here.
While KB840024 accurately describes how OWSSUPP can be 'lost' as a result of
installing , say Frontpage 2003 over Office XP
or applying maintenence, it does not explain what I am seeing now:\
half a dozen machines I know have had no software installed and no
maintenence applied having this problem.
Detect and Repair does not always fix the problem, and this is becomming a
support issue.
We would not have chosen to deploy a technology which requires repeated
reinstallation of Office


Initially, we had some problems with Sharepoint / Office integration, where,
even though Windows Sharepoint Services Support was installed with Office
XP, users would get 'Edit Document' requires a Windows SharePoint
Services-compatible application and Microsoft Internet Explorer 5.0 or
greater" and occasionally Excel documents would open in Word. We licked all
these problems by re registerring Excel
"C:\Program Files\Microsoft Office\Office10\excel" /unregserver
"C:\Program Files\Microsoft Office\Office10\excel" /regserver
,Regegisterring OWSSUPP.DLL
regsvr32 -u "C:\Program Files\Microsoft Office\Office10\OWSSUPP.DLL"
regsvr32 "C:\Program Files\Microsoft Office\Office10\OWSSUPP.DLL"

or in a few instances by running Office Detect and Repair

The Office XP Service Pack 3 install 'broke' about 1/10 of our machines, but
we were prepared.

Now I am getting a handfull of random 'broken' machines every week, although
there has been no maintenence.

I am wondering, Is this 'expected' behavior.

On the 'Good, Better, Best' scale I rank this Fair, not Better.
^_^

 

[Bob Buckland ?:-\)]

Hi David,

In this scenario it may be helpful for both you and
MS to review your scenarios more closely if the
KB 840024 didn't resolve the OWSsupp becoming
unregistered, (i.e. it shouldn't reoccur)
by opening a support case with MS.
http://support.microsoft.com

=======
I posted this to the Sharepoint group.
Microsoft (in the personal of Wei-Dong Xu) referenced
http://support.microsoft.com/?id=840024
and suggested that I should post this issue here.
While KB840024 accurately describes how OWSSUPP can be 'lost' as a result of
installing , say Frontpage 2003 over Office XP
or applying maintenence, it does not explain what I am seeing now:\
half a dozen machines I know have had no software installed and no
maintenence applied having this problem.
Detect and Repair does not always fix the problem, and this is becomming a
support issue.
We would not have chosen to deploy a technology which requires repeated
reinstallation of Office <<


Initially, we had some problems with Sharepoint / Office integration, where,
even though Windows Sharepoint Services Support was installed with Office
XP, users would get 'Edit Document' requires a Windows SharePoint
Services-compatible application and Microsoft Internet Explorer 5.0 or
greater" and occasionally Excel documents would open in Word. We licked all
these problems by re registerring Excel
"C:\Program Files\Microsoft Office\Office10\excel" /unregserver
"C:\Program Files\Microsoft Office\Office10\excel" /regserver
,Regegisterring OWSSUPP.DLL
regsvr32 -u "C:\Program Files\Microsoft Office\Office10\OWSSUPP.DLL"
regsvr32 "C:\Program Files\Microsoft Office\Office10\OWSSUPP.DLL"

or in a few instances by running Office Detect and Repair

The Office XP Service Pack 3 install 'broke' about 1/10 of our machines, but
we were prepared.

Now I am getting a handfull of random 'broken' machines every week, although
there has been no maintenence.

I am wondering, Is this 'expected' behavior.

On the 'Good, Better, Best' scale I rank this Fair, not Better.
^_^ >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx