VB 6 > ARS > Screen pop issue

[William Rentfrow]

**

We have a VB6 application that launches the Remedy user tool (7.1), opens a form and submits a value. The section of code for that is as follows:

Set arSession = New ARUSER.COMAppObj 'Added 3NOV
   
    sessionNumber = arSession.Login(g_sRemUserName, g_sRemUserPassword, False)
   
    arSession.OpenForm sessionNumber, "remedyservername", "remedyformname", ARSubmit, 1
   
    Set arForm = arSession.GetActiveForm
   
    Set arField = arForm.GetFieldById(536870953)

g_sEINFieldName = m_sScreenPopData

arField.Value = g_sEINFieldName

arForm.Submit

If we close the form and reopen it or another form, the session seems to disconnect and we receive:

ARERR [90] Cannot establish a network connection to the AR System server : servername : RPC: Rpcbind failure - RPC: Authentication error

The purpose of the application is to automatically populate information from a phone call into the Remedy form. The agent would work the issue by searching and modifying information in one or more forms, then close all the forms at the end of the call and wait for the system to deliver the next call.

My question is whether the session disconnection is correct given how the API works or whether this is an actual problem. I would like any information on handling sessions so that the client can stay open and the VB program can continue to open new forms in the existing instance of the user tool.

Thanks

William Rentfrow
Principal Consultant, StrataCom Inc.
wrentfrow@...
O 715-592-5185
C 715-410-8056

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

[Brian Goralczyk-2]

** William,

It has been a while but I am gonna try to help you on this one.

I think you want to move the session creation, and the form pop work into different functions.  Then call the session creation if the sessionNumber variable is not populated.  The problem is that you are trying to log into the server more than once.

Mind you, it has been a few years, but from my quick perusal of the code, that is what jumps out at me.

Hope that helps.

Brian Goralczyk

On Tue, Nov 10, 2009 at 11:33 AM, William Rentfrow <WRentfrow@...> wrote:

**

We have a VB6 application that launches the Remedy user tool (7.1), opens a form and submits a value. The section of code for that is as follows:

Set arSession = New ARUSER.COMAppObj 'Added 3NOV
   
    sessionNumber = arSession.Login(g_sRemUserName, g_sRemUserPassword, False)
   
    arSession.OpenForm sessionNumber, "remedyservername", "remedyformname", ARSubmit, 1
   
    Set arForm = arSession.GetActiveForm
   
    Set arField = arForm.GetFieldById(536870953)

g_sEINFieldName = m_sScreenPopData

arField.Value = g_sEINFieldName

arForm.Submit

If we close the form and reopen it or another form, the session seems to disconnect and we receive:

ARERR [90] Cannot establish a network connection to the AR System server : servername : RPC: Rpcbind failure - RPC: Authentication error

The purpose of the application is to automatically populate information from a phone call into the Remedy form. The agent would work the issue by searching and modifying information in one or more forms, then close all the forms at the end of the call and wait for the system to deliver the next call.

My question is whether the session disconnection is correct given how the API works or whether this is an actual problem. I would like any information on handling sessions so that the client can stay open and the VB program can continue to open new forms in the existing instance of the user tool.

Thanks

William Rentfrow
Principal Consultant, StrataCom Inc.
wrentfrow@...
O 715-592-5185
C 715-410-8056

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_

_Platinum Sponsor: rmisolutions@... ARSlist: "Where the Answers Are"_