Skip to Content
avatar image
Former Member

DbServerType = 0 when trying to use dst_MSSQL2014

Hello, I'm working on a windows service that connects to SAP via DI API using SAPBobsCOM.

To connect to the company, I load all the parameters in the normal way. Here's a part of the code:

            oCompany = New SAPbobsCOM.Company

            'Set settings

            oCompany.Server = ConfigurationManager.AppSettings("DatabaseServerName")

            oCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2014

I'm having a problem on just one machine, where when I run the service I'm getting the error "(-125) no database server type specified". If I print oCompany.DbServerType then I get as result a zero ( 0 ) .

This is not related at all with having or not SQL 2014 installed, as I already tested this on a machine runnnig SQL 2008 and I can see dst_MSSQL2014 even if it does not connect. It has to be related to that particular machine since on another machine of the same network the service runs OK. Maybe something important to mention is that this machine did not have anything related to SAP until I installed the DI API yesterday.

I compiled using SAPBobsCOM version 9.10.150, this machine has on its machine a version 9.10.105.

Any help would be greatly appreciated.

Thanks in advance,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jun 20, 2015 at 02:45 AM

    Hi Sergio,

    Which DotNet Framework is the project targetting?

    Regards,

    Eric

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Sergio,

      As stated by Owen, SQL Native Cleint has to be installed for the DI to work. You can have the impression it is working, but at some point or another one it will break.

      Besides this, the 910105 PL was (if my memory is not too bad) 9.10 PL01 (first ramp-up) and at that time, support of SQL2014 was included, but undocumented, in the SDK.

      So, a good try, would be to have the same version installed anywhere and the addon recompiled with it by checking the correct proxies are referenced / used

      Issue is in the proxies and the fact that the COM object (SAPbobsCOM) doesn't recognize the enumerate.

      Regards,

      Eric

  • avatar image
    Former Member
    Jun 24, 2015 at 06:47 PM

    I would try to update the DI API

    Add comment
    10|10000 characters needed characters exceeded