Yes. I have Index Server cataloging the content already and I have a test windows app that queries the content of the catalog using OLEDB. This works fine when I run it on the index server. The problem is that I can't access the catalog from another machine. Is there an easier way???

No, I want to be able to search content. I want to have a form in my application where the user types search terms and I return a list of documents that the content thereof matches the search criteria.

I am trying to find some direction on document searching. We have a Desktop application (VB.NET) and I want to incorporate document searching into the application. The application runs on a terminal server and accesses a standalone SQL server. I am currently looking into using the Indexing Service on a file server to index the documents(and possibly Exchange)) and then I will query the catalog(s), either directly from my application or, from my SQL server. When searching this topic I find that almost all of the discussions/examples revolve around web sites and searching web content. There seems to be no mention of doing this for a desktop application. Am I on the right track? Any pointers on: -Querying index catalogs (VB.Net)? -Running SQL queries on remote index servers -Performance. -Other options...

I get a SOAP envelope with the following: - - - soapenv:Server Unsupported Request + - 7 Unsupported Request

I have been supplied a URL from a web service I want to use. The URL is a directory and not an asmx file as the endpoint. When I try to create a service reference to the service I get the following error: There was an error downloading 'https://www.mlc.com.au/epi/episervices'. The request failed with HTTP status 404: Not Found. Metadata contains a reference that cannot be resolved: 'https://www.mlc.com.au/epi/episervices'. There was no endpoint listening at https://www.mlc.com.au/epi/episervices that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The remote server returned an error: (404) Not Found. If the service is defined in the current solution, try building the solution and adding the service reference again. The owners of the service insist that this is the address/endpoint. The WSDL file supplied to me has some localhost address. ie. useless. I have been given .xsd files as well as the .wsdl files. The service address is https://www.mlc.com.au/epi/episervices/ How do I create a service reference to this service?