Sage 100

Going bats**t crazy so I give up to the 90minds gods. I have a batch file for a VI job that the client created, which appears to be all set up nice and correct, but it won't run because it gives the message ""the user logon or password does not match"". They have the Unified Login in place so that when accessing MAS you don't have to login to MAS. The VI job runs just fine from the menu. What is wrong????? S: cd ""Sage Software\Version 440\MAS90\Home"" PVXWIN32.EXE ""S:\Sage Software\Version 440\MAS90\Launcher\sota.ini"" ""S:\Sage Software\Version 440\MAS90\SOA\startup.m4p"" -ARG DIRECT UION BLC """" LGT VIWI0M DISPLAY

One would guess you have to put a user/PW in the command line or how else is PVX going to know who the user is. There are several posts on SC that have addressed this topic and probably gives an example... Here is a recent one. https://90minds-com.socialcast.com/messages/18951860

I've spent days working on VI automation issues and as the song goes, ""I've got 99 problems and a ***** ain't one"". The issue you are having isn't one of the many I was chasing down but I think the error message is pointing you to where your challenge lies. If you are using unified login, doesn't that mean your user name is something like {domain\user} and your password would be the same as your domain password? It appears you are passing a user name of BLC with no password. Is this correct? BTW, what edition? (Standard, Advanced, or Premium) Advanced and Premium work differently than Standard.

Have you looked at DSN? Gary Feldman President I-Business Network,LLC www.I-BN.com

The original KB article ID the word document is from is ID:19387

No sure you can run a vi job for. Command prompt under unified login. @alnoorcassim might be able to answer that. Jim

Two things: 1) Even with Unified Logon, if they originally didn't have that on when MAS was implemented, their old non-blank password may still be stored in Sy_User even though it's not used during startup of MAS (this might be a good thing though). So DFDM Sy_User and see if it's blank. You could blank it out I s'pose but it might be better to just include the password (unencrypted) in the bat file. 2) Use relative paths instead of absolute ones in your command line: pvxwin32.exe ..\launcher\sota.ini ..\soa\startup.m4p -ARG DIRECT UION BLC """" LGT VIWI0M DISPLAY

If still no go one more thing you could try related to Unified Logon. Create a copy of the SOTA.INI file and edit that one (e.g. copy it as SotaVI.ini). If this is MAS 200, you're doing this on the client side, not server side. In the [Config] section add a LOGON=YES Note the YES is case sensitive - must be in upper-case Now in command line point to the other INI file: pvxwin32.exe ..\launcher\SotaVI.ini ..\soa\startup.m4p -ARG DIRECT UION BLC """" LGT VIWI0M DISPLAY

@AlnoorCassim password is blank in the SY_User record. I did already retype the command in the batch file using the relative paths, but then when I saved the batch file it replaced it with the syntax I provided in my posting. There already was a section in the sota.ini file (I copied it) where logon=yes -- so I just changed the lower case to YES (and changed the command line in the batch file to my new sota_vi.ini file). Now when I run the batch file I get the message ""Another task is attempting to start up. Wait for this task to start before invoking another task"".

It sounds like something fundamental is amiss. I'd have to take a look at it.

I've attached it.

Have you rebooted since getting that last error, and/or cleared all tasks

Jane I meant I would need to remote in. But it looks like this BAT file is generated from some external app. I would just try to run it in a more simpler form first. In Windows click on Start (unless you're on Windows 8) then paste this in: ""S:\Sage Software\Version 440\MAS90\Home\pvxwin32.exe"" ..\launcher\sota.ini ..\soa\startup.m4p -ARG DIRECT UION BLC """" LGT VIWI0M MANUAL The original sota.ini file is used and MANUAL instead of DISPLAY because you don't need to run the whole import to make sure the command line works. Once it does change it to DISPLAY or AUTO

OK, when I do that I get that User Logon or Password does not match message. This really seems to be a Unified Login issue, and I give up. I'm going to have them run the VI job from the Jobs menu and I'm going to add logic to it to rename the source file after it runs the job. Unless you have any other ideas ....