Upgrading from FactorySQL to Ignition (when problems arise)

General Discussion
1

Normally, to upgrade from FactorySQL to Ignition, you can just export your FactorySQL backup, and use the legacy upgrade tool in the gateway.

However, for various reasons, this can sometimes fail. This is especially true when Ignition is not installed on the same machine as FactorySQL. In this case, you may not have the .Net framework installed. Installing the .Net 2.0 runtime can help, but sometimes errors persist.

The process of upgrading a FactorySQL project consists of converting it to an XML file, and then importing the XML into Ignition. The tool to convert the file to XML can be run alone, and the XML imported manually. Generating the XML on the FactorySQL machine usually avoids any difficulty.

Instructions:

  1. Download and extract the tool from this link
  2. Run the ProjectConverter.exe app from the command line:
>ProjectConverter.exe old.fdb out.xml

for example…

ProjectConvertor.exe "C:\Program Files\Inductive Automation\FactorySQL\system_database.fdb" "c:\factorysql.xml"
  1. Take the XML file, and load it into the legacy upgrade tool in the Ignition gateway. The page says that it accepts FDB files, but it will also accept the XML.

Everything else about the upgrade will remain the same.

2

anything else I could do to get FactorySQL into Ignition??? This convertor doesn’t want to work on my computer.

3

Is it a computer that has FactorySQL installed? If not, you may not have the .Net 2.0 Runtime installed. Try installing from that link and see if that helps.

If you still can’t get it to work, I can create a support ticket that will let you upload the file to us, and I can convert it here.

Regards,

4

Still couldn’t get it to work.

5

I’ve PM’d you with a ticket number.

Regards,

6

We’ve also just found a problem with the legacy upgrade tool and Java 7, which would result in the following error during import:
“Type of property value cannot be coerced to the correct type.”

This has been fixed for version 7.3.3.

7

Hi Mike,

The link you have mentioned is not working. Could you please update the correct link to download the tool

it says an error as follows. We are using licensed Ignition

AccessDenied

Access Denied

Q4R08AQ5MXGHJK92

ernKlXJ4qG0zMvTqXnK0vYXDEDvUH315AiUpSQd3T5UvU3D/xNdEp8UxQOtdlIbeRR4jN2PsAGfNGP0VMZ+jn1wNEirF6np4

8

Who is Mike?
The thread is almost 14 years old so I suggest you open a new thread and explain what you are trying to do.

3 Likes
9

I was reffering to Colby.CleggSoftware Development. Apologies for the wrong name.

We recieved the tool from the Ignition support and tried the migration it has only imported the transactions.

10

The too was specifically for FSQL, which was just transactions.

What, specifically, are you trying to do?

2 Likes
11

Thanks Jordan . We migrated the FSQL transactions to Ignition 7 using the Legacy option and then later migrated to Ignition 8.1.25 by exporting the project from Ignition 7 as XML . This really worked well