Prev: Command Line Options for Navision 5.0 Setup
Next: Navision 4.0 SP3 is crashing over RDP/ICA session
From: NatJev on 8 Aug 2007 00:00
I have installed NAS & ADCS on one of our servers.

Microsoft 2003 & SQL2005

When i direct NAS to the test CRONUS database i can login without a problem
via hyperterminal. However if i direct NAS to our Navision Database i get the
error below.

If l look at versions of the database i notice that our origninal DB

Version AU 4.00 SP2 (4.0 SP3)

whereas Cronus is

Version AU 4.00 SP3 (4.0 SP3)

Another thing i notice is when NAS starts up with Cronus DB (this is in
event viewer)

I get the following;
The following information is part of the event: Socket Port : 11322.

Whereas if i startup NAS with our database Australia. i get the following;
he following information is part of the event: Named Pipe :
RequestPipe_Australia__NAS1.

I dont know why the Australia. database is trying named pipe whereas the
Cronus is Socket Port?

Event Type: Error
Event Source: Navision VT100 Plugin
Event Category: None
Event ID: 0
Date: 7/08/2007
Time: 11:42:55 AM
User: N/A
Computer: SEVER02
Description:
Could not communicate with Socket localhost:11322. No connection could be
made because the target machine actively refused it

any suggestions would be great.

From: Jorge on 13 Aug 2007 17:44
Well, you have to see if the services you have matches de AL objects you have
on the DB.

Older versions of ADCS will have the CSS & VT100 services. This use name
pipes and are bound to your company name for the pipe name.

Newer versions of ADCS will only use 1 service (VT100) and they tend to use
Sockets.

The "trick" here is that the AL code has been written specifically to use
either Sockets or Named pipes.

So it seems that you are trying to use the Socket ADCS objects with Named
pipe AL code. As far as I remember the only object that needs to be replaced
is codeunit 7700, and in both cases the ComCom needs to be registered on the
host machine (but this should be fine if you have gotten any replies from any
NAS).

If you can, try importing codeunit 7700 from the working system into the non
working system (I really hope this is the only object, but as far as I
recall, this is responisble for the communication).

Good luck!

"NatJev" wrote:

> I have installed NAS & ADCS on one of our servers.
>
> Microsoft 2003 & SQL2005
>
> When i direct NAS to the test CRONUS database i can login without a problem
> via hyperterminal. However if i direct NAS to our Navision Database i get the
> error below.
>
> If l look at versions of the database i notice that our origninal DB
>
> Version AU 4.00 SP2 (4.0 SP3)
>
> whereas Cronus is
>
> Version AU 4.00 SP3 (4.0 SP3)
>
> Another thing i notice is when NAS starts up with Cronus DB (this is in
> event viewer)
>
> I get the following;
> The following information is part of the event: Socket Port : 11322.
>
> Whereas if i startup NAS with our database Australia. i get the following;
> he following information is part of the event: Named Pipe :
> RequestPipe_Australia__NAS1.
>
> I dont know why the Australia. database is trying named pipe whereas the
> Cronus is Socket Port?
>
> Event Type: Error
> Event Source: Navision VT100 Plugin
> Event Category: None
> Event ID: 0
> Date: 7/08/2007
> Time: 11:42:55 AM
> User: N/A
> Computer: SEVER02
> Description:
> Could not communicate with Socket localhost:11322. No connection could be
> made because the target machine actively refused it
>
> any suggestions would be great.
>
From: NatJev on 13 Aug 2007 20:40
Thanks Jorge, yes this fixed the problem~! I got a reply from mibuso forum in
regards to this too. thank you very much for your help!

"Jorge" wrote:

> Well, you have to see if the services you have matches de AL objects you have
> on the DB.
>
> Older versions of ADCS will have the CSS & VT100 services. This use name
> pipes and are bound to your company name for the pipe name.
>
> Newer versions of ADCS will only use 1 service (VT100) and they tend to use
> Sockets.
>
> The "trick" here is that the AL code has been written specifically to use
> either Sockets or Named pipes.
>
> So it seems that you are trying to use the Socket ADCS objects with Named
> pipe AL code. As far as I remember the only object that needs to be replaced
> is codeunit 7700, and in both cases the ComCom needs to be registered on the
> host machine (but this should be fine if you have gotten any replies from any
> NAS).
>
> If you can, try importing codeunit 7700 from the working system into the non
> working system (I really hope this is the only object, but as far as I
> recall, this is responisble for the communication).
>
> Good luck!
>
> "NatJev" wrote:
>
> > I have installed NAS & ADCS on one of our servers.
> >
> > Microsoft 2003 & SQL2005
> >
> > When i direct NAS to the test CRONUS database i can login without a problem
> > via hyperterminal. However if i direct NAS to our Navision Database i get the
> > error below.
> >
> > If l look at versions of the database i notice that our origninal DB
> >
> > Version AU 4.00 SP2 (4.0 SP3)
> >
> > whereas Cronus is
> >
> > Version AU 4.00 SP3 (4.0 SP3)
> >
> > Another thing i notice is when NAS starts up with Cronus DB (this is in
> > event viewer)
> >
> > I get the following;
> > The following information is part of the event: Socket Port : 11322.
> >
> > Whereas if i startup NAS with our database Australia. i get the following;
> > he following information is part of the event: Named Pipe :
> > RequestPipe_Australia__NAS1.
> >
> > I dont know why the Australia. database is trying named pipe whereas the
> > Cronus is Socket Port?
> >
> > Event Type: Error
> > Event Source: Navision VT100 Plugin
> > Event Category: None
> > Event ID: 0
> > Date: 7/08/2007
> > Time: 11:42:55 AM
> > User: N/A
> > Computer: SEVER02
> > Description:
> > Could not communicate with Socket localhost:11322. No connection could be
> > made because the target machine actively refused it
> >
> > any suggestions would be great.
> >
 | 
Pages: 1
Prev: Command Line Options for Navision 5.0 Setup
Next: Navision 4.0 SP3 is crashing over RDP/ICA session