the installer only shows a white screen, or shows a “net452” error
This means that the component Microsoft .NET Framework 4.5.2 needs to be installed on your computer. This is more common on WIndows 7 and older, because the newer operating systems already have this installed automatically.
you get an “oops! we’ve had a problem installing inflow” error message
This means that an unknown error occurred when attempting to install inFlow or one of its prerequisites (eg. SQL server).
You may want to try the following:
1. Check that your computer name and your Windows log on user name are not the same. The installation can fail if this is the case. Go to the Control Panel > System and Security > See the name of this computer > and click on Change Settings in order to change the computer name. This will require a restart.
2. Check that your Windows is up to date: click Start (or hit your Windows Key) > type in Windows Update and click Check for updates. Install any “Important updates” you see and also restart your computer first before trying to install inFlow.
3. Try turning on “.NET Framework 3.5” and “.NET Framework 4.5” fully in Control Panel > Programs and Features > Turn Windows Features on or off. This is a component that’s needed in order to run and complete the inFlow install successfully.
4. Disable any antivirus software which could be interfering with the installation. Usually you can find an icon for your antivirus software in the system tray (bottom-right corner of Windows), and if you right-click on it there’s often an option to disable it temporarily. You can re-enable this after the installation is done.
5. If the installation is failing on a client computer (i.e a computer that only needs to connect to another “main” computer / the server), you can try customizing your installation to “Client-only” (run the installer > Customize my installation > Client-only).
6. If you are using Windows Vista, try to install using SQL Server 2008. At the start of the installation wizard choose to customize your installation, then choose Server and Client, then check SQL Server 2008 R2 and click Install. If you are using Windows 7, 8, or 10, try to install using SQL Server 2014 instead.
7. If you are getting this message while updating from an older version of inFlow to the current version, you may instead want to try backing up your data (see instructions here) and then uninstalling your current version of inFlow. Then install the latest version of inFlow and restore your data.
8. Perform a manual clean up in preparation for the install. See this article for more information on how to do a manual cleanup.
If none of the above work you may want to submit your installation logs to our support team for investigation. You can do that by downloading and running our inFlow Logs Uploader from here. Enter your email address and a brief description of your problem and our support team will get back to you.
you get an error message saying “safari cannot open the file inflowinstaller.exe…”
This means you’re on a Mac and unfortunately inFlow is not compatible with Macs! However it is possible to run inFlow on a Windows environment installed on the Mac itself. You can read more about it here.
you get an error message “you must uninstall the alpha before installing v3”
This means that at one point the inFlow Inventory alpha version was installed on your computer. The alpha program was introduced around the summer of 2013 as a way to test the beginnings of inFlow v3 while simultaneously running inFlow v2. Unfortunately it is not possible to run the alpha and inFlow v3 together so the alpha version must be uninstalled first from the Control Panel. It will show in your programs list as inFlow Inventory v3, simply right-click on it to uninstall.
you get a warning during the installation “there were some errors with updating your data…”
This means that you are upgrading inFlow from v2 to v3 and there were some records in your data that are incompatible with the way records are stored in v3. It does not necessarily mean that the installation has failed. These records have been automatically adjusted in order to successfully update, but the changes might affect your accounting reports. See this article for more information.