x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 47 subscribers
  • Views 5522 views
  • Users 0 members are here
Browse Forums
Announcements
51
topics
34
replies
General Discussion
1k
topics
2k
replies
Matthew S

Problems authenticating via ODBC

SOLVED
Posted By

Yesterday I upgraded from BusinessWorks 2012 to BusinessWorks 2013. I also reinstalled Windows on the UPS Worldship computer. That computer previously connected to BW via ODBC. Sage KB #17817 covered using the CreateDSN tool and now within Windows Vista's ODBC connection utility I do see a System DSN for the data on the server. However, every attempt to authenticate using that ODBC connection fails. Per Sage KB #18769 I tried the BW MANAGER user and password in multiple variants, all without success (manager, MANAGER, password all lower case, password all upper case). Prior to reading that second KB article I tried the domain user I had been using when installing the BW client on users' computers, the domain administrator user, and at least two other BW users, all were unsuccessful.


What do I need to do? Did something get turned off on the MANAGER user with the upgrade from BW 2012 to BW 2013? I don't know what username they used previously for this ODBC connection.

  • 0

    lets see if I understand this.

    1. you upgraded your system from BW 2012 to BW 2013  ( service packs ? )

    2. You wiped the UPS computer, installed a fresh copy of MS Vista (32bit or 64bit?)

    3. You installed UPS Worldship (2014?) on the UPS pc

    4. Your having trouble connecting UPS computer to BW data bases via ODBC

    5. When installing BW on UPS computer it fails

    Lets work on #5,

    Are you running the install from the "Server" and is the UNC  paths correct in the 1st part of the BW install

    It will ask for confirmation before you need to click "NEXT",

    The password that I have always provided for the BW install is the BW SERVER'S ADMINISTRATOR and its password.

    #4,   the BW account to get read access is MANAGER and its password ( case sensitive )

    I always install MS Office then I run the CREATEDSN.exe on the local PC - check that is connecting to the correct SERVER its at the top (connecting to {servername}  )

    tick the check boxes that are needed and "CREATE DSN"

  • 0 in reply to Vince Settipane

    1. I upgraded from BusinessWorks 2012 to BusinessWorks 2013 SP 7.

    2. I wiped the UPS computer and installed a fresh copy of Windows Vista x86 followed by SP1, SP2, and the latest Windows Updates. The shipping domain user is a powerless Windows user on this computer. I installed the programs by logging in as the domain administrator. I did some configuration, such as using the Sage tool to create the DSN, while logged in as the powerless Windows user and entering the domain admin credentials in the UAC.

    3. Yes, I installed UPS Worldship 2014 on the UPS computer.

    4. I installed BW 2013 on the UPS computer by going to the server's BW share via UNC. On the UPS computer we can run BW 2013.

    4.1 It appears that in the past, when people installed the BW client on end users' computers, when prompted for Pervasive SQL domain user credentials they used the domain administrator's creds. I prefer using a different user account with domain administrative rights (if needed) on apps (backup programs, firewalls doing an AD DS bind, etc) so a few weeks ago I created a separate domain user called bwuser and made it a member of the "domain admins" group. I used those creds when installing BW 2012 on a number of new computers a month ago without issue and also used them on this UPS computer. I don't think that is an issue but I wanted to point it out all the same.

    5. MS Office is not installed, nor is it needed, on the UPS computer.

    6. Within Vista I can go to the Control Panel > Administrative Tools > Data Sources (ODBC) (by right clicking and choosing run as administrator and entering the domain admin credentials) > System DSN I can see the DSN created by BW. No credentials are set. When I try to enter various combinations of MANAGER and its password it won't authenticate me.

    7. There is only one server, so it's not a case where the user could be looking to an old server with a previous version of BW.

    8. We have rebooted the UPS computer multiple times. I don't think we have rebooted the server since the BW version upgrade. Could that be needed? I think the Widows firewall is turned off on the server. I'm not sure on the UPS computer.

  • 0 in reply to Matthew S

    #6  - I have BW DSN installed on my Win7 box ( we run Client Server) , and my Datasources (ODBC) is empty , but if I open Excel 2010 and open Data Connection Wizard - I  see the System1400 and the 2 data sources i activated with the CREATEDSN tool from Sage

    Again in Access 2010, I see the same sources as in Excel when I need to link to ODBC data sources

  • 0 in reply to Vince Settipane

    On Windows 7 64 bit you would need to go to C:\windows\syswow64\odbcad32.exe for the odbc

  • 0 in reply to CShular
    verified answer

    Apparently Businessworks sometimes has trouble creating the DSN. The steps to fix it are:

    1. On the client computer open the Windows Registry and navigate to hklm\software\odbc\odbc.ini. Backup this part of the registry. Expand odbc.ini and you'll see entries for every DSN in Windows. Delete the keys for Businessworks. Close the registry.

    2. On the client computer use the CreateDSN utility in the Start Menu to create the ODBC connection to your Businessworks database.

    3. Configure UPS WorldShip to use keyedimport for an ODBC source. Select your BW database in the box. When prompted for a password enter MANAGER with the password in upper case. It should work.

*Community Hub is the new name for Sage City