search

googlegsa / sharepoint.v3

Google Search Appliance Connector for SharePoint
5 stars 10 forks source link

Cannot create sharepoint connector instance with Sharepoint 2003 and GSA 5.2 #72

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. installed sharepoint connector interface on a client PC
2. created connector manager in GSA with green light
3. added robots.txt in sharepoint with URL check
4. attempted to create connector instance with proper credentials

What is the expected output? What do you see instead?
I failed to create the instance. Instead, an error "Cannot connect to the 
given SharePoint Site URL with the supplied Domain/Username/Password. 
Please re-enter" prompted
http://www.imgplace.com/image/view/da6b50be9180b0079eb55b7f41d306ca

What version of the product are you using? On what operating system?
GSA 5.2
Windows 2003 with sharepoint 2003
Windows XP with sharepoint connector interface installed, the same machine 
used as a client to access the GSA admin console

Please provide any additional information below.
I have tested the sharepoint portal and find some hints for this problem
With IE, I can access it with the short name, ie http://sharepoint/.
But it will show "Under Construction" if I access it with the FQDN, ie 
http://sharepoint.domain.com.

http://code.google.com/apis/searchappliance/documentation/connectors/...
I have checked the official doc, in order to use FQDN, I need to use 
Alternate Access Mappings with MOSS 2007.
Unfortunately, I found it is a new feature for MOSS2007 but seems nothing 
similar in MOSS 2003.

And from the FAQ, I found this Q&A regarding the integration between GSA 
4.x and Sharepoint 2003.
https://support.google.com/enterprise/faqs?&question=277

I found the doc is 4 years and written for an older version and without 
mentioning things like sharepoint connector. Therefore I would like to 
confirm whether this is compatible with the existing v5.2 GSA.

In addition, according to the doc, there are plenty of changes for the 
templates, therefore I need to confirm the exact procedures and impacts 
before asking the client Sharepoint admin to do the changes.

Original issue reported on code.google.com by cks...@gmail.com on 8 May 2009 at 9:51

Attachments:

GoogleCodeExporter commented 9 years ago 
- For SharePoint 2003 you do not need to make FQDN changes explicitly like MOSS 
2007. 
You should be able to browse the sharepoint site with\without FQDN Name.Please 
check 
your network settings if you are having problems. Connector requires URLs to be 
entered in FQDN format.

-Google SharePoint Connector also accepts URLs in IP address format. Please try 
entering the SharePoint URL in IP address and check if it is able to crawl the 
contents.

- In case of problem, please upload all the connector logs (with log level = 
ALL) 
which will help us in further diagnosis of the problem. Also, let us know the 
connector version you are using.

Original comment by amit.per...@gmail.com on 8 May 2009 at 10:15

GoogleCodeExporter commented 9 years ago 
hi, i would like to know how to change the log level.
which parameter of the tomcat config i should change?

Thanks

Original comment by cks...@gmail.com on 8 May 2009 at 10:29

GoogleCodeExporter commented 9 years ago 
Following are the steps to change the log level: 
------------------------------------------------
1. Go to the directory \Tomcat\webapps\connector-manager\WEB-INF\classes 
2. Open the file "logging.properties"
3. Check if ".level=ALL" if not please set it accordingly.

(sample "logging.properties" file attached)
Note: 
-----
1. You need to restart the connector service for the log related changes to 
take 
effect.
2. You will find all the logs in Folder "\Tomcat\logs". Please attach all the 
logs.

Original comment by amit.per...@gmail.com on 8 May 2009 at 10:44

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Problem fixed after adding an internal FQDN entry in the IIS server.
Thanks very much!

Original comment by cks...@gmail.com on 11 May 2009 at 3:48

GoogleCodeExporter commented 9 years ago 
Closing this issue as the connector is confirmed to be working after the fix 
done by 
the user in his setup.

Original comment by th.nitendra on 30 Jun 2009 at 9:14