bcp.exe and bc.rll error message while restoring MSSQL Database ( Build 9450 and above)

bcp.exe and bc.rll error message while restoring MSSQL Database ( Build 9450 and above)

Question : 

I am trying to restore  OpManager database to my new MSSQL DB, getting error message asking me to copy bcp.exe and bcp.rll files to OpManager home folder.


Copy bcp.exe and bcp.rll  files from your MSSQL server to OpManager home folder , if you still get the error message, MSSQL native client should be installed on OpManager server based on the Operating system (64/32 bit) on the server.

Download  it from the link below and install it on OpManager server:

      • Related Articles

      • OpManager DB migration from PGSQL to MSSQL on the same server in Version 12.3

        Please follow the below mentioned steps to migrate DB from PGSQL to MSSQL on the same server. These steps are applicable only on builds 12.3.045 and above. If you are in older versions below 12.3.045, please upgrade to 12.3.045 and follow these ...
      • No Database listed while adding MSSQL Monitors

        Issue/Scenario: When I try to add MSSQL performance Monitors, I get to the stage to add databases but there were no databases listed .  This issue could occur if   32bit MSSQL is installed  on a 64bit Widows2008  R2. Solution/Workaround: Apparently ...
      • Upgrading OpManager to the latest build

        Question : How to upgrade OpManager to the latest build. Solution: Based on the current version choose the below  path for the upgrade. 8000/8721/8723/8800                                  -->> 8810                              8810/8811/8812/9000  ...
      • OpManager Backup and Restore for build 9450 and above

        Question: How to do Backup and Restore for Builds above 9540  Solution: The backup and restore commands have been changed from build 9450  to 10100 and again from 10200 for different database types, go to <OpManager-Home\bin\backup>  folder and ...
      • MSSQL Transaction Logs Full

        Steps to clear the Transaction logs. 1. Shutdown opmanager service. 2. Change the Recovery Model to Simple by following the steps below: Go to SQL server-->OpManagerDB properties-->Options-->Recovery Model-->Simple. (You can replace it with full mode ...