Running IBER.EXE as a Terminal Server on v5.5.5x

[jdkseattle]

When attempting to run iber as a terminal server on v5.5.5x I get the following error in the terminal's DEBOUT log.

Jan 22, 10:45:17, [3252], [INFO],,"COM libraries have been initialized"
Jan 22, 10:45:17, [3252], [INFO],,"Successfully setup the ATL COM Libraries for execution..this does NOT necessarily mean it is registered!!"
Jan 22, 10:45:17, [3252], [INFO],,"Delete ExitingFile(C:\Bootdrv\Aloha\TMP\EXITING)"
Jan 22, 10:45:17, [3252], [INFO],,"LoadIberStrings() - Loaded version 6.5.55.0, C:\BootDrv\Aloha\bin\IBERSTR.DLL"
Jan 22, 10:45:17, [3252], [STATUS],,"RFSInitReady flag is set to true..."
Jan 22, 10:45:17, [3252], [STATUS],,"DeboutsThread() called..."
Jan 22, 10:45:17, [3252], [INFO],,"Begin initializing network..."
Jan 22, 10:45:17, [3252], [INFO],,"Initializing network..."
Jan 22, 10:45:17, [3252], [INFO],,"Node = 100 String = 'BAA'"
Jan 22, 10:45:17, [3252], [INFO],,"NBInit()-> Before NBAddName()-> StationName = "IBERBAA ""
Jan 22, 10:45:20, [3252], [INFO],,"NBInit()-> After NBAddName()-> StationNumber = 2"
Jan 22, 10:45:20, [3252], [INFO],,"NBInit()-> Before NBAddGroupName()-> SessionName = "IBERLINK""
Jan 22, 10:45:20, [3252], [INFO],,"NBInit()-> After NBAddGroupName()-> SessionNumber = 3"
Jan 22, 10:45:20, [3252], [INFO],,"Station number 2, session 3"
Jan 22, 10:45:20, [3252], [INFO],,"Network initialization complete."
Jan 22, 10:45:20, [3252], [INFO],,"Done initializing network."
Jan 22, 10:45:20, [3252], [INFO],,"Determining Master And Fileserver"
Jan 22, 10:45:20, [3252], [INFO],,"Local DOB is 1/22/2014 in C:\Bootdrv\Aloha\DATA\ALOHA.INI (01 22 2014)"
Jan 22, 10:45:20, [3252], [INFO],,"AutoMakeFileserver: FALSE"
Jan 22, 10:45:20, [3252], [INFO],,"Creating terminal status for 3"
Jan 22, 10:45:21, [3252], [INFO],,"Creating terminal status for 2"
Jan 22, 10:45:21, [3252], [INFO],,"Terminal 2 asserts 2 is master"
Jan 22, 10:45:21, [3252], [INFO],,"Master terminal is 2. Now determining fileserver..."
Jan 22, 10:45:21, [3252], [INFO],,"Master Terminal 2 asserts fileserver is 'ALOHA2BOH'"
Jan 22, 10:45:21, [3252], [INFO],,"Attempting to connect to server 'ALOHA2BOH'..."
Jan 22, 10:45:21, [3252], [INFO],,"Drop connection of Z: to \\ALOHA2BOH\BOOTDRV returns 0"
Jan 22, 10:45:21, [3252], [INFO],,"Successfully connected Z: to \\ALOHA2BOH\BOOTDRV"
Jan 22, 10:45:21, [3252], [INFO],,"Entering CreateFilenamesFromIberdir"
Jan 22, 10:45:21, [3252], [INFO],,"Exiting CreateFilenamesFromIberdir"
Jan 22, 10:45:21, [3252], [INFO],,"Couldn't find \\TERM2... assuming master down"
Jan 22, 10:45:21, [3252], [INFO],,"Removing master 2 from termstatus"
Jan 22, 10:45:21, [3252], [INFO],,"** Sending stop event to all the threads ..."
Jan 22, 10:45:21, [3252], [STATUS],,"Exiting program 1..."
Jan 22, 10:45:21, [3252], [INFO],,"Create ExitingFile(C:\Bootdrv\Aloha\TMP\EXITING)"
Jan 22, 10:45:21, [3252], [INFO],,"unloading InterceptAlohaPrinting handlers..."
Jan 22, 10:45:21, [3252], [STATUS],,"Exiting program 2..."
Jan 22, 10:45:21, [3252], [STATUS],,"Exiting program 3..."
Jan 22, 10:45:21, [3252], [INFO],,"net shutdown!"
Jan 22, 10:45:21, [3252], [INFO],,"Canceling datagrams..."
Jan 22, 10:45:21, [3252], [INFO],,"Canceling datagrams second time..."
Jan 22, 10:45:21, [3252], [INFO],,"Dropping names..."
Jan 22, 10:45:28, [3252], [INFO],,"Net shutdown complete"
Jan 22, 10:45:28, [3252], [STATUS],,"Exiting program 4..."
Jan 22, 10:45:28, [3252], [INFO],,"exit program A"
Jan 22, 10:45:28, [3252], [STATUS],,"Exiting program 5..."


I know that TERM2 is up and running because I have additional order entry terminals using it as the Master with no problems.

Thanks for all the help and ideas. Even an "I don't know" response is better than the black hole I get when trying to go through our VAR or NCR!

 

[jdkseattle]

Correction. It's not 5.5.5x it's 6.5.5x. Got a little 5 happy there.

 

[AlohaRoss]

Couldn't find \\TERM2

Check to see if from a run command you can map to term2 and access its share folder. If not you may not have the same user name and password on both FOH machines

 

[jdkseattle]

Thanks for the reply AlohaRoss but I think I've eliminated a right's issue. One, I can interact with the shares from both directions and two, the exact same configuration and setup works on 6.7.

jdk