How to Handle 2 SmartPost Errors: Login Failed for User ‘SmartPost’ & “Unhandled Exception has Occurred in a Component in Your Application”.

Login Failed for User ‘SmartPost’

The following error occurred when opening Dynamics GP after reinstalling SmartPost.

Error: Login failed for user ‘SmartPost’.

Unhandled Exception has Occurred in a Component in Your Application

While trying to process SmartPost records, the following error message appeared.

Error: Unhandled exception has occurred in a component in your application.

Both of these issues are related and can be fixed with a couple of steps.

Cause

The underlying issue is that the SmartPost user is unable to connect to or log in to SQL Server.

During the first time installation, the SmartPost user password is requested on screen, and the SmartPost SQL user is created with a password in SQL.

However, if SmartPost is reinstalled, it is most likely that the password entered during the SmartPost reinstallation does not match the password that was originally used when the SmartPost SQL user was created.

As a result, the credentials no longer align, causing the login failure.

If you check the Windows Event Viewer for SmartPost, you should see a related SQL login error.

Solution

1. Open the GP installation folder (On the machine where the SmartPost tool is installed, navigate to: C:\Program Files (x86)\Microsoft Dynamics\GP), then go to the Addins folder and open eOne.SmartPost.dll.config.
2. Locate the password recorded in that config file (the one used during installation). Installation Step
3. Open SQL Server Management Studio (SSMS) and locate the smartpost login under Security.
4. Reset the smartpost login’s password to match the value found in the config file.
5. While in SQL, confirm one of the following:
   • Option A: The SmartPost login is a sysadmin (this is the default)
     OR
   • Option B: the login is mapped to the DYNAMICS database, has access to the company databases, and belongs to the DYNGRP role.

If the config file is missing, it indicates that SmartPost is not installed on this machine.

Question: Why does this account need to be a member of the SYS ADMIN server role within SQL?

In GP2013 (and likely in newer versions as well), the smartpost user is set as a sysadmin by default to ensure it has full permissions across all existing and newly created GP company databases.
 
If you prefer to remove the sysadmin role, that’s fine — just make sure to do the following:

• In SSMS, under User Mapping, grant the user access to the DYNAMICS database and all GP company databases, setting dbo as the default schema.
• Assign DYNGRP permissions for each mapped database.

Finally, run the grant.sql script on the DYNAMICS database to ensure the SmartPost tables have the proper DYNGRP permissions (these are not granted by default).
For Example:

Doing these steps should resolve the error messages. Have a question? Please reach out to us at support@eonesolutions.com.