Hi,
I am stumped about the Active Directory Authority Service regarding sharepoint, as I want to have a proper installation of Sharepoint connector else not at all. Some of my queries are. 1) Why does LCF need domain controller's Admin username and password? 2) Does LCF Assume domain controller's Admin username and Password will be same as AD DS username and password ? Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, June 01, 2010 5:31 PM To: [email protected] Subject: RE: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 No, it's not a bug. The issue is that, for SharePoint 3.0, the connector expects you to have deployed a custom webservice on the SharePoint server. This service allows the connector to obtain security information for folders and files, not just libraries. The "How to build and deploy" describes the reason for the existence of this custom webservice. Since you are operating without security, and since the only difference between SharePoint 2.0 and SharePoint 3.0 as far as the connector is concerned is the existence of this additional custom web service, then you may safely select SharePoint 2.0 and everything should work for you. Karl -----Original Message----- From: ext [email protected] [mailto:[email protected]] Sent: Tuesday, June 01, 2010 7:22 AM To: [email protected] Subject: RE: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 Hi, Yes going to http://ctsinbtpvmtech0:2122/_vti_bin/webs.asmx will show this webpage The following operations are supported. For a formal definition, please review the Service Description. CreateContentType CustomizeCss DeleteContentType GetActivatedFeatures GetAllSubWebCollection GetColumns GetContentType GetContentTypes GetCustomizedPageStatus GetListTemplates GetWeb GetWebCollection RemoveContentTypeXmlDocument RevertAllFileContentStreams RevertCss RevertFileContentStream UpdateColumns UpdateContentType UpdateContentTypeXmlDocument WebUrlFromPageUrl. And I found one more weird thing. When I change the sharepoint version to 2.0 instead of 3.0(3.0 is what I need) the status is connection working! But it won't work if the Server version is 3.0. Is it a bug ?? Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, June 01, 2010 4:08 PM To: [email protected] Subject: RE: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 OK, so this is not SharePoint "Global Security", but rather LCF's. Can you try going to: http://ctsinbtpvmtech0:2122/_vti_bin/webs.asmx ... and see what you get? It is possible that this SharePoint has access to its web services disabled, which is why you are seeing the 302. Karl ________________________________________ From: ext [email protected] [[email protected]] Sent: Tuesday, June 01, 2010 12:46 AM To: [email protected] Subject: RE: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 Hi, I didn't not use any Authority Service to connect to the Sharepoint. Authority Service needs domain controller's admin username and password which I am unable to procure at the moment, Therefore I selected "Authority" as "None(Global Security)" and after I did wire level debugging I got to know that it was some security issue with IIS, Even when I used the admin username and password of the machine where the Server is installed. And secondly when I enter "http://ctsinbtpvmtech0:2122"; I am taken to " http://ctsinbtpvmtech0:2122/default.aspx"; Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, June 01, 2010 4:43 AM To: [email protected] Subject: RE: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 What do you mean by "Global Security"? When you use a browser, and enter the URL "http://ctsinbtpvmtech0:2122";, what do you see? Specifically, when the page is done loading, what is the URL displayed? The SharePoint connector is tested against SharePoint 3.0, but it's a pretty plain-vanilla installation, secured only with NTLM. The connector attempts to communicate via SOAP to the web services in the _vti_bin area under the SharePoint root site. It sounds to me like one of the attempted web service communications is getting redirected for some reason. The possible reasons I can think of are: (1) The url in question in fact redirects to a different url. (2) The credentials are incorrect, and SharePoint issues a redirection for that reason. Thanks, Karl ________________________________________ From: ext [email protected] [[email protected]] Sent: Monday, May 31, 2010 1:26 AM To: [email protected] Subject: HTTP 302 Error when using LCF to connect to Sharepoint 3.0 Hi, I am using Global Security to connect to Sharepoint 3.0 Site and I get this error "Connection status:Unexpected http error code 302 accessing SharePoint at http://ctsinbtpvmtech0:2122: (302)Found" The Site is http://ctsinbtpvmtech0:2122/default.aspx The Screenshot is... [cid:[email protected]] Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001 [email protected]<mailto:[email protected]> This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful.
