TeraByte Unlimited

On 2016-05-13 2:05 AM, TeraByte Support wrote:
> It would go to D:\log.txt provided logging results were enabled and not
> overridden on command line. If /logl:0 is there then logging is disabled,
> if /logfile: points to something else, that is where it wants to go (should
> do it early the the command line). Otherwise the default is ifw.log in the
> program folder.
>
> You'll need to see what it says in the log, the event log may have it as
> well, but more details in the .log file.
>
> "AlanD" wrote in message news:[email protected]...
>
> On 2016-05-11 11:03 PM, Brian K wrote:
>> Alan,
>>
>> Open IFW, Settings. Do you have a path for Log file? If it is blank check
>> this folder...
>>
>> C:\Program Files (x86)\TeraByte Unlimited\Image for Windows\V2
>>
>>
> Re: log file in V2 folder, there is not one.
> Only IFW log file on my computer is in a folder I created a long time
> ago to store batch files, and as I said, that one terminated in June
> 2015-no entries since that time.
>
> In IFW Settings, there is an entry in Log File box that says D:\log.txt
> D: is the drive on which my TBI images are stored.
>
> So, at this point, I do not have any current log files, even though
> there is a checked entry in IFW options to create a log file.
>
>
A bit of a conundrum, when I can't examine the log file to see log path,
because there is no log file.
And no, I don't have logging overridden in command lie, and no, there is
no D:\log.txt file anywhere.
In short, there is no log file related to IFW on either drive, and it is
not being overriden, and it is ticked in options.

We seem to be dealing with two, possibly related, issues here:

1. Your friend's backup is failing.

2. You don't have a log file.

Do you know if your friend has a log file?

I suggested your friend try to create a backup via the GUI. You say you think she is doing that. Which leads me to ask why she needs a batch file. What's in the batch file. I'm just trying to eliminate variables and unknowns.

Regarding your absence of a log file, are you using a batch file? If so can you try creating a backup (and log file) without using a batch file? Again, just trying to reduce the number of variables and unknowns.

What happens if you remove D:\log.txt from IFW Settings? Do you then get a log file in the program folder? I get one there every time I run IFW.

Also, for whatever it's worth, I create the image files in a partition with drive letter J. I just tried putting J:\log.txt in the Settings and I did get both the image file and the log file on J:.

Also, possibly worth mentioning, all my recent IFW activity including everything described here is on 64-bit Windows 10 using imagew64.exe.

I would also try clearing the log path in IFW settings and see if it shows up when using the defaults.

You could try setting the log level to 10 so the log gets written directly to the log file. Use /logl:10 on the command line (e.g. imagew.exe /logl:10 /b .....). Also, you could specify a known good location with /logfile (e.g. imagew.exe /logl:10 /logfile:c:\ifw.log /b .....).

There should also be entries for IFW in Windows Event Viewer (Event Viewer | Windows Logs | Applications). There might be something helpful there.

If you have IFW running unattended (/uy, /un, etc.) you could remove those commands so that issues won't get automatically handled. Once things are figured out you could add them back.

On 2016-05-13 4:07 PM, Bob Coleman wrote:
> We seem to be dealing with two, possibly related, issues here:
>
> 1. Your friend's backup is failing.
>
> 2. You don't have a log file.
>
> Do you know if your friend has a log file?
>
> I suggested your friend try to create a backup via the GUI. You say you think she is doing that. Which leads me to ask why she needs a batch file. What's in the batch file. I'm just trying to eliminate variables and unknowns.
>
> Regarding your absence of a log file, are you using a batch file? If so can you try creating a backup (and log file) without using a batch file? Again, just trying to reduce the number of variables and unknowns.
>
> What happens if you remove D:\log.txt from IFW Settings? Do you then get a log file in the program folder? I get one there every time I run IFW.
>
> Also, for whatever it's worth, I create the image files in a partition with drive letter J. I just tried putting J:\log.txt in the Settings and I did get both the image file and the log file on J:.
>
> Also, possibly worth mentioning, all my recent IFW activity including everything described here is on 64-bit Windows 10 using imagew64.exe.
>
>
Bob, thank you for your interest.

To answer your questions first re my friend:
I wrote the batch so she would never have to walk though IFW to set up
every backup, and to control where and how many backups are kept. In
short, she just clicks on an icon and walks away.

A new development this afternoon when I called her and explained how to
determine if the external drive was recognized by Windows - it was not.
I instructed her to remove the drive and re-connect it. That cured the
problem, at least for now, since I don't no why that happened.

My apologies for mixing two issues, with two different computers into
one call for help. Stupid on my part.

My computer is still an issue with the lag of a logging problem.
It always worked in the past (before June 2015), so I attribute the
change to an update. However, as far as I can tell I am and always have
been doing everything right. The IFW option to create a log file is and
has been checked, and there is nothing in my command line which would
negate that logging. Of course the old log (the file itself) is still
where it was - in

I have followed TB's advice and made sure there was a path and name for
the log file, and that cured the problem

Cases closed

thanks to all

On 2016-05-13 7:31 PM, TeraByte Support (PP) wrote:
> I would also try clearing the log path in IFW settings and see if it shows up when using the defaults.
>
> You could try setting the log level to 10 so the log gets written directly to the log file. Use /logl:10 on the command line (e.g. imagew.exe /logl:10 /b .....). Also, you could specify a known good location with /logfile (e.g. imagew.exe /logl:10 /logfile:c:\ifw.log /b .....).
Done
> There should also be entries for IFW in Windows Event Viewer (Event Viewer | Windows Logs | Applications). There might be something helpful there.
IFW source event only says operation completed Error Code 0

> If you have IFW running unattended (/uy, /un, etc.) you could remove those commands so that issues won't get automatically handled. Once things are figured out you could add them back.
Duly noted, /UY deleted
>

Followed your advice above and that worked.

Thank you