Internet Security and Acceleration Server 2004: An Internet Security and Acceleration Server configuration or Forefront Threat Management Gateway configuration becomes corrupt when you edit the configuration in two management consoles

SUPPORT SOLUTION:
You try to synchronize a configuration in Microsoft Internet Security and Acceleration Server (ISA) or Microsoft Forefront Threat Management Gateway (TMG). However, you may receive an error message that resembles the following:Upload New Configuration to Services Failed.
The ISA Server configuration agent was unable to upload the configuration to the ISA Server services.
This could be due to a corrupt configuration. The ISA Server configuration agent is reverting the configuration back to the last known configuration.
The service that failed to load the configuration is: fwrsv.
The failure is due to error: The data is invalid.If this issue occurs, you may find that the To or From fields in a policy rule is blank. When you try to view the properties for the rule, you receive an error message that resembles the following:ISA Server cannot load the property page.
Error: 0×80070002
The system cannot find the file specified.When you try to export the configuration, you may receive an error message that resembles the following:A failure occured. The task was not activated.
Error: 0xc0040357If you try to synchronize the configuration from a member server, you may receive an error message that resembles the following:0×8007000d (ERROR_INVALID_DATA).This issue may occur if you connect two management consoles to the same ISA or Forefront TMG array and then change the configuration in both consoles..To work around this issue, do one of the following:Try to export the configuration. When the export fails, note the corrupted policy rule in the error message. Delete this rule, and then apply the changes.Make all the configuration changes from the same computer.Note To prevent this issue, you may have to set the maximum number of Terminal Services connections to 1..Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section..Steps to reproduce the problem

Open an ISA console. Create a domain name set, and then apply the change. Do not close the console.Open a second ISA console, and then create an access rule that references the domain name set that you created in Step 1. Apply the change, and then close the second ISA console.In the first ISA console, delete the domain name set. Apply the change, and then close the first ISA console.Open a new ISA console. You should be aware that the access rule that you created in step 2 does not include the domain name set.Try to export or synchronize this configuration from a member server..

For File Repair and Data Recovery, visit File Repair / Data Recovery