database login failed failed to open connection

SOLVED

Error occurs on any report after upgrading to 2013 from 4.4 on 64 bit workstations

This occurs only on 64 bit WS and with is related to some new permission issues on server2012 where the drivers don't get written to the registry unless you run wksetup from a command prompt as administrator -

I don't understand why the issue and many others result in NO MATCHES FOUND in the new? database 

Informational only-

  • 0

    Hi,  Couple things for you to check.

    ODBC Driver Version ODBC Data Source Administrator  

    Drivers Tab: MAS 90 4.0 ODBC Driver 4.40.04.00?

    User DSN Tab: Does the SOTAMAS90 DSN Path point to the 2013 Install?

    Debug Tab - Run Test Connection - Succesfull?

    If running the CS ODBC driver verify the appropriate driver is running in Services or running the

    pvxiosvr.exe from ...\mas90\home on the server (i.e. not running the 4.40 version).

    Administrative rights has always been required to run workstation setup. It should

    not require running it from a dos(command) prompt.

    Right mouse click on the Sage 100 Workstation and run as Administrator. Does reporting work?

    If you can post the exact error message I'll see if I can track it down.

    Thanks

    John Nichols

    Sage

  • 0 in reply to jcnichols
    verified answer

    THANKS ISSUE IS RESOLVED WITH ADMIN CMD INSTALL IN 2012 AND NEW W7 64 BIT PERMISSIONS ISSUES

  • 0 in reply to dlcottet

    I have a few workstations that work initially after installing wksetup.  However, after a few days, the errors occur again.  

    Sage 100 ERP 2013 Advanced

    Please advise how to correct this issue from happening in the future!

  • 0 in reply to BShockley

    HI, Can you provide details on the error message, Operating system, CS ODBC Driver?  

    Thanks

    John Nichols

    Sage  

  • 0 in reply to jcnichols

    John,

    Windows 7, 32 bit

    Not using CS ODBC driver

    Sage 100 Advanced 2013 update 4

    Thanks

  • 0 in reply to BShockley

    Hi, With the 2013 release, Sage 100 reporting no longer uses the SOTAMAS90 DSN, instead we

    pass an ODBC connection string to establish a connection. The DSN is however useful for validating

    an ODBC connection.

    Please try the following:

    *********************************************

    Exit the Sage 100 Workstation

    On a x86 (32bit) workstation

    C:\Windows\System32\odbcad32.exe

    On a x64 (64bit) workstation

    C:\Windows\SysWOW64\odbcad32.exe

    User DSN Tab

    SOTAMAS90

    Remove | OK

    Start The Sage 100 workstation (The SOTAMAS90 DSN is recreated at startup)

    Double Click the SOTAMAS90 DSN

    Go To Debug Tab

    Click Test Connection

    Login In

    The result should be # of Tables

    If Test returns a login/connection failed message, click the connection string button

    and verify the "Directory= "

    *********************************************

    *********************************************

    Check that the login being used has at a minimum "Read" permissions to the Server Sage 100

    Data directory i.e \mas90\MAS_ABC...

    *********************************************

    *********************************************

    Check the values in the workstation \mas90\launcher\sota.ini

    Verify the [Server] and [Active Server] values

    *********************************************

    Q: Just curious,  why are you not using the CS ODBC Driver?

    If you're still have issues please let me know.

    Thanks

    John Nichols

    Sage

  • 0 in reply to jcnichols

    Is there a limit to the number of users for the c/s odbc driver in version 2013?

  • 0 in reply to BShockley

    Hi, In Sage 100 2013 the CS ODBC driver license key user count is 50.  In Sage 100 2014,  the CS ODBC driver license key user count is 255.

    If you're using 2013 and require a larger user count,  you can contact support and they will provide a 255 user key.

    Thanks

    John Nichols

    Sage

  • 0 in reply to jcnichols

    John,

    I'm having problems finding the csodbcservice.exe file.  I looked in MAS90\Home\Lib\_appserv.

    Is this file located somewhere else in the 2013 version?

    Thanks,

    Brian

  • 0 in reply to BShockley

    HI Brian,

    pvxiosvr.exe is located in ..\mas90\home.  See the Sage 100 ERP Install Guide pages 63-67 for running as a service. 

    Thanks

    John Nichols

    Sage