The timeout period elapsed prior to completion of the operation

[Former Member]

suddenly the synch is failing and started to get the following error message:

<event>

<messagetype>E</messagetype>

<date>2009-03-30 13:06:31.54<;/date>

<synchmodule>Synch</synchmodule>

<message>Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

at netpoint.api.data.DataFunctions.ExecuteReader(CommandType commandType, String SQL, String connectionstring)

at NetPoint.SynchSBO.framework.SBOQueue.GetQueue()

at NetPoint.SynchSBO.SynchObjectBase..ctor(Company company, SecurityTicket st, Boolean synch)

at NetPoint.SynchSBO.Synch.LoadQueues()

at NetPoint.SynchSBO.Synch.SynchAll2()</message>

<synchmethod>SynchAll()</synchmethod>

<objecttype />

<objectid />

</event>

i already tried to set the time out in the Synch.exe.config to 3600

any ideas?

Thanks,

Moty

[Former Member]

Hmmm is this an initial synch? If so I would take a look at the prx_transaction_queue table in the SBO database and see how many records are there. If there are a lot you may need to make a copy of the data and do the synch in steps. Delete everything first and re-add a subset of the records, run a synch and see if that runs then add another subset.

The tricky thing is to know which subset to add first .. for example if you add orders before synching items they will all fail.

My suggestion is to remove data that you know will be the last step ... orders, deliveries, invoices, gltransactions, etc .. hopefully that will reduce the table size enough to get the main data synched over ... then re-add the remaining data.

If the transaction queue isn't too large .. the only other time I have seen this error is dealing with synching prices because the partspricing table had too many rows and it timed out deleting the old data. I don't think this is the case for you though based on the error message ... it seems to be erroring as soon as it tries to loads the queue.

[Former Member]

Hi Moty,

we identified an issue with synchronization of object 31, which entries are kept in the PRX_Transaction_Queue instead of being removed after successful synchronization run. This results in increasing size of PRX_Transaction_Queue. When it reaches several millions of entries, we are unable to load this table - Timeout expired exception.

This issue is still in investigation and there can be other objects keeping cumulating in PRX_Transaction_Queue. To find out which object could cause timeout, execute this query on Business One company database:

SELECT object_type, COUNT(object_type) object_count

FROM PRX_Transaction_Queue

GROUP BY object_type

ORDER BY object_count DESC

If it is mostly object 31, make sure this object is not used in any of your custom plugins (if you have any) and you can easily delete these entries from transaction queue as they are not required by WebTools:

DELETE FROM PRX_Transaction_Queue WHERE object_type = 31

Regards,

Jaro