Attempted to open a previously opened tablespace

[Barbara Lazzerini]

Due to a virus I lost all the content of "data" directory and I replaced it with a back up. When I replaced the complete back up eveything was ok and I could access to the data base and the data, but when I replaced the incremental back up I was not able to start MySql Service.
I cannot remember how many things I tried to do, I googled aroud for hours, but nothig.
The problem is with Innodb table. The MyISAM table are ok.
Here is the message that I can read in SERVER-PC.err when I try to startthe service:

*****************
2015-02-27 00:08:08 7148 [Note] Plugin 'FEDERATED' is disabled.
2015-02-27 00:08:08 cc8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-27 00:08:08 7148 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-27 00:08:08 7148 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-27 00:08:08 7148 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-27 00:08:08 7148 [Note] InnoDB: Memory barrier is not used
2015-02-27 00:08:08 7148 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-27 00:08:08 7148 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-27 00:08:08 7148 [Note] InnoDB: Initializing buffer pool, size = 294.0M
2015-02-27 00:08:08 7148 [Note] InnoDB: Completed initialization of buffer pool
2015-02-27 00:08:10 7148 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-27 00:08:10 7148 [Note] InnoDB: The log sequence numbers 314253221 and 314253221 in ibdata files do not match the log sequence number 314324767 in the ib_logfiles!
2015-02-27 00:08:10 7148 [Note] InnoDB: Database was not shutdown normally!
2015-02-27 00:08:10 7148 [Note] InnoDB: Starting crash recovery.
2015-02-27 00:08:10 7148 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-27 00:08:10 7148 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace gazie/gaz_002tesmov2013_2014 uses space ID: 105 at filepath: .\gazie\gaz_002tesmov2013_2014.ibd. Cannot open tablespace gazie/gaz_002tesmov2013_2014ok3aprile which uses space ID: 105 at filepath: .\gazie\gaz_002tesmov2013_2014ok3aprile.ibd
InnoDB: Error: could not open single-table tablespace file .\gazie\gaz_002tesmov2013_2014ok3aprile.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

***************************
PLASE NOTE that if I remove the table above (.gazie/gaz_002tesmov2013_2014 and .\gazie\gaz_002tesmov2013_2014ok3aprile.ibd) the same error is reported on other ibd tables.



While here is the the message reported in the SERVER-PC.err at the startup of the MySQL service before the virus:
**************************
2015-02-19 08:10:18 2668 [Note] Plugin 'FEDERATED' is disabled.
2015-02-19 08:10:19 a84 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-02-19 08:10:19 2668 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-19 08:10:19 2668 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-19 08:10:19 2668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-19 08:10:19 2668 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-19 08:10:19 2668 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-19 08:10:19 2668 [Note] InnoDB: Initializing buffer pool, size = 294.0M
2015-02-19 08:10:19 2668 [Note] InnoDB: Completed initialization of buffer pool
2015-02-19 08:10:19 2668 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-19 08:10:20 2668 [Note] InnoDB: 128 rollback segment(s) are active.
2015-02-19 08:10:20 2668 [Note] InnoDB: Waiting for purge to start
2015-02-19 08:10:20 2668 [Note] InnoDB: 5.6.16 started; log sequence number 314074599
2015-02-19 08:10:20 2668 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-19 08:10:20 2668 [Note] IPv6 is available.
2015-02-19 08:10:20 2668 [Note] - '::' resolves to '::';
2015-02-19 08:10:20 2668 [Note] Server socket created on IP: '::'.
2015-02-19 08:10:20 2668 [Note] Event Scheduler: Loaded 0 events
2015-02-19 08:10:20 2668 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)

***********************

I tryed also the suggestion in --- Bug #67595 Conflicting table spaces upon application restart --- but nothing changed.
The content of the table is really important because used in a contabily application and we need to restore then ASAP.
Please, have you any siggestion?
Thanks in advance