SOLUS Version History

• Solus 2.22 – Released 10th March 2009

This update is to allow SOLUS 2 to execute an addition step when running SIMS upgrades to import files into the Document Management Server.

• Solus 2.21 – Released 12th January 2009

Under certain circumstances FMS upgrades were causing the removal of the FMS sub-folder in the setups folder - This will no longer occur.

This has been resolved in this release.

When performing an SLG upgrade through the user interface SOLUS would force the user to login to a SIMS database before it would continue - this is unnecessary for a SLG only upgrade and has been corrected.

This has been resolved in this release.

• Solus 2.20 – Released 8th August 2008

SOLUS has been updated to allow "/TRUSTED" connections to be used via the Command-Line (Note: the August release of DBUpgrade 2.20 is needed to work in conjunction with this.).

This has been resolved in this release.

• Solus 2.15 – Released 23rd April 2008

Issue #1:
SOLUS reported an error when attempting to connect to an FMS database where the 'FMSConnect.ini' was redirected to a central connection setting file.

This has been resolved in this release.

Issue #2:
A number of users reported a 'Microsoft.net Framework Error - General Network Error' or 'No process is on the other end of the pipe' error message when running SOLUS which would appear before the login screen. This was due to a change in behaviour between SQL server and the Microsoft .net framework. SOLUS has now been updated to cater for this.

This has been resolved in this release.

• Solus 2.14 – Released 19th March 2008

Updating FMS using the /AUTO=Downloadonly parameter, when SOLUS was executed a second time to apply the downloaded update the wizard was not detecting the existing package and starting the download again.

This has been resolved in this release.

• Solus 2.13 – Re-Released 27th February 2008

Two issues were discovered following the release of SOLUS 2.12 for FMS SQL Server updates;

Issue #1:
Users who had already applied FMS patch 1273 were experiencing an error message when logging into the SOLUS wizard.

This has been resolved in this release.

Issue #2:
Updating FMS using the /AUTO=Downloadonly parameter, when SOLUS was executed a second time to apply the downloaded update the wizard was not detecting the existing package and starting the download again.

This is currently a known issue, and will be fixed in the next version of SOLUS. We recommend using /AUTO=DownloadandUpgrade for FMS SQL updates until that time.

• Solus 2.12 – Released 11th February 2008

This version of SOLUS has been released to deliver the following functionality;

SOLUS has been updated to allow the usage of 'SA' credentials when running a SIMS upgrade - Previously when using the /FORCEUPGRADE switch and supplying the relevant 'SA' user name and password, these credentials would only be used to force out open database connections and lock the database for upgrades - from v2.12 (and SIMS February Main Release) onwards SOLUS and DBUpgrade will use these credentials to run the upgrade scripts as well as lock the database.

FMS SQL server upgrades. An issue was discovered post august 2007 that would prevent the a successful upgrade if an FMS upgrade was attempted at the same time as SIMS, this has now been resolved.

• Solus 2.11 – Released 9th August 2007

Two issues were discovered following the release of SOLUS 2.10;

Issue #1:
If the SIMS .ini on the PC running SOLUS had entries for both [FinanceDirectory] & [SIMS Directory] pointing to the same directory (and that directory contained a valid installation of FMS 6.8x) then SOLUS would incorrectly switch into 'Microsoft SQL 2005' login mode and would report a login failure.

Issue #2:
When using the /INFRPACKAGE switch to automatically download the new CCS infrastructure package, SOLUS would report (in the log file) that 'SIMSIN' credentials could not be validated, and would not download the package. (manual download was working correctly).

Both these issues have now been corrected. .

• Solus 2.10 – Released 6th August 2007

This release of SOLUS is to enable the download of the new CCS Infrastructure packages (SQL2005 migration & tools) and for future compatibility with the new SIMS security model.

• Solus 2.09 – Released 1st June 2007

Bug fix release to resolve an issue where the download and application of patches with an ID number greater than 9999 were being reported as successfully applied even if the download had failed.