InfoPath Dev

I have been ususing the web service sucessfully for about 5 months now, to pull usernames from AD.

Out of the blue I get this error when loading the form in preview mode or to fill out.

The following DataObject either cannot be created or cannot be initialized: GetMyInfo
The query cannot be run for the following DataObject: GetMyInfo
InfoPath cannot run the specified query.
Access is denied.

I don't believe anything has changed on the server end, the service works right from the local server using the tests. I am using a default value of Value[Key="cn"]

Hi BSlaght,
Great to hear that you have been using for 5 months. This is an error due to security in InfoPath preview mode. InfoPath preview mode is special since it has to run local and local is more restricted than domain (but less than "restricted" mode). It's a bit complicated to explain and chapter 6 tries to explain this more in detail. The crux is that local solutions must run with greater security due to people pasting xml links in IE that execute XSN code on your local machine.

You'll have to start the form from the domain site where you published and then attach to the process and debug it. That should work though.

I have recently installed the AD Web Service on a new web server and am yet again experiencing this issue.

The new server is:

Windows 2003 - R2 - SP2
WSS 3.0

I am trying to open our form, but am getting the same error as above.

However this time, if I try to access the following path (http://net3/adservice/aduserinfo.asmx)  I get this error:

Server Error in '/' Application.
--------------------------------------------------------------------------------
Cannot complete this action.
Please try again.

It is like WSS 3.0 is taking over the ADService virtual directory.  However if I replace the "net3" with "vm04" which is the name of the server, the ADService works fine via the web browser, but I still get the error in my first message in InfoPath.

 It is worth noting that these servers were recently upgraded to SP2.  Could this be part of the issue?

 Thanks

Brett

 

 

Hi Brett,

Could be any number of things from cross domain security (is the new server in the same domain as the user opening the form? does making the form full trust solve the issue?) to host header issues resulting from the SP2 reinstall. 

You've been using ADWS for several years. We have a more recent version if you're interested in that, send me an email. I don't think it has anything to do with a bug in ADWS, but it would be good to have you on the most recent version anyway (more features, etc.).

If you want to purchase 1 support incident, I can also have an engineer call you and debug the issue over live meeting.

Otherwise, please investigate whether making your form full trust makes the problem go away. If so, it's likely a domain trust issue. That's my guess. If that doesn't work, we need to check the SharePoint install.

Best regards,

Hi Patrick,

Thanks for the quick reply.  I don't believe it is a domain trust issue as the server and users are in the same domain.  I tried making the form Full Trust, but it either has to be digitally signed or installed before it works when the users pull it down from SharePoint.

I didn't need to do either of these tasks before.  I really believe if I could make WSS3.0 leave the ADService directory alone, we would be in good shape, but for whatever reason I can't seem to make that happen.

 I will send you an email about support incidents and version upgrade.

 Any other advice is still very welcome.

Thanks

Brett