Need to append output to 1 log file

[wcroth]

Hi - The attached script will log each session to it's own logfile but I am trying to append all the sessions / output to 1 logfile ex: output.txt. Any assistance is appreciated. Thanks

[tnygren]

Hi Wcroth,

It is possible to append the log data to a single log file.

This can be done my modifying the start of the logging. The following will start the logging but append the data to the end of the log file:

crt.Session.Log True, True

Does this help?

Do multiple sessions need to log at the same time?

[wcroth]

Perfect, thanks!

[wcroth]

What would the pause cmd be after it sends command and see's # sign?
If DeviceType = "IOS" then
crt.Screen.Send "term len 0" & chr(13)
crt.Screen.WaitForStrings "#"
crt.Screen.Send "sho ver | in System image" & chr(13)
crt.Screen.WaitForStrings "#"
WANT A PAUSE RIGHT HERE B4 ITS STARTS NEXT SESSION maybe a 2 or 3 sec pause
End If

[WesR]

crt.Sleep <millisec>

i.e.

crt.sleep 2000

Wes

[wcroth]

Thanks WesR, new at this. Need help w/ error handling, If a device in my device list is not reachable and I am unable to connect I need the script to continue and also log that in my output file as "Unable to Connect".

[kbarnette]

Hi wcroth,

I have attached an example script that demonstrates error-handling while connecting in SecureCRT.

Using the information contained therein, are you able to successfully accomplish what it is you are looking to do?

[wcroth]

Thanks Kevin, having trouble with and where to plug it in my current script and writing it to my output file. I know the funtion will go at the bottom, but not sure where to put the actual error check and how to write it to the ouput file.

[wcroth]

attached current script

[kbarnette]

Hi wcroth,

The example script I provided demonstrates the ability to use the vbscript 'On Error Resume Next' command to tell the scripting engine to let us (the script itself) handle all errors.

The following is an explanation of how to handle connection errors and log the errors to the SecureCRT log file:

Replace your crt.Session.Connect() calls to actually be calls to the Connect() function.

If the connect is not successful, the example script I provided demonstrates how to structure an if statement to handle the error. The following code is an example of how to log custom data to the SecureCRT log file:

Dim objFSO, objLogFile
Set objFSO = CreateObject("Scripting.FileSystemObject")

Const ForAppending = 8
Const bStart = True
Const bStop = False

' Retrieve the SecureCRT log file
szLogFile = crt.Session.LogFileName

' Stop logging in SecureCRT briefly so we can write to the log file
crt.Session.Log bStop

' Open the log file
Set objLogFile = objFSO.OpenTextFile(szLogFile, 8)

' Write our custom data
objLogFile.Write "Connection failed with the following error:" & vbcrlf & _
    vbcrlf & Err.Description

' Close the log file so we can resume logging in SecureCRT
objLogFile.Close

' Start logging in SecureCRT
crt.Session.Log bStart, True

Does this information help to handle connection errors and log the errors to the SecureCRT log file?