Solved

ISA 2004  - 06 Upgrade - Setup error - export config

Posted on 2007-04-11
9
358 Views
Last Modified: 2012-05-05
Hi All

We are trying to upgrade our ISA 2004 Server to 2006. When i try to run the upgrade i receive the error - "Setup failed to export the configuration required for this upgrading the product"

Notes - I am able to connect to the sql server using OSQL, but the service is not shownn in the SQL server agent in teh system tray.
The setup is a test system with windows 2003, sp1, ISA 2004, and settings imported from live machine.
The machine has a domain IP address, but is not part of the domain
Both Message Screener and Firewall Client Installation share are not installed ( As 2006 does not support these)

Any ideas.
Regards, Alan
0
Comment
Question by:Singnetsvc
  • 5
  • 3
9 Comments
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 18889251
Not sure of which version of ISA you are running so here is the upgrade guide for both. You will note that there are a number of pre-requisites you need to meet. Are you following these?

ISA2004 Standard version
http://www.microsoft.com/technet/isa/2006/upgrade_guide_se.mspx
ISA2004 Enterprise Edition
http://www.microsoft.com/technet/isa/2006/Upgrade_Guide_EE.mspx

Regards

Keith

0
 
LVL 3

Author Comment

by:Singnetsvc
ID: 18889437
Hi Keith

I have already followed these steps, which is why I specified the other information under "notes" above.

The error code which is specified in the setup log file is 0x80070643, but searching for this code only finds articles relating to WSUS.

I have run a repair on the installation and reinstalled with sp1, but still the same error.
0
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 18892260
Just so I am clear, you are not yet trying the upgrade on the production system but on a replica test system, correct?

Are there any substantial differences between the test system and the production system?
Presumably the machine names are not the same for example if you are using the same ip infrastructure otherwise you'd have had a clash with Netbios conflicts etc.

If you backup the existing config before you start and then run the network template wizard so it creates a clean setup, does the upgrade on the test box work OK then?
0
 
LVL 3

Author Comment

by:Singnetsvc
ID: 18896451
To confirm

We are actually testing the upgrade process on a test machine first. the test machine does have an ip address of the domain, but has not been added to the domain.
The only differences between the two machines are the host name and the fact that the test is running under virtual Server ( This should not affect the operations )

For some reason i keep thinking that the issue could be with accessing the Database MSFW.
We did export the config from the live machine and import to the new machine, so that we were not importing any information that was machine specific

We did try setting up a new box with ISA 2006, and importing the data. This failed with an error code i dont actually remember which is why we are trying to d a direct upgrade

Regards, Alan
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 18900348
The .xml file that is exported includes the machine name as far as i recall

On the test box, run up the best practice analyser and lets make sure it is clean on 2004 before you start. In the meantime I will edit my 2004 version files and see what is listed.
http://www.microsoft.com/downloads/details.aspx?FamilyID=D22EC2B9-4CD3-4BB6-91EC-0829E5F84063&displaylang=en
0
 
LVL 3

Author Comment

by:Singnetsvc
ID: 18904024
I wanted to make sure that the test box was not the issue, so i recreated the windows 2003 installation with SP1 then installed ISA 2004 Clean +SP1

I imported the .xml file again and tried the update again but go the same error.
So i started again fresh, installed ISA 2004 then added a few custom configurations and rules, updated to 2006 with no issues.

I beleive the problem could be caused by importing the xml file which does not include user information and confidential information.

If i was to upgrade our live box, and the same error happened again, then the pre-installation would fail, but would not attempt to install ISA 206, which should leave the box intact.

What would you suggest?
0
 
LVL 51

Accepted Solution

by:
Keith Alabaster earned 500 total points
ID: 18906950
This was the point I was trying to make earlier albeith badly may be. The xml file holds information that identifies the installation.

<?xml version="1.0" encoding="UTF-8" ?>
- <fpc4:Root xmlns:fpc4="http://schemas.microsoft.com/isa/config-4" xmlns:dt="urn:schemas-microsoft-com:datatypes" StorageName="FPC" StorageType="0">
  <fpc4:Build dt:dt="string">5.0.5720.157</fpc4:Build>
  <fpc4:Comment dt:dt="string" />
  <fpc4:Edition dt:dt="int">16</fpc4:Edition>
  <fpc4:ExportItemClassCLSID dt:dt="string">{E603489F-FA78-41CA-ADFE-EDC572C944DE}</fpc4:ExportItemClassCLSID>
  <fpc4:ExportItemScope dt:dt="int">0</fpc4:ExportItemScope>
  <fpc4:ExportItemStorageName dt:dt="string">{44AB1BB3-7A68-4682-986F-E8DF7179AC72}</fpc4:ExportItemStorageName>
  <fpc4:IsaXmlVersion dt:dt="string">5.30</fpc4:IsaXmlVersion>
  <fpc4:OptionalData dt:dt="int">14</fpc4:OptionalData>
  <fpc4:Upgrade dt:dt="boolean">0</fpc4:Upgrade>
- <fpc4:Arrays StorageName="Arrays" StorageType="0">
- <fpc4:Array StorageName="{44AB1BB3-7A68-4682-986F-E8DF7179AC72}" StorageType="1">
  <fpc4:Components dt:dt="int">62</fpc4:Components>
  <fpc4:DNSName dt:dt="string">keiths</fpc4:DNSName>
  <fpc4:Name dt:dt="string">keiths</fpc4:Name>
  <fpc4:Type dt:dt="int">0</fpc4:Type>
- <fpc4:Servers StorageName="Servers" StorageType="1">
- <fpc4:Server StorageName="{3339C8CF-EB11-4045-9D87-45965CCC6295}" StorageType="1">
  <fpc4:FQDN dt:dt="string">keiths.internal.com</fpc4:FQDN>
  <fpc4:FwUserName dt:dt="string">Dummy</fpc4:FwUserName>

This is just a sample from one of my test systems and you will note that the .xml holds the domain info, server info even container info; it is not really for transferring between completely different setups; its more to let you recraete the box and then put the config back on after a rebuild or a quick restore to a previous config on the same system. I have to say my in-place upgrades from 2004-2006 have gone without a hitch which is more than I can say for isa2000 - isa2004 sometimes.

Perform the full ISA config export on isa2004 production and save the file to memory stick or somewhere off machine as well. Do the upgrade to 2006 - if you end in problems, fully remove ISA then reinstall isa2004 plus what ever service packs/updates you have now then reimport the config.

As ISA is the main system I support I am consatntly swapping between versions (2004/2006) both upwards and downwards depending on the questions I am working on and to date all is OK. Arrays are a little more tricky but single boxes are good to go.

Regards
keith
0
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 19059214
Thank you :)
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

In all versions of ISA Server and the current version of FTMG, the default https protocol uses TCP port 443 and 563 only. This cannot be changed within the ISA or FTMG GUI and must be completed from a Windows cmd prompt on the ISA Server itself. …
There are several problems reported according slow link speeds or poor performance in TMG 2010, UAG 2010 or ISA 2006. I want to collect here some of the common issues together to give a brief overview what can be the reason. Nevertheless, not all of…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now