Sage 100

Has anyone else had any issues with a missing SOTAMAS90 User DSN? I have a client who has seen this from 4.40 up to 2013 that we just upgraded to. He has run the workstation install, and you can see the driver on the Driver's tab, but just not a User DSN. I forwarded him a Microsoft article I found on some registry entries to check, but he still feels this is a Sage issue. These are Windows 7 32-bit machines too (with UAC disabled), so there's not any confusion as to where to look for the DSN.

I have seen something like this with two other customers, but the crystal reports still worked... I never found a solution.

Same as @ClarkWalliser - missing but Crystal still worked.

So does an Excel query work? I always try to install the DSN's as a system, not user.....

Jeff, we do not see the User DSN that gets automatically created with the workstation install. I don't want to have the client create manual User or System DSN's for 60+ machines, as they shouldn't have to.

Is the user logged in to run the wksetup.exe a local admin? Make sure to disable antivirus during the workstation setup install. The only other thing I can think of would be there could be a restrictive group policy in place - ask IT folks what policies they have configured. Usually logging in to PC as a Domain Admin allows all installs.

We have tried this under various domain admin accounts. It's got to be environmental, but can't find anything very helpful on the web. I did notice yesterday that none of the standard Office DSNs are showing up either (Excel, Access) and let them know that.

Double check 64 bit - sure sounds like it's a 64-bit PC running 32-bit Office. If you have a c:\program files (x86) folder it's a 64-bit PC.

Hey Amber, has to be a policy or some other restriction on the workstation. There must be a way to get the IT Admin to realize it is their issue, not Sage's. Do they have any workstations that work correctly? Do they have any 64-bit workstations? You could create a silent DSN just to test, see if that gets fully created and is functional. How about on the server? In 2013 you can use the 64-bit ODBC Driver if they have a 64-bit server, which might be an interesting test.

Thanks for the suggestions Cullen. Something came to mind, but until I hear back from the client, I don't want to get my hopes up. But I don't believe this client maps any network drives to my Sage sharepoint and then runs the wksetup from there. I think he just navigates through Explorer via UNC path. I asked him if he does do that, and if so, could he try using a network drive instead. I will update here as soon as I hear back.

Running the wksetup.exe via a mapped drive vs. a UNC path did not make any difference. Just wanted to give everyone a heads-up. I'll google ""group policy"" to see if I find anything useful.

Any further info on this? @AmberPrayfrock, I see your last post was 3yr ago, but do you recall?

Sorry, no. We never got anywhere without having to manually create the DSN.