Sage 100

Those are VI Job logs (added as a feature in v2019, linked from the system activity log) and should be safe to delete. 

Recent versions also have a VI Options panel to control the settings...

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

changed to reuse.   Its strange that the files are going to the VI folder instead of the mas_system log file folder like it says.   but no matter, we are upgrading them and going on a new server so should be not an issue.     

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

How do you do it within Sage?

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

From the Activity Log (LM).

How do you do it within Sage?

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

is there a way to email the vi job log with each vi job run in task manager?

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

No.  AFAIK, only the summary text you see in the Activity Log description field is available for reporting.

Alnoor posted about something custom here:

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/100540/custom-report-based-on-vi-job-logs 

is there a way to email the vi job log with each vi job run in task manager?

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).

:(.   The customer wants to import customers, items, vendors, pos, and sales orders from another system every hour  9 to 5 every day.   I am trying to convey the nightmare that this will be for the one person keeping track of these.    

No.  AFAIK, only the summary text you see in the Activity Log description field is available for reporting.

Alnoor posted about something custom here:

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/100540/custom-report-based-on-vi-job-logs 

is there a way to email the vi job log with each vi job run in task manager?

There is no way to write a report on the contents of a VI job log.  (Neither the job's Live log, nor one linked from the Activity Log).  There is simply no ODBC link to the table.

The only way to view details is to open the log file from within Sage 100.

Kevin, I have a different customer where I now need to keep the logs and report on them.   How do I report on the older logs?      I am sending the user an email of the activity log that shows where Records were Invalid and the name of the Log File.   But not sure how to report on the vi..m4t file.  Any suggestions?

I think the original idea for keeping the VI job logs came from a discussion Elliott and I had once, where I mentioned how frustrating it was that scheduled / automated VI job error details were unavailable for ODBC / reporting, and that the job logs were lost with the next schedule.  (IIRC, he was asking for feedback on a design change they were working on... probably the Activity Log...).

Keeping the job logs as M4T's is a great solution for that problem... but I think the log file sizes caught us all by surprise.

What Kevin said! Since it's clear your client was once on early 2019 or 2020, where this issue was unpatched, after you decide whether to delete all the V/I logfiles in Mas_System\Logfiles to recover the disk space (note there are some non-V/I files too), if not already set, go into V/I Options and set the Log File Creations to Reuse Same Log File or however you see fit for the client. It was introduced as a feature that was supposed to be helpful but heavy V/I usage clients, especially export job ones and ones with frequently scheduled auto-run jobs (via BAT file or Task Scheduler), started running out of disk space. (Thru an Ideas site entry I wrote and direct contact with Sage engineers, I sort of led the charge to getting the V/I options menu added with reusing the logfile being the default behavior and having an alternate path for logging).