Views:

Question
I get the error "LDS Connection Error" in the web client, import or workflow, what can I do to solve the behavior?

Answer
This error indicates that the connection between the Local Data Connector and the cloud system is broken or interrupted.

This can have several causes.

  • The Windows service "DocuWare Local Data Connector" has lost the connection to the Cloud System
  • The Windows service "DocuWare Desktop Apps" has lost its connection to the Cloud System
  • The server running the Local Data Connector has lost the connection to the Internet
  • Your local database does not meet the requirements to work with the Local Data Connector
  • You need to update the Local Data Connector and your Desktop App
  • You have not installed the DocuWare Desktop Apps (these are required for a connection)

Basically, the Local Data Connector also needs the DocuWare Dekstop Apps because it communicates with the DocuWare Cloud based on the DocuWare Dekstop App Framework.

What are the first steps I can take to solve this behavior?

  • Restart the Windows service "DocuWare Desktop Apps
  • Restart the Windows service "DocuWare Local Data Connector
  • Enter the access data again in the Local Data Connector and confirm them
  • Check if the Local Data Connector HUB addresses are available and can be accessed from your network, the Local Data Connector HUB addresses can be found in this KB article here
  • Do the desktop apps have a connection to your cloud system?
  • Check if the database server is reachable and can receive requests. You can also create a new connection as a test

Question:
What are the requirements for my database to work with the Local Data Connector?

Answer:
MSSQL:

  • Microsoft SQL databases and your tables must be located in DBO schema
  • At least DATAREADER and DATAWRITER are required as rights.

ODBC:
The Local Data Connector expects a standard driver ODBC connection which works in the standard case, due to the different ODBC drivers and architectures,
we can only support the standard case, more information can be found in this KB article here

Oracle:
The TNS_NAME variable must be available system-wide and accessible via SQLPLUS / SQL DEVELOPER.

Question:
I get the following error message:

System.ServiceModel.EndpointNotFoundException: 
There was no endpoint listening at net.pipe://localhost/DwLocalDataConnector that could accept the message.
This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
 ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/DwLocalDataConnector' 
could not be found on your local machine. 

Answer
This error message means that the Local Data Connector has no connection to the Windows service of the Local Data Connector or the Desktop Apps.
Please restart the Local Data Connector service and the Desktop Apps service



Important notes:
Please note that DocuWare always requires the native driver for the respective databases.
Accessing a MSSQL or ORACLE database via ODBC is not as efficient as using the native driver.

Please send DocuWare the Local Data Connector Logs always!
These are usually located in the standard directory: %Programdata%\DocuWare\Logs
Please also send DocuWare the connection information and the settings file
These are usually located in the standard directory: %Programdata%\DocuWare\LocalDataConnector

In case of database error messages, check whether the local database instance is performing well and your network infrastructure is functional.
Interruptions in the connection to the DocuWare Cloud can also be caused by timeouts in the local database or if the server
cannot maintain the connection to the DocuWare Cloud due to a connection interruption
The Local Data Connector has a built-in repeating mechanism to resolve this behavior, but we cannot guarantee local restrictions.

The Local Data Connector can read or process a maximum of 1000 records in an external database.
This means that you cannot update local data sources with more than 1000 entries or transfer the records to the DocuWare Cloud.
This is a technical limitation.

Local Data Connector does not support fields that utilize the max prefix, for example varchar(max).
To use the fields, you must define a fixed number between 1 and 255 in the condition clause. We recommend the default value for example varchar(255)

Comments (1)
  • This KBA isn't correct, if you change the default schema of the user that is accessing the database directly within SQL you are able to access any database under that schema. If you need to connect to multiple schema's you need to run multiple accounts which each have the relevant default schema setup.
     

    Question:
    What are the requirements for my database to work with the Local Data Connector?

    Answer:
    MSSQL:

    • Microsoft SQL databases and your tables must be located in DBO schema