Our Pilot testing is not working and we’re just curious of others on .400 have had any issue?
Thanks!
Mark W.
I’ve got my .400 DEV instance installed (and DB upgraded) but haven’t really tested it yet. Anything you want us to check specifically?
Yeah, does it run?! 
Nothing has been moving when we enter new documents. It was working in Pilot .300. When we refreshed Pilot and upgraded to .400, we had to make some configuration changes that we were using before but it hasn’t moved a document yet. We have Epicor Support on it right now. I just want to know, is it .400 or is it us?
Thanks!!!
Well, wish I could help. We do not send documents back and forth yet, just parts, customers, contacts,
configurators, etc. because the configurator details(releases or multiple lines of the same part#) wouldn’t move back and forth correctly on until 10.2 - and we just haven’t gotten to it yet.
Oh, by “Documents”, I mean anything. 
No parts, nothing.
ok - basic testing here so far. I/C currency exchange rates are moving across IntQueIn/IntQueOut tables just fine between our 28 companies.
Excellent! That’s good to know. That may lead to a problem on our side and gives me comfort in the go Live once we get it working. Thanks!
Just tested Part Master updates and they work too…
Good luck with that diagnoses. I’ll tell you that I find that no matter how I do the upgrades or patches, I’ve found the only way to really make sure my task agents work is to just go ahead and delete/recreate them - both inside the UI and in the Task Agent Config tool.
I’ve seen messages ranging from ‘bad agent password’ to 'task submitted by user blah in company blahblah: cannot run task". Log files don’t have anything more useful, so I just quickly whack and re-create them and it saves me so much time/effort.
@Mark_Wonsil Do you install and update the Task Agent or does Epicor? We had this problem before on another version and the solution was to completely delete the Task Agent including the ProgramData folder before installing the new agent.
@hkeric.wci had a similar issue with another post.
1 Like
Thanks @John_Mitchell and @MikeGross!
I will check with the SaaS team to see if they did in fact create a new Task Agent.