If you are using STSDEV to create your workflow templates, I bet you’ve run into errors (Most common being “Could not resolve field type”) when executing workflows that reference the workflowProperties object. Turns out that STSDEV does not bind the workflowProperties object to the SPWorkflowActivitationProperties object during activation.
In order to resolve this problem, simple add a OnWorkflowActivated event control to the workflow (if not already present) and under Properties, bind the workflowProperties object (member in your workflow class) in to the WorkflowProperties property (control in workflow) as show below.
(Click image for full size)
SharePoint 2010 RTM English bits went live last week (official launch on May 12). Though it will only be available for general use somewhere in June, you can try out SharePoint Foundation (previously WSS) and SharePoint Server using the links below.
I recently went through the event log on one of my dev servers running 2008 R2 and realized that the Application Server has been quite active in logging errors about not being able to start the following services.
- NetTcpPortSharing
- NetTcpActivator
- NetPipeActivator
- NetTMsmqActivator
The errors were along the lines of what’s shown below.
Error: Installation of [Application Server] TCP Port Sharing failed. Attempt to install TCP Port Sharing failed with error code 0x80070002. The system cannot find the file specified
It turns out that when I updated .Net Framework 4.0 to the latest version, windows did not automatically change the location of the service libraries to reflect the updated version.
To fix this, open the the registry (regedit) and go the following location.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Select the Services listed above and make a not of the file path for the Description, DisplayName and ImagePath keys.
Now open up windows explorer and navigate to,
C:\Windows\Microsoft.NET\Framework64\
and copy the latest version number of the .Net framework (mine was v4.0.30128). Change the version number in the registry keys to match this number and try starting the services manually.
That’s it! The next time you restart the server, your Application Server should be running without any errors!
If you have tried to develop custom definitions/features for SharePoint in Visual Studio (using VSeWSS) and have run into one of the following errors, it’s most likely you have not completed the post-installation checklist.
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8).
This error is mainly due to the WCF HTTP Activation feature not being enabled. Go to you’re Server Manager (or Control Panel -> Add Windows Features) and Install the WCF HTTP Activation feature under .Net Framework 3.0 Features.
After enabling the WCF HTTP Activation feature, if you run into the following error, chances are the service account running the SharePoint Central Administration v3 Application Pool does not have local admin access to the machine you’re trying to deploy to.
VSeWSS Service Logging Error: Access to the path ‘C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\VSeWSS 1.3’ is denied.
Logging failed attempting to write to C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\VSeWSS 1.3\VSeWSS1.3 service.log. This may occur because the VSeWSS WCF Service does not have local administrator permissions.
To fix this error, you need to provide admin access to the service account running the application pool. Most folks have suggested the use of Network Service to run SharePoint Central Administration which is not a good practice (and should be avoided, specially in a production environment). The best way to workaround this is to create a new Application Pool called “VSeWSS” in IIS. Go to Advanced settings in the AppPool and set the Identity to your local admin account. Now, under Sites, select “VSeWSS” and click on Advanced Settings. Change the Application Pool from “SharePoint Central Administration v3” to “VSeWSS” and perform an IISRESET.
You should now be able to deploy your custom features within Visual Studio without a problem.
I guess people are causing too much havock in Twitterland.
I upgraded Visual Studio 2010 from Beta to RC along with the .Net Framework 4.0 and oh my, I’m very impressed by the performance improvements. If you haven’t got it yet, here are the download links.
Happy Developing!
Ever since I discovered jQuery (that’s a couple of years ago) my life has been a joy ride when it comes to developing web apps. So I figured it’s only fair that I start writing about it. I would like to start with one of my favorite plug-ins written by Mike Alsup called Cycle. Among it’s numerous functionalities, I’d like to simply point out it’s ability to tick your tweets in the most basic form.
All you need to do is follow instructions from Twitter to retrieve your tweets using the RSS feed and put them in nested div containers in your page. Then call the following function to start ticking them.
$(function() {
$("div#twitter_feed").cycle('scrollUp');
})
Obvisouly, there’s so much more you can do with it. To get an idea of how this really looks like, take a look at Alsup’s page itself. You can also download the plugin along with some examples to get started.
