Answered by:
Sync Tool Crashes at very end of wizard

Question
-
I just created my Azure account, added a sql database (about an hour ago) and downloaded the sync tool.
When I stepped through the wizard, everything proceeds simply and appears it is all working. I Test the connection it works, it displays a list of tables, I select one table, and then when I select the "Process" the whole program crashes and I am presented with that windows screen that offers to look online. (It doesnt return if I say look on line)
I have tried it several times and crashes each time with no error code and within the first few seconds of starting.
Anyone know how to make this tool work instead of crashing immediately?
If this tool doesnt work, is there another way to upload and sync tables?
I havent really tried any steps because everyhing appears to be working correctly, right up to the time it crashes. The table has three fields, and no key.
THe event log shows this was reported to MS.
Fault bucket 828764339, type 5
Event Name: CLR20r3
Response: None
Cab Id: 0
Problem signature:
P1: syncprovisionwizard.exe
P2: 1.0.0.0
P3: 4afc4ac0
P4: PresentationCore
P5: 3.0.0.0
P6: 498d25f5
P7: 20c0
P8: 1d
P9: System.IO.FileNotFoundException
P10:
Attached files:
C:\Windows\System32\config\systemprofile\AppData\Local\Temp\WERE474.tmp.version.txt
These files may be available here:
C:\Users\TEMP\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report2c3bfded
And the report shows this
Version=1
EventType=CLR20r3
EventTime=129123787454857939
ReportType=2
Consent=1
UploadTime=129123787517507939
Response.BucketTable=5
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=syncprovisionwizard.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=1.0.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=4afc4ac0
Sig[3].Name=Problem Signature 04
Sig[3].Value=PresentationCore
Sig[4].Name=Problem Signature 05
Sig[4].Value=3.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=498d25f5
Sig[6].Name=Problem Signature 07
Sig[6].Value=20c0
Sig[7].Name=Problem Signature 08
Sig[7].Value=1d
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.IO.FileNotFoundException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6002.2.2.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Sync Framework\Power Pack For SQL Azure November CTP\SyncProvisionWizard.exe
UI[3]=SyncProvisionWizard has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=SyncProvisionWizard
AppPath=C:\Program Files\Microsoft Sync Framework\Power Pack For SQL Azure November CTP\SyncProvisionWizard.exe
ReportDescription=Stopped workingSaturday, March 6, 2010 8:11 PM
Answers
-
Hello danielsn,
It seems that transaction is no longer valid for many possible reasons. One of them being trying to commit a transaction when connection has timed out or some sql exception is thrown from database.
Can you copy and paste the stack trace and possibly the snippet? I will take a look and see what the problem might be.
Thanks,
Patrick- Marked as answer by Sid Singh [MSFT]Microsoft employee Tuesday, March 23, 2010 9:52 PM
Tuesday, March 9, 2010 6:54 PM
All replies
-
There is no PK on the user table which you would like to upload data to the SQL Azure, right?
Please to create a Primary Key on the user table and do the process again.
Thanks.
Leo Zhou ------ This posting is provided "AS IS" with no warranties, and confers no rights.Sunday, March 7, 2010 4:20 PMAnswerer -
I had so many problems on that computer, I moved to a new computer, started over, and carefully followed the install directions, and got the following error, on a different database, and a different table, which has a primary key.
The SqlTransaction has completed; it is no longer usable
No data was uploaded, but it did show a table with the correct name.Monday, March 8, 2010 10:55 PM -
Hello danielsn,
It seems that transaction is no longer valid for many possible reasons. One of them being trying to commit a transaction when connection has timed out or some sql exception is thrown from database.
Can you copy and paste the stack trace and possibly the snippet? I will take a look and see what the problem might be.
Thanks,
Patrick- Marked as answer by Sid Singh [MSFT]Microsoft employee Tuesday, March 23, 2010 9:52 PM
Tuesday, March 9, 2010 6:54 PM -
hey did you ever figure this out? It's happening to me now.
Sunday, October 24, 2010 2:54 AM -
Yeah, I had the wrong version of SQLSaturday, November 13, 2010 1:58 AM