Login Page - Create Account

Support Board


Date/Time: Thu, 16 May 2024 20:16:18 +0000



Seirra Charts 2148 corrupts Trade Activity log after bar based backtest

View Count: 593

[2020-08-13 00:39:22]
MHC - Posts: 2
When I upgraded from 2146 to 2148 today, I ran into a problem with the new version. After a bar-based backtest, when I open the Trade Activity Log, the Trade Service Log will display a series of error messages of the type: "File version is -1. Expected: 2. File not read and renamed". As a result, I would be unable to view the results of my back-test.

Down-grading to 2146 fixes the problem.
[2020-08-13 01:11:31]
Sierra Chart Engineering - Posts: 104368
We do not see any problem like this. Provide several of the messages from the Trade Service Log and not a fragment of them. We need to see the entire messages.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2020-08-13 01:12:08
[2020-08-13 01:31:53]
MHC - Posts: 2
Okay. (If there is a better way to do this, please let me know. This is literally my first day using the software, and I'm still learning how to use everything.)

After running the back test, the Trade Service Log says:

Auto-trade: Bar Backtest: MSFT Daily #11 | DefaultSpreadsheetSystemForTradingStudy | SellEntry | Bar start date-time: 2020-07-23 00:00:00.000 | SellEntry signal is ignored because a Short position exists or working order quantities indicate a potential Short position, and 'Multiple Entries in Same Direction' is not enabled. Position: -1. Position with all working orders: -1. Position with Market working orders: -1 | 2020-08-13 01:17:01.443
Auto-trade: Bar Backtest: MSFT Daily #11 | DefaultSpreadsheetSystemForTradingStudy | SellEntry | Bar start date-time: 2020-07-23 00:00:00.000 | SellEntry signal is ignored because a Short position exists or working order quantities indicate a potential Short position, and 'Multiple Entries in Same Direction' is not enabled. Position: -1. Position with all working orders: -1. Position with Market working orders: -1 | 2020-08-13 01:17:01.446
Cleared trade data | Symbol: [Sim]MSFT | TradeAccount: Sim1 | 2020-08-13 01:17:01.500

And the Message Log says:
Bar Backtest: MSFT Daily #11 | Back test processing: NumberOfTimesCalculateCalled (Cumulative) = 0 | 2020-08-13 01:17:01.499

Now when I open the Trade Activity Log, the Trade Service Log displays several dozen lines like these:
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2005-10-27_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.049 *
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-01-19_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.054 *
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-02-15_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.058 *
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-03-29_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.060 *
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-04-11_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.063 *
File version is -1. Expected: 2. File not read and renamed to C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-05-22_UTC.Sim1.simulated.data.2020-08-12 202010.corrupt | 2020-08-13 01:20:10.066 *

Afterwards it displays this line:
TradeActivity files query time: 0.231628 seconds. Entries: 737. Current queries: 1 | 2020-08-13 01:20:10.272

The message log has corresponding lines saying the files were successfully moved.
Successfully moved C:\SierraChart\TradeActivityLogs\TradeActivityLog_2005-10-27_UTC.Sim1.simulated.data file to the folder C:\SierraChart\TradeActivityLogs\ | 2020-08-13 01:20:10.049
Successfully moved C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-01-19_UTC.Sim1.simulated.data file to the folder C:\SierraChart\TradeActivityLogs\ | 2020-08-13 01:20:10.054
Successfully moved C:\SierraChart\TradeActivityLogs\TradeActivityLog_2006-02-15_UTC.Sim1.simulated.data file to the folder C:\SierraChart\TradeActivityLogs\ | 2020-08-13 01:20:10.058

Date Time Of Last Edit: 2020-08-13 01:33:42
[2020-08-13 05:34:41]
Sierra Chart Engineering - Posts: 104368
At this point we are not sure why that is occurring. We want you to use version 2150. Instructions:
Software Download: Fast Update

And let us know if you still see the problem.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account