Sage 100

 View Only
Expand all | Collapse all

Anyone familiar with the OITEST.exe errors? ""OI A

  • 1.  Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 13:46
      |   view attached
    Anyone familiar with the OITEST.exe errors? ""OI ACCESS FAILED"" We checked user permissions (KB 31475); external access, and are running it from the server (KB 31463) but still no luck. This client is running Sage 100 Standard (v 2018) and having trouble with Fusion POS pushing data back to Sage. Jeremy Sharp asked him to Run the OITEST, runs fine from the server, and a workstation install fixes it temporarily for a few days. Sage KB (46242) has a resolution for this error, but only for Premium Installs. Maybe recreate Console and Workstations files?


  • 2.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 13:50
    Maybe try running regom.bat


  • 3.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 13:51
    Ugh... long day regcom.bat


  • 4.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 03-03-2021 14:10
    I'm dealing with the same issue on a v2020 Premium system.  I've gone through the Sage KB articles with no luck.  Details here: link.

    Reading this, I try regcom.bat, and get a bunch of failures.  Is this the root problem?


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 03-04-2021 14:40
    Sage support call unsuccessful.  Escalation call booked for Tuesday... fun!

    Not knowing how this is supposed to work, they tried a script, with the resulting error below... which seems to indicate something is not installed properly.


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 6.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 03-04-2021 22:53
    Kevin - Probably it's saying the Init() method failed earlier. It's the line you typically see as oPvxScript.Init(PathToHomeFolder). Behind the scenes it creates a temp file in \mas90\Home\Lib with a .YYY extension then deletes it. If it can't BOI doesn't work. Simple test is go to Lib folder with File Explorer, create a text file, then try to rename it from .TXT to .YYY. If you are unable, the Microsoft FSRM is most likely installed and needs to be configured to exclude YYY files (and LCK files I learned from @Doug Higgs post). I've run into it 3 - 4 times.​

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

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



  • 7.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 03-05-2021 09:49
    What's in the image is the script (from Sage, used to test)... the error comes during the CreateObject.  It doesn't get to the Init line.

    I had already checked with .zzz file, and there was no problem with .yyy either.

    Thanks for the suggestion.


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 8.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 03-09-2021 13:27
    Found the problem... pvx.ini (in the server's MAS90\Home folder) was blank.  Partial credit to a David Speck post on Sage City for inspiring me to look at this file.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 9.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 07-30-2021 15:11
    Hey @Kevin Moyes can you upload that OIKeyTest.vbs? ​

    That might come in handy instead of using the exe

    ------------------------------
    Eric Lunceford
    First Mate Business Solutions
    Oklahoma City, OK
    877-880-8960
    https://www.firstmatellc.com/
    ------------------------------



  • 10.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 07-30-2021 15:54
    ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    '	OIKeyTest, Tests ability to set a single company in MAS 90
    '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    
    
    ' The Following must be filled in with the correct MAS 90 path (in quotes)
    '
    'MAS90Path = "C:\Program Files\sage software\mas 90\Version420\MAS90\Home\"
    vMAS90Path= "E:\Accounting\Sage2020\MAS90\Home"
    vCompany_Code = "ABC"
    vModule = "A/P"
    vDate = "20061201"
    vUserName = "km"
    vPassword = "password"
    vModuleUI = "AP_Vendor_ui"
    vModuleBUS = "AP_Vendor_bus"
    '
    
    '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    ' Data Collection
    ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    
    'Get Path
    
    
    '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    'Call PVXScript
    'MsgBox "NOTE: if an error results, run PVXCOM.EXE from the "+vMAS90PATH+" directory.",,"Attempting to call com object ProvideX.script"
    on error resume next
    	Set oScript = CreateObject ("ProvideX.Script")
    	oScript.Trace = 1
    
    		if Err.Number Then
    			Call QuitProgram ( err.description,"Unable to call ProvideX.Script")
    		end if
    
    'Call MAS Path
    on error resume next
    oScript.Init (vMAS90Path)
    
    		if Err.Number Then	
    			Call QuitProgram ( err.description,"Bad Path or Failed to open path: " + vMAS90Path)
    		end if
    
    'Instantiate session object
    Set oSS = oScript.NewObject("SY_Session")
    '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    
    'Set company code
    
    retVal= oSS.nSetCompany(vCompany_Code)
    
    		if retVal  <> 1 then
    			Call QuitProgram ( oSS.sLastErrorMsg,"unable to set company code:"+vCompany_Code) 
    		end if
    
    ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
    'Call user methods
    
    if len(vUserName) = 0 then
    	retVal = oSS.nLogon()
    		if retVal  <> 1 then
    			Call QuitProgram ( oSS.sLastErrorMsg,"User Security May Be Enabled") 
    		end if
    end if
    
    if len(vUserName) > 0 then
    	retVal = oSS.nSetUser(vUserName,vPassword)
    
    	if retVal  <> 1 then
    		Call QuitProgram ( "User Sign-on failure, possible bad password, username or security not enabled: " +vUserName,oSS.sLastErrorMsg)
    	end if
    end if
    
    
    
    'OI Cleanup
    'msgbox "Now closing and cleaning called objects...",,"Garbage Collection"
    
    
    
    Call QuitProgram ("Test Complete","Completion" )
    
    
    
    Sub QuitProgram (ExitMessage, ExitErrororDescription)
    
    CStr(ExitMessage)
    CStr(ExitErrororDescription)
    
    	MsgBox ExitMessage,, ExitErrororDescription
    	
    	'Object Cleanup
    	On error resume Next
    	vProgram.DropObject()
    	oSS.nCleanUp ()
    	oSS.DropObject()
    	Set oSS = Nothing
    	Set oScript = Nothing
    	wscript.quit
    	
    
    End Sub​


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 11.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 13:57
    @NicoleRonchetti on the local machine? from the local install? Or on the local machine from the server? Or it doesn't matter? I am not 100% familiar with that process.


  • 12.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 14:02
    @NicoleRonchetti Nevermind I found a KB on it :)


  • 13.  RE: Anyone familiar with the OITEST.exe errors? ""OI A

    Posted 12-18-2018 14:06
    May not be relevant but in the server's \mas90\home\Lib folder try creating a new TXT file then attempt to rename from .TXT to .ZZZ. If it fails (""access denied"" or whatever), you likely have FSRM installed and in turn BOI doesn't work. See this thread for more info - https://90minds-com.socialcast.com/messages/36695878