T O P I C R E V I E W |
reneg |
Posted - 16 Apr 2011 : 15:52:38 Ciao,
I've installed EMM 7.1.1.9, and now when i start the software i get this error:
and the software won't work.
Database is ok, if i try to open it with an older version , it works.
Thank you |
7 L A T E S T R E P L I E S (Newest First) |
Alessio Viti |
Posted - 18 Apr 2011 : 10:21:12 Hello guys,
I will investigate.
Thank you! |
KCWhiteKnight |
Posted - 17 Apr 2011 : 14:19:25 I have the same problem when I'm creating a new database and I'm not working on a server. Example: I'm starting with the default databate example. With that open and running I click on new database and the program starts to build the new database and I get this errror message. I have to close down EMM and restart and it opens the new database and is ready to move forward. This error for me just started with then newest release. Before that it worked fine. When I check the database file folder I noticed it has the two databases open and didn't close the example. |
reneg |
Posted - 17 Apr 2011 : 10:12:48 Problem Solved, There was a service connected to the DB in background.
Thank you |
Alessio Viti |
Posted - 17 Apr 2011 : 07:02:13 Please close the connection to the database from the server. with the new release, when XMM start, must add the new fields to the database.
Probably cannot perform this operation because the connection with the server.
This operation is made only once, after that you can re-open the database of XMM from the server again.
Ale |
reneg |
Posted - 16 Apr 2011 : 19:44:06 Tryed to update EMM (the working one) , from 7116 to 7119 and now i have the same error.
Any ideas ? |
reneg |
Posted - 16 Apr 2011 : 19:33:03 i have a server machine with EMM (Now Ver. 7119). The DB is in a shared folder, and i can access from an other PC with EMM 7116 and everything works perfect. So i thought that the problem come with the new version.
Now i'll try to Re-Download EMM and re-install.
Ill let you know.
|
Alessio Viti |
Posted - 16 Apr 2011 : 17:33:29 Seem that the database is "locked" by Admin user in the SERVER Machine...
Is that correct?
Ale |