Sync Service Failure

[Former Member]

Hey all,

We have noticed that after a few days of processing, the sync service will continue to fail. We believe it may be related to this error message that appears in the Windows Event Viewer.

We also noticed that the memory allocated to the synch service gradually increases until it gets to an unusually high level. When checked this morning after letting it run over the weekend, it was using about 1.8 gigs of memory compared to right now it is running about 242 mb.

What could be causing this memory leak?

Thanks,

Kevin

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

at SAPbobsCOM.CompanyClass.Connect()

at NetPoint.SynchSBO.SBOObjects.SBOUtility.SetCompany(Company TheCompany, SecurityTicket securityTicket)

at NetPoint.SynchSBO.Synch.SetCompany()

at NetPoint.SynchSBO.Synch..ctor(SecurityTicket ticket)

at NetPoint.SynchSBO.Synch..ctor(SecurityTicket ticket, Int32 pricinginterval)

at NetPoint.SynchService.NPSynchThread.SynchOnce()

[Former Member · Accepted solution]

Its a failure in the DI API memory management. Basically connections to company databases are not closed. However, this scenario is difficult to troubleshoot, and a search on Google for this error in any application would result in this same conclusion.

Setting the service to restart after first and second failure will help extend the time between failures, but the best thing to do if you are experiencing this issue is to write a batch script that restarts the service, then set it to run every night at midnight using the windows task scheduler.

the commands are:

net stop servicename

net start servicename

Where servicename = the name of the netpoint.synchservice as shown in the service properties in control panel -> services

[Former Member · Accepted solution]

Hey Bryce,

Thanks for your help, I've deployed the batch file as you recommended. Do you know if this is a trappable bug that SAP will be fixing in a future patch? That seems like a particularly nasty one.

Thanks,

Kevin