Post reply

‘Time Out Expired’ - ERROR

  • August 11, 2005 at 12:27 am

    #102702

    Hi,

     

    I am dealing with merge replication.

     

    I am getting ‘Time Out Expired’ in one of our modules. Users ignores this and continue to input data. The data is getting stored in the respective tables and users are able to generated reports and print the same. Once the user logs out of the machine, data is getting rolled back completely.

     

     How such data is getting committed and then gets rolled back when users logs out. ?

     

    This database also is merge replicated. During this process we also notice “ merge process could not perform retention-based meta data cleanup in database “. We have close to 20 + databases on the server and they are merge replicated to remote servers.

     

    What parameters we need to review to find out symptoms to this problem

     

    Thanks,

    Soura.

  • August 11, 2005 at 11:48 am

    #581507

    I don't really understand your problem, but I had "timeout" errors with transactional replication when initializing large snapshots. To fix my problem, I changed the distribution agent to use a new profile that I created with a larger timeout setting, instead of the default setting.  I changed the "query timeout" setting from 300 to 8000, and that fixed my problem.

    Of course, I have plenty of other problems to work on !!!

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply