ISA 2004 - 06 Upgrade - Setup error - export config

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
LVL 3
SingnetsvcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Keith AlabasterEnterprise ArchitectCommented:
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
SingnetsvcAuthor Commented:
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
Keith AlabasterEnterprise ArchitectCommented:
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
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

SingnetsvcAuthor Commented:
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
Keith AlabasterEnterprise ArchitectCommented:
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
SingnetsvcAuthor Commented:
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
Keith AlabasterEnterprise ArchitectCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keith AlabasterEnterprise ArchitectCommented:
Thank you :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.