The problem is the Microsoft SQL Server ODBC driver (shipped with Windows), which seems to go on strike after Office updates. All databases suddenly showed the value 'DELETED' in the tables. We have heard of situations where a server is restarted after Windows updates and suddenly the network type switches from the Domain Profile (less restrictive) to Private Profile (more restrictive) and the different Firewall rules prevent the PaperCut client from connecting. I received a user message that Microsoft Access suddenly had problems with SQL database access. If you’re running Windows, double check the Windows Advanced Firewall rules to make sure that the network profile (Domain/Work, Private, Public) of the network interface matches how the rule is configured. If you’re using a Firewall in between clients and the Application Server, take a look through the Firewall Ports page to see what ports need to be opened for PaperCut to work.Īs a test, open a browser Window on the client and try navigating to and If this doesn’t work, try opening these ports on the firewall or disabling the firewall on the server altogether as a test. Ideally you’ll have a static IP address set up for your Application Server, so that the connection details remain the same. macOS - /client/mac/PCClient.app/Contents/Resources/config.properties.Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section. This has proven to be much more reliable and consistent between the small and large RDBMSs. When I have to interface between sql server and Access - I use ADODB. General protection fault in the client layer used by Native Access. Microsoft came up with ADODB as a workaround for this problem. but I cannot see an sql user name or password there.In the SQL Server Configuration Manager I enabled all protocolls for the Server and the Native Client (except VIA) I did a Login with 'testuser. Windows - \client\win\config.properties If the first connection is established in a single thread, the SQL Server Native Client 11 driver (that is, the earlier ODBC driver version) wont be used to make the first connection attempt. The details of this error are contained in the error message. The Server is configured in mixed mode, SQL Server Authentication is activated.
The central config.properties file can be found in one of these locations on the primary Application Server, where is the install path of the Application Server component. Note: PCClient.app can be opened like a folder by right-clicking it and choosing to Show Package Contents macOS - /Applications/PCClient.app/Contents/Resources/config.properties.Windows - C:\Program Files (x86)\ PaperCut MF (or NG) Client\config.properties.
The local copy of the config.properties file can be found in one of the following locations on a workstation, assuming a default install path.