Client - Server Connectivity

• Ensure the service is running under the correct user account. If SQL is sitting on a different server to the server running the SDM service, ensure the service user is a domain user
• In Client Administration on the client machine, check the server name or the server IP address is pointing to the server that's running the SDM service
• Ascertain if the SDMServiceUser (or the user account running the service) is setup in SQL under Security > Login. This user should have the correct schemas (db.owner preferred) and should be mapped to the Draycir.SDM database. This is only applicable if in Server Admin > Database Details > Windows Authentication is being used. If SQL credentials are being used, ensure that the account specified has the correct permissions
• In Server Administration > Service Address, make sure the address is set to localhost and not the IP address of the server
• In Server Administration > Database Details, check that the test connection is successful
• Check version of SDM is compatible with version of Sage 200 including any service packs applied
• If the archived documents or the SQL database sits on a different server, the SDMserviceuser must be a domain user
• In Server Administration > Service Address, it should be set to localhost to avoid SDM thinking an outside connection is trying to connect to the service
• Open the User Profiles window to ensure the service is running
• Check if firewall is being used and if so, check the inbound and outbound rules on the server are specified for port 34251-34258. For reporting function to work, this range must be specified
• Check client and server versions correlate i.e. the same/very similar
• Check machines are on the same domain
• Ping the server name/IP address and check for a response