Windows Mobile Sync跟踪问题 - 无法使SyncTracer正常工作 [英] Windows Mobile Sync Tracing issue - cannot get SyncTracer to work
问题描述
大家好，
在我的Windows Mobile应用程序上工作了几天使用同步服务我仍然遇到问题。
相应的PC应用程序可以非常快速地下载初始数据并快速处理更新，因此我知道WCF服务器端工作正常。这是WM应用程序似乎有奇怪的速度问题。
我正试图做两件事来解决问题：
1） 让SyncTracer正常工作，我遇到了很多问题用这个。
我按照说明操作并将trace.config.txt文件放入应用程序文件夹中，其中包含正确的内容（显示在本文的底部）。
我已经找到了输出文件的路径，并尝试将trace.config.txt更改为trace.config。
任何运气都没有运气。 我是否必须对应用程序本身执行任何操作才能启用此功能？
我已经看过各种SyncTracer标记并且它们都报告错误。
2）
使用我自己的跟踪我输出的数据来自SessionProgress事件（我也用它来显示进度条）。
最后显示的是部分输出。 各个阶段之间的持续时间是否正常？
有趣的是，辅助同步的速度大约是初始同步速度的2倍，即使在辅助同步中我再次重新连接到WCF服务。
同步设置有3个双向表（在下载到PDA的过程中ALL将为空）和另外16个仅下载表（所有表中的660个记录），它们全部在显示示例中的单个组。
总填充数据库大小为448K。
< span style ="font-family：Calibri">我正在使用模拟器进行测试并获得显示的速度数据我已经停止了所有不必要的程序，并确保模拟器在
运行时处于前台。 span style =""> 通常，第一次同步（在预先填充的数据库上）约为60秒，后续同步约为30秒。
我有以下问题：
1） &NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
任何人都可以指出我正确的方向SyncTracer问题？
2） ;&NBSP;
给定表的数量进行同步时间考虑到这是一个Windows Mobile应用程序，看看是对吗？
如果没有任何基准数字，我很难知道我的应用程序是否运行缓慢或正常！
最好的问候，
Jon
trace.config.txt文件的内容
<？xml version =" 1.0"编码= QUOT; UTF-8英寸？>
< ;配置>
< span style ="">
< traceSettings>
< add key =" FileLocation"值= QUOT; TraceOutputSync.txt" />
< span style ="">
< add key =" LogLevel"值= QUOT; 4英寸/>
< span style ="">
< / traceSettings>
< / configuration>
跟踪输出文件的示例内容
**跟踪级别设置**
错误：错误
警告：错误
Info：False
详细：错误
***********************************
14:07:38同步开始
14:07:43 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:07:51 SessionProgress已触发。阶段：DownloadingChanges
55％已完成
14:08:38 SessionProgress触发。阶段：DownloadingChanges
91％完成–我认为这是本集团的完成过程
14:08:39 SessionProgress触发。阶段：WritingMetadata
100％完成
14:08:39同步完成
同步花了61秒
下载的更改：0
更改上传：0
***********************************
***********************************
14:08:49同步开始
14:08:49 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:08:58 SessionProgress已触发。阶段：DownloadingChanges
55％已完成
14:09:26 SessionProgress触发。阶段：DownloadingChanges
91％完成–我认为这是本集团的完成过程
14:09:26 SessionProgress触发。阶段：WritingMetadata
100％完成
14:09:26同步完成
同步花了37秒
下载的更改：0
更改上传：0
***********************************
***********************************
14:09:31同步开始
14:09:31 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:09:37 SessionProgress触发。阶段：DownloadingChanges
55％已完成
14:10:04 SessionProgress触发。阶段：DownloadingChanges
91％完成–我认为这是本集团的完成过程
14:10:04 SessionProgress已触发。阶段：WritingMetadata
100％已完成
14:10:04同步完成
同步花了33秒
下载的更改：0
更改上传：0
***********************************
***********************************
14:10:09同步开始
14:10:09 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:10:19 SessionProgress触发。阶段：DownloadingChanges
完成55％
14:10:41 SessionProgress触发。阶段：DownloadingChanges
91％已完成–我认为这是本集团的完成过程
14:10:41 SessionProgress触发。阶段：WritingMetadata
100％完成
14:10:41同步完成
同步耗时32秒
下载的更改：0
更改上传：0
***********************************
***********************************
14:10:52同步开始
14:10:52 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:11:02 SessionProgress已触发。阶段：DownloadingChanges
55％已完成
14:11:29 SessionProgress触发。阶段：DownloadingChanges
91％完成–我认为这是本集团的完成过程
14:11:29 SessionProgress已触发。阶段：WritingMetadata
100％已完成
14:11:29同步完成
同步花了37秒
下载的更改：0
更改上传：0
***********************************
***********************************
14:11:32同步开始
14:11:32 SessionProgress已触发。阶段：ReadingMetadata
已完成1％
14:11:38 SessionProgress触发。阶段：DownloadingChanges
完成55％
14:12:04 SessionProgress触发。阶段：DownloadingChanges
91％已完成–我认为这是本集团的完成过程
14:12:04 SessionProgress触发。阶段：WritingMetadata
100％完成
14:12:04同步完成
同步耗时32秒
下载的更改：0
更改上传：0
***********************************
有一份支持文档可以解决您的问题。请参阅
http://support.microsoft.com/kb/973058/en-us 。
您是否介意尝试从
http：//下载刷新的位support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=973058&kbln=en-us 并希望它有助于解决这个问题。
谢谢。
Hi All,
After quite a few days of working on my Windows Mobile application that uses Sync Services I’m still running into issues. The corresponding PC app downloads the initial data pretty quickly and processes updates very quickly so I know that the WCF server side is working just fine. It’s the WM app that seems to have strange speed issues.
I’m trying to do two things to resolve the issue:
1) Get the SyncTracer working, I am having great problems with this. I follow the instructions and have put the trace.config.txt file into the application folder with the correct content in it (shown at bottom of this post). I’ve mucked around with the path to the output file and tried changing the trace.config.txt to trace.config. No luck on any of it. Do I have to do anything to the app itself to enable this? I’ve watched the various SyncTracer flags and they all report false.
2) Using my own tracing I’ve output data from the SessionProgress event (I also use it for showing a progress bar). Shown at the end is some of the output. Is the duration between the various stages normal? Interestingly secondary syncs are about 2 times the speed of the initial sync even though on the secondary syncs I reconnect to the WCF service again. The sync is setup with 3 bidirectional tables (ALL will be empty on the way down to the PDA) and a further 16 download only tables (660 records across all of the tables), they are all in a single group in the example shown. Total filled DB size is 448K.
I am using the emulator for testing and to get the speed data shown I have stopped all unnecessary programs and made sure that the emulator had front stage while it was running. Generally the first sync (on a prefilled database) is approx 60 seconds and subsequent syncs are approx 30 seconds.
I have the following questions:
1) Can anyone point me in the right direction re the SyncTracer issue?
2) Given the number of tables do the times for syncing look about right given that this is a Windows Mobile app? Without any benchmark figures for this it’s very hard to know if my app is working slowly or normally!
Best Regards,
Jon
Content of trace.config.txt file
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<traceSettings>
<add key="FileLocation" value="TraceOutputSync.txt" />
<add key="LogLevel" value="4" />
</traceSettings>
</configuration>
Sample content of my trace output file
** Tracing Level Settings **
Error: False
Warning: False
Info: False
Verbose: False
***********************************
14:07:38 Sync started
14:07:43 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:07:51 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:08:38 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:08:39 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:08:39 Sync finished
Sync took 61 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
***********************************
14:08:49 Sync started
14:08:49 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:08:58 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:09:26 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:09:26 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:09:26 Sync finished
Sync took 37 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
***********************************
14:09:31 Sync started
14:09:31 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:09:37 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:10:04 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:10:04 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:10:04 Sync finished
Sync took 33 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
***********************************
14:10:09 Sync started
14:10:09 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:10:19 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:10:41 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:10:41 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:10:41 Sync finished
Sync took 32 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
***********************************
14:10:52 Sync started
14:10:52 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:11:02 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:11:29 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:11:29 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:11:29 Sync finished
Sync took 37 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
***********************************
14:11:32 Sync started
14:11:32 SessionProgress triggered. Stage: ReadingMetadata 1% completed
14:11:38 SessionProgress triggered. Stage: DownloadingChanges 55% completed
14:12:04 SessionProgress triggered. Stage: DownloadingChanges 91% completed – I ASSUME THAT THIS IS THE FINISH OF THE GROUP PROCESS
14:12:04 SessionProgress triggered. Stage: WritingMetadata 100% completed
14:12:04 Sync finished
Sync took 32 seconds
Changes Downloaded: 0
Changes Uploaded: 0
***********************************
There is a support document what may address your issue. Please see, http://support.microsoft.com/kb/973058/en-us.
Would you mind trying to download the refreshed bits from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=973058&kbln=en-us and hopefully it helps this issue.
Thanks.
这篇关于Windows Mobile Sync跟踪问题 - 无法使SyncTracer正常工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
