Environment :- Only Vista Machines.
Note :- Before making any registry changes, take Reg back up
Resolution :- Delete the follow registry keys and reboot is a MUST
HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11D1-A9F0-00AA0060FA31}
HKEY_CLASSES_ROOT\CLSID\{0CD7A5C0-9F37-11CE-AE65-08002B2E1262}
Thursday, December 18, 2008
Thursday, December 11, 2008
Files opens as Read Only after Check-out
Note:- Please take precautionary steps before applying the below steps. Backup your registry.
Issue:- Files will open as Read-Only after checking Out a document in SharePoint and trying to Edit it.
Environment:- XP + Office 2003 or Vista + Office 2007
Follow the below steps to resolve the issue.
---------------------------------------------------
1.) Search for oledb32.dll on the workstation and make sure it exists in this location. The default location is c:\program files\common files\system\ole db\oledb32.dll
2) Copy and paste the information below to Notepad and save as a .reg file. This will correct the entries in the Registry that are probably missing.
===========================================================
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\InprocServer32]@="C:\\Program Files\\Common Files\\system\\ole db\\oledb32.dll""ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\OLE DB Binder]@="Microsoft OLE DB Root Binder"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\ProgID]@="MSDAURL.Binder.1"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\VersionIndependentProgID]@="MSDAURL.Binder"
[HKEY_CLASSES_ROOT\MSDAURL.Binder.1]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\MSDAURL.Binder.1\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"
[HKEY_CLASSES_ROOT\MSDAURL.Binder]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\MSDAURL.Binder\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"
[HKEY_CLASSES_ROOT\MSDAURL.Binder\CurVer]@="MSDAURL.Binder.1"
===========================================================
3) From Start->Run, type Regsvr32.exe "[Drive]:\Program Files\Common Files\System\OLE DB\MSDAIPP.DLL"
4) Test and see if the issue is resolved.
Issue:- Files will open as Read-Only after checking Out a document in SharePoint and trying to Edit it.
Environment:- XP + Office 2003 or Vista + Office 2007
Follow the below steps to resolve the issue.
---------------------------------------------------
1.) Search for oledb32.dll on the workstation and make sure it exists in this location. The default location is c:\program files\common files\system\ole db\oledb32.dll
2) Copy and paste the information below to Notepad and save as a .reg file. This will correct the entries in the Registry that are probably missing.
===========================================================
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\InprocServer32]@="C:\\Program Files\\Common Files\\system\\ole db\\oledb32.dll""ThreadingModel"="Both"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\OLE DB Binder]@="Microsoft OLE DB Root Binder"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\ProgID]@="MSDAURL.Binder.1"
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\VersionIndependentProgID]@="MSDAURL.Binder"
[HKEY_CLASSES_ROOT\MSDAURL.Binder.1]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\MSDAURL.Binder.1\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"
[HKEY_CLASSES_ROOT\MSDAURL.Binder]@="Microsoft OLE DB Root Binder for Internet Publishing"
[HKEY_CLASSES_ROOT\MSDAURL.Binder\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"
[HKEY_CLASSES_ROOT\MSDAURL.Binder\CurVer]@="MSDAURL.Binder.1"
===========================================================
3) From Start->Run, type Regsvr32.exe "[Drive]:\Program Files\Common Files\System\OLE DB\MSDAIPP.DLL"
4) Test and see if the issue is resolved.
Thursday, December 4, 2008
Windows SharePoint Services Search (SPSearch) Errors File Not Found / 'start' action failed
Disclaimer: Take all possible backups, Since you have decided to troubleshoot on your own we hold no responsibility if anything goes wrong.
Note: After every troubleshooting step run following command
stsadm -o spsearch -action fullcrawlstart
& monitor Eventviewer>Application log for Success or Failures related to Windows SharePoint Services Search Service
On Failures try next step.
1. Open a Command prompt
Browse to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
stsadm -o provisionservice -action stop -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"stsadm -o provisionservice -action start -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"
stsadm -o spsearch -action stop
From SQL Server Management Studio backup & remove Old WSS_Search databases
stsadm -o spsearch -action start -farmserviceaccount [Domain\user]-farmservicepassword [Password] -databaseserver [SQL Server\Instance] -databasename [New WSS_Search DatabaseName]
Note: Replace above parameters with proper values
2. Run following from command prompt Before Reboot
net stop sptimerv3
net stop spsearch
sc config sptimerv3 start= disabled
sc config spsearch start= disabled
Run following from command prompt After Reboot
sc config spsearch start= demand
sc config sptimerv3 start= auto
net start sptimerv3
net start spsearch
3. From Windows Explorer go to backup cache.ini file from following location
C:\Documents and Settings\All Users\Application Data\ Microsoft\ SharePoint\ Config\
Change the contents of cache.ini to 1
From command promptnet stop spsearch net start spsearchstsadm -o execadmsvcjobs
4. psconfig -cmd secureresources
attrib -s %windir%\tasks.
Go to Properties of windows\tasks folder and add wss_wpg and wss_admin_wpg groups and give the full control permissions.
5. Repair MOSS from Add/Remove programs
Reboot server
Run PSCONFIG without changing any settings
NOTE: Do not perform following step if you want to use Network Service as SharePoint Service Account on SingleServer Installation with SQL Internal Engine
6. Central Admin>Operations>Servers in Farm
Note down the Configuration Database name
Run PSCONFIG Disconnect from Configuration Database
Run PSCONFIG Reconnect to same Configuration Database disconnected above.
Note: After every troubleshooting step run following command
stsadm -o spsearch -action fullcrawlstart
& monitor Eventviewer>Application log for Success or Failures related to Windows SharePoint Services Search Service
On Failures try next step.
1. Open a Command prompt
Browse to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
stsadm -o provisionservice -action stop -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"stsadm -o provisionservice -action start -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"
stsadm -o spsearch -action stop
From SQL Server Management Studio backup & remove Old WSS_Search databases
stsadm -o spsearch -action start -farmserviceaccount [Domain\user]
Note: Replace above parameters with proper values
2. Run following from command prompt Before Reboot
net stop sptimerv3
net stop spsearch
sc config sptimerv3 start= disabled
sc config spsearch start= disabled
Run following from command prompt After Reboot
sc config spsearch start= demand
sc config sptimerv3 start= auto
net start sptimerv3
net start spsearch
3. From Windows Explorer go to backup cache.ini file from following location
C:\Documents and Settings\All Users\Application Data\ Microsoft\ SharePoint\ Config\
Change the contents of cache.ini to 1
From command promptnet stop spsearch net start spsearchstsadm -o execadmsvcjobs
4. psconfig -cmd secureresources
attrib -s %windir%\tasks.
Go to Properties of windows\tasks folder and add wss_wpg and wss_admin_wpg groups and give the full control permissions.
5. Repair MOSS from Add/Remove programs
Reboot server
Run PSCONFIG without changing any settings
NOTE: Do not perform following step if you want to use Network Service as SharePoint Service Account on SingleServer Installation with SQL Internal Engine
6. Central Admin>Operations>Servers in Farm
Note down the Configuration Database name
Run PSCONFIG Disconnect from Configuration Database
Run PSCONFIG Reconnect to same Configuration Database disconnected above.
Subscribe to:
Posts (Atom)
Total Pageviews
-
Issue : You Get "Invalid Client Secret" error even if the same secret key works fine in Postman. Scenario : You are using HTTP...
-
Requirement How to get the Task ID or Plan ID or even Group ID if you are creating a Plan in O365 groups? I was trying to get this for M...
-
Scenario : you have a SharePoint List where a field with 'Person or Group' having multiple entries is selected. you want to send a ...