2018-02-28 02:32 PM
I need to upgrade our WFA system from 4.1 to 4.2.
When I launch the Windows installer it tells me that it is going to do an upgrade, then fails with this error (see also screenshot attached):
WFA installation has identified an existing MySQL data directory in your machine. You must delete the existing MySQL data directory and reinstall WFA
What could that mean? (and why not include the name of the offending directory in the message!).
I first moved (renamed) the existing MySQL related directories under D:\NetApp.
Then I renamed the whole D:\NetApp hierarchy.
Then I ran the 4.1 installer and uninstalled WFA.
The 4.2 installer still fails with exactly the same error message! What is it finding that it does not like? Suggestions?
I'm too scared to try a reinstall of 4.1 ... if it also fails with that same error then we'll be in a really bad place :-(
Thanks in advance!
Solved! SEE THE SOLUTION
2018-02-28 09:37 PM - edited 2018-02-28 09:39 PM
Please delete the MySQL directory in C:/Program Data/MySQL
Which is an hidden directory..
Go to View and enable view hidden files and folders
2018-03-01 09:05 AM
Thanks for getting back to me so promptly - excellent help!
Indeed, once I deleted the directory "C:\ProgramData\MySQL" the version 4.2 installation program was willing to continue ...
Unfortunately, after a short time it seems to fail again. This time the error message is:
Installation Wizard Completed. The wizard was interrupted before OnCommand Workflow Automation could be completely installed.
In the InstallShield GUI window, below that message, an empty box is displayed, which looks as if it is meant to contain some more information (see attached screenshot).
I tried this several times, with the same result each time.
I then tried installing 4.1 again. Strangely, the 4.1 install doesn't experience the above problem and seems to have completed. It takes a long time, stopping a couple of times, saying that it has timed out trying to verify things, but after it completes I am able to log in to and use the WFA Web UI.
I then tried the version 4.2 installation again, thinking it might work once 4.1 was already installed. The installer recognises that WFA is already present and says it will perform an upgrade, but then fails just as before with the same "The wizard was interrupted" error.
So it seems as if we have at least got 4.1 working again. However we really need 4.2 for the improved AD/LDAP user authentication support.
Any suggestions on fixing this one? Seen it before? You did great last time!
2018-03-01 09:18 PM
Please provide the machine configuration. This is the first time we are seeing the issue.We will try to reproduce the issue in our setup.
2018-03-02 01:15 AM
Thanks again for taking an interest in our problem.
The system identifies itself as being: Windows Server 2008 R2 Standard Service Pack 1
We are trying to install (actually upgrade to) WFA version 4.2. It should be installed in "D:\NetApp\WFA", where version 4.1 is already installed and functioning.
I believe that the WFA application on this system has been upgraded several times. I think the first version to be installed may have been 2.1 or 2.2.
I attached the screenshot of the InstallShield error already. The following event is logged by Windows when the failure occurs:
Windows Installer reconfigured the product. Product Name: OnCommand Workflow Automation. Product Version: 4.2.3223.
Product Language: 1033. Manufacturer: NetApp, INC. Reconfiguration success or error status: 1603. (hostname_removed) Windows Server 2008 R2 Standard Service Pack 1
I imagine there is a good clue in the fact that I was able to (re-)install version 4.1 apparently successfully (apart from some timeouts) but that the version 4.2 installation fails. That would seem to suggest that something has changed in the InstallShield code ...
Thanks in advance!
2018-03-02 01:40 AM
WFA 4.2 is not supported in Windows 2008R2.
This issue is happening because of MySQL 5.7 which needs a 2013 VC Runtimes and during the install of VC Runtimes on Windows Server 2008R2 machine, a certificate chain need to be established. This certificate chain can be established only when machine is connected to internet.
2018-03-08 05:02 AM
OK, that would be my mistake. Didn't think to check the InteropMatrix - sorry! Though you could consider adding a check of the Windows version to the install program ...
So we will probably deploy a new VM guest with a newer version of Windows and (re-)install WFA there.
Do you have any suggestions regarding migrating the workflow we have developed? What's the best way to do that? Via backup and restore, or via an export? It seems as if I can only export "everything", or individual items?
Thanks again for your support!
2018-03-08 05:19 AM
Export All or Export each. I feel Backup restore is the best option since u will have all your data's.
Regarding Installer Feedback , sure will add check for supported verions in our next release.
2018-03-27 08:16 AM
Well hey, that worked nicely. VM guest has been re-installed with a newer version of Windows and I have installed WFA v4.2 again.
Workflow development can continue ... it should be completed by the end of the quarter ... not long left now. And nothing works ;-(
I.e. volume create in preview mode does complete successfully. But in an actual run, the volume create fails with this error:
'_x0017_', hexadecimal value 0x17, is an invalid character. Line 1, postion 719.
I found other discussions in this forum that suggest this may be caused by having restored WFA from a backup.
Apparently backup+restore does not backup something called a "wfa key". This should be done separately/manually. I didn't do this.
(The information that it necessary to do so is "hidden" under "migration" on page 57 of 70 in the Installation document.)
Is this the cause of my 0x17 error?
Is there an alternative fix/workaround? (the original WFA installation has been overwritten.)
What is a "wfa key" anyway?
Thanks in advance!