Write, Bureaucrats, Administrators
1,991
edits
Difference between revisions of "Logs"
no edit summary
| Line 4: | Line 4: | ||
== General == | == General == | ||
* All log files generated by BudgetLink are filed under the following folder [BudgetLink Folder]\System\Logs\ | * All log files generated by BudgetLink are filed under the following folder: [BudgetLink Folder]\System\Logs\ | ||
* The system will only retain the last 200 log files by default before recycling the space and removing the older files. | * The system will only retain the last 200 log files by default before recycling the space and removing the older files. | ||
* The files are prefixed with a date/time stamp being the year-month-day DASH hour-minute-seconds as in 130601 – 1200 – Auto Upload.txt | * The files are prefixed with a date/time stamp being the year-month-day DASH hour-minute-seconds as in 130601 – 1200 – Auto Upload.txt | ||
| Line 11: | Line 11: | ||
== Related == | == Related == | ||
[[Get Data Logs]] | [[Get Data Logs]] | ||
Any manual get data process get logged under C:\Program Files (x86)\ExcelLink\System\Logs\Get Data Logs\ | |||
[[Auto Upload Logs]] | |||
All automated get data process that get scheduled by windows get logged under C:\Program Files (x86)\ExcelLink\System\Logs\Auto Upload Logs\. | |||
Your error checking mechanism should scan the file name prefixes or the date modified of the file to work out when the log was generated. Then open the content of the log and search for the word “Failed”. Anything that says Failed implied something failed reading CMS or MYOB or BOTH. | |||
Also, you should probably check for files you expect to be created and raise an exception if you don’t see an auto upload log each and every day. This implies the process didn’t even start and something may be wrong with the scheduled task. | |||
[[MYOB Export Logs]] | |||
All writes to MYOB get logged (whether manual or automated) under the following folder C:\Program Files (x86)\ExcelLink\System\Logs\MYOB Export Logs\. | |||
Your error checking mechanism should scan the file name prefixes or the date modified and work out when the log was generated. These files are generated by MYOB when we write data to MYOB. We simply copy them and archive them. Each time the overnight process run, you should get 4 files (one ending n Customers, Suppliers, Customer Invoices or Supplier Invoices). Your error checking should also make note of anything missing files. | |||
The main parts you want to read are the last three lines which will always be included. See the sample below. | |||
364 records imported without errors. | |||
0 records skipped. | |||
0 records imported with warnings. | |||
Where it says XXX records skipped, this means MYOB rejected some records and implies something didn’t write into MYOB. | |||
Where it says XXX records imported with warnings, this means MYOB manipulated the data somewhat. It may have truncated something, defaulted something or changed something. I believe you should raise this as a possible error as we did try hard to mitigate this from happening. It’s not fatal, but should be looked into. | |||
Any lines above those last three lines indicate the actual error that was raised. As such, any line starting with a negative number is an error. Any line starting with a positive number is a warning. And MYOB will detail the description that applies to those lines. I wouldn’t worry too much about this content, but if you want to know what it’s for or care to interpret, this gives you a rough idea. | |||