I am running into the same error upgrading from 2.1.3 to 2.2.1:
'exp_file_watermarks' already existsDid we find a reliable fix?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
June 22, 2011 6:15pm
Subscribe [10]#16 / Jul 05, 2011 8:02pm
I am running into the same error upgrading from 2.1.3 to 2.2.1:
'exp_file_watermarks' already existsDid we find a reliable fix?
#17 / Jul 06, 2011 3:07pm
Hi Michael,
Is it possible you were using the 2.1.4 or 2.1.5 betas at any point? Have you seen this troubleshooting page?
#18 / Jul 06, 2011 3:21pm
Hi, Michael Rog.
What we think is happening is that during the upgrade, something causes the update to have issues. Not all the time but occasionally.
The update to 2.1.5 is what builds those new tables.
Can you check to see if this was run:
CREATE INDEX field_type on exp_channel_fields(field_type)
Is there a setting similar to this when you use desc exp_channel_fields ?
See attached screen shot.
#19 / Aug 08, 2011 2:14am
Hello Sue,
I am getting the same error while upgrading from 2.1.3 to 2.2.2—Table ‘exp_file_watermarks’ already exists. I used Google Chrome.
I checked before the upgrade, and the table was certainly already there in 2.1.3 (and no, this was not a restore from a failed upgrade attempt where I forgot to drop all tables first).
Rgds,
Bernhard
#20 / Aug 09, 2011 10:30am
Hi, bfrei.
It wasn’t in EE 2.1.3 - see the attached screen shot from EE 2.1.3. Watermarking didn’t show up until at least 2.1.5 beta, and 2.2 was when it was non-beta.
#21 / Aug 09, 2011 11:58pm
Hi Sue,
I guess you’re right. It’s strange. The CP shows 2.1.3, Build 20110411. Could it be that the version information was not upgraded? I may have upgraded to 2.2.1 (I never downloaded any version in between after 2.1.3) and forgotten about it.
Regards,
Bernhard
#22 / Aug 11, 2011 4:47pm
Hi there bfrei,
Are you still experiencing any trouble updating?
Cheers,