Archive: Posts Tagged ‘SharePoint 2007’

SharePoint Performance Counters Missing

No comments January 19th, 2011

I had a client issue today that I’d never run across before. Their SharePoint Performance Counters were missing from PerfMon, and thier workflows weren’t running. The WorkFlow issue oddly enough makes sense although you wouldn’t think so from first glance. The OWSTimer service for SharePoint uses these performance counters, if they’re missing, you may not notice it from trying to run PerMon, but you’ll definitely notice when your workflows no longer execute. You’ll also start to see errors such as this one in the event view and ULS logs:  

w3wp.exe (0x1674) 0x07CC Windows SharePoint Services Workflow Infrastructure 72fq Unexpected Start Workflow: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. at System.Diagnostics.PerformanceCounter.Initialize() at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly) at System.Workflow.Runtime.PerformanceCounterManager.CreateCounters(String name) at System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService.OnStarted() at System.Workflow.Runtime.Hosting.WorkflowRuntimeService.HandleStarted(Object source, WorkflowRuntimeEventArgs e) at System.EventHandler`1.Invoke(Object sender, TEventArgs e)

Continue reading…

Windows Registry Scripts

No comments January 3rd, 2011

Often we find ourselves looking up the same registry paths and mods over and over again every time we deploy a SharePoint Farm. If we’re lucky we’ll remember to export the registry key after we modify them for use down the road, but of course it either never leaves the server or sits on a media we no longer use. So for my benefit and yours, I figured I’d add the scripts here:

Just copy and paste them into a .reg file and double click, or you can download it (Click the name of the file) from here:

Disable Loopback:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"DisableLoopbackCheck"=dword:00000001

Disable FIPS:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy]
"Enabled"=dword:00000000

Disable UAC:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000000

NothingButSharePoint.com

No comments December 29th, 2010

Check out an awesome new SharePoint site with more SharePoint information than any other site on the web:

NothingButSharePoint.com (NBSP) was started in December of 2010 by combining the resources of three existing sites: SharePointDevWiki.com, EndUserSharePoint.com and SharePoint Joel.com. Our mission is to be the world’s largest SharePoint Community, open to every level of SharePoint user.  By combining sites that are already highly visible in the SharePoint Community, we hope to become a central repository of real world Sharepoint knowledge. NBSP includes the SharePoint Community Calendar, an aggregated list of SharePoint User Groups, Q&A forums and constantly updated content for all levels of SharePoint user.  Dozens of authors are commited to providing content on a daily basis to each area of the site: End User, IT Pro, Developer, Business. Content on the site is created by contributing authors as well as members of the SharePoint Community.  All members of the SharePoint Community are encouraged to submit articles, no matter what their level of expertise.

Preparing W2K8 for SharePoint 2007/2010 Installation.

5 comments December 9th, 2010

The following tweaks can be made to the Windows 2008 Operating System to allow for a smooth installation of SharePoint while increasing the performance of the sites as well:

  1. Remove Internet Explorer Enhanced Security – This option is removed in order to prevent Enhanced Security from interfering with the process of ensuring farm configuration is proceeding correctly

Continue reading…

An error occurred in the form’s rules or code

1 comment July 12th, 2010

The error is referring to a condition limit of 16, meaning there is a hardcoded limit of 16 changes that can be performed on a field without user interaction.  This is actually a very hard limit to hit.  One field would literally have to contain over 16 conditions set within a rule for this error to occur.

The error is likely occurring in the form because a condition of a rule has been applied that is causing an infinite loop that exceeds 16 and the error described is thrown.  The customer should check for multiple “or” statements within a condition that was set on a rule.

You should attempt to change one of the “or” statements to “and” to see if the form still throws this error.  This could be occurring with any condition that is set, but seems to happen a lot when someone uses a lot of “or” statements.