In Version 15 HF2 of SoftPro Classic, Pro1099 on some systems likes to start up needing local machine Administrator access. Not all machines, but some of them. I have clients who for good reasons don't want users to have Administrator access. That usually happens as more hands touch more desktops.

 

Talking with SoftPro about the options, didn’t find anything workable, turn off UAC, run as Administrator in various ways, or reinstalling were the suggestions. None of them seemed appropriate for the situation at hand. A reinstall might be worth it if the installer missed something along the way. Otherwise the users aren’t allowed Administrator access.

I was surprised that setting Pro1099 (p1win.exe) to run in compatibility mode for XP Service Pack 3 fixed it. It must not work all the time otherwise it would be the first thing suggested.

To do that, I recommend locating the p1win.exe file, normally under C:\Program Files (x86)\SoftPro\ sometimes in that folder, other times under that folder in Enterprise or Standard\Client folder.  Right click on the p1win.exe file and select Properties.

 

Click on the Compatibility tab, then select “Run this program in compatibility mode for Windows XP (Service Pack 3).

Click OK to save it and try Pro1099 by double clicking on p1win.exe

 

I didn’t think it would be that simple, so I went looking for things Pro1099 was trying to do which Windows wouldn’t allow. Some registry keys were being denied access if Pro1099 were not started in Administrator mode.  So if the above doesn’t fix the problem the next step is to give Users full permissions to these registry keys using regedit.exe.

HKLM\Software\Wow6432Node\ODBC\ODBC.INI
HKLM\System\CurrentControlSet\Services\WinSock2\Parameters
HKLM\Software\Wow6432Node\Description\Microsoft\Rpc
HKLM\Software\Wow6432Node\Microsoft\MSSQLServer\Client

where HKLM = HKey_Local_Machine

Do that by opening the Registry Editor and navigating to each of the keys, right clicking and selecting Permissions.

Select Users, Select Full Control and Click Apply or OK.

Close the window if necessary, navigate to the next key and update the permissions.

The actual calls from p1win.exe to the registry which failed that I captured are:

Let me know what fixed it for you.