kipper's .net, sharepoint, infopath, and c# notes

SharePoint 2010 Error 8313 Dead SearchService.svc

2011-11-29T15:07:00.000-08:00

Search is dead on your SP2010 farm.

You see this error in the ULS logs:

CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)

You also see this error in your server application logs:

SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
Process Name: OWSTIMER
Process ID: 7596
AppDomain Name: DefaultDomain

AppDomain ID: 1
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:2313ae1967844030a54407c13c36d972#authority=urn:uuid:3f2c33a4777749139422ac1249fc9288&authority=https://server:32844/Topology/topology.svc
Active Endpoints: 1
Failed Endpoints:1
Affected Endpoint: http://server:32843/2313ae1967844030a54407c13c36d972/SearchService.svc

You have tried everything that every other blog post, forum answer, KB article has told you to do. You've used your insanely good SharePoint debugging skills, you have rebuilt your search service application (2x) and for some reason this error just won't go away.

I have no idea what causes this, but I know how to fix it.

To know for sure that you are having the same problem as me, find the virtual application in IIS Manager under "SharePoint Web Services" that has the same ID as referenced in BOLD above in the windows application logs. (If you aren't actually doing round robin with this service, it may be on one server and not the other, so check both). See the connection in the pic below to the error above?

Click advanced settings and find the application pool it's running under. Mine was a bunch of crazy letters and numbers, like 71283482842042sdf203402. Go to the application pool under "application pools" and you'll see it is stopped. Am I right so far? Well the problem you are having seems to be an issue with the managed account that app pool is running under not working anymore for some reason. Here's how I fixed it:

Logged into AD users/computers and manually reset the password to something I know.
Logged into WFE and went back to IIS Manager and reset application pool credentials to use new password.
Started app pool and made sure it stayed up
Logged into WFE server and ran SharePoint powershell command: Set-SPManagedAccount -Identity domain\searchapppoolAccount -UseExistingPassword
Updated the services MMC with this new password and restarted the SharePoint Server Search 14 Service (on all machines in the farm)
Now navigate on your WFE server to the URL that I had bolded above and instead of seeing a 503 error, you should now see a nice service WSDL page: http://server:32843/2313ae1967844030a54407c13c36d972/SearchService.svc

No idea what just happened, but it worked. Now, beer.

Error 'CE_OTHER' when trying to convert document to page using the document conversion feature.

2010-05-17T12:47:00.000-07:00

I went back and forth, googling my brains out for a day trying to figure out why I couldn't get document conversions working on my '07 MOSS farm. It turns out that I had to run the "Office Document Conversions Launcher Service" and the "Office Document Load Balancer Service" as the Local System account. Nothing else is good enough apparently. When restarting these services be sure to start the load balancer first, but you probably already knew that since you've been googling your brains out all day trying to find the solution to this. Here's the fun you'll find in the logs on the WFE if you're having this problem:

Requesting launcher from load balancer
Executing method on launcher
Trying to get launcher from load balancer
error code CE_OTHER from the document conversions framework in the callback handler
ScheduledItemEventReceiver:ItemUpdating for item '[page name]
Error 'CE_OTHER' when trying to convert document to page using the document conversion feature.
Failed to generate .
Converting the document to a page failed. The converter framework returned the following error: CE_OTHER
CreatePage: DocumentPagificationException when attempting to convert page: Converting the document to a page failed. The converter framework returned the following error: CE_OTHER at at Microsoft.SharePoint.Publishing.Internal.TransformDoneHandler.Microsoft.SharePoint.ISPConversionProcessor.PostProcess(SPExecutingConversionRequest etr, CreateDCInfo cdti, Boolean& runDefaultPostProcessing) at Microsoft.SharePoint.Administration.SPDocumentTransformDriver.Transform(SPWebApplication wa, ExecutingTransformRequest etr) at Microsoft.SharePoint.SPFile.Convert(Guid ConverterId, String newFileName, String configInfo, String handlerAssembly, String handlerClass, Byte priority, String peopleToAlert, Boolean sendACopy, Boolean synchronous, Guid& workItemId) at Microsoft.SharePoint.Publis

SharePoint Forms Based Authentication on IIS7, Server 2008

2009-11-19T10:34:00.000-08:00

Most tutorials available on the internet for setting up DBA on MOSS are specific to IIS6. I just found a quirk with IIS7 that may slow you down. If you are getting

provider: SQL Network Interfaces, error: 26

and you know that your connection string and connectivity between servers is good, then you may need to force IIS7 to see your new membership and role providers by default. From onenote:

For IIS 7 and forms based authentication, you have to go to your site and specify the default provider for membership and roles in IIS after you have made the additions to the web.config that all the tutorials tell you. The first time you click each, you have to let it try the default and then time out, this takes a minute. Once it has timed out, you click "Set Default Provider" in the right hand column and select your provider. You have to do this for both Roles and Users. Prior to doing this make sure both of your providers appear in the Providers feature of IIS.

Type: SchemaValidationException, Exception Message: Schema validation found non-datatype errors.

2008-08-13T08:47:00.000-07:00

If you get that error when opening an infopath form after programmatically editing the form, you need to set the PreserveWhitespace property to true:

XmlDocument myDoc = new XmlDocument();
myDoc.PreserveWhitespace = true;
myDoc.Load(myInStream);

helpful post on updating infopath form programmatically

2008-08-13T07:26:00.001-07:00

http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/

TaskProperties Null in CreateTask activitiy

2008-08-12T08:40:00.000-07:00

In a statemachine workflow I was building recently, I made the mistake of assigning my TaskProperties in a CreateTask activity to a new Property instead of a new Field (Bind to a new Member tab). Fields get initialized as SPWorkflowProperties objects with all the properties such as Title and AssignedTo instantiated and ready for you to assign values to them in your invoked event. This is not the case with Properties, the Title and AssignedTo sub props won't be accessible because the prop isn't setup as a strongly typed SPWorkflowProperties object yet. Instead, you get "Object reference not set to an instance of an object" when you try to access title or any other sub props. There you go.

Infopath development with Visual Studio 2008 Issues

2008-08-07T10:24:00.000-07:00

Anyone else out there having build and publish weirdness with Visual Studio 2008 VSTO? I can't build my form when the manifest.xsf file is open, yet when it's closed, I can't publish it because the Publish option only appears in the build menu when you have a form open. Anyone know what's up there?

Unhandled exception when rendering form System.Xml.XmlException: 'something' is an unexpected token. The expected token is '<>'.

2008-08-07T10:19:00.000-07:00

if you see something like this in your logs when developing an InfoPath form that is browser enabled in Sharepoint:

Unhandled exception when rendering form System.Xml.XmlException: 'Number' is an unexpected token. The expected token is '='. Line 247, position 673. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ThrowUnexpectedToken(String expectedToken1, String expectedToken2)

... then you have a problem with one of your secondary data connections that is or was bound to a field on your form. delete one by one until you find the culprit, and troubleshoot from there.

statemachine workflow and correlation tokens

2008-08-07T10:08:00.000-07:00

does your first task create just fine, then the second one gives you problems? do you see an error in visual studio when you attach the debugger? you're probably doing what i was doing and assigning correlation tokens for each task to the workflow as the OwnerActivityName. that's what all the examples tell you to do right? well, all the examples also only have one state in which tasks are being created. correlation tokens need to be assigned to the STATE OwnerActivityName! i learned this here: http://blog.goedvriend.com/?p=49