I could be a locked file. Rebooting should release it if that is the case.

Skip 

Paul, 

Here is the error definition: 

Error #12: File does not exist (or already exists)

Possible Reasons:

• Cannot create a file (DIRECT, INDEXED, SORT, etc) if a file of the same given name already exists.
• Filename does not exist cannot ERASE, OPEN, LOAD, RUN, or CALL a non-existent file.
• In [TCP] Can't OPEN, server is not listening

Suggestion - Do a thorough evaluation of what was happening at the time the error occurred.  

Thanks I've been told that this is a very generic message so I'll start looking at what you have suggested.

It seems to be leaning towards a network issue as I have seen some errors on the server that loosely coincide with the MAS 90 errors... We had a few 'Delayed Write Failed' errors right in the same time frame.

So I'm looking at replacing the NIC in the server and possibly the RAM in the server as well.

Paul

ps. Isn't it funny that the spellcheck on this fourm thinks MAS is not a word...

Do these tend to be data entry files or temporary working files?

In the past I have seen these types of files that may are required to be deleted after an update not be deleted because of a virus scanning software that was not telling the program to wait a second.  Essentially the virus scanner locks the file,  MAS 90 tries to delete the file while it is still locked.  The file does not get deleted.  This does not happen with all virus scanners, just the ones that don't put a "please wait" signal out.

The next time you try to do data entry or an update, the file is alrelady present when it should not be.  You rename/delete the file in question and everything is OK.

My fix is to make sure that you have excluded from virus scanning the M4T, M4L, SOA and PVC files.  Works like a charm when you run into this.

I really wish that error 12 could be separated into two error messages.  One for file does not exists and one for the file already exists.

At this point it looks like this indeed was a permissions error.

With a little help from my reseller we determined that the network share for MAS 90 need some help.

It had been originally set up with Full COntrol rights for "Everyone". I ended up having to delete the "Everyone" permissions and then reestablish permissions for Domain Users and Domain Admins. Since I have done that I have not had any more of the vague Error #12's.

I think that I will clean it up a little and create a group called MAS 90 Users and give it the permissions instead of the global Domain Users group. Not everyone on my domain needs to access MAS 90 so this might be a good way to address it.

Sad thing is that my reseller was the one that set up my server originally and used this less than perfect way of setting up the share... So they were nice and didn't charge me for troubleshooting this issue.

Seems strange that use of Everyone would cause this issue you described, but if it works, great!

However, I wouldn't use Everyone anyway, because it means essentially that there is no network security at all.  Someone not even logged in could gain access.

Uno - Welcome to the Sage Community

Dos - You should start a new thread for your issue. You will get more responses.

Can't find any documentation? Have you, I don't know, read the Help files? Gone to the Sage support page and downloaded the manuals? Worked with your reseller on this?

simpleweb, what are you trying to do with the Visual Integrator job? Import or export?  What file(s)?  There is documentation in the help system which is right in the program.  Just go to Help --> Help Topics on the MAS 90/200 menu bar.  From there you can click on the Visual Integrator module on the left.  The help is very generic as people who use the module use it for different things.

I hope that helps.

Dawn