Posted under Sage Accounts
Permalink
Tags Bug, Gotcha, Install, Sage, Tip
Update 15/5/2012
Further to the issues below, whilst I could run Sage satisfactorily for the most part, some features still needed ODBC to be working, such as Invoice preview and VAT return printing.
After a couple of attempts I was able to setup ODBC after the event by running E:\Salient Soft\Accounts\Sage\Instant Accounts\ODBC32\Disk1\Setup.exe. This allowed ODBC setup/install even after Sage had been installed.
Sage was happy even though there was no mention of the ODBC driver or connection for Sage under Administrative Tools/Data Sources (ODBC). The real underlying issue was not discovered, but the problem was finally resolved.
I was then able to successfully print a VAT return and preview invoices, which previously had failed.
Original Post
This was a reinstall using a fresh windows install, but the same location for Sage on a data disk. The following issues were hit:-
- On install, it hung at the point where it said “Setup is configuring the ODBC”
- I tried installing from a shortcut to the CD, with administrator mode set and Windows XP compatibility of various flavours, but the same error persisted.
- I then tried removing the “ODBC files” option from the (custom) install. This changed the problem – the install now hung at the point where it said “configuring MIS files”.
- I then did another custom install removing everything that I did not need, including ODBC, MIS support, E-Banking, web/email templates etc.
- This time, the install finished successfully. Furthermore, Sage ran fine even though I had not told it to “configure the ODBC”.
Note that it is possible that the previous duff installs did configure ODBC and that the final install was dependant on the previous ones to work. This should be borne in mind if trying again. However, all the installed files for Sage were all there anyway as this was a reinstall – I was only doing it to install the windows/registry settings/shortcuts etc. that Sage needed.
I did not try a new install to a new directory as I did not need to – this may have worked, but I cannot say. If so, it may be possible to import or copy the old company data into a new install. A quick look at the menus and a quick google did not reveal any obvious way to do this, but a judicios copy may work.
Note also that this issue did not occur the first time I installed on Windows 7 64. This first time was also an install over an existing Sage installation copied from Windows XP.