So I have rather extensive customization written in Job Tracker which parses through an entire project’s jobs and their materials, does some checks for spare parts, copies service literature, drawing PDFs, etc. Too much to explain but in the end, what it creates is a fully navigational HTML with folder structure for each and every job within the project. All encompassing. Our service clerk can now zip this entire folder and send to our customer. Worked great in E9 and works great in E10 until you attempt to create a service manual on a large project. I kicked off the process on a project which contains 34 large jobs. I went home and a few hours later, I remoted into my computer and Epicor was closed. The process had just began to parse into job # 24 but then just stopped. It should take nearly 3 hours, I would say, to complete this entire project.
It seems like some sort of timeout or memory issue. Do you know where I could check and where I can check for timeout/memory settings? By the way, this customization does zero writing to the DB, only lookups.
Thanks,
Chris
Guys, it is definitely something in the code. I did capture an error in Event Viewer yesterday when trying to figure this all out. However, I cannot find exactly where/what is causing it. Here’s the error:
##!Message:##! Column ‘PartNum’ is constrained to be unique. Value ‘’ is already present.
##!Program:##! System.Data.dll
##!Method:##! CheckConstraint
Could be an issue with the data in the that particular job. I usually find that if something has been working for a while then suddenly breaks its caused by bad data.
The error is saying you have 2 rows with a blank part number and that is not allowed.
Another option is to run/debug the customisation in Visual Studio.
Brett
PS taking 3 hours to run seems like a long time (unless you are producing Gb’s of data…)
Brett,
Well, I changed the code to just run through that last job that it completed prior which was successful then had it run through the job that it had errored on and that was successful. The reason why it takes so long is that it parses through every material on every job and also every make to job within each job. It finds parts that are marked as spare parts, calculates suggested spare quantities, and then finds parts which have service literature (PDF document) assigned to it, finds the PDF and copies it to the service manual folder, etc. All while creating hyperlinks to them all within the HTML. All kinds of things.
I am far from being a master in VB.net so I have no doubt that the code could be finessed by someone who knows more to make it run much faster.
We have the same environment and also use Veeam. Makes me wonder. However, I have ran this at all different times and even in the evening and it fails at the same exact spot every single time.