Archive for category: Frontpage Article

You may have come across this message on Lawson MHC – An error occurred while printing. This problem happens when printing Lawson forms or checks from MHC Image Express, and users may receive the error on their screens while printing.

In MHC, users often print 1099 forms, checks, etc. and may need to re-print a form.

When re-printing they sometimes run into this error and are unable to resolve on their own:

1. First, you’ll need an MHC or Lawson trained individual who understands the application.
2. Locate the output files via the print routines in the same account the user previously printed from.
3. Below is an example of where our print routines point to. Delete or move these files to a backup directory to resolve this error:

MHC Image Express integrates with Lawson and it’s a lot to ask of an individual Lawson employee to maintain when they may be tied up with other daily issues.

To combat this, organizations often bring on Lawson consultants who offer managed service and typically have expertise in maintaining and updating MHC related products (especially around year-end).

 

Good luck!

Problem: User is trying to login to Lawson add-ins and receives a Script Error, blocking them from entering their credentials.

1. Update the users add-ins version MOA32bit or MOA64bit installer depending on version of Excel. See compatibility matrix for add-ins on Infors Concierge website.
2. Make sure the user is on the latest internet explorer version: https://www.microsoft.com/en-us/download/internet-explorer.aspx (Microsoft is planning on leaving support for IE on 6/15/2022 so it is recommended to update the users operating system).

Temporary workaround: Copy the users username and click Yes on the dialog error and quickly paste in the username. Do the same thing for the password.

NOTE: As of posting this article, this info may still be relevant but likely will be resolved through updating the users PC to the latest Windows OS as well as a later version of add-ins and Microsoft Excel.

 

Here is a simple solution for common LBI Install Errors.

 

Problem:

During an LBI install you get this error regarding a trigger name not the same collation as refencing column.

 

Resolution:

Run this query

IF NOT EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'[dbo].[EJS_SIMPROP_TRIGGERS]’) and

                OBJECTPROPERTY(id, N’IsUserTable’) = 1)

                CREATE TABLE [dbo].[EJS_SIMPROP_TRIGGERS]

                                ( [SCHED_NAME] NVARCHAR(120) NOT NULL,

                                [TRIGGER_NAME] NVARCHAR(130) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

                                [TRIGGER_GROUP] NVARCHAR(160) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

                                [STR_PROP_1] NVARCHAR(512) NULL,

                                [STR_PROP_2] NVARCHAR(512) NULL,

                                [STR_PROP_3] NVARCHAR(512) NULL,

                                [INT_PROP_1] INT NULL,

                                [INT_PROP_2] INT NULL,

                                [LONG_PROP_1] BIGINT NULL,

                                [LONG_PROP_2] BIGINT NULL,

                                [DEC_PROP_1] NUMERIC(13,4) NULL,

                                [DEC_PROP_2] NUMERIC(13,4) NULL,

                                [BOOL_PROP_1] NVARCHAR(2) NULL,

                                [BOOL_PROP_2] NVARCHAR(2) NULL,

                                CONSTRAINT PK_EJS_SIMPROP_TRIG PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP),

                                CONSTRAINT FK_EJS_SIMPROP_TRIG FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP)

                                REFERENCES EJS_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP));

 

 

Start your install over and the same error should not repeat.