Archive for category: Articles

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.

 

Sometimes uninstalling Crystal Reports Application Server from the Programs utility leaves behind extra “stuff” that needs to be removed.  Else, you won’t be able to upgrade or reinstall CRAS.

To clean up CRAS after an uninstall, first make sure install files are deleted (usually under the Business Objects or SAP BusinessObjects folder).

Next, delete the following registry keys:

 

HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects

HKEY_CURRENT_USER\Software\SAP BusinessObjects

HKEY_USERS\S-#-#-##-…-####\Software\SAP BusinessObjects

The number signs (#) represent a series of numbers that are different on each computer.

 

Restart the computer

 

You should now be good to install a new version of CRAS.

 

Problem: When deleting an ActorRole we receive the following error: “Error deleting ActorRole record. Error – (Access Denied for Update on Actor for actor=<ActorName>)”

 

To resolve this issue, follow the steps below:

The root cause of this error is the ALLGenAccess_ST security class was removed from the SecurityAdministrator_ST role.

 

To resolve the issue perform the following steps:

1. Run the adminlaw command to place the Landmark environment in a restricted state.
2. Run the following command to turn security off for the Landmark environments GEN productline: secadm security activate gen ALL_ACCESS
3. Log into the rich client as an administrator, open the RoleSecurityClass business class and assign the ALLGenAccess_ST security class to the SecurityAdministrator_ST role and save the change.
4. Run the following command to turn security on for the Landmark environments GEN productline: secadm security activate gen PROCESS_RULES
5. Run the startlaw command to take the Landmark environment out of a restricted state.
6. Test the S3 LSF Security Administrator.

 

NOTE: You may also see the following error attempting to update a user’s Identity record.

“Landmark error adding Identity – (Access Denied for CreateNewIdentityForActor on Actor for actor=<ActorName>)”