#1  
Old 28th March 2013, 05:08 PM
Sue King
 
Posts: n/a
Default Problem using remoting in a DLL in a third party app that uses MSSQL

Hi,

Hopefully you can understand this setup.

A third party app needs to talk to our software. It is a .Net app
using MSSQL.

I've created a DLL that wraps up accessing our NexusDB, and using a
remoting client to a server we have, to pass a message to another of
our programs.

The third party can get all this working successfully with a test .NET
application.

Once they try and run the code in their real application, it isn't
working so well.

The calls in the dll to the nexus database server work fine.

The remoting client connects if the app has not connected to their
MSSQL database. If they have connected to their database, the remoting
client fails to start.

I intend to put in more trace and see what is failing, as it appears to
be the call to FRemotingClient.open. At this stage I'm not sure if it
is an exception or just doesn't start, and will get more information.

What I am asking is whether there is anything you can think of that the
MSSQL connection being active might change that would have an impact,
that I should be looking for/at.

TIA

Sue



--

  #2  
Old 28th March 2013, 05:44 PM
Ad Franse [NDX]
 
Posts: n/a
Default Re: Problem using remoting in a DLL in a third party app that usesMSSQL

Op 28-3-2013 7:08, Sue King schreef:
> Hi,


> The third party can get all this working successfully with a test .NET
> application.
>
> Once they try and run the code in their real application, it isn't
> working so well.


Same machine ?
diffent machine ?
IP address/servername correct?
if servername : DNS is correctly working
can you connect and work from the new machine with EM and the wanted
nexus configuration ?
firewall ?

is the test-app doing "the same" as the prod-app ?
if not: what is the difference

Ad Franse
  #3  
Old 28th March 2013, 07:57 PM
Sue King
 
Posts: n/a
Default Re: Problem using remoting in a DLL in a third party app that usesMSSQL

Ad Franse [NDX] wrote:

> Op 28-3-2013 7:08, Sue King schreef:
> > Hi,

>
> > The third party can get all this working successfully with a test
> > .NET application.
> >
> > Once they try and run the code in their real application, it isn't
> > working so well.

>

Hi Ad,

> Same machine ?
> diffent machine ?


Same machine.

> IP address/servername correct?
> if servername : DNS is correctly working
> can you connect and work from the new machine with EM and the wanted
> nexus configuration ? firewall ?
>
> is the test-app doing "the same" as the prod-app ?


Yes

> if not: what is the difference


The difference is whether there is an active MSSQL database connection
or not.


The problem is not with connecting to the Nexus server, just with
starting a remoting client to an independent remoting server.

I'll post more information when it becomes available, but I don't
expect to know more until after Easter.

Regards

Sue

--

  #4  
Old 28th March 2013, 08:44 PM
Thorsten Engler [NDA]
 
Posts: n/a
Default Re: Problem using remoting in a DLL in a third party app that usesMSSQL

Sue King wrote:

> The difference is whether there is an active MSSQL database connection
> or not.


I've no idea why that should make any difference.

> The problem is not with connecting to the Nexus server, just with
> starting a remoting client to an independent remoting server.
>
> I'll post more information when it becomes available, but I don't
> expect to know more until after Easter.


You know that the remoting client and server components are no longer required
with the current version of NexusDB?

If you have an open TnxSession, you can just call:

nxSession.AbstractSession.CreateInstanceFor('<Regi stry>', ...)

Not that I think it should make any difference.
  #5  
Old 8th April 2013, 11:39 AM
Sue King
 
Posts: n/a
Default Re: Problem using remoting in a DLL in a third party app that uses MSSQL

Sue King wrote:

> Hi,
>
> Hopefully you can understand this setup.
>
> A third party app needs to talk to our software. It is a .Net app
> using MSSQL.
>
> I've created a DLL that wraps up accessing our NexusDB, and using a
> remoting client to a server we have, to pass a message to another of
> our programs.
>
> The third party can get all this working successfully with a test .NET
> application.
>
> Once they try and run the code in their real application, it isn't
> working so well.
>
> The calls in the dll to the nexus database server work fine.
>
> The remoting client connects if the app has not connected to their
> MSSQL database. If they have connected to their database, the
> remoting client fails to start.
>
> I intend to put in more trace and see what is failing, as it appears
> to be the call to FRemotingClient.open. At this stage I'm not sure if
> it is an exception or just doesn't start, and will get more
> information.
>
> What I am asking is whether there is anything you can think of that
> the MSSQL connection being active might change that would have an
> impact, that I should be looking for/at.
>
> TIA
>
> Sue


The error message that is being generated is 'Out of memory'.

It is being generated in CreateInstance call of the remoting client.

According to the third party, 'It's just standard MS SQL2008 windows
authentication login and no other special control involved'.

In summary, if our call is made prior to the login it works. If it is
made after the login it fails. I'm asking questions on any memory
settings for MSSQL, but am a bit out of my depth here.

Do you have any suggestions ?

How much memory would expect it would need for the remoting client ?
My code is quite small.

The PC being used for testing has 8Gb memory, so it shouldn't be a
physical limit.

My remoting is standalone so I don't compromise the Nexus server.

Sue



--

  #6  
Old 11th April 2013, 09:21 PM
Sue King
 
Posts: n/a
Default Re: Problem using remoting in a DLL in a third party app that uses MSSQL

Sue King wrote:

> Sue King wrote:
>
> > Hi,
> >
> > Hopefully you can understand this setup.
> >
> > A third party app needs to talk to our software. It is a .Net app
> > using MSSQL.
> >
> > I've created a DLL that wraps up accessing our NexusDB, and using a
> > remoting client to a server we have, to pass a message to another of
> > our programs.
> >
> > The third party can get all this working successfully with a test
> > .NET application.
> >
> > Once they try and run the code in their real application, it isn't
> > working so well.
> >
> > The calls in the dll to the nexus database server work fine.
> >
> > The remoting client connects if the app has not connected to their
> > MSSQL database. If they have connected to their database, the
> > remoting client fails to start.
> >
> > I intend to put in more trace and see what is failing, as it appears
> > to be the call to FRemotingClient.open. At this stage I'm not sure
> > if it is an exception or just doesn't start, and will get more
> > information.
> >
> > What I am asking is whether there is anything you can think of that
> > the MSSQL connection being active might change that would have an
> > impact, that I should be looking for/at.
> >
> > TIA
> >
> > Sue

>
> The error message that is being generated is 'Out of memory'.
>
> It is being generated in CreateInstance call of the remoting client.
>
> According to the third party, 'It's just standard MS SQL2008 windows
> authentication login and no other special control involved'.
>
> In summary, if our call is made prior to the login it works. If it is
> made after the login it fails. I'm asking questions on any memory
> settings for MSSQL, but am a bit out of my depth here.
>
> Do you have any suggestions ?
>
> How much memory would expect it would need for the remoting client ?
> My code is quite small.
>
> The PC being used for testing has 8Gb memory, so it shouldn't be a
> physical limit.
>
> My remoting is standalone so I don't compromise the Nexus server.
>
> Sue


I never did get to the bottom of this. It seemed easier to change the
way of achieving the desired result than to debug what might be wrong
in the remoting implementation, or might have nothing to do with
remoting and be in the VB .Net side of things and related to MSSQL.

Sue

--



Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
mssql question David Guest nexusdb.public.discussions 0 20th March 2013 09:49 PM
Migrating from MSSQL Leslie nexusdb.public.support 6 14th December 2010 02:12 PM
Is there a way to convert MSSQL .mdf files to .csv? Don Miller nexusdb.public.discussions 6 1st June 2010 12:36 AM
Third Party software Connection problem lesm nexusdb.public.support.odbc 4 8th August 2008 03:24 PM
Re: NexusDB to MSSQL Martijn Tonies nexusdb.public.support.thirdparty 2 6th September 2006 01:23 AM


All times are GMT +11. The time now is 12:28 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.