MOSS 2007 - C# Protocol Handler

Source code checked in, #81799

Project Collection Service Accounts — Mon, 01 Oct 2012 21:57:23 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #81798

Project Collection Service Accounts — Mon, 01 Oct 2012 21:51:05 GMT

Checked in by server upgrade

Created Issue: A pretty bug in HRESULT code [12157]

SharePointX — Wed, 16 May 2012 20:54:22 GMT

0x0000007A is the correct value of the HRESULT.ERROR_INSUFFICIENT_BUFFER, 0x00000122 is wrong.

New Post: Moving from SharePoint 2007 (x86) to SharePoint 2010

alexlab15 — Thu, 25 Aug 2011 22:01:08 GMT

Bonjour,

je suis absent pour tout le mois d'Aout. Pour toute urgence, contacter Mme.Chantal Lamarre par t�l�phone au 514-920-0020 (poste 282) ou par courriel � l'adresse lamarre@irosoft.com

Merci. Bonne journ�e.

Alexandre Laberge
Analyste principal
Irosoft inc.

3100, C�te-Vertu, bureau 510
St-Laurent (Qu�bec) H4R 2J8
T�l�phone : (514) 920-0020 p. 244
T�l�copieur : (514) 920-0028
Courriel : laberge@irosoft.com
Site Internet : www.irosoft.com

New Post: Issues in 2010 with filter termination

Maxim_Dykhtyaruk — Fri, 12 Aug 2011 13:57:28 GMT

Has your PH passed initialization?

New Post: Moving from SharePoint 2007 (x86) to SharePoint 2010

Maxim_Dykhtyaruk — Fri, 12 Aug 2011 13:56:11 GMT

Hi smithga2000,

Try to build your project for 64bit, it is possible on 32bit environment - just need to setup solution configuration in VS.

New Post: Moving from SharePoint 2007 (x86) to SharePoint 2010

smithga2000 — Thu, 28 Jul 2011 18:22:33 GMT

Guys,

I'm trying to convert our PH to work with Search Server 2010 on Windows 2008 R2 64 bit. I'm using Visual Studio 2008 on a windows 2003 32bit development box. I updated the project reference for Microsoft.Office.Server.Search to v14 (2010) from v12 (2007). I can not get the app to compile. I think it's because this assembly is 64 bit only and VS is 32 bit. Am I missing something? How are you guys getting the code to compile?

New Post: Issues in 2010 with filter termination

crhill1979 — Fri, 15 Jul 2011 19:39:19 GMT

I've ported my 2007 custom protocol handler (which was working perfectly, in both x86 and x64 environments) over to 2010 and am having a vexing issue. No errors are showing up in the mssdmn.exe log, but in the crawl logs I'm seeing "The filtering process has been terminated", and in the Sharepoint logs I'm seeing the following:

07/15/2011 14:44:08.12 mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server Search      Common                        g2em Assert location: d:\office\source\search\libs\utild\memthrow.cxx(98) condition: !"Service caused access violation" StackTrace: at Microsoft.Office.Server.Native.dll: (sig=35b73ac2-5d4b-41d9-b101-286fc6f53dd5|2|microsoft.office.server.native.pdb, offset=203FD) at mssdmn.exe: (sig=196f2ac8-7472-42a3-8e6a-d2a70f144a70|2|mssdmn.pdb, offset=3AE45) at mssdmn.exe: (offset=3B631) at mssdmn.exe: (offset=2DA16) at MSVCR90.dll: (sig=5b26d767-7dfb-4b01-8ebc-7ac00706c1a0|1|msvcr90.amd64.pdb, offset=45129) at MSVCR90.dll: (offset=442D6) at MSVCR90.dll: (offset=449DE) at MSVCR90.dll: (offset=44C1D) at MSVCR90.dll: (offset=4502B) at mssdmn.exe: (sig=196f2ac8-7472-42a3-8e6a-d2a70f144a70|2|mssdmn.pdb, offset=40066) at ntdll.dll: (sig=6192bfdb-9f04-4429-95ff-cb0be95172e1|2|ntdll.pdb, offset=29D0D) at ntdll.dll:...
07/15/2011 14:44:08.12* mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server Search      Common                        g2em Assert ... (offset=191AF) at ntdll.dll: (offset=51278) at mssdmn.exe: (sig=196f2ac8-7472-42a3-8e6a-d2a70f144a70|2|mssdmn.pdb, offset=D36D) at mssdmn.exe: (offset=13ECE) at kernel32.dll: (sig=7fbe5c47-fc10-4c35-925d-71d76a8d4660|2|kernel32.pdb, offset=1652D) at ntdll.dll: (sig=6192bfdb-9f04-4429-95ff-cb0be95172e1|2|ntdll.pdb, offset=2C521)
07/15/2011 14:44:08.12 mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server             Unified Logging Service       c91s Monitorable Watson bucket parameters: SharePoint Server 2010, ULSShipAssert12, g2em, 14.0.4763.0
07/15/2011 14:44:08.12 mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server Search      Exceptions                    cd2u High    Exception caught at                                                             [memthrow.cxx:119] d:\office\source\search\libs\utild\memthrow.cxx
07/15/2011 14:44:08.12 mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server Search      Exceptions                    15y3 High    <Exception><HR>0xc0000005</HR><eip>000000013FA4DB8E</eip><module>d:\office\source\search\libs\utild\memthrow.cxx</module><line>133</line></Exception>
07/15/2011 14:44:08.12 mssdmn.exe (0x1ADC)                     0x04C8 SharePoint Server Search      FilterDaemon                  e4xl High    Exception caught in filter daemon (thread): 0xc0000005                          [fltrdaemon.cxx:4969] d:\office\source\search\native\mssdmn\fltrdaemon.cxx

This looks very similar to the issue that people were seeing when trying to run the code in an x64 environment, but like I said I had made the Pack=0 change quite awhile ago and things have been working successfully on SharePoint 2007 in x64 for a couple of years. It being an Access Violation, it seems like another case of it expecting different-sized memory than what it's getting. Has anyone else had a similar issue?

Chris

New Post: Sharepoint 2010 problems

Maxim_Dykhtyaruk — Thu, 30 Jun 2011 09:36:54 GMT

Well, I solved the problem myself - there were some errors in our Custom Security Trimmer....

New Post: Sharepoint 2010 problems

Maxim_Dykhtyaruk — Fri, 10 Jun 2011 14:15:22 GMT

Hello everybody!

I've finally managed to create installation files and setup PH for SP 2010. And finally it crawled all items from my content source, but I can't find anything that have been crawled (In the PH log all items are green). Could anybody help me - how could I find out what is the reason for that? Sharepoint logs are clear as well...

New Post: MOSS 2007 - C# Protocol Handler on SharePoint 2010

mhompus — Mon, 23 Aug 2010 05:06:45 GMT

SharePoint doesn't delete files from the index on the first crawl, it takes 2 or 3 crawls before SharePoint realy deltes something from the index.

This is at least 2007 behaviour

New Post: MOSS 2007 - C# Protocol Handler on SharePoint 2010

togrean — Sun, 22 Aug 2010 00:03:14 GMT

I cannot get the SharePoint 2010 gather to remove deleted files using the same protocolhandler that works in 2007. is says cannot find file in crawl log, but does not remove it from the index when i search i still find it.

any ideas what might be differnt?

thanks

Source code checked in, #55578

_TFSSERVICE — Mon, 26 Jul 2010 20:06:06 GMT

Checked in by server upgrade

New Post: SharePoint 2010

alexlab15 — Tue, 23 Mar 2010 19:36:23 GMT

Thank you very much for your response. I fixed the problem by registering manually the assembly using the x64 version of regasm :

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm MOSSPH.ProtocolHandler.dll /codebase

Have a good day.

I forgot to say in my earlier post that I also applied the following fix to the code :
http://blog.hompus.nl/2009/07/09/moss_2007_-_c_protocol_handler_errors_fixed/

New Post: SharePoint 2010

mhompus — Tue, 23 Mar 2010 07:26:32 GMT

Just 2 thoughts on the matter.

1. Did you register your DLL from the x86 hive (default) or the x64 hive (manually)?

2. Sometimes I need to de a IISRESET or reboot to get the handler to work for the first time.

New Post: SharePoint 2010

alexlab15 — Mon, 22 Mar 2010 17:26:01 GMT

Hello,

My custom PH made with VS2008 is working fine in Sharepoint 2007 on Windows Server 2003 SP2 x86. I'm trying to move it to Sharepoint 2010 on Windows Server 2008 R2 Standard (x64) and recompiled the sources with VS2010 RC1. The installation was pretty much the same beside these changes :

I ajusted the .reg so that it is added here :

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ProtocolHandlers]
"MOSSPH"="MOSSPH.ProtocolHandler"

Added the content source using this method :

http://httpcode.com/blogs/PermaLink,guid,25e758cd-bdcc-4bfd-972c-af0fb7497c44.aspx

When I do a Full crawl I get this error in the log file :

03/22/2010 12:55:13.25 mssearch.exe (0x0750)
0x1184 Office Search Server  Gatherer   cd11 Warning
The start address mossph://fake.myp cannot be crawled. Context: Application 'Search_Service_Application', Catalog 'Portal_Content' Details: The protocol handler cannot be found. Check that the handler has been installed.   (0x80040d1a)

Not sure why it can't find the protocol handler. Anybody has an idea ? Is it a Sharepoint 2010 configuration problem ? a x86 to x64 problem ? or else ?

Thank you for your time. Good day.

Alex

New Post: SharePoint 2010

alexlab15 — Fri, 19 Mar 2010 01:47:43 GMT

Hi, as anybody installed the Protocol Handler on SharePoint 2010 ? If so, anything different we need to do to make it work ?

Thank you for your time.

New Post: Office 2007 documents

triock — Wed, 10 Mar 2010 22:16:05 GMT

There was an issue with custom protocol handlers and (I believe) container document types such as the new Office file formats, MSG, etc. It is resolved in a post-SP2 rollup (June?)

Our protocol handler works by providing pseudo links to items within our filestore. These links do not have extensions on them, the file type is identified to SharePoint via the appropriate interface method. This was being ignored for container file types. Our workaround was to append the extension to the link for affected file types - it wasn't pretty but it did work.

Again, the issue should be resolved in the latest fix rollups though you might need to talk to Microsoft support to gain access to it.

New Post: Office 2007 documents

ciprian — Fri, 15 Jan 2010 02:56:10 GMT

My only suggestion at this stage will be to re-check your code and also the settings. I assume that you can successfully crawl doc , xls and other types of files.

Cipri

New Post: Office 2007 documents

togrean — Thu, 14 Jan 2010 03:32:33 GMT

ciprian,

i have completed the steps you described above and when i crawl a docx or xlsx i get no errors, and i can search the file via metadata. unfortunatly i am not getting a full text index of the document. in my trace code i see a IFilter is requesting the document chunks (and this works for other document types) but i just does not seem to be doing the cracking of the documents to get its contents.

any suggestions would be appreciated.

thanks