Skip to Content
author's profile photo
Former Member

Problem with .Net connector losing connection

I'm writing my first .Net connector project (i.e. please be gentle with me!) - it's an ASP.NET page (using vb.NET) that connects to SAP and checks for failed jobs.

It works fine the first time it runs - calls the Bapi_Xmi_Logon then calls Bapi_Xbp_Job_Select.

I've got a timer set up that calls the subroutine that calls Bapi_Xbp_Job_Select every 30 seconds - but this fails after the first time with "Object reference not set to an instance of an object" - the only way to prevent this seems to be to call the logon routine every time.

Is this how it should work?, or should the logon remain until I explicitly close it?

Any help gratefully received, and sorry if I'm being thick!

Martin Dolphin

Bentley Motors Limited

martin.dolphin@bentley.co.uk

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Apr 01, 2004 at 09:38 AM

    Hi Martin,

    it might be that you use the SAPLoginProvider for Login (in conjunction with Login form). In this case you must not close the connection. The connection is stored in session state and will be automatically closed on session end event.

    If this information doesn't help, you might want to post some code snippets.

    Regards,

    Reiner.

    Add comment
    10|10000 characters needed characters exceeded

    • Currently you create a new RFC connection for each call and never close it.

      proxy.Connection = New SAP.Connector.SAPConnection(Me.Destination1)

      You should either keep the connection open (store is somewhere - for Web applications usually in Session state) or open and close in on each request.