If using the “Open with Windows Explorer” option in SharePoint is slow use the following procedure to fix this and increase the performance:

1. Open Internet Explorer
2. Go to the Menu “Tools” > “Internet Options” then go to the “Connections” tab
3. Click on button “LAN Settings”
4. Uncheck the box “Automatically detect settings” (culprit)
5. Close and restart all running Internet Explorer processes
6. Restart the “Web Client” Service, if needed.
7. Try it again!

via Open with Windows Explorer in SharePoint (Fix Slow WebDAV Performance on Windows 7 / Vista)

After applying the latest Windows updates for Windows Server 2003, we received many “Timed Out” errors when trying to run content deployment jobs.  The main culprit of there errors seemed to be the OWSTIMER.EXE process and it taking 100% of the CPU… yeah, I know “it’s a pain!”

Anyway, one of the things I did to try and get the issue resolved was to clear out the years of Content Deployment objects that had built up on the target server.

This was a 2 step process:

1. Find all the Content Deployment Job objects in the config database and get their IDs

   select * from Sharepoint_Config.dbo.[Objects]  where [Name] like 'ContentDeploymentJobDefinition%'

2. Run an stsadm command to delete the object based on its ID
   

   STSADM -o deleteconfigurationobject -id "<object id>"

I was able to do some text manipulating and get a really long .bat file that ran for a really long time. When it was done, all the Content Deployment Job objects were gone.

However, it did not seem to fix my issue with OWSTIMER.EXE taking 100% of the CPU.

The solution for that seemed to be narrowing down which Content Deployment Job was causing the issue by disabling them all and then re-enabling them one at a time and deleting the target site collection and doing a full deployment.

I’m not sure which update caused the issue but after doing a Windows Update the OWSTimer.exe job started using 100% CPU on the target server of a content deployment job.

The trace logs showed the following errors:

CSsoResourceManagerCache cannot find SSO connection string value in the registry! Error code is: -2147418113 CSsoResourceManagerCache has set SSO connection string value to be empty …  SSO is not configured any more. Error code is: -2147418113 IResourceManager::Refresh() failed Error code is: -2147024809 ForceRefreshOfSPSResMgr() failed. This may be ok if SSO has not been configured yet and the run-as service gets an access denied Error code is: –2147024809

Thanks to Kerry’s SharePoint Blog for the tip about stopping the SSO service (Microsoft Single Sign-on Service) and setting it to manual.

I ran across an issue this morning that had the Sharepoint WSS Search Server in a “Pausing” state.  I had to restart the Office SharePoint Server Search service in order to resolve the issue.

Now to see if it will complete successfully.

Today, I came across a Windows Service on a server that I inherited. By the name of the service I could tell that it was built in-house and I even found enough information to determine who the developed it.  However, since it was not in the Add / Remove Programs list of the Control Panel, I wasn’t sure how to remove it.  So, I found the following on Geeks With Blogs – Shahed’s Blog:

Recently, I was trying to delete a windows service. Normally it should not be necessary to manually delete a service. Uninstalling an application should remove its associated service (if any).

However, I installed some beta products and a service created by one of the applications was not removed automatically. Its very easy to remove a service from registry if you know the right path. Here is how I did that:

1. Run Regedit or Regedt32

2. Find the registry entry "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services"

3. Look for the service there and delete it. You can look at the keys to know what files the service was using and delete them as well (if necessary).

alternatively, you can also use command prompt and delete a service using following command:

sc delete < SERVICE name>
or to create, simply type
sc create <SERVICE name>

Update:
If you have space in the file path you need to use quotation marks ("). For example: 
sc create "MySQL" binpath= "C:Archivos de programaMySQLMySQL Server 5.1binmysqld.exe"

I used the “sc delete” method to remove the service.

Thanks, Shahed!