[FMICParticipant July 31, 2015 at 12:02 pm Post count: 8]

in reply to: .NET Version #20966

Why not make “TickStory” not depend on .NET at all?

I don’t know what language you are developing in, but if you use C or C++, you could with not much difficulty switch to using a Windows API and not depend on .NET!

Not only would it be much faster and more compact, but would function on almost any version of Windows (including Wine) without worrying about the version of .NET installed on the PC.

[FMICParticipant July 21, 2015 at 1:58 am Post count: 8]

in reply to: FXT is being used by another process #19623

Could it be related to .NET version and not OS?

What .NET version are you targeting?

[FMICParticipant July 20, 2015 at 11:09 pm Post count: 8]

in reply to: FXT is being used by another process #19621

I am now confirming for the THIRD time, that no other application is running and that no other process is locking the file!!!!

With regards to disk cache flushing, I’ve previously tested that possibility by forcing a complete system file cache flushing of all drives, but the lock remains active on the file by “TickStory”.

However, If I leave “TickStory” and the “FXT Editor” dialog box window open for approximately 5 to 10 min and then check on the lock status again, by then “TickStory” has release the lock on the file and is then able to save it properly, but as soon as it does this, it locks it again and is not able to save changes for a second time without waiting another 5-10 mins for the lock to be released.

PS! I am a software developer and IT consultant by trade!

[FMICParticipant July 20, 2015 at 2:46 pm Post count: 8]

in reply to: FXT is being used by another process #19619

Yes, I confirm that the 4 steps are just as I have outlined with nothing else being done in between those steps. Had there been any other steps, I would have stated them.

Yes, the Data store is on the same drives as the installation, and both S: and D: are fixed internal hard drives (not removable) and formatted as NTFS.

However, what does the Data Store have to do with it? This is not an export problem, but to do with the “MT4 Data Editor”!

Just as I have stated before, with the help of the “Unlocker” tool, “TickStory” is the only application accessing the file. There is no other access to the file by any other application/process. The fact, that by unlocking the “TickStory” process from the file (with “Unlocker”), allows it to continue with the save operation, clearly indicates, that “TickStory” is the one locking the file for some unknown reason under particular conditions. No other application is to blame.

However, I do agree that some particular environmental differences may be causing “TickStory” to behave is this peculiar manor. If you have a debug version of TickStory which produces a debug log, I would be happy to run it for you on my systems in order to find the problem.

[FMICParticipant July 19, 2015 at 10:53 pm Post count: 8]

in reply to: FXT is being used by another process #19617

The problem is occurring on two different machines, one is running Windows 2008 R2 Standard Server (64 bit) and the other is running Windows 7 Ultimate (64 bit).

In both cases, TickStory was installed to a non-standard folder (i.e. not “Program Files”) and not on the C: drive. On one it as “S:TradingTickstory Lite” and on the other it is at “D:TradingTickstory Lite”.

[FMICParticipant July 18, 2015 at 10:47 am Post count: 8]

in reply to: FXT is being used by another process #19615

There are no special steps. It happens EVERY TIME I use the “MT4 Data Editor” on any “.fxt” file on any drive, whether it is previously set to read-only or not.

Example Procedure:
1. No other application is running, therefore not even the MetaTrader application is open.
2. Open “TickStory” application.
3. Navigate to the menu option “Tools”->”MT4 Data Editor”.
4. Click “Open FXT…”
5. Select any “.fxt” file and click “Open”
6. Change any parameter to a new value
7. Click on “Save”
8. A notification window appears with the message “Error occurred while saving: The process cannot access the file ‘???’ because it is being used by another process.” where ‘???’ is the full path to the “.fxt” file in question.

No work around the problem, I do the following:
9. Press OK to close the error notification on “TickStory”.
10. In Windows explorer, I right-click the “.fxt” file in question and choose the “Unlocker” tool.
11. Enter in the Administrator password as the tool runs in Administrator mode.
12. The process list window is presented where only the “TickStory” is listed as holding the file handle locked.
13. I select that process and click “Unlock”.
14. I return to the still opened “MT4 Data Editor” window and click “Save” again.
15. “TickStory” silently saves the file but does not present any message that it has been saved.
16. I close the “MT4 Data Editor” Window and then call it up again.
17. I reopen the “.fxt” file with the “Open FXT…” and confirm that the data has indeed been changed.

That is it!

[FMICParticipant July 18, 2015 at 3:16 am Post count: 8]

in reply to: FXT is being used by another process #19613

Sorry to “reawaken” an old thread but I’m having the exact same problem. I was however able to find the “culprit” which is none other than “TickStory” itself! 😮

When I got the exact same problem and message, I used the “Unlocker” tool to find out which process was “hogging” the file, and on that list, the only process was “TickStory” itself. So, as a last ditch attempt, I instructed “Unlocker” to unlock the file from “TickStory” itself and then proceeded to click the “Save” button on “TickStory”; and guess what – it worked! The alterations to the file were then saved without the error message. 😀

In other words, this is in fact a BUG in “TickStory” (both in v1.5 and v1.6) and is probably locking the file up in a different thread to the one that is saving the file, causing it to think that “another” process is “locking” it, when it is “TickStory” itself that is causing the problem.

So, I would humbly ask the developer(s) to look into this and fix the problem please, since the work-a-round for the problem is not really that practical. 😥

Should the developer(s) need any further information or technical details, please feel free to contact me directly via email.

[Author]

Posts