DriveWorks Pro Server is a service that helps connect DriveWorks modules such as DriveWorks Administrator and DriveWorks Live to a shared group.
A shared group is a database in SQL Server or SQL Server Express.
There is also a Pro Server Configuration Tool that is an application used for configuring Pro Server.
Pro Server supports both SQL Server Authentication modes
This article discusses issues relating to DriveWorks Pro Server connections
In some instances you may not be able to connect to the Pro Server. Reasons for this could be:
Adjust Firewall settings on the machine that hosts the DriveWorks Pro Server.
To establish if the firewall is preventing access we recommend disabling the firewall on the Pro Server machine temporarily and try re-connecting from the DriveWorks application that is trying to access the Pro Server. If this is then successful re-enable the firewall and check the following settings:
- Set an inbound rule to allow port 8025 on UDP
- This port is used to allow any DriveWorks application on the network to discover this instance of the Pro Server.
- Set an inbound rule to allow port 8000 on TCP
- This port is used for the actual data connection to the Pro Server.
Check the machine name of the Pro Server was entered correctly.
This is only relevant if the discovery port is not open and the machine name is being manually entered.
A possible cause for Pro Server stopping is the Pro Server Service User not having the correct permissions in SQL Server.
If you are using SQL Authentication, make sure the SQL User you have registered in the DriveWorks Pro Server Configuration Tool has the correct permissions to the Group (Database in SQL Server)
If you are using Windows Authentication, make sure the Pro Server Service User has the correct permissions to the Group (Database in SQL Server):
When testing the connection in the DriveWorks Pro Server Configuration Tool when using Windows Authentication, the test is performed against the logged in user on the machine and NOT the user that the Pro Server Service is running as.
If the problem persists, this may be an indication of a bigger issue, in which case look for an exception report in the Pro Server Exception reports folder located here: C:\Windows\System32\config\systemprofile\AppData\Local\DriveWorks\Health\Pending
The SQL Authentication User or Windows Authentication User set up in DriveWorks requires the following permissions in SQL Server
|Knowledge Base Article Ref:||KB13103030|