Personalization, Customization and Productivity Tools

[IBPIT]

It is in the VI directory on the server.

[marker6789]

Hmmm...That's where I have mine.  How did you decide that 59 would be the correct channel to read, or how do I see which channel I should be accessing?

Thanks!

[IBPIT]

Sorry.  That was part of the original script I used.  Not sure.

Are you using MAS90 or MAS200?

[mboldrick]

Whenever I add the perform logic sequence being discussed in this thread by adding a command pointing to an external file (stored in the VI directory) and run the VI job, it throws the error "Error 105 in program SO_SALESORDERHISTORY.PVC at line 0265." When I reopen the import job, it has restored the default perform command "..\SO\SO_VIPerform.M4P;SO_" My command is listed via the search button.

Any help getting past this would be appreciated.

Mike

[BigLouie]

Uno : Contact Reseller

Dos : Have Reseller contact Scott Brady at Sage

Say are you replacing the default perform logic? This is suppose to be in addition to the default perform logic.

[mboldrick]

I've gotten to the same problem marker6789 is having - Error #14 on line 7 of Slade's PL file. The output file is created (in a MAS subdirectory), but with 0 bytes, and the VI script is left running. Has anyone gotten past this point? If so, how?

Thank you Kemp and Big Louie for your continued help.

Mike

[IBPIT]

As BL mentioned, if you replaced the PL instead of just adding the new one, this could possibly causing your issue.

You may want to start with a fresh import and just add the PL to see if you still get the error.

Possibly look at the security settings for the directories.  Just for clarification, you are using a subdirectory of the MAS90 directory on the server, right?

Are you using MAS90 or MAS200?  If you are using MAS90, you may need to point the files to the local PC instead of the server.

If these suggestions do not work, you may need to talk with your reseller to get this working.

[okochavi]

Did anyone ever get this working? Anyone know why channel 59 was chosen to go get the logfile that needs to be translated to human?

(BTW Running MAS 200 4.4)

[KateKrueger]

Hello,

I ran in to the same errors when trying to use the .pl with the GL on version 4.3.0.19. I verified with Sage that even though it looks like the ODBC would work, those tables don't actually interact and can't be reported on. Maybe others have done this but I found some success using Crystal to report on SY_ActivityLog and filtered out error codes and anything from other modules. I wrote some comparisons to print in red if the description said Skipped :# that wasn't zero or Invalid :# that wasn't zero. I figure this way the client can at least run the report and tell at a glance if one of the jobs had lines that failed and could then investigate further. This client is running 43 jobs nearly simultaneously and needed a quick way to identify if something didn't import.