Workflow fails to serve InfoPath form after SP2 upgrade

Tue, 23 Jun 2009 21:54:22 Z

We have a MOSS 2007 server recently upgraded to SP2. It seems that after the upgrade a workflow has stopped functioning. The workflow should start up an InfoPath form, and it does, but with errors. A typical one is:

An error occurred accessing a data source.
An entry has been added to the Windows event log of the server.
Log ID:5566

The log file shows:

System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.GetResponse() at Microsoft.Office.InfoPath.Server…

The form skeleton is displayed, but data which should populate some of the fields is missing. I’m not sure if the error is with the form being served, or with an backend data connection.

The account credentials have not changed, and we have checked the deployment in Solution Management. Was there some security setting which changed with SP2 that might be causing this?

Thanks,

Jim

Workflow fails to serve InfoPath form after SP2 upgrade

Thu, 25 Jun 2009 01:40:08 Z

Please try to disable the authentication loopback check by following the steps below to see if it works:

1. Click “Start”, click “Run”, type “regedit”, and then click “OK”.

2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

3. Right-click Lsa, point to “New”, and then click “DWORD Value”.

4. Type “DisableLoopbackCheck”, and then press “ENTER”.

5. Right-click “DisableLoopbackCheck”, and then click “Modify”.

6. In the Value data box, type “1”, and then click “OK”.

7. Exit Registry Editor.

8. Restart the computer.

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.

Hope this helps.

Lu Zou

Workflow fails to serve InfoPath form after SP2 upgrade

Thu, 02 Jul 2009 19:17:53 Z

Lu Zou,

Thanks for your suggestion. It has apparently fixed the problem.

Best,

Jim