We have a problem with some bespoke software that I cannot get to the bottom of.
Said software is for a production environment. When a user loads up a sales order to print and initiates the print process they get the error message: "Cannot open SQL server".
When I try logged in as Administrator it works.
Speaking with the author of the software, he suggests that it's because non-administrator users don't have permission to access ODBC (although they can read/write to the SQL database - so I'm not so sure about that).
The users are all members of a domain on Server 2008.
Any ideas what I should be checking to give all users access to ODBC? Could it be anything to do with ports?
Due to a situation the author won't come into the factory to assist and the IT support person is on holiday. I've been drafted in to assist.
I have had to do this before as well. This is what I did. I installed a msi creator software (can't remember name, sorry) and then installed the user end software as an administrator. Then I looked at the logs created by the msi creator software that just watched my entire computer, making note of every new file added or registry added, and compliling a list of files and registry keys that were changed or added. Then I manually set the permissions on those keys and files (a lot of them were in c:\windows\system32\) to the user persmissions. As a software support tech, most companies will say its not supported, but as an admin, we have to find work arounds.
Might be totally wrong here, but is said software digitally signed? I know the registry is out-of-bounds for non-signed software unless authorised - might not allow access to ODBC either? Just a thought.