Sage 100

Just installed PU2 for 2020 at a client and now every VI export job throws an Error 88 VI_EXPORT_UI.PVC at line 1001.  I tried creating a new job from scratch and get the same error.  I renamed and re-initialized the VI_JobLob.M4T file too.  Any idea what might be causing this?

Thanks!

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------

issues with the file folder location you are trying to write to?

------------------------------
alan niergarth
Velosio LLC
------------------------------

Log file.  Do the Info/Debug then
? logfileName$      - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------

When I try ?logfileName$ at the debug prompt it returns a blank
I tried ?logfileName and got a 0
Every VI Export job fails, Import jobs work fine

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------

Original Message:
Sent: 06-23-2021 12:03
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file.  Do the Info/Debug then
? logfileName$      - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------

Log file. Do the Info/Debug then - should be cLogFileName$ - forgot the "c"
? cLogFileName$ - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------

Original Message:
Sent: 06-23-2021 14:20
From: Bernie Lehman
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

When I try ?logfileName$ at the debug prompt it returns a blank
I tried ?logfileName and got a 0
Every VI Export job fails, Import jobs work fine

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------


Original Message:
Sent: 06-23-2021 12:03
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file.  Do the Info/Debug then
? logfileName$      - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.

Probably a permissions or Path issue.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------

Original Message:
Sent: 06-23-2021 16:46
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file. Do the Info/Debug then - should be cLogFileName$ - forgot the "c"
? cLogFileName$ - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------


Original Message:
Sent: 06-23-2021 14:20
From: Bernie Lehman
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

When I try ?logfileName$ at the debug prompt it returns a blank
I tried ?logfileName and got a 0
Every VI Export job fails, Import jobs work fine

------------------------------
Bernie Lehman
Lehman Wesley & Associates


Original Message:
Sent: 06-23-2021 12:03
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file.  Do the Info/Debug then
? logfileName$      - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.

I still get a blank when I try the ? cLogFileName$ and I did verify that the service user (Advanced version) has all rights to the Logs folder

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------

Original Message:
Sent: 06-23-2021 17:12
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Probably a permissions or Path issue.

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------


Original Message:
Sent: 06-23-2021 16:46
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file. Do the Info/Debug then - should be cLogFileName$ - forgot the "c"
? cLogFileName$ - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.


Original Message:
Sent: 06-23-2021 14:20
From: Bernie Lehman
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

When I try ?logfileName$ at the debug prompt it returns a blank
I tried ?logfileName and got a 0
Every VI Export job fails, Import jobs work fine

------------------------------
Bernie Lehman
Lehman Wesley & Associates


Original Message:
Sent: 06-23-2021 12:03
From: Lee Graham
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Log file.  Do the Info/Debug then
? logfileName$      - which is the file it is working with.

------------------------------
Lee Graham
Friendly Systems, Inc.

Definitely for v2021 and possibly for 2020.2, new features were added to let you manage the VI log. This stemmed from a discussion I created here last year about export job logging (more so than import jobs) being excessive and taking up too much disk space. Then submitted to Enhancements site. 

The new options includes the location of the log folder, whether to fall back to a single log per job (the way it's done before v2019), whether to turn off logging entirely for either exports or imports, and possibly turning off verbose logging (that one was a maybe)

In short look for a V/I Setup Options or something like that to see if anything needs to get set or changed. 


------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

@Alnoor Cassim you are right, there are setup options for VI now after the 2020 PU2 install.  I have verified rights to the folder, tried changing to a different folder and tried switching from use the same log to create a new one and still get this error on every VI export.  It pops up immediately.  I am going to take a chance and call Sage..... I'll report back.​

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------

Original Message:
Sent: 06-24-2021 04:07
From: Alnoor Cassim
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Definitely for v2021 and possibly for 2020.2, new features were added to let you manage the VI log. This stemmed from a discussion I created here last year about export job logging (more so than import jobs) being excessive and taking up too much disk space. Then submitted to Enhancements site.

The new options includes the location of the log folder, whether to fall back to a single log per job (the way it's done before v2019), whether to turn off logging entirely for either exports or imports, and possibly turning off verbose logging (that one was a maybe)

In short look for a V/I Setup Options or something like that to see if anything needs to get set or changed.


------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

I just looked at code for VI_EXPORT_UI for 2020.2 and getting an 88 there indicates something seems to be more fundamentally amiss. I couldn't tell you specifically without remoting in. Agree you should call Sage Support. Also just in case, check the LINKS folder for VI_EXPORT_UI.pvc. This would mean there's a mod override for it. Now I've done an overrides for VI_EXPORT_UI myself, related to the log file in fact! If it was my mod you had previous to 2020.2, I'd definitely have to retrofit it for the new V/I Setup Options pertaining to the log file.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

Original Message:
Sent: 06-24-2021 16:26
From: Bernie Lehman
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

@Alnoor Cassim you are right, there are setup options for VI now after the 2020 PU2 install.  I have verified rights to the folder, tried changing to a different folder and tried switching from use the same log to create a new one and still get this error on every VI export.  It pops up immediately.  I am going to take a chance and call Sage..... I'll report back.​

------------------------------
Bernie Lehman
Lehman Wesley & Associates
------------------------------


Original Message:
Sent: 06-24-2021 04:07
From: Alnoor Cassim
Subject: Error 88 VI_EXPORT_UI.PVC at line 1001 on all export jobs

Definitely for v2021 and possibly for 2020.2, new features were added to let you manage the VI log. This stemmed from a discussion I created here last year about export job logging (more so than import jobs) being excessive and taking up too much disk space. Then submitted to Enhancements site.

The new options includes the location of the log folder, whether to fall back to a single log per job (the way it's done before v2019), whether to turn off logging entirely for either exports or imports, and possibly turning off verbose logging (that one was a maybe)

In short look for a V/I Setup Options or something like that to see if anything needs to get set or changed.


------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA