SP2010: "Open with Windows Explorer" option is displayed in the "Actions" menu of Document libraries after disabling Publising feature

Problem description: Open with Windows Explorer option is displayed in the "Actions" menu of Document libraries after disabling Publishing feature

One of our user using a SP2010 team site from a long time. As per the requirements arises, he made some changes in the contribute permissions and activated “publishing feature” also.

What exactly happens?

After changing contribute permission of users to exclude “Use Client Integration Features" option, enabling Publishing feature results “Open with Windows Explorer” action to be available in the “Actions” menu of Document libraries. Later if we disable Publishing feature, that does not prevent users to open Windows explorer through “Open with Windows Explorer” option.

Troubleshooting started:

Let’s do the postmortem of this publishing feature.

Publishing feature is well known feature but it makes drastic changes when we do the activation.

Base location of publishing feature-C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\PublishingSite

Feature Id: F6924D36-2FA8-4f0b-B16D-06B7250180FA

Which features gets activated when we activate SharePoint Server Publishing Infrastructure at the site collection level:

Name:Publishing Prerequisites

Description: Enable Publishing prerequisites for site collection

Folder name: PublishingPrerequisites

Feature Id: A392DA98-270B-4e85-9769-04C0FDE267AA

Functionality:

This feature enables the publishing prerequisites for a site collection. It doesn’t activate any other features; it just runs the code in the feature receiver to set up a site so it can use the publishing features.

Name:Publishing Resources

Description: Enable Publishing for site collection

Folder name: PublishingResources

Feature Id: AEBC918D-B20F-4a11-A1DB-9ED84D79C87E

Functionality:

This feature enables the publishing resources on a site collection. The publishing resources are site columns and content types and site settings. The feature also contains three feature upgrades that are added to the feature when it gets activated.

Groups created when we activates Publishing feature:

Style Resource readers

Designers

Approvers

Restricted Readers

Quick Deploy users

Hierarchy managers

Cause:

Even after disabling Publishing feature, the groups that are created as part of enabling publishing feature are NOT removed. When enabling publishing feature, by default all users are added to a SharePoint group called “Style Resource Reader” . This group has "Read" permission by default which also includes “Use Client Integration Features" permission level by default. Because of that reason, users will get “Open with Windows Explorer” action in the “Actions” menu of Document libraries.

Workaround/Fix that found:

We only have workarounds for this behavior.

Workaround 1:

Remove “Style Resource Reader” SharePoint group.

Workaround 2:

Create a new SharePoint Group that does not include "Limited Access" permission level for it. Then add required users to that SharePoint group.

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

I would be more than happyJ to help you as well as resolves your issuesJ

Installation of WSS/SP2 package was failing

Problem Description:

To install the SP2 & April Update for MOSS

ERROR MESSAGE:

"Installation of this package failed." Error while installing the WSS package”

What is happening?

When we tried to install the WSS/Sp2 and WSS Hot fix package we get "Installation of this package failed" error

ULG logs digging:

“MSI (s) (60:44) [17:51:28:748]: Product: Microsoft Windows SharePoint Services 3.0

Error 1921.Service 'Windows SharePoint Services Search' (SPSearch) could not be stopped. Verify that you have sufficient privileges to stop system services.”

Cause determined:

This package was trying to stop the "Windows SharePoint Service Search" and was failing.

Resolution provided:

1. Stopped manually SPSEARCH service from the services.msc console and found we were able to install the WSS package without any issue.

2. On Another server we were unable to stop this service and were showing some errors.

3. We manually set the status to "DISABLED" and rebooted the server

4. Found we were able to install the package successfully.

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 :-)

This installation is forbidden by system policy. Contact your system administrator

Problem Description:

When installing Excel Viewer 2007, about half through he gets the error "your system administrator has set policies to prevent this installation" - The verbose log shows: This installation is forbidden by system policy. Contact your system administrator.

When we were running Excel Viewer 2007, about half through he gets the error
"Your system administrator has set policies to prevent this installation".

The verbose log shows:

This installation is forbidden by system policy. Contact your system
administrator.
C:\Program Files\MSECache\xlview_en-us\xlview.msi
MSI (c) (10:E0) [17:37:07:981]: Product: Microsoft Office Excel Viewer - Update
'Microsoft Office Excel Viewer 2007 Service Pack 1 (SP1)' could not be installed.
Error code 1625. Additional information is available in the log file
C:\DOCUME~1\p112279p\Local Settings\Temp\MSId301e.LOG.

Steps taken to resolve this issue-

There may be an invalid past reference in the registry to Excel viewer here:

[HKEY_CLASSES_ROOT\Installer\Products\00002159F30090400000000000F01FEC]

"ProductName"="Microsoft Office Excel Viewer 2007"

Points of interest -

1. The product name for the current version of the Excel viewer should be:

"Microsoft Office Excel Viewer"

2. There are no other values under

"HKEY_CLASSES_ROOT\Installer\Products\00002159F30090400000000000F01FEC". Only the

ProductName.

If we delete the key

HKEY_CLASSES_ROOT\Installer\Products\00002159F30090400000000000F01FEC, and reattempt the Excel Viewer 2007 install, it succeeds without the bogus Policy error.

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

Office Security Updates failing with error 0x80070663

Problem:

System Center Configuration Manager 2007 Service Pack 1 (SP1) will not restart the client computer automatically. It prevents pending important updates from being installed successfully on these computers.

What I did to resolve this issue:

HKEY_LOCAL_MACHINE\Software\Microsoft\Sms\Mobile Client\Reboot
Management\JobCounter
- set JobCounter to 0 (zero)

under very specific conditions; the persistent job counter is not decremented when a job is finished. The coordinating system prevents these client computers from being restarted because it believes that a job is still running based on the JobCounter value.

Root Cause:
- client incorrectly concludes that a job is running because JobCounter <> 0
- hotfix prevents problem from happening again
- hotfix does not correct the JobCounter value.

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 J Thank you

Office 2010 installation fails with Error 2203

Problem:

User is trying to upgrade from Office 2007 to Office 2010 Pro Plus

What happens exactly?

The upgrade process fails about halfway through and rolls back Office 2007 is removed, but Office 2010 apps are not installed, the Error 2203 comes up in the error message.

How to analyze and what to analyze:

The setupexe log should have lines like the following

MSI(ACTIONSTART): 'Action 9:21:41: SetODBCFolders. Initialisation des répertoires
ODBC'
MSI(INFO): 'Action start 9:21:41: SetODBCFolders.'
MSI(INFO): 'Action ended 9:21:41: SetODBCFolders. Return value 0.'
MSI(ACTIONSTART): 'Action 9:21:41: InstallValidate. Validation de l’installation'
MSI(INFO): 'Action start 9:21:41: InstallValidate.'
MSI(INFO): 'Action ended 9:21:41: InstallValidate. Return value 1.'
MSI(ACTIONSTART): 'Action 9:21:41: InstallInitialize. '
MSI(INFO): 'Action start 9:21:41: InstallInitialize.'
MSI(ERROR): 'Error 2203. An internal error has occurred.
(C:\Windows\Installer\1e8942e.ipi -2147287035 ) Contact Microsoft
Product Support Services (PSS) for assistance. For information about how to
contact PSS, see C:\Users\jludwick\AppData\Local\Temp\Setup00000824\PSS10R.CHM.'
Log level changed from: Standard to: Verbose
MSI(INFO): 'Action ended 9:21:41: InstallInitialize. Return value 3.'
MSI(INFO): 'Action ended 9:21:41: INSTALL. Return value 3.'

It appears that an Office 2007 add in could have caused the issue

If Office Live Addin 1.3 is installed then please remove that

If Office 2007 Programmable Interop Assemblies are installed then remove that. Office 2010 should install fine now.

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 J Thank you