Status 3103 and 3014 with UAC ON

[trims30]

Customer has PSQL9 Workgroup and has been running fine till the other day when they turned on UAC.
Now getting 3103 and 3014 errors.
Also they're running database engine as service.

Data is on share drive with no pervasive components.
Tried copying a data file to a workstation c: drive and opening it with Function Executor - Same Problem.

If we turn off UAC all is fine.

My guess is it's a security issue or something like that but have no idea as to where to start in troubleshooting.
Could be a firewall or something blocking communication with Database Service Manager (W3dbsmgr.exe).
Workstation we tested is Win10.

Any help is appreciated.
Lee

 

[mirtheil]

Is the service running as LocalSystem or as a specific user? If it's LocalSystem, try it as a specific user(that has appropriate rights to the share). If you stop the service and run the engine (W3DBSMGR.EXE) as a regular app with UAC on doe it fail?
Have you tried it on a non-Windows 10 machine?

As a note, PSQL v9 has been unsupported for quite a while (last update was Nov 2008) and PSQL v12 is the first to support Windows 10. The latest version is v13. It might be worth upgrading to at least PSQL v12 and retry to see if it's been fixed.



Mirtheil

http://www.mirtheil.com