Hi and welcome!
I would start with this checklist:
Looks like an access or space issue. Pay particular attention to the sql requirements. Basically, the sql account needs to be SA and owner of the database...
Thanks for your reply Andre.
We run trough the check list already and all settings are correct. We also checked the SQL permissions and the service account used in the upgrade it's both SA and db_owner.
If 'CIX_EPOProductProperties' is the index name, then I do not have that on my table epoproductproperties on my 4.6.6 server...
But it amounts to either that index shouldn't be there or it should be but can't be dropped
I'm not an SQL expert but that index looks like it's present.
Got one of the DBA's to drop that index in the table and the upgrade was successful. We are login a call with McAfee to see what their view is on this.
I'll get back when I have more informations.
Thinking out-loud I wonder if this came from an Sql Engine tuning recommendations exercise.
That index is definitely not there by default, and I can see why the installer would not know what to do with it on upgrade as a result.
Perhaps it would be worth also asking your DBA's if they've submitted any work like that on the ePO DB whilst it was at V4.6.6 ?
Can you be more explicit about the SQL Engine tunning exercise. There were some problems with the ePO DB about 2 years ago but since other upgrades were performed.
I was thinking really of: http://technet.microsoft.com/en-us/library/ms173494(v=sql.105).aspx
But you really do need to be careful about adding, removing or modfiying indexes on the ePO DB outside of ePO or without McAfee recommendation - as you've seen it can cause unrelated issues.
Thanks, i thought that it might be some McAfee article that recommends some SQL tunning.
We are waiting for McAfee support to contact us. I'll update this with their resolution.
If you are using SQL cluster and followed the KB71825 completely.
I suggest to check the database mirroring option is disabled from the Menu/Configuration/Server setting/ user policies / Database mirroring.......
Note: This option is only on EPO 4.6.6 version for the EPO 4.x platform..
Please have a check on this and if this is enabled, disable and then backup epo folder and EPO db and then follow Kb71825 and proceed for upgrade...
Hope this may helps...
Database mirroring.PNG 79.6 K