Skip to main content

Hi,

I've been using the Rumba ODBC driver to allow .NET windows service application to receive and send data to AS/400 over an ODBC connection but getting below error but same code works for .NET window application. We have ensured that the Windows service runs as same user used to run the windows application. Can you please help?

Thanks


#Rumba

Hi,

I've been using the Rumba ODBC driver to allow .NET windows service application to receive and send data to AS/400 over an ODBC connection but getting below error but same code works for .NET window application. We have ensured that the Windows service runs as same user used to run the windows application. Can you please help?

Thanks


#Rumba
Hi selva012,
there are more information needed to troubleshoot your problem.
I suggest to contact the Micro Focus support line and provide them more information about your environment.
Can you please provide an ODBC Trace to the supportline it may shows a bit more.

Hi,

I've been using the Rumba ODBC driver to allow .NET windows service application to receive and send data to AS/400 over an ODBC connection but getting below error but same code works for .NET window application. We have ensured that the Windows service runs as same user used to run the windows application. Can you please help?

Thanks


#Rumba
is there way to get error message string or number from rumba application ?using any functions or classes ?

Hi,

I've been using the Rumba ODBC driver to allow .NET windows service application to receive and send data to AS/400 over an ODBC connection but getting below error but same code works for .NET window application. We have ensured that the Windows service runs as same user used to run the windows application. Can you please help?

Thanks


#Rumba
Hi babu1093,

if you have a question which is unrelated to the thread you are in please open a new thread.

Can you elaborate on your question above?

What kind of error are we talking about? A Rumba application error or a Rumba script error.

For application errors, most errors should pop an error dialog giving the error message.
For scripts error, you can use "On Error" to pop a message box with information relevant to the error.

e.g.
Sub Main
On Error goto ErrHandler
Err.Clear
:
:
:
:
:
Exit Sub
ErrHandler:
Msgbox Err.Number & Err.Description
End Sub

Tom