Last week I upgrade our DSS-SAM from version 1.2 to 1.3.1. I had already upgraded our software catalog to the May update. The 1.3.1 installer has an older version of the catalog. At the time I did not notice, but the log file shows the following error
Supplied catalog is not newer than catalog already in database.
This catalog is revision 34024, generated on 2011-04-15T00:46:13+00:00 but the
active catalog is revision 34025, generated on 2011-05-16T23:21:46+00:00.
Use the --force option to override.
I am not sure what the --force override is supposed to apply to, the DSS-SAM upgrade or the Catalog upgrade? Will this then override the catalog back to the old version?
The --force option forces the version in the installer to overwrite the existing catalog in the deployment. If you don’t use --force, then the existing catalog will stay in place.
BTW, we released the June catalog today, so whatever you choose to do with the 1.3.1 upgrade, you should update to June anyway.
I experienced a different problem yesterday when I tried to upgrade from 1.2.4 to 1.3.1. During the upgrade I was given an error message that the account I was using for the upgrade did not have sufficient rights to perform the upgrade - I was missing “Create Any Database, Administer Bulk Operations, View Server State, Create Database (Runtime Error)”. The account has SA rights on the BFInventory database. I contacted Support and was basically told I would have to uninstall and reinstall the software losing all of my data (which makes absolutly no since to either myself or my DBA). Has anyone else had this issue and if so - how did you fix it.
Got a call back from Support and we resolved the issue. It appears that both the service account that the SUA services run under and the local SQL accoutn used to access the database need SA to perform the upgrade. The error message was slightly confusing as it only asked for the credentials for the service account. Anyway once we elevated the SQL account to SA the install worked flawlessly.