Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

We have Success Factor as a source and BW as target, sometimes we used to get the below error and the jobs will be in hanged state or will be very slow. We got an update that reboot of system will help, but we have to leave the job to run slow as other DB jobs will be running as it will be affected.


Success Factor Adapter in DSMC during issue


Even reboot was not helping, and adapter was going into stopped state.

Adapter Status in DSMC after server reboot.



Adapters in BODS will write their trace and error in server path like all the other jobs.


Z:\ProgramData\SAP BusinessObjects\Data Services\adapters\log

File name : SuccessFactorAdapter_trace.txt

When the path of adapter file was investigated it occupied the whole drive space and the file size was bigger. We renamed the existing file as backup and started the Success Factor Adapter, it started working and created new file in the adapter path of server. The old file was kept in a shared path for any further issue after retention policy so it can be removed.



We have to figure what are the necessary files needed and always clear up logs after checking their importance. Cleaning it up in a retention period will be a best practice. Instead of reboot this work around help us to fix the issue and completes our job within SLA. After this there was no hang or slowness to the jobs.
Labels in this area