Summary
Description
Cause
Resolution
CAUTION: This solution requires advanced knowledge of Windows security and network settings. Sage isn't responsible for any issues that arise from changes to these settings. Ensure you back up all system and application databases necessary for a complete restoration. It's advisable to contact a certified consultant or your system administrator for assistance.
CAUTION: Sage support can't assist with third-party products, hardware, report customizations, or state and federal tax questions. Refer to our Scope of Support for more info. Contact your Sage business partner, network administrator, or accountant for assistance.
If necessary, review Microsoft SQL Server documentation.
Sage MyAssistant uses a Microsoft SQL Server database called Notification to store Task and Notification information. This database is installed on a server and can be accessed by any number of workstations.
Possible causes of SQL connectivity issues
- The Microsoft SQL Server Service is not running on the server. (see Error: "MyAssistant failed to connect to the database" below)
- Windows User Account Control(UAC) is enabled. (see Disable Windows User Account Control below)
- A Firewall or Anti-Virus program is blocking access to the SQL Server database.
Note: The default TCP/IP port that Sage MyAssistant communicates with the SQL Server is TCP/IP port 45812. - The current Windows user does not have administrative privileges.
- An incorrect Server Name is entered.
Note: The Server Name is the name of the computer where the MyAssistant resides. - An incorrect SQL Server User name or Password is entered.
Note: Sage MyAssistant will attempt to create a username MyAssistant and an algorithmic password generated by the system that is also used on the workstation. If you change/create the SQL user during the server configuration then this is the username and password that must be used during the workstation configuration. - An incorrect Instance name is entered.
Note: The default instance name that is installed with Sage MyAssistant is ISD. - The TCP/IP port entered is not the same port that SQL Server instance is listening for.
Note: The default TCP/IP port that Sage MyAssistant communicates with the SQL Server is TCP/IP port 45812. - The SQL Server instance is not in mixed mode.
- The TCP/IP protocol is not enabled or is not using a fixed port.
- The Shared Memory protocol is not enabled for the SQL Server instance.
Tools to use
- Can you connect to the instance using SQL Server Management Studio?
Note: You can download this 3rd party product from the Microsoft Download Center. - Can you connect to the SQL Server instance from a command line?
DocLink: Installing MyAssistant with full version of SQL Server.
DocLink: Error: "An error occurred installing Microsoft SQL Server Express Result code: -[number]"
DocLink: MyAssistant has encountered a problem and needs to close. (SM DSN)
DocLink: Error: "MyAssistant failed to generate an SM DSN." (SM DSN not on server)
DocLink: Disable Windows User Account Control.
DocLink: Error: "Login failed for user 'MyAssistant'."
Related Solutions
Installing MyAssistant with full version of SQL Server.
Error: "An error occurred installing Microsoft SQL Server Express Result code: -[number]"
MyAssistant has encountered a problem and needs to close. (SM DSN)
Error: "MyAssistant failed to generate an SM DSN." (SM DSN not on server)
Disable Windows User Account Control.
Error: "Login failed for user 'MyAssistant'."