Second Engine Installation 1

[adbonn]

Hi,

We have the following setup:

1) Unicenter TNG 2.4
2) SDO v3.1
3) Amo v3.2

We are trying to install a second engine on another computer other than the TNG Server. Accordingly we are trying to setup two engines: one on the TNG Server (AUTOENGINE)which is up and running, and the other on another PC (Win2000).

Although we succesfully install the second engine on the Win2000 computer, we keep getting the following error:


3.2.0.14 2002-07-24 12:01:38 Performing Job:Engine Collect: E16NTS5
3.2.0.14 2002-07-24 12:01:38 Sector Open() Failed, returned:-7
3.2.0.14 2002-07-24 12:01:38 Unable to Open Sector:E16NTS5
3.2.0.14 2002-07-24 12:03:03 Performing Job:Engine Collect: E16NTS5
3.2.0.14 2002-07-24 12:03:03 Sector Open() Failed, returned:-7
3.2.0.14 2002-07-24 12:03:03 Unable to Open Sector:E16NTS5

where E16NTS5 is the sector we have linked, inorder to test the installation.

We would appreciate any help which could help us solve the problem.

Regards

Adrian

 

[ondrae]

Adrian,

so this error is present on the second engine only ? If you keep getting the problems with both the engines, you can have a problem with the sector.
Anyway, check:

1. basically - access to the sector computer from the engine (RW permissions, etc.)
2. the sector has a network share properly defined
3. the sector sharename is defined to the null sessions in the sector system local registry

Cheers,

Ondra

 

[adbonn]

Ondra,

Thanks a lot for your help. According to CA the -7 error means that we need to install the Engine using the Admin user name. Although we do not know whether they refer to the TNG server Administrator or else the Network Administrator.

Anyway I will surely keep you informed of the outcome.

Regards

Adrian

 

[ondrae]

Adrian,

we are running the Engine service under the local system account. That's why we needed to define the share name of the sector (AMsector$ by default) to the system registry (HKLM/SYSTEM/CurrentControlSet/Services/lanmanserver/parameters/NullSessionShares - AMSECTOR$) on the sector server.
Verify this first.

Regards,

Ondra

 

[Roofrax]

Adrian, check that you can actually connect from the engine machine to the sector using the exact name as registered in the console. I have found that at this "early" stage of version 3.2 there are bugs in the engine, for instance I have experienced "Sector Open() Failed, returned:-7" on the following 2 occasions

1. The sector path had a leading blank space in it
2. After upgrading from version 3.00 to 3.2 and the original sectors where set as preconnected

Another obvious one is paths, (the second machine will not see the sector on its d:\ drive etc) I now always use UNC paths which should be the same from any "NT trusted" machine

hope this helps

 

[adbonn]

Dear All,

Thank you for all the tips you are suggesting.

I have, up to a certain extent, got rid of the error message on 41 (out of 47) sectors. I still have to check the remaining six sectors. Accordingly I will check the Registry (as Ondra suggested) and then the paths.

My real concern is that on the main engine all sectors are returning OK - the main engine is installed on the TNG Server. It is only the second engine, that it is displaying the errors.

Roofrax, the only method I know of how a sector path can be checked is through the console. But since the error is being displayed on the second engine, I don't think it is concerned with the sector paths. Although I shall check about it also.

Thanks

Adrian

 

[Roofrax]

No worries, just bouncing all the available options around. I agree the engine will access the console for its path to the sector, just saying that if a "hard" path is used (eg d:\tngam\sector) then the 2nd engine will look on its own machine for this location. Sounds obvious I know but have had word from CA that this has tripped a number of their clients up.

Thing is, -7 "cannot connect sector" is a generic message that is returned for loads of reasons. What sector path is showing in your d:\tngam\engine\engine.log when you stop/restart the engine?

 

[adbonn]

Roofrax,

Thanks a lot for the tips. Infact one of the sectors had the path pointing towards the TNG Server, and no wonder that the second external enine could not find the sector !! In another case the engine was not included in all VLans, and accordingly not even basic communication (i.e. pinging) was available.

Anyway, thanks again to both of you for the help

Regards

Adrian