InfoPath Dev

I just downloaded and successfully installed the Qdabra software. I installed it on a WSS 3.0 box and we are using Office 2003. On the WSS box I am able to successfully hit the AD web service url  - http://mydomainname/qdabrawebservice/aduserinfo.asmx. I am prompted for credentials and, when entered, I can get to the list of methods. I am then able to successfully invoke the GetMyInfo method, obtaining the expected results. Next I go over to my InfoPath form and set up a Data Connection - successfully. Lastly, I follow the steps to populate the default value of a field using 'Value[Key = "name"]'. When I preview the form or launch a new instance of a form published to a SharePoint form library the field is blank - I get no results from the service call. I am not getting an error (though I haven't checked logs) so I assume everything is set up correctly. Any ideas? I am so close! I am thinking it is a security issue but where should I look?

Hi Twirlaround and welcome to our forum,

Thanks for taking the time to donwload and install our software. You have specified the set field rule correctly and it should work, but if you are setting the default value for the field, please make sure that the data connection has been queried first. Go to Tools->Data Connections and modify the GetMyInfo connection. Click next until you ge to the dialog with the checkbox that says "Automatically retrieve data when form is opened". Make sure that is checked. If it wasn't, that explains your problem. If it was checked, then the rule you have created may not be running. Did you double click on the field in the view and add the function Value[Key = "name"] to the Value field under Default Values? Did you add it by clicking on the Fx and walking through the dialog to insert the field and choose and filter it, or did you just type it in. Note, it won't work if you just type it in. You need to go through the wizard to select. Hope this helps!

Thanks Patrick. Unfortunately still no results. In answer to your questions:

1. Checked the Data Connection and the "Automatically retrieve data..." setting was already checked. I even tried remove and recreating the connection from scratch.
2. The function you listed is exactly what shows up in the Default Value setting for the field. I did not type it in - I created it via the Fx button, following the subsequent dialog boxes. In the settings field it does show underlined - signifying that it was not typed in.

Any other suggestions? As I said before, I am able to get results from the server (Dameware'd into the box) using the localhost call. I am thinking that this is a security issue but I don't know what to check. Any help would be appreciated.

OK, so it worked on the server. That's a key piece of info. And you can get to the Web service from the local machine, so it should work. Is the local machine joined to the domain where the web service is running?

To clarify, Qdabra is installed on the same box as WSS 2003, and I installed it as a Virtual Directory off of the SharePoint website. The installation created an Application Pool with the Identity set to Predefined: Network Service. Additionally, for the virtual directory the Authentication Method is set to Integrated Windows authentication and Anonymous is unchecked. From a browser instance on the server when I call the web service I am prompted (Windows challenge/response dialog) for my credentials. When I enter them I receive the AdUserInfo page with the Invoke button - which does return my information when pressed. From my local workstation I am also able to call the web service and I do receive the AdUserInfo web page. This time I am not prompted for credentials and the page does not display the Invoke button. Does all of this seem correct?

Regarding the local machine, I log into a domain called Domain A (for purposes of illustration) when I boot my machine. The SharePoint server is in Domain B. When I invoke the SharePoint site from my local machine it does authenticate me using Windows Integrated Authentication - against Domain B. The two domains are trusted - though I am not sure if they are "joined" as I am not an AD person.

Regarding the calling of the Qdabra service, I have a SharePoint form library from which I launch the InfoPath form. I want to pick up the user's information (the user who launches the form), based on their SharePoint credentials. Is there anything else I should be doing? Are there additional configuration or security settings that I need to be aware of? I am assuming, based on what I have written in paragraph 1 above, that the Qdabra would pick up the user's credentials and then make the attempt to query AD on Domain B. And since the Qdabra software (virtual directory) is configured to use Windows Integrated Authentication the Windows user would need to have read access to query the domain - correct?

Any help or clarification would be appreciated.

Hi can you trying changing AD to use the global catalog ("GC") instead of the "LDAP" (local directory) in AD?

syntax should be something similar to GC://abc.abc.com  instead of LDAP://DC=abc,DC=xyz,DC=123,DC=com

 Ted

Ted ---

I did as you suggested and I am still getting no results. With this change I am still able to call the web service page, while Dameware'd into the server, and I do get results. However, when I go back to the InfoPath form I get no results. Is there a Qdabra/Web Service log file I can check to see if the there was an error and, if so what it was? I am still a bit unclear as to how the web service is obtaining credentials and what identity is being used to make the call into the Global Catalog. When I am on the server itself and go to the aduserinfo.asmx url I am asked for credentials - so obviously it is not using my Windows credentials (the browser does have Windows Integrated Authentication enabled). Once I put in a username and password I get the page with the Invoke button - which, when clicked, does return my information. Is that correct behavior? Any other suggestions?

No way!  You're from my hometown (actually, I'm from Morris Plains, but I went to Morristown High).

 One more thing you can do to verify whether or not the form is receiving the data is to select the GetMyInfo data source in the taskpane, drag the ADProp node onto your form, represent it as a repeating table, and preview the form.  If the form is getting the data, the table should be populated with all the values, and if that's the case then it's likely that the form just needs a little tweak to start working right.

Please give that a try and let us know how it goes.

To answer your other question, there is an error log, and it can be accessed via Control Panel -> Administrative Tools -> Event Viewer.
Most DBXL bugs should be in the Qdabra log, but it's worth checking the Application log just in case.

Jimmy -- Thanks for your response and suggestions, as well as to everyone else who has helped on this problem. I was actually able to get this to work and I just haven't had a chance to post back to the forum. The fix was a combination of security rights to the catalog, along with setting the correct path to the catalog itself. You see in our organization there are actually two A.D. forests - turns out that I was setting the path to query Forest A while I was logged in with an id that only existed in Forest B. I was aware of the 2 forest issue (which I won't go into details on, but it is a situation that will remain in this organization due to structure of the company and its internal clients) but my assumption all along was that there somehow, somewhere existed a consolidated catalog. I was wrong. So, once I changed the query path to the correct catalog I got results without a problem. Everything was set up correctly all along in the InfoPath form, I just wasn't getting results because that user couldn't be found.

Now, because of this I am trying to find a way to work around the 2 forest problem. Unfortunately I will always run into a situation where the incoming user could be logged in to a Domain in either Forest. So, in the C# code behind I am trying to write a routine that queries Forest A first (since 90% of users will come in via that route) and if the results are null, try to query Forest B. In theory this should work but it is going to force me to load Qdabra onto separate servers. This is the piece I have not done so far. Has anyone else ever encountered a similar situation or have any other suggestions?

 Bobby

PS. Jimmy, I actually live in Florham Park, a couple of towns over from Morris Plains, and I work in Morristown. Great areas but it is getting hard to stay here due to high taxes and the overall high cost of living in this area. Are you really in Japan? That is a far cry from Central NJ!

Yup, I really am in Japan, but I spent 16 years plus 4 summers in Morris County.

 Glad to hear that you figured out what the trouble was, and your idea of using DBXL on two servers sounds like it just might work, though I have not encountered a scenario like that before.

 Best of luck.

Hello,

I'm having an issue where the GetMyInfo isn't working.  A little history: I exported the mapping, template, cat from my laptop where everthing worked fine.  the form would open and the Author and email would populate from values cn and mail from the GetMyInfo data connection.  I imported eveything to a new workstation and the form and mapping look/feel just like the original on my laptop.  EXCEPT that the 2 fields for pre-populating the author and author's email aren't working.  I tried recreating the data connection and Fx but it still won't work.  I went to the aduserinfo.asmx page (http://system/qdabrawebservice/aduserinfo.asmx), go to GetMyInfo and Invoke but only get this in response...

 <?xml version="1.0" encoding="utf-8" ?>

Hi Phil,

Where is the Web service installed? Is the new workstation in the same domain as the machine where the Web service is installed? Is the workstation running Windows XP or Vista? If the Web service is running on a Windows XP machine, you will have to read the config notes in this document: http://www.infopathdev.com/files/folders/installation_and_setup/entry30050.aspx.

Sorry, I don't have a silver bullet, but please do reply with more information and we'll try to help.

Thanks!

Hi Patrick,

This was it.  I forgot all about reregistering aspnet.  Everything looks just fine now.  Thank you for your help!

Phil.