Register Now


Lost Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Add question

You must login to ask question.


Register Now

APPSeCONNECT community provides a new way for integration super heros connect the external world. Join hands together to build a community of people to help each other, solve problems or share knowledge.

SAP Business One DI Server: Could not find METADATA file

SAP Business One DI Server: Could not find METADATA file

Amongst a large number of errors that you might encounter, some of the problems are totally not a part of your application to fix. One of such error is the one mentioned in the title. “Could not find METADATA file” is one of the error which is thrown from SAP B1 DI Server when there is some corruption in SAP B1 DI Server service memory.


You are getting the aforementioned error since SAP B1 DI Server requires regular restart after a certain amount of time passed by. Depending on how heavily the data is getting transferred between SAP B1 to 3rd party applications, the DI Server might face such an issue. Mostly this will be fixed by restarting the DI server service once regularly, but in some cases, this might come more frequently than once daily.


The solution of this issue is as follows:

  1. Stop DI Server Service (“SBODI_Server”) using Task Manager or Services console in Windows. You need to make sure the service is stopped successfully. If you see the service status saying StopPending for long, you need to kill the B1_DIServer.exe process from Task Manager.
  2. After the service is completely stopped, go to “C:\Windows\Temp” folder and delete the folder “SM_OBS_DLL” with all its content.
  3. Once deletion is complete, start the DI Server Service again (“SBODI_Server”).

Now with APPSeCONNECT, we provide a ready made solution to the same using Prepackaged rule. To enable this rule, go to the Rules Section of your project and activate. Use the following steps:

  • Login to
  • Go to Manage -> Rules
  • Select “Choose Rule” button.
  • Activate the SAPB1DISERVERRestartRule.
  • Download the configuration on Agent, and you are done.

This rule will automatically detect the error message and if DI Server is not accessible, your DI Server will be automatically restarted after taking care of the mentioned steps.


Sometimes it happens that the application is having some limitation which needs some way around to fix the issue. May be this is not a correct approach to do regular restart, but after through discussion with SAP, we have found there is no other way to fix this problem without going to another solution in SAP. Hence this becomes the only approach that you can take to ensure things working correctly in integration projects.

I hope this will help you cure occasional downtime of SAP B1 integration.

About Abhishek SurVerifiedExpert

VP, Products at InSync Abhishek Sur has been a Microsoft MVP since 2011. He is currently working as a Product Head with Insync Tech-Fin Solutions Pvt Ltd. He has profound theoretical insight and years of hands-on experience in different .NET products and languages. Over the years, he has helped developers throughout the world with his experience and knowledge. He owns a Microsoft User Group in Kolkata named Kolkata Geeks and regularly organizes events and seminars in various places to spread .NET awareness. A renowned public speaker, voracious reader, and technology buff, Abhishek's main interest lies in exploring the new realms of .NET technology and coming up with priceless write-ups on the unexplored domains of .NET. He is associated with Microsoft's Insider list on WPF and C# and stays in touch with Product Group teams. He holds a Master's degree in Computer Application along with various other certificates to his credit. Abhishek is a freelance content producer, developer, and site administrator. His website guides both budding and experienced developers in understanding the details of languages and latest technologies. He has a huge fan following on social networks. You can reach him at, get online updates from his Facebook account, or follow him on Twitter @abhi2434.

Follow Me