Dynamics GP Workflow Emails not sending anymore

So your workflow emails used to send but suddenly it stopped.

Reason - Windows password saved on the worflow maintenance window is invalid. Now the system will not tell you this.

All you need to do is go to Admin - Setup  - System - Worflow and update the password of the account saved there. Send your test mail and you shall receive it now.

Voila!

Capture Login Issues

Ok so you run the capture login script and then get the below message.

supplied parameter sid is in use

you then try to remove the sid from the syslogins table but you get some message related to 'adhoc' something is not allowed.

then you try to create the record manually and get 'the server principal already exists'


How to fix run the below and replace name with the name of the record you have the issue with. You should be fine now.

EXEC sp_droplogin 'namehere'

SmartList Builder Security

All SmartList Builder windows are denied access by default. To use SmartList Builder, the user must be in a POWERUSER role, or be granted access to the following windows in a Microsoft Dynamics GP Security Task:

First go to Security Tasks and select the following as seen in screen below.

Product: Smartlist Builder

Type: Windows

Series: Project

               Go To

               Set Field Options (3 windows)

               SmartList Builder

Second change series to System and select the below as per screen:

·        Background

·        Copy List

·        Display SQL

·        Preview

·        Process Queue

·        Resource Lookup

·        Smartlist Builder Progress

·        Smartlist Lookup

·        Table Details

·        Table Finder(2 items)

·        Upgrade Modified SmartLists

Third - Beyond the Window permissions, there are SmartList Builder Permissions that need to be granted as well.  These SmartList Builder Permissions can be granted in the Microsoft Dynamics GP Security Task as well.

 In same security task change Product to SmartList Builder, Type to SmartList Builder Permissions and Series to SmartList Builder.

·        Create a Go To that opens a Dynamics GP Form

·        Create a Go To that opens a file

·        Create a Go To that opens a website

·        Create a Go To that opens another SmartList

·        Create a Go To that runs a procedure

·        Create SmartLists with SQL Tables

·        Enter Calculated Fields

·        Update SmartList

·        View SmartLists with SQL Tables

Integration manager - Invalid string

Error: The destination could not be initialized due to the following problem input string 


This happens when you run IM as admin and GP as admin BUT - your GP company as a default company marked so when you sign in you have to switch the company you signed in to.

To resolve, remove the 'remember this company' mark from your account just by unclicking it on the sign in window.

Then run GP as admin and select the correct company before getting in and then run IM as admin as well.

Voila!!

It worked for me. Hope it works for you!

Management Reporter Database in Suspect Mode

So you check SQL and notice your backups stop running.

Only to notice it is because your MR database is in suspect mode. To resolve the issue i would first suggest, removing MR from the database backup plan and complete your GP backups.

Then run the below script to resolve the MR suspect mode issue. Then create your separate plan for MR backups.

Script:

EXEC sp_resetstatus ManagementReporter;

ALTER DATABASE ManagementReporter SET EMERGENCY

DBCC checkdb(ManagementReporter)

ALTER DATABASE ManagementReporter SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB (ManagementReporter, REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE ManagementReporter SET MULTI_USER

Dynamics GP Letter Writing Assistant; where are the reports pointing to?

You can identify where the system is looking to for the Letters by going to the Dex ini file in the Data folder of Dynamics GP on the C drive.

The user could not be added to one or more databases. Dynamics GP

This error usually goes away by deleting the user login from the security area for the specified database in SQL. Then re-add the user to the User Security in GP.

If that doesnt resolve the issue, the below will help:
In SQL Server Security=>Logins=>User Mapping, to uncheck the Map checkbox on the restored company.  After doing that the User Access function in GP will allow you to add the users to the company.