locked
Batch Spool Loaction RRS feed

  • Question

  • I am getting the following error during the synchronization

    Error

    in GetChanges()Cannot access the spooling directory 'C:\Windows\TEMP\sync_37793d4649d54a6bb3cd5d6fc566d2b8df67830677424c0ba8842fc9d5c602f7' for synchronization session 37793d4649d54a6bb3cd5d6fc566d2b8df67830677424c0ba8842fc9d5c602f7. See the inner exception for more details.

    any help would be really appreciated.

    Wednesday, November 10, 2010 1:52 PM

All replies

  • have you check the folder permissions on the temp folder?

    Wednesday, November 10, 2010 1:57 PM
  • When I restart the IIS the incremental Synch works. But i dont know how?

    First of all I dont understand why the batch files are getting created under Temp when I am setting the batch directory path to the application folder.

    Wednesday, November 10, 2010 3:03 PM
  • Is is possible that in the batch directory is set on change application but not change enumeration? This would explain getting the error in the GetChanges() call.

    --

    Kyle

     

    Thursday, November 11, 2010 1:05 AM
    Answerer
  • are you setting the batching directory on both providers (the local and remote)?
    Thursday, November 11, 2010 1:31 AM
  • yes june. And both are being set to the directory where the application is running and not the temp directory.
    Thursday, November 11, 2010 4:00 AM
  • hard to tell without the code.
    • Edited by JuneT Thursday, March 29, 2012 9:11 AM
    Thursday, November 11, 2010 6:23 AM
  • Thanks June

    I called the CleanUp method after calling the EndSession method, and it started working fine without any errors. Does this make sense?

    One more question,

    On the Server the BatchFiles are not getting deleted which is under the windows Temp directory during first time synch, However the files get deleted in the subsequent synch process when there are no batches to apply( i.e if only fewer record are there to synch). Why is this happening?

     

    Thursday, November 11, 2010 2:34 PM
  • not entirely sure, the default setting for CleanUpBatchingDirectory is true, so you shouldnt have to set it explicitly either. how are you calling the CleanUp btw?
    Thursday, November 11, 2010 4:25 PM
  • Ok.

    I am calling the CleanUp in the EndSession method.

    Is there any other chances when the batch directory on client machine does not get deleted?.

    We have implemented one way Synch(download) and we have exactly the same code written that is provided in MSDN.

    Our server database contain 25-30 tables. If these tables are updted with 1000 records each their will be a large amount of data that needs to synch with the Client DB. Is there any limitation in the Synch Framework with the amount of data that can be synched ?.

    We have enabled batching but the Synch Framework takes a lot of time to complete the synch process and most of the time it fails.

    Kindly tell me the limitations if any and also to is there any speed up mechanism that we need to follow.

     

    Friday, November 12, 2010 6:44 AM
  • I'm getting the same problem. What's causing the error is that the batch file is not present. I too would be interested to know how you are calling CleanUp in the EndSession method. I can't see how to do it? Thanks.
    Monday, November 15, 2010 11:35 PM
  • Just like you call end session call the Cleanup method.
    Wednesday, November 17, 2010 9:26 AM
  • you can enable sync tracing just in case its logging something on the batch file creation and deletion
    Wednesday, November 17, 2010 9:28 AM