Sage 100

 View Only
  • 1.  ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:17
    ODBC logon failure. 4.3 to 2013 upgrade. On a converted report, trying to Verify Database. Get the following messages. Think I've seen this somewhere, but can't get past it. Sitting on workstation. Sage KB indicates missing PVXSEC32.dll in MAS90 root folder, but it's there. I'm on a Win7 Pro 64-bit computer. TIA.


  • 2.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:19
    Ooops. Might help.


  • 3.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:20
    Should it be in the syswow64 folder?


  • 4.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:33
    Test the SOTAMAS90 DSN in the ..\syswow64\odbcad32.exe. (you can populate the company /user/password)


  • 5.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:36
    Since it's mentioning the vendor code, could it be related to missing vendor division numbers in CI_Item or IM1 in v4.3?


  • 6.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:44
    @JimWoodhead , connection succeeded. This is a report that is pulling from the AP Invoice Header/Detail, AP_Vendor, GL_Account, and SY0_CompanyParameters tables. I wonder if the SY0_CompanyParameters is the culprit. Thinking I may need to replace it with . . . which table?


  • 7.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:44
    Notes from something I think Jeff recently encountered - not an exact match to this but maybe a help? Turns out the pvodbsec.ini file went missing from the /MAS90 Folder. This file points Crystal (or any other odbc data call) to look to the pvxsec.ini for instructions. When it goes away the system fails over to the old MAS log-on screen and pass-thru security doesn't seem to work. Bottom line...don't loose this file.


  • 8.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:46
    @WayneSchulz , that file is present.


  • 9.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:46
    The vendor code refers to Sage. I've gotten this, when you get the login prompt, hit the back key, then make sure that the top option is picked and then click on SOTAMAS90. Should be fine from there. Somehow it gets a connection string embedded (which you should see when you hit back, note the button on your second screenshot).


  • 10.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:51
    ok... I just pulled up a report: the top option is Select Data Source: and the Data Source Name: is SOTAMAS90. I'm guessing right now it's set to Connection String: blah blah blah (the normal connection string) but something is wrong with it. If you just set it to SOTAMAS90, it fixes itself.


  • 11.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:57
    @BarbaraOlson , that worked. Thanks!


  • 12.  RE: ODBC logon failure. 4.3 to 2013 upgrade. On a co

    Posted 08-14-2013 13:58
    @BarbaraGoldstein Sure thing, you're welcome :)