A client that synchronizes over the internet encountered Error #3003:
"Could not start transaction; too many transactions already nested"
when attempting to synchronize.
I checked user groups and MS Knowledge Base and found nothing helpful.
This didn't seem to be acknowledged as a synchroization error.
Investigations revealed data errors that resulted in a cascade of
related errors. Resolving the data errors apparently cured whatever
was ailing.
The errors re-generated in each replica after synchronization , so I
had to resolve them multiple times. Perhaps if I were more clever or
understood the whole data conflict business better I could have found
a more efficient, once-and-for-all method of dealing with the errors.
There were about 800 of them, so I felt a bit like Jane Jetson
complaining about her ailing "push button finger" by the time I was
done.
P. Emigh
"Could not start transaction; too many transactions already nested"
when attempting to synchronize.
I checked user groups and MS Knowledge Base and found nothing helpful.
This didn't seem to be acknowledged as a synchroization error.
Investigations revealed data errors that resulted in a cascade of
related errors. Resolving the data errors apparently cured whatever
was ailing.
The errors re-generated in each replica after synchronization , so I
had to resolve them multiple times. Perhaps if I were more clever or
understood the whole data conflict business better I could have found
a more efficient, once-and-for-all method of dealing with the errors.
There were about 800 of them, so I felt a bit like Jane Jetson
complaining about her ailing "push button finger" by the time I was
done.
P. Emigh